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

  1. Home
  2. Support
  3. NetXMS Shows VLAN at wrong Ports

NetXMS Shows VLAN at wrong Ports

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 8.2k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    S
    Spheron
    wrote on last edited by
    #1

    Hello @all,

    having here NetXMS V5.0.4 at Linux Debian 12 running. 

    Today i installed a new switch (Netgear GS728TPv3 / Software Version 6.2.0.25). At switch UI i see/set my configured VLAN at the ports:

    VLAN1 -  g1 - g18, g25 - g28
    VLAN2  - g19 - g24

    In NetXMS the VLANs for VLAN2 shows on Port g11-g16 !!! The switch is polled via SNMP 2C.

    Is this a bug in NetXMS or sends the switch wrong data via snmp?

    Having anyone else such an issue?

    Greetings
    Marco

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Server reads VLAN names from 1.3.6.1.2.1.17.7.1.4.3.1.1, then ports from 1.3.6.1.2.1.17.7.1.4.2.1.5 and 1.3.6.1.2.1.17.7.1.4.2.1.4, optionally also 1.3.6.1.2.1.17.7.1.4.3.1.2. For all those 3 tables index is VLAN ID and value is byte string, where each bit represent port membership in VLAN. You can check what values are actually returned. Below is description from Q-BRIDGE-MIB:

      Each octet within this value specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port.  Thus, each port of the bridge is represented by a single bit within the value of this object.  If that bit has a value of '1' then that port is included in the set of ports; the port is not included if its bit has a value of '0'.

      Also note that "port number" in this context is bridge port number (as obtained from 1.3.6.1.2.1.17.1.4.1.2), not interface index.

      Best regards,
      Victor

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • 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