Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

SNMP OID different that expected

We have deployed switch stacks of 3750 on many location, and all of them are discovered by our NetView (latest patches and so on applied) correctly. They are recognized as devices which perform L2 duties. On the other hand we have deployed a single 3750 (WS-C3750G-12S) and it should be present as that swicth (according to the OID info), but it represents itself as switch stack. Is this normal behaviour? If not how could I remove the switch from starting any of the switch stack functionalities?

I would appreciate any comments on this.

Vladan

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: SNMP OID different that expected

Yes, this is normal behavior. The default sysObjectID for all 3750s is that of a stack. If you would rather this switch identify itself by its own sysObjectID, just configure:

no snmp-server sysobjectid type stack-oid

3 REPLIES
Cisco Employee

Re: SNMP OID different that expected

Yes, this is normal behavior. The default sysObjectID for all 3750s is that of a stack. If you would rather this switch identify itself by its own sysObjectID, just configure:

no snmp-server sysobjectid type stack-oid

Community Member

Re: SNMP OID different that expected

Thanks a lot.

there is only one nuisance, we have to restart the L3 switch... Uptime 1 year, 11 weeks... I like them all running until we have to reboot them.

We will manage. I wonder if we delete complete SNMP config and reapply it, with your command before any snmp command, would it change anything?

Vladan

Cisco Employee

Re: SNMP OID different that expected

No, that will not help. You will need to reboot.

200
Views
5
Helpful
3
Replies
CreatePlease to create content