cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4004
Views
5
Helpful
6
Replies

SNMP OID for speed and duplex on a Cisco 3850

arsandi
Level 1
Level 1

Does anyone knows the SNMP OID to read and write the speed and duplexMode values on a Cisco 3850? The Cisco 3850 is running IOS 3.7.2E. I was able to perform those actions on a Cisco 3750 using 1.3.6.1.4.1.9.5.1.4.1.1.9 and 1.3.6.1.4.1.9.5.1.4.1.1.10 but apparently the Cisco 3850 does not recognize them.

Thanks.

6 Replies 6

Rolf Fischer
Level 9
Level 9

Hi,

please have a look at the linked discussion an try the dot3StatsDuplexStatus object (according to the c3850 Datasheet, EtherLike-MIB is supported):

https://supportforums.cisco.com/discussion/11848411/snmp-walk-issue-lms

HTH
Rolf

Hi Rolf,

     Thank you for the prompt response. I read the description for the OID but it is a read-only value. I need to actually change the duplex value.  I also looking for the OID to change the speed value too.

did you happen to figure out which OID? having issue on 3.6.6. I can set change the snmp and duplex but the snmp read shows as auto-auto but the running config still 100-full. maybe i need a different OID which is why i'm asking. thanks

I have exactly the same problem.
Did you find the right OID?

Change switch to auto-auto (sets auto negotiate to integer 1 which is enabled)

snmpset -v 2c -c {your community string here} {your ip here} 1.3.6.1.2.1.26.5.1.1.1.9.1 i 1

 

Change switch to 100-full (set ifindex 9 (my case Gi1/0/2) to 100-full and then disable auto negotiate interger 2 = disabled)

snmpset -v 2c -c {your community string here} {your ip here} 1.3.6.1.2.1.26.2.1.1.11.9.1 o SNMPv2-SMI::mib-2.26.4.16

snmpset -v 2c -c {your community string here} {your ip here} 1.3.6.1.2.1.26.5.1.1.1.9.1 i 2

FYI there is a bug in 3.6.6 (maybe other versions as well) that resets the snmp value after a reload. for example, change running config to 100-full then do snmpget. It will come back with correct values. Then reload the switch and try the snmpget again. This time it'll come back as auto-auto even though port is specifically configured for 100-full. 

 

I worked with TAC on this issue back in Nov 2017. Here are the 2 bugs that were created. 

CSCvg62818

CSCvg58488