Kb187

Emulab FAQ: Testbed Operations: How do I handle SNMPIT switch control errors?

> I was trying to create an experiment on schooner and I got the following
> email back (then I received another email saying the exp failed):
>
> > Subject: SCHOONER.NET: snmpitError - SNMP SET failed
> >
> > SNMP SET failed - In /usr/testbed/bin/snmpit
> > SNMPIT set failed - variable was [vmVlan,3,22,INTEGER]
> > Returned (undefined), ErrorNum was 6
> > Error string is: noAccess

One of your switches refused an SNMP connection, probably due to an incorrect community string.

> I checked the routers and the community is set correctly.
> Is there another reason for this to happen or is there a place where I can
> see the logs to try to find out what happened?

Unfortunately, what you see is what you get, there are no other logs. You could try running tcpdump while you run smpit - tcpdump does know how to parse snmp packets. We could look for the last couple things it was doing.

Have you added any new switches to the DB lately?

Also, do you have a console open to any of the switches? If you left something half-finished (ie. creating a VLAN from the CLI), then that might hold some lock that would prevent SNMP from working.