- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- A5500 Vlan Interface Latency Spikes
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
03-05-2012 02:37 PM
03-05-2012 02:37 PM
Hello -
I was wondering if anyone had any input on this. I am currently testing a pair of A5500G EI (JD377A) switches. I currently have 2 Vlan's configured on them. If I ping the vlan interface ip I see random spike's from 2ms all the way up to 80ms. I currently only have 2 machines plugged into the switches for testing with intervlan routing. Everything else seems to be working correctly but I was wondering if anyone has seen this issue and what the fix was for it. Any insight is appreciated.
Switch 1
Vlan 5
protocol-vlan ipv4
ip-subnet-vlan ip 10.5.1.0 255.255.255.0
Vlan 10
protocol-vlan ipv4
ip-subnet-vlan ip 10.10.1.0 255.255.255.0
Int Vlan 5
Ip address 10.5.1.254 255.255.255.0
Int vlan 10
ip address 10.10.1.254 255.255.255.0
int g1/0/1
port link-mode bridge
port access vlan 10
int g1/0/24
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 5 10
Switch 2
vlan5
No settings
vlan 10
no settings
int vlan 5
no settings
int vlan 10
no settings
int g2/0/1
port link-mode bridge
port access vlan 5
int g2/0/24
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 5 10
Solved! Go to Solution.
- Tags:
- VLAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-07-2012 01:11 AM
03-07-2012 01:11 AM
SolutionHi ccavanna
Thats usual. pinging a vlan-interface is not reliable, because it is processed be the cpu and answering a icmp request has the lowest priority. It will be also the first packet to be dropped.
If you want test latency, ping a device behind the switch (i.e. a client or server).
BTW: you use a strange configuration. never seen that before
br
Manuel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-07-2012 05:48 AM
03-07-2012 05:48 AM
Re: A5500 Vlan Interface Latency Spikes
I am sure it is a strange configuration... I am new to vlaning so i am trying to get this figured out. These are going to be a pair of iscsi storage switches stacked via irf (once I get the correct modules). I ordered the AIS and ASE books to get a better grasp on things they will be in my hands today. Thanks for the reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2012 08:08 PM
03-16-2012 08:08 PM
Re: A5500 Vlan Interface Latency Spikes
If you're new to VLANs & stuff, i would suggest not using protocol-based VLANs like you have in your current configuration. Stick with static access or trunk ports and then you know exactly which port is in which VLAN(s) at all times.
As Manuel mentioned, pinging the switch's interface isn't a reliable indicator (much as i wish that it would be). I've seen up to 20% packet loss to the switch's VLAN interfaces even under light traffic load.
Paul
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP