In the /report/interfaces it does show up with the interfaces, also with the right names. But in the /report/netbox detail list, it doesn't show the interfaces as switchports, wich probably the reason why cricket doesn't graph the ports.
Correct, cricket will only be configured to get data from what NAV recognizes as either switching or routing interfaces.
Follow the BRIDGE-MIB lead and tell us what you find.
-- Morten Brekkevold UNINETT
The snmpwalk gives me the following output:
snmpwalk -v2c -c public 172.17.205.17 .1.3.6.1.2.1.17.1.4.1.2 iso.3.6.1.2.1.17.1.4.1.2.1 = INTEGER: 257 iso.3.6.1.2.1.17.1.4.1.2.2 = INTEGER: 258 iso.3.6.1.2.1.17.1.4.1.2.3 = INTEGER: 259 iso.3.6.1.2.1.17.1.4.1.2.4 = INTEGER: 260 iso.3.6.1.2.1.17.1.4.1.2.5 = INTEGER: 261 iso.3.6.1.2.1.17.1.4.1.2.6 = INTEGER: 262 iso.3.6.1.2.1.17.1.4.1.2.7 = INTEGER: 263 iso.3.6.1.2.1.17.1.4.1.2.8 = INTEGER: 264 iso.3.6.1.2.1.17.1.4.1.2.9 = INTEGER: 265 iso.3.6.1.2.1.17.1.4.1.2.10 = INTEGER: 266 iso.3.6.1.2.1.17.1.4.1.2.11 = INTEGER: 267 iso.3.6.1.2.1.17.1.4.1.2.12 = INTEGER: 268 iso.3.6.1.2.1.17.1.4.1.2.13 = INTEGER: 269 iso.3.6.1.2.1.17.1.4.1.2.14 = INTEGER: 270 iso.3.6.1.2.1.17.1.4.1.2.15 = INTEGER: 271 iso.3.6.1.2.1.17.1.4.1.2.16 = INTEGER: 272 iso.3.6.1.2.1.17.1.4.1.2.17 = INTEGER: 273 iso.3.6.1.2.1.17.1.4.1.2.18 = INTEGER: 274 iso.3.6.1.2.1.17.1.4.1.2.19 = INTEGER: 275 iso.3.6.1.2.1.17.1.4.1.2.20 = INTEGER: 276 iso.3.6.1.2.1.17.1.4.1.2.21 = INTEGER: 277 iso.3.6.1.2.1.17.1.4.1.2.22 = INTEGER: 278 iso.3.6.1.2.1.17.1.4.1.2.23 = INTEGER: 279 iso.3.6.1.2.1.17.1.4.1.2.24 = INTEGER: 280