- Community Home
- >
- Networking
- >
- Legacy
- >
- Switching and Routing
- >
- 5300 routing
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
Forums
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
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-04-2012 08:00 AM
04-04-2012 08:00 AM
5300 routing
Two procurve 5308 connected together on port c1. Switch A and Switch B are connected together on port c1. Switch A and Switch B are procurve 5308s. Also,these 5308 also have layer 2 switch connected to them on port c1.When i do a show ip route i see that vlan 1 is the vlan that the switches are learning there routes from. Do i need RIP enabled on every VLAN or can i just leave RIP enabled on VLAN 100 and have that VLAN be the vlan where the switch learns its routes from
SWITCH A
vlan 1
name "DEFAULT_VLAN"
untagged B16,E1-E4,F1-F4,G1-G4,H1-H4
ip address 172.16.16.1 255.255.255.0
no untagged A1-A16,B1-B15,C1
ip igmp
exit
vlan 10
name "SERVERS"
untagged A1-A16,B1-B5,B7,B10-B14
ip address 172.31.30.254 255.255.255.0
tagged B6,G1,H3,C1
ip igmp
exit
vlan 12
name "comps"
ip address 172.31.31.254 255.255.255.0
ip helper-address 172.31.30.1
tagged B6,G1-G2,C1
ip igmp
exit
vlan 100
name "Building Connect"
untagged B8-B9,B15
ip address 192.168.1.1 255.255.255.0
tagged B6,F1,C1
ip igmp
spanning-tree
spanning-tree priority 0
router rip
exit
vlan 1
ip rip
exit
vlan 10
ip rip
exit
vlan 12
ip rip
exit
vlan 100
ip rip
exit
SWITCH B
vlan 1
name "DEFAULT_VLAN"
untagged B16,E1-E4,F1-F4,G1-G4,H1-H4
ip address 172.16.16.254 255.255.255.0
no untagged A1-A16,B1-B15,C1
ip igmp
exit
vlan 9
name "SERVERS"
untagged A1-A16,B1-B5,B7,B10-B14
ip address 192.168.35.254 255.255.255.0
tagged B15,C1
ip igmp
exit
vlan 12
name "comps"
tagged B15 ,C1
untagged A1-A5
ip igmp
vlan 11
name "comps"
ip address 192.168.30.254 255.255.255.0
ip helper-address 192.168.35.1
tagged B6,F1,G1-G2
ip igmp
exit
vlan 100
name "Building Connect"
untagged B8-B9,B15
ip address 192.168.1.254 255.255.255.0
tagged B6,C1
ip igmp
exit
vlan 1
ip rip
exit
vlan 9
ip rip
exit
vlan 11
ip rip
exit
vlan 100
ip rip
exit
- Tags:
- VLAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2012 04:07 PM
04-21-2012 04:07 PM
Re: 5300 routing
If I understood you correctly...
You can do the RIP-stuff in only one of your VLANs, then the switches exchange routes through that VLAN.
Drawback might be (depending on your topology) that routing of the traffic will probably also take place over that VLAN, possibly causing more L3 hops than neccessary.
Thinking of it: I even suspect you are doing something unsupported if you want to have the switches form a RIP-partnership in every VLAN. After all, the goal of RIP is to exchange routes, and the routing-table is valid for the whole switch, not for just one VLAN.