06-17-2013 03:00 AM
Hello Experts,
I tried SNMP walk from LMS for below OIDS but getting the error as attached..
MIB Name :- c2900PortDuplexState
OID's : 1.3.6.1.4.1.9.9.87.1.4.1.1.31
1.3.6.1.4.1.9.9.87.1.4.1.1.32
But while i do with OID 1.3.6.1.4.1.9.5.1.4.1.1.10 its showing the results.
My requirement is the pull the current negotiated Duplex status of interfaces, but with the OID 1.3.6.1.4.1.9.5.1.4.1.1.10 its only showing the configured values [ Auto , full or Half] not the negotiated duplex status if the port is in auto state. Please suggest.
Regards
Deben
Solved! Go to Solution.
06-17-2013 03:43 AM
Hi Deben,
here's a small list of OIDs for duplex for the Catalyst platforms I know and use:
1) 2900XL, 3500XL, 2900LRE, etc.: c2900PortDuplexState, c2900PortDuplexStatus
2) 2960, 3550, 3560, 3750, 4000, 6500: CISCO-STACK-MIB::portDuplex
3) 4500, 4900: EtherLike-MIB::dot3StatsDuplexStatus
For some reason I don't have access to the Object Navigator at the moment, so I can't provide the details.
I remember that one or more OIDs only work for active interfaces ("up"), just give it a try.
Hope that helps
Rolf
06-17-2013 03:50 AM
Topping up on Rolf's from cisco Object Navigator:
Object | c2900PortDuplexState |
OID | 1.3.6.1.4.1.9.9.87.1.4.1.1.31 |
Type | INTEGER |
Permission | read-write |
Status | current |
Values | 1 : fullduplex 2 : halfduplex 3 : autoNegotiate |
MIB | CISCO-C2900-MIB ; - View Supporting Images |
Description | "Set to fullduplex(1) to operate in full duplex mode, port will allow simultaneous transmit and receive which can double its bandwidth. Set to halfduplex(2) to operate in half duplex mode. Set to autoNegotiate(3) to allow the switch to negoti- ate with the other end of the connection. The status of duplex mode on a port is available with c2900PortDuplexStatus object." |
|
Object | portDuplex |
OID | 1.3.6.1.4.1.9.5.1.4.1.1.10 |
Type | INTEGER |
Permission | read-write |
Status | current |
Values | 1 : half 2 : full 3 : disagree 4 : auto |
MIB | CISCO-STACK-MIB ; - View Supporting Images |
Description | "Indicates whether the port is operating in half- duplex, full-duplex, disagree or auto negotiation mode. If the port could not agree with the far end on port duplex, the port will be in disagree(3) mode." |
Object | dot3StatsDuplexStatus |
OID | 1.3.6.1.2.1.10.7.2.1.19 |
Type | INTEGER |
Permission | read-only |
Status | current |
Values | 1 : unknown 2 : halfDuplex 3 : fullDuplex |
MIB | EtherLike-MIB ; - View Supporting Images |
Description | "The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy." |
|
-Thanks
06-17-2013 03:43 AM
Hi Deben,
here's a small list of OIDs for duplex for the Catalyst platforms I know and use:
1) 2900XL, 3500XL, 2900LRE, etc.: c2900PortDuplexState, c2900PortDuplexStatus
2) 2960, 3550, 3560, 3750, 4000, 6500: CISCO-STACK-MIB::portDuplex
3) 4500, 4900: EtherLike-MIB::dot3StatsDuplexStatus
For some reason I don't have access to the Object Navigator at the moment, so I can't provide the details.
I remember that one or more OIDs only work for active interfaces ("up"), just give it a try.
Hope that helps
Rolf
06-17-2013 03:50 AM
Topping up on Rolf's from cisco Object Navigator:
Object | c2900PortDuplexState |
OID | 1.3.6.1.4.1.9.9.87.1.4.1.1.31 |
Type | INTEGER |
Permission | read-write |
Status | current |
Values | 1 : fullduplex 2 : halfduplex 3 : autoNegotiate |
MIB | CISCO-C2900-MIB ; - View Supporting Images |
Description | "Set to fullduplex(1) to operate in full duplex mode, port will allow simultaneous transmit and receive which can double its bandwidth. Set to halfduplex(2) to operate in half duplex mode. Set to autoNegotiate(3) to allow the switch to negoti- ate with the other end of the connection. The status of duplex mode on a port is available with c2900PortDuplexStatus object." |
|
Object | portDuplex |
OID | 1.3.6.1.4.1.9.5.1.4.1.1.10 |
Type | INTEGER |
Permission | read-write |
Status | current |
Values | 1 : half 2 : full 3 : disagree 4 : auto |
MIB | CISCO-STACK-MIB ; - View Supporting Images |
Description | "Indicates whether the port is operating in half- duplex, full-duplex, disagree or auto negotiation mode. If the port could not agree with the far end on port duplex, the port will be in disagree(3) mode." |
Object | dot3StatsDuplexStatus |
OID | 1.3.6.1.2.1.10.7.2.1.19 |
Type | INTEGER |
Permission | read-only |
Status | current |
Values | 1 : unknown 2 : halfDuplex 3 : fullDuplex |
MIB | EtherLike-MIB ; - View Supporting Images |
Description | "The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy." |
|
-Thanks
06-17-2013 10:33 PM
Thanks Guys.. Its really helped .. Now able to get the duplex as expected.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide