Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

R

rsk

@rsk
Unfollow Follow
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • The string "[0]" instead of interface name in FDB for non-vlan1 ports
    R rsk
    Support

    Hello.

    I have just started setting up NetXMS, and I'm very impressed with the software.
    I have been looking for monitoring software that's not "Nagios style" text configs and subprocess-plugins-for everything since quite a while.

    However, I just can't find a way to solve this issue myself - hope you can help me.

    NetXMS:
    Version: 2.0.4
    Platform: Windows, 64-bit
    Database: PostgreSQL

    Network:
    All Cisco Catalyst.
    Access switches are a mix of 3560G (IOS 12.x) and 2960X (IOS 15.x).
    Core switches handling site's internal routing are 3750G (also IOS 12.x).
    Everything is detected as CATALYST-GENERIC driver by NetXMS.

    Problem:
    Switchports that are in access mode in vlan 1, and ports that are in trunk mode and include vlan 1 in trunk vlans list are identified properly.
    However, ports that do not include vlan 1 are shown as interface name "[ 0 ]" in the "Topology -> Switch forwarding database (MAC address table)" screen.

    Because of that, the "Find MAC address" function falls back to showing "indirectly connected on <router trunk port>", for example.

    I have verified with Wireshark that NetXMS is using the Cisco "community@123" vlan-indexing syntax.
    However maybe that's part of issue - names for interfaces are retrieved for base "community" only, and it's somehow not matched to same interface index numbers in the @vlan data?

    I have attached CSV dumps from the FDB screens for one of the switches - same behavior on all of them.
    I'll be happy to attach a sanitized snmpwalk if you'll tell me what subtree you need.

    switch13-infoFDB.csv: "Tools->Info->Switch forwarding database (FDB)"
    * port 49 and 50 (SFP+ uplink trunks, including vlan 1)
    * port 456 (PortGroup1 trunk, including vlan1)
    * port 4 (access port in vlan1)
    * no rows for other access ports

    switch13-topologyFDB.csv: "Topology-> Switch forwarding database (MAC address table)"
    * huge number of results for ports Gi1/0/49-50 (SFP+ uplink trunks, including vlan1)
    * multiple results for port Po1 (PortGroup1 trunk, including vlan1)
    * single result for port Gi1/0/4 (access port in vlan1)
    * Many entries for devices connected to other access ports, showing "[ 0 ]" instead of the expected "Gi1/0/xxx".

    Thank you very much!


    switch13-infoFDB.csv

    switch13-topologyFDB.csv

  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups