- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- LAN 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
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
03-13-2013 12:41 PM
03-13-2013 12:41 PM
5300 routing
Please forgive im new to networking. We recently leased metro Ethernet. We have two locations (Site A, Site B) with 5300 series switches Routing is enabled at site A and site B. we have a server VLAN and PC VLAN at both sites. The uplink ports to the metro E are tagged for both VLANs. We have servers at both locations. Lately we’ve been having latency issues on the server VLAN. Should I create a new VLAN that has the unlinks port untagged to the metro E network and create static routes to each location
Site A:
vlan 12
name "PC"
untagged A8-A16,A19-A23
ip address 192.168.2.254 255.255.255.0
ip helper-address 192.168.99.5
tagged B15-B16,C1,C4,D4
ip igmp
exit
vlan 13
name "Servers"
untagged B3-B6,B8-B11,B13
ip address 192.168.99.254 255.255.255.0
tagged B15,D4
ip igmp
exit
Site B:
vlan 13
name "Servers"
untagged B5,B13-B14
tagged B16
ip igmp
exit
vlan 12
name "PC"
no ip address
tagged B12,B15-B16
ip igmp
exit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2013 08:42 PM
03-17-2013 08:42 PM
Re: 5300 routing
Generally, if you have a new site, I find it best to design the subnets for that site as independent ones - then it can function independently of Site A if required.
As you say both routers have routing enabled, it seems even more obvious that SIte B's local hosts have their default gateway locally, with routing to get them off-site.
However, often a link between sites used by *servers* requires layer2 connectivity for the server subnet (VMotion, etc...).
In any case, "latency issues on the server VLAN"?
- Sounds like a Server Team trying to pass off their problems as being a "network problem".
--> Work with them to pinpoint the exact location of the issue: what you will be trying to do is prove exactly which server/switch interfaces are on the path of the "latency issues" and demonstrate that each relevant switchport is always running with lots and lots of spare capacity.