Folks,

We ran into this problem recently and made a slight adjustment to the
InterfaceMap.py file that lives in:

$ZENHOME/Products/DataCollector/plugins/zenoss/snmp

I have attached the modified file.  This is only applicable to certain Cisco
devices running CatOS.  I have only tested with 6509s and 6513s.  This fix
changes the interface names from the generic 10/100 utp ethernet to the
correct port number, but only the slot/port is listed, like 2/3.

Make a copy of your InterfaceMap.py, then copy the attached
InterfaceMap.pyto the path above.

Then run the following against a device to test:  zenmodeler run -v 10 -d
<yourdevicename> --collect='InterfaceMap' --force

You have to use the --force option because zenmodeler will not remodel
devices that haven't changed.

Let me know if this helps and if you run into any problems.

BobJ

On 4/10/07, rauchg <[EMAIL PROTECTED]> wrote:

I have the same problem with CatOS switches.  I think I have found the
OIDs that get useful information, but I don't know how to program in python
to implement it.

The name currently seems to get populated from OID .1.3.6.1.2.1.2.2.1.2
which returns "10/100 utp ethernet (cat 3/5)" for all the 10/100 ports.

It would be somewhat better if it were populated from OID
.1.3.6.1.2.1.31.1.1.1.1 which returns "2/3" for port 2/3.

Even better would be parsing through OID table .1.3.6.1.4.1.9.5.1.4.1.1
.4.mod.port -> User defined name string for the Description field
.11.mod.port -> interger index of port in .1.3.6.1.4.1.9.5.1.4.1.1.4.1.2
for collecting performance data
.25.mod.port -> integer portEntPhysicalIndex which can be used in
1.3.6.1.2.1.47.1.1.1.1.7.nn to get physical port name "port 2/3"

If anyone can take a stab at implementing this, I would be glad to
collaborate and test it.




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=5465#5465

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Attachment: InterfaceMap.py
Description: Binary data

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to