Hi
Having migrat3e to VSS (2xcat 6509), NAV is not longer able to recognize any interfaces/modules/etc.
Is there a way to make this work?
The system identifies as type "catalyst65xxVirtualSwitch" and has OID 1.3.6.1.4.1.9.1.896
Regards,
Ørjan Sæbø
On Sat, Sep 25, 2010 at 11:22:23PM +0200, Ørjan Sæbø wrote:
Hi
Having migrat3e to VSS (2xcat 6509), NAV is not longer able to recognize any interfaces/modules/etc.
Is there a way to make this work?
Unfortunately, we have no experience with monitoring VSS. I'm not sure why it would look any different than a regular Cisco router via SNMP, though.
The first way to check what's going on in NAV is to retrieve an excerpt of getDeviceData.log (grep for the VSS box' name), to see what it says.
A full SNMP dump of the device would be nice as well, but since you are a UNINETT member, I might ask you if we could be granted SNMP read access to the device in question? If so, please follow up off-list. The current betas have replaced getDeviceData as NAV's SNMP collector, and it would be interesting to know if this helps at all with your VSS setup.
On Tue, Sep 28, 2010 at 09:47:56AM +0200, Morten Brekkevold wrote:
Hi
Having migrat3e to VSS (2xcat 6509), NAV is not longer able to recognize any interfaces/modules/etc.
Is there a way to make this work?
Unfortunately, we have no experience with monitoring VSS. I'm not sure why it would look any different than a regular Cisco router via SNMP, though.
The first way to check what's going on in NAV is to retrieve an excerpt of getDeviceData.log (grep for the VSS box' name), to see what it says.
A full SNMP dump of the device would be nice as well, but since you are a UNINETT member, I might ask you if we could be granted SNMP read access to the device in question? If so, please follow up off-list. The current betas have replaced getDeviceData as NAV's SNMP collector, and it would be interesting to know if this helps at all with your VSS setup.
After having been granted SNMP access to the device, I can say that it seems to collect nicely in NAV 3.6.0b6. It presents more or less like a regular Cisco routing switch.
So it seems your specific problem is gDD related. I cannot say much without seeing your gDD logs, but I might suggest that you have been afflicted by the problem described in https://bugs.launchpad.net/nav/+bug/283240 . If your gDD logs indicate repeated timeouts for your VSS, this is likely, and you should try the workaround described in the bug report.