Dnia ?roda, 19 stycznia 2005 15:34, Kristian Eide napisa?:

...

module | port | ifindex | vlan | vlanid --------+------+---------+------+-------- 1 | | 28 | | 1 | 2 | 3 | 2 |

Thank you. The vlan-number is there, but before it becomes visible on the web the networkDiscovery module needs to "see" it as well. Could you run the command:

/usr/lib/nav/networkDiscovery.sh debug vlan

And then send me the file:

/var/log/nav/networkDiscovery/networkDiscovery-debug.html

With this information I should hopefully be able to tell you what is going on.

first: networkDiscovery.sh in debian is in: /usr/lib/nav/networkDiscovery.sh after i run this: /usr/lib/nav/networkDiscovery.sh debug vlan /usr/lib/nav/networkDiscovery.sh: line 39: /var/lib/nav/log/networkDiscovery/networkDiscovery-debug.html: No such file or directory so i create networkDiscovery dir and here is output of debug: --------------------------------------------- Begin Generated on: Wed Jan 19 15:41:37 CET 2005 WARNING: Multiple trunks between 2950_p_core and CR1_p WARNING: Multiple trunks between 2950_p_core and CR1_p WARNING: Multiple trunks between 2950_p_core and CR1_p WARNING: Multiple trunks between 2900_pr_core and TR2_pr WARNING: Multiple trunks between 2950_p_core and TR1_p VLANs with no router to start from: Report: (found 0 records) New count: 0, Update count: 0 Dup count: 0, Rem count: 0 Unused count: 0, Rename vlan count: 0 Allowed, but non-active VLANs: (Note: VLANs 1 and 1000-1005 are for interswitch control traffic and are always allowed) A total of 0 / 0 trunks have allowed VLANs that are not active. Jan 19 15:41:37 2005 null EVENTQ-6-POST_EVENT Posted event from getDeviceData to eventEngine (notification, null) on eventq All done. -- Wojciech (Woj) Kozicki