- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- LAN Routing
- >
- Re: routing issue?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
04-20-2012 01:51 PM
04-20-2012 01:51 PM
I have several Procurve switches (5412zl, 4204vl, and a few 2810-48G's). Currently we have a number of vlans (1-7). 1 is the business network which is addressed as 192.168.1.x/24. We have recently added vlan id 7 (PROCESS) addressed as 192.168.30.x/24. The 30.x network contains online power monitoring devices located in several electrical substations. These device report back to a HP ProLiant DL380 and record data to a SQL database. This server has 2 NIC's. Our users on the 1.x network need to be able to run reports from the server. My initial thoughts were to address each of the NIC's for the two networks and in theory users should be able to see the server. However it appears that between these two switches I have no connectivity on the PROCESS vlan, yet I have connectivity on the other vlans. I've included the configs for the two switches in question.
hostname "ProCurve Switch 5412z
module 1 type J9307A
module 2 type J9308A
module 3 type J9307A
module 4 type J9307A
module 5 type J9307A
interface B23
speed-duplex 1000-full
exit
interface B24
speed-duplex 1000-full
exit
interface E3
flow-control
exit
trunk B23-B24 Trk1 Trunk
trunk D19-D21 Trk10 Trunk
trunk D22-D24 Trk11 Trunk
ip default-gateway 192.168.1.1
vlan 1
name "BUSINESS"
untagged A3-A24,B1-B22,C1-C21,C23,D1-D16,D18,E1-E24,Trk10-Trk11
ip address 192.168.1.18 255.255.255.0
tagged Trk1
no untagged A1-A2,C22,C24,D17
exit
vlan 2
name "CAMP"
untagged A1
tagged Trk1
no ip address
exit
vlan 3
name "VOIP"
untagged A2
tagged Trk1
no ip address
exit
vlan 5
name "MGMT"
tagged D13-D14,Trk10-Trk11
no ip address
exit
vlan 6
name "ISCSI"
untagged D17
no ip address
exit
vlan 7
name "PROCESS"
untagged C22,C24
tagged Trk1
no ip address
exit
snmp-server community "public" unrestricted
snmp-server host 64.15.135.153 "public"
snmp-server host 192.168.1.177 "public"
snmp-server contact "Information Technologies" location "IT Room - ADMIN"
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk10 priority 4
spanning-tree Trk11 priority 4
no autorun
password manager
ProCurve Switch 5412zl#
; J8770A Configuration Editor; Created on release #L.11.20
hostname "ProCurve Switch 4204vl"
snmp-server contact "IT Department"
snmp-server location "Old Sub Station"
module 1 type J8768A
module 2 type J9033A
module 3 type J8776A
interface B21
speed-duplex 1000-full
exit
interface B22
speed-duplex 1000-full
exit
interface B23
speed-duplex 1000-full
exit
interface B24
speed-duplex 1000-full
exit
trunk B21-B22 Trk2 Trunk
trunk B23-B24 Trk3 Trunk
ip default-gateway 192.168.1.1
snmp-server community "public" Unrestricted
snmp-server host 64.15.135.153 "public"
snmp-server host 192.168.1.177 "public"
vlan 1
name "BUSINESS"
untagged A13-A24,B1-B20,C1-C4
ip address 192.168.1.10 255.255.255.0
qos priority 1
tagged Trk2-Trk3
no untagged A1-A12
exit
vlan 2
name "CAMP"
no ip address
qos priority 6
tagged Trk2-Trk3
exit
vlan 3
name "VOIP"
tagged Trk2-Trk3
exit
vlan 7
name "PROCESS"
untagged A1-A12
ip address 192.168.30.4 255.255.255.0
tagged Trk2-Trk3
exit
fault-finder bad-driver sensitivity low
fault-finder bad-transceiver sensitivity low
fault-finder bad-cable sensitivity low
fault-finder too-long-cable sensitivity low
fault-finder over-bandwidth sensitivity low
fault-finder broadcast-storm sensitivity low
fault-finder loss-of-link sensitivity low
fault-finder duplex-mismatch-HDx sensitivity low
fault-finder duplex-mismatch-FDx sensitivity low
spanning-tree Trk2 priority 4
spanning-tree Trk3 priority 4
password manager
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2012 04:47 PM
04-20-2012 04:47 PM
Re: routing issue?
Without seeing the output of "show lldp info remote-device", my guess is that you have a VLAN tagging issue. My simplistic answer to this is: turn on GVRP. It is a protocol which tags the VLANs on your switch-to-switch links without manual configuration. However, you may need to add an untagged management VLAN to those links to allow it to work (i'd have to refresh my memory on the GVRP requirements to be sure).
If you want to debug this further, paste the output of the above LLDP show command, along with the output of "show vlan", "show vlan 1", and "show vlan 7" (from both switches).
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2012 05:59 AM
04-21-2012 05:59 AM
Re: routing issue?
I really appreciate the help.
My post cannot exceed 20000 charcters so I put the output into a text file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2012 02:50 PM
04-21-2012 02:50 PM
Re: routing issue?
Your trunk tagging looks fine: both VLAN 1 and VLAN 7 are tagged on both ends of the link.
Note that you don't have any active ports on VLAN 7 on the 5400 - all ports other than the trunk are showing as down. If you want to test it, put a test machine on a port in that is untagged on that VLAN and try to ping something else on the 4200. If my reading of your status and config is right, it should work.
How did you test connectivity previously?
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2012 05:58 AM
04-22-2012 05:58 AM
SolutionI figured that the switch was configured correctly. I have other vlans running on various network segments at this site all configured the same way - and they work fine. After you confirmed that the trunk tagging is correct, I began to physically examine the cabling.
Bingo! The cabling was patched to ports E22 and E24 on the 5412. The vlan was established on ports C22 and C24. Moved the patch cables and voila!
Now if I can only find someone to blame for this.....ah crap. It sucks having only 1 person the IT department!
Thank you for the help!