- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Re: 2530 switch port counters freezing
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-28-2015 12:48 AM
04-28-2015 12:48 AM
2530 switch port counters freezing
Hi all!
My company uses HP 2530 8G, 24G and 48G swithes and we monitor port counters via SNMP. Now and then we are experiencing port counters freezing at those switches. When the counters stop to increment, one of the Total Bytes port counter at the particular switch is always near 2^32 value:
swa# show interface
Status and Counters - Port Counters
Port Total Bytes Total Frames
----- -------------- --------------
1 3,535,555,073 1,293,926,141
2 0 0
3 4,276,546,335 1,527,795,391
4 0 0
5 2,460,528,005 263,988,780
6 0 0
7 0 0
8 0 0
9 0 0
10 459,308,314 1,794,836,185
At 2530-48G switches we can observe freezing a block of port counters - port1..24 or port 25..28. The counters are dead and doesn't help resetting them via CLI nor Menu. The only way to get counters alive is to reboot the switch, which is really not desirable in production environment. We have tried different firmwares, from 15.12.0014 to 15.16.05 without any change.
Is it a HW or SW bug? Is anyone else experiencing this syndrome?
Petr
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2015 11:50 AM
06-05-2015 11:50 AM
Re: 2530 switch port counters freezing
I've got the same issue. the counters were working and suddenly stopped. The web interface and snmp show no changes over many hours of known traffic which most certainly should have increased them.
I can't reboot now but I'm betting that will fix it but what I want to know is why they stopped globally and is this going to happen on a regular basis?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2015 03:48 AM
08-25-2015 03:48 AM
Re: 2530 switch port counters freezing
After some investigations I have found solution: query 64 bit counters.
Now it works for more than 4 months without any problem.
In our case we use MRTG and we changed its configuration to:
community@switch:::::2
where "2" means SNMP version 2 requests. This allow you to poll 64 bit traffic counters in the switch.
Side effect is that not only MRTG counters do not freeze, but also web interface counters and CLI counters stay alive!
Petr
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2015 09:09 AM
08-25-2015 09:09 AM
Re: 2530 switch port counters freezing
What version of code? I wasn't able to immediately reproduce. Will check to see if this was fixed at some point.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2015 09:12 AM
08-25-2015 09:12 AM
Re: 2530 switch port counters freezing
Sorry, I missed the versions you tried and couldn't reproduce on any of those. Any chance you could attach the config?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2015 01:07 AM - edited 09-01-2015 04:40 AM
09-01-2015 01:07 AM - edited 09-01-2015 04:40 AM
Re: 2530 switch port counters freezing
Today I found another one with dead counters on ports 25-48. It has 255 days uptime.
Here is config (ports 37,39,41,43,45 are attached to Motorola wifi APs) :
net300# show version
Image stamp:
/ws/swbuildm/rel_orlando_qaoff/code/build/lakes(swbuildm_rel_orlando_qaoff_rel_
orlando)
Nov 19 2014 15:11:53
YA.15.16.0005
330
Boot Image: Primary
net300# show config
Startup configuration: 33
; J9775A Configuration Editor; Created on release #YA.15.16.0005
; Ver #06:04.9c.63.ff.37.27:12
hostname "net300"
timesync sntp
sntp unicast
sntp server priority 1 172.16.0.2
time daylight-time-rule western-europe
time timezone 60
ip default-gateway 172.16.0.1
interface 37
speed-duplex auto-100
exit
interface 39
speed-duplex auto-100
exit
interface 41
speed-duplex auto-100
exit
interface 43
speed-duplex auto-100
exit
interface 45
speed-duplex auto-100
exit
snmp-server community "xxx" operator
snmp-server community "yyy" unrestricted
snmp-server contact "ProCurve Switch 2530-48G" location "Designstudio"
vlan 1
name "DEFAULT_VLAN"
no untagged 46
untagged 1-45,47-52
ip address 172.16.4.20 255.255.0.0
exit
vlan 202
name "symbol"
tagged 48
no ip address
exit
vlan 888
name "video"
tagged 18,48
no ip address
exit
vlan 999
name "guest"
tagged 37,39,41,43,45,48
no ip address
exit
vlan 1012
name "facility"
untagged 46
tagged 48
no ip address
exit
vlan 1014
name "wifi_wh"
tagged 37,39,41,43,45,48
no ip address
exit
spanning-tree
spanning-tree 37 admin-edge-port
spanning-tree 39 admin-edge-port
spanning-tree 41 admin-edge-port
spanning-tree 43 admin-edge-port
spanning-tree 45 admin-edge-port
spanning-tree instance ist 37 path-cost 200000
spanning-tree instance ist 39 path-cost 200000
spanning-tree instance ist 41 path-cost 200000
spanning-tree instance ist 43 path-cost 200000
spanning-tree instance ist 45 path-cost 200000
no tftp server
no dhcp config-file-update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2015 12:54 PM
09-03-2015 12:54 PM
Re: 2530 switch port counters freezing
Hmm, I was not able to reproduce on that switch with your config. A few questions:
- What speeds are the "frozen" ports linked at? 100? 1000?
- What management system are you using to collect SNMP stats?
- Would you be willing to run some diagnostic commands? I'd like to read the hardware couters directly to see if they are "stuck". If so I will send you a follow up message to your forum "inbox".
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2015 11:34 PM
09-13-2015 11:34 PM
Re: 2530 switch port counters freezing
-ports are connected at mixed speeds - 10,100,1000 mbps
-for statistics collecting we use mrtg (http://oss.oetiker.ch/mrtg/)
-yes, I am keen on solving this issue
Petr
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2015 11:35 PM - edited 11-04-2015 11:38 PM
11-04-2015 11:35 PM - edited 11-04-2015 11:38 PM
Re: 2530 switch port counters freezing
I have to admit that using 64-bit counters didn't help. The issue occurs occasionally, switches had different uptimes - from 30 to 226 days.
I am still waiting, if anybody can help. Rebooting is not solution in production environment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2015 08:19 PM - edited 11-05-2015 08:21 PM
11-05-2015 08:19 PM - edited 11-05-2015 08:21 PM
Re: 2530 switch port counters freezing
I had no luck reproducing it. Time for a support ticket. I sent you a message for some follow up info, sorry this has dragged out.
Will report back to the thread if we find a solution (or fix).