This page is not finished (and may not ever be) - please ignore it for the time being

We have put a lot of effort into making the SNMP collection system as general as possible. All SNMP OIDs are i.e. structured in a separate OID database. Whenever possible we have chosen standard MIBs for our collection. In certain circumstances however, this is not possible and proprietary vendor MIBs are used. There may also be cases when a proprietary MIB is used even when not neccessary. If so, we should improve.

As evident NAV has its outspring from a Cisco based environment. HP support is also good. We would like to strengthen support for other vendor's equipment as well. With our general design we are optimistic. Added support can in many cases be done with not so much work.

We do however need help in this process! We need help to test and verify the extent of support for equipment types that are familiar to NAV. And we need assistance in pinpointing what OIDs we should use for new equipment.

As seen on this page, NAV support for a product can be characterized by many attributes (of varying importance). We describe over 20 different features that NAV are able to support. Keep in mind that we here are addressing the basic support for individual boxes, not the value added ability of understanding the intercennection between boxes, the layer 3 structere or the vlan topologies.

We are inspired by the NetDisco product page. For long we have wanted a simular overview of our own. This is our brave attempt :)

And here is our ProductsSupported page.

Here is a list of attributes that NAV can support. The list is organized into four categories; box, router ports, switch ports and module attributes.

|| Category ||Attribute || Description || || box || serial || Serial number || || box || sw || Software version || || box || mem || Memory information, including statistics || || box || cpu || CPU statistics || || box || temp || Temperature statistics || || box || cdp || CDP data (in the future we would like to see LLDP support)|| || router port || ports || All router ports with ifindex, interface name, speed, gateway IP address || || router port || descr || Router port description (ifAlias, will be stored raw in NAV 3.2) || || router port || hsrp || Support for Cisco HSRP (we would like to see VRRP support)|| || router port || metric || Support for OSPF metrics (we would like to see ISIS support) || || router port || static || Support for static routes || || router port || arp || Support for arp data collection || || router port || stat || Octets and error counter statistics for all interfaces || || switch port || ports || All switch ports with ifindex, interface name, link, speed and media || || switch port || duplex || Duplex value for all ports || || switch port || descr || Description value / port name for all switch port || || switch port || vlan || Vlan value and trunk flag set for all port || || switch port || cam || Bridge table data collected || || switch port || stp || Spanning tree data collected || || switch port || stat || Octets and error counters statistics for all ports || || module || serial || serial numbers of all modules in the box || || module || sw || software of all modules || || module || p2mod || correctly relation from module to ports; i.e. the interfaces are sitting on the correct modules ||

We give a detailed description of each attribute.

For the products you are testing, please verify support for each of the attributes listed. In many cases you can classify support simply by using the NAV web. You may also need to go in depth and query the database and/or snmp walk the product (typically using snmpwalk -v2c -c yourcommunity yourbox oid). We provide the necessary information below.

Each attribute is scored on a scale from 0-3:

|| 0 || No support || || 1 || Moderate support || || 2 || Most important aspects covered || || 3 || Fully supported ||

The serial number for the box.

• Is the collected serial number same as the physical visable serial number of the box/chassis?

Currently, we do not show the serial for the box on NAV web. In 3.2 IP device center will show this.

   SELECT sysname, serial FROM netbox 
   JOIN device USING (deviceid) 
   WHERE sysname='yourrouter';

We check a number of serial OIDs, try the ones we use, see the list produced from this query:

   SELECT oidkey,oidname,snmpoid FROM snmpoid WHERE oidkey LIKE '%eria%';

Software version of the box

• Not much

Take a look at IP device center for the box:

http://yournav.yourdomain/browse/yourbox/

   SELECT sysname, sw_ver FROM netbox 
   JOIN device USING (deviceid) 
   WHERE sysname='yourrouter';

Software is picked from a substring in sysDescr with a regexp that at least works for Cisco, HP and Nortel (it seems):

|| Variable || OID name || OID || || software || sysDescr || 1.3.6.1.2.1.1.1.0 ||

Memory information, including statistics

• Currently we only support Cisco here.

For the inventory information:

http://yournav.yourdomain/report/mem?sysname=yourrouter

For the statistics, you should have a “mem”-link from the router and switch pages in Cricket:

https://yournav.yourdomain/cricket/?target=%2Fswitches
https://yournav.yourdomain/cricket/?target=%2Frouters

   SELECT memtype,device,size,used 
   FROM mem 
   JOIN netbox USING (netboxid) 
   WHERE sysname=yourbox;

SNMP walk using these OIDs:

   SELECT oidkey,oidname,snmpoid,mib FROM snmpoid WHERE mib LIKE '%MEMORY%' OR mib LIKE '%FLASH%' ORDER BY snmpoid;

CPU statistics

• Cisco and HP is currently supported

Look for the 'cpu' link from:

https://yournav.yourdomain/cricket/?target=%2Fswitches
https://yournav.yourdomain/cricket/?target=%2Frouters

• Not relevant

SNMP walk these OIDs:

SELECT oidkey,snmpoid,mib,oidname,oidsource FROM snmpoid WHERE oidkey LIKE '%cpu%';

Temperature statistics

• Currently only Cisco

Look for the 'temp' link from:

https://yournav.yourdomain/cricket/?target=%2Fswitches
https://yournav.yourdomain/cricket/?target=%2Frouters

• Not relevant

SNMP walk these OIDs:

SELECT oidkey,snmpoid,mib,oidname,oidsource FROM snmpoid WHERE oidkey LIKE '%temp%';

CDP data from the box.

• CDP is Cisco proprietary. HP supports it (maybe not on newer software). Requires the CDP MIB

• Not relevant. CDP is used as additional information (along with bridge table data) to derive the physical topology.

• We also insert data inte netboxinfo related to CDP. In 3.2 this will be in a report. Try this query:

   SELECT sysname,key,var AS ifindex,val 
   FROM netboxinfo JOIN netbox USING (netboxid) 
   WHERE key LIKE '%CDP%' AND sysname='yourbox';

SNMP walk these OIDs:

SELECT oidkey,snmpoid,mib,oidname FROM snmpoid WHERE oidkey LIKE '%cdp%';

All router ports with ifindex, interface name, speed, gateway IP address (including secondary addresses)

• Check that speeds of 10Gig and above are correct! There is a separate ifHighSpeed oid for this.
• Check that subinterfaces (if relevant) are correctly represented in NAV. You may need to upgrade your router software if you have errors here.
• Check that secondary IP addresses is supported.

https://yournav.yourdomain/report/gwport?sysname=yourrouter

The report should show all interfaces for yourrouter with names, speed and IP addresses. Not ifindex (it will in NAV 3.2…).

This query will list all interfaces sorted by ifindex for yourrouter. If secondary IP addresses is used the interface is listed multiple times.

   SELECT ifindex,interface,speed,gwip
   FROM gwport
   JOIN gwportprefix USING (gwportid)
   JOIN prefix USING (prefixid)
   JOIN vlan USING (vlanid)
   JOIN module USING (moduleid)
   JOIN netbox USING (netboxid)
   WHERE nettype !='static' AND sysname='yourrouter'
   ORDER by ifindex;

Walk these OIDs:

|| Variable || OID name || OID || || ifIndex || ifIndex || 1.3.6.1.2.1.2.2.1.1 || || interface || ifDescr || 1.3.6.1.2.1.2.2.1.2 || || speed || iSpeed || 1.3.6.1.2.1.2.2.1.5 || || speed || ifHighSpeed || 1.3.6.1.2.1.31.1.1.1.15 || || gwip || ipAdEntIfIndex || 1.3.6.1.2.1.4.20.1.2 || || gwip || ipAdEntIfNetMask || 1.3.6.1.2.1.4.20.1.3 ||

Router port description (ifAlias, will be stored raw in NAV 3.2)

• Not much

Not stored raw today, the closest you get is the vlan.netident value. See the gwport report:

https://yournav.yourdomain/report/gwport?sysname=yourrouter

We will provide this when the gwport table is extended.

 || **Variable** || **OID name** || **OID** ||
 || ifAlias || ifAlias ||  1.3.6.1.2.1.31.1.1.1.18 ||