- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- ProCurve 2626
Switches, Hubs, and Modems
1745847
Members
4205
Online
108723
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2007 04:50 AM
тАО05-16-2007 04:50 AM
ProCurve 2626
I have added a second VLAN to my 2626. The configuration is as follows:
hostname "ProCurve Switch 2626"e
snmp-server contact "Robert Peirce"X | Yes Auto Disable
time timezone 1
mirror-port 24
8 1
ip default-gateway 204.68.155.248Disable
ip routing
no timesync10/100TX |
vlan 1
name "DEFAULT_VLAN"
untagged 4-26
ip address 204.68.155.44 255.255.255.0
tagged 1
no untagged 2-3
exit
vlan 2
name "Sys_Admin"
untagged 1-3
ip address 172.168.70.1 255.255.255.0
exit
interface 25
monitor
exit
ip authorized-managers 204.68.155.135 255.255.255.0
ip authorized-managers 204.68.155.102 255.255.255.0
ip authorized-managers 204.68.155.121 255.255.255.0
ip authorized-managers 204.68.155.109 255.255.255.0
primary-vlan 2
password manager
password operator
When I connect to PCs to VLAN 2 (Sys_admin) and assign them 172.168.70.2 and .3 they can ping each other, but can no longer ping any machine on the 204.68.155.0 segment. The port connected to the 204.68.155.0 segment is port 1.
Any help with this will be greatly appreciated.
hostname "ProCurve Switch 2626"e
snmp-server contact "Robert Peirce"X | Yes Auto Disable
time timezone 1
mirror-port 24
8 1
ip default-gateway 204.68.155.248Disable
ip routing
no timesync10/100TX |
vlan 1
name "DEFAULT_VLAN"
untagged 4-26
ip address 204.68.155.44 255.255.255.0
tagged 1
no untagged 2-3
exit
vlan 2
name "Sys_Admin"
untagged 1-3
ip address 172.168.70.1 255.255.255.0
exit
interface 25
monitor
exit
ip authorized-managers 204.68.155.135 255.255.255.0
ip authorized-managers 204.68.155.102 255.255.255.0
ip authorized-managers 204.68.155.121 255.255.255.0
ip authorized-managers 204.68.155.109 255.255.255.0
primary-vlan 2
password manager
password operator
When I connect to PCs to VLAN 2 (Sys_admin) and assign them 172.168.70.2 and .3 they can ping each other, but can no longer ping any machine on the 204.68.155.0 segment. The port connected to the 204.68.155.0 segment is port 1.
Any help with this will be greatly appreciated.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2007 09:19 AM
тАО05-16-2007 09:19 AM
Re: ProCurve 2626
The clients in VLAN1, is their default gateway set to 204.68.155.44?
If not, you will need to make this change, and then add a default route to your external router,
e.g.
ip route 0.0.0.0/0 204.68.155.1
On the external router you will also need to add routes pointing back to the 172.168.70.0/24 network.
If not, you will need to make this change, and then add a default route to your external router,
e.g.
ip route 0.0.0.0/0 204.68.155.1
On the external router you will also need to add routes pointing back to the 172.168.70.0/24 network.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2007 03:38 AM
тАО05-18-2007 03:38 AM
Re: ProCurve 2626
The default gateway of the 172 vlan connection is 172.168.70.1, which is also the VLAN IP. I fixed the problem of not being able to connect to 204.68.155.x by doing two things. First, I followed your advice and added a static route to our Cisco router and then had to configure port 1 on the ProCurve 2626 as a Trunk.
Thanks for your help.
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2007 03:41 AM
тАО05-18-2007 03:41 AM
Re: ProCurve 2626
The default gateway for VLAN_ID 1 is 204.68.155.248, which is a Cisco router.
The default gateway of the 172 vlan connection is 172.168.70.1, which is also the VLAN IP. I fixed the problem of not being able to connect to 204.68.155.x from VLAN_ID 2 (172.168.70.x) by doing two things. First, I followed your advice and added a static route to our Cisco router and then had to configure port 1 on the ProCurve 2626 as a Trunk.
Thanks for your help.
The default gateway of the 172 vlan connection is 172.168.70.1, which is also the VLAN IP. I fixed the problem of not being able to connect to 204.68.155.x from VLAN_ID 2 (172.168.70.x) by doing two things. First, I followed your advice and added a static route to our Cisco router and then had to configure port 1 on the ProCurve 2626 as a Trunk.
Thanks for your help.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP