- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: Wrong Value for SNMPv3 LACP ActorOperState
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
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
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
тАО09-08-2016 02:32 AM - edited тАО09-08-2016 04:02 AM
тАО09-08-2016 02:32 AM - edited тАО09-08-2016 04:02 AM
Wrong Value for SNMPv3 LACP ActorOperState
Hello,
we are implementing a new monitoring system at the moment. We want to integrate our HP A5500-48G SI IRF stack in the monitoring system, especially the LACP link states.
The switch is running version 5.20.99 R2221P06.
The monitoring system can connect to the switch via SNMPv3 without problems.
The problem is the value that is returned for the following MIB: 1.2.840.10006.300.43.1.2.1.1.21
This should be an IEEE MIB for 802.3ad aggregated ports ( http://www.mibdepot.com/cgi-bin/getmib3.cgi?win=mib_a&n=IEEE8023-LAG-MIB&r=avaya&f=ieee8023-lag.mib&t=tree&v=v2&i=0 ), which should return values 0 to 7 in an octet string. But it returns the following:
08.09.2016 10:44:48 (465 ms) : 1.2.840.10006.300.43.1.2.1.1.21.4 = "┬г" [ASN_OCTET_STR] 08.09.2016 10:44:48 (588 ms) : 1.2.840.10006.300.43.1.2.1.1.21.5 = "┬╝" [ASN_OCTET_STR] 08.09.2016 10:44:48 (704 ms) : 1.2.840.10006.300.43.1.2.1.1.21.6 = "┬╝" [ASN_OCTET_STR] 08.09.2016 10:44:49 (834 ms) : 1.2.840.10006.300.43.1.2.1.1.21.7 = "┬в" [ASN_OCTET_STR]oct 08.09.2016 10:44:49 (943 ms) : 1.2.840.10006.300.43.1.2.1.1.21.8 = "┬в" [ASN_OCTET_STR]
This walk was made with the "Paessler SNMP Tester 5.2.3" but the server shows the same values.
Is the problem in the software interpreting the values wrong, can I change the character set or something on the switch or did I simply use the wrong MIB for my purpose?
Alternatively we would monitor the single ports and the speed of the link aggregation to see when a problem occurs but that costs us more sensors (we pay per sensor).
Thank you for your help.
EDIT:
When I check the MIBs in our IMC I get the same values as hexa numbers:
***** SNMP GET REQUEST STARTED ***** 1) 1.2.840.10006.300.43.1.2.1.1.21.4 (dot3adAggPortActorOperState.4) A3 ***** SNMP GET REQUEST FINISHED ***** ***** SNMP GET REQUEST STARTED ***** 1) 1.2.840.10006.300.43.1.2.1.1.21.5 (dot3adAggPortActorOperState.5) BC ***** SNMP GET REQUEST FINISHED ***** ***** SNMP GET REQUEST STARTED ***** 1) 1.2.840.10006.300.43.1.2.1.1.21.6 (dot3adAggPortActorOperState.6) BC ***** SNMP GET REQUEST FINISHED ***** ***** SNMP GET REQUEST STARTED ***** 1) 1.2.840.10006.300.43.1.2.1.1.21.7 (dot3adAggPortActorOperState.7) A2 ***** SNMP GET REQUEST FINISHED *****
Converting these into a string will get you the characters our monitoring shows.
But they are supposed to be the following:
LacpState ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The Actor and Partner State values from the LACPDU." SYNTAX BITS { lacpActivity(0), lacpTimeout(1), aggregation(2), synchronization(3), collecting(4), distributing(5), defaulted(6), expired(7) }
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2016 12:20 PM
тАО09-08-2016 12:20 PM
Re: Wrong Value for SNMPv3 LACP ActorOperState
Hmm,
Based upon your testing so far I don't think that there's much we are going to be able to do to help on the forums.
I would just uplift the software to the latest publically available version (there's a p22 version) and if that doesn't help I'd get a support case raised with HPE Networking support team. The support team will probably ask you to uplift the code anyway so you might as well be on the front foot.
Not much help I'm afraid this time.
Cheers
Ian
## ---------------------------------------------------------------------------##
Which is the only cheese that is made backwards?
Edam!
Tweets: @2techie4me
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2016 07:12 AM
тАО10-03-2016 07:12 AM
Re: Wrong Value for SNMPv3 LACP ActorOperState
Hi,
Isn't it so that the hexvalue you get in return, is the value of the those 8 bits?
So that
A3 = 10100011 BC = 10111100 A2 = 10100010
I'm not sure which would be the highend bit, but
If the the first bit is considered highend.
then BC would "mean":
lacpActivity : TRUE lacpTimeout : FALSE aggregation : TRUE synchronization : TRUE collecting : TRUE distributing : TRUE defaulted : FALSE expired : FALSE
I think its as simple as that.
Regards
Region Midtjylland