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. VRRP MAC addresses and Layer 2 Topology

VRRP MAC addresses and Layer 2 Topology

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 33.8k 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.
  • T
    T
    Tursiops
    wrote on last edited by
    #1

    Hi,

    I've been gradually adding devices to NetXMS and now that I have three firewall clusters in the system, I stumbled over the fact that they are all using VRRP with the same MAC addresses (VRRP using 00:00:5E:00:01:XX for MAC addresses). As they belong to completely different networks that's not a problem for the firewalls themselves, but it does cause NetXMS to move firewalls into other networks on Layer 2 Topology maps and you can't really use the MAC address finder tool on them either.
    I have been excluding the relevant interfaces from Topology Discovery to avoid the Topology map issue, but at the same time that means the firewalls are invisible on any such maps.

    Is it possible to restrict Topology Discovery for devices or interfaces to specific zones?
    That way switches could be configured to only see the VRRP MACs in their zone, which would fix Topology mapping.
    I guess the Find MAC Address tool would then also need a Zone selector (probably an optional setting for the search, as most MACs "should" be unique).

    Is that already possible in some way?

    Cheers

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

      Hi,

      actually NetXMS server should handle VRRP MACs differently, as they will not be unique. Zoning will not help because you may have multiple VRRP interfaces within same zone. As for the topology - usually routers also provide information about real interfaces with unique MACs and VRRP MAC address should be shown only for VRRP interface, so router could be placed into correct network using it's physical interfaces. If VRRP MACs will be excluded routers should be placed correctly in L2 topology.
      I've registered issue for that: https://dev.raden.solutions/issues/1196

      Best regards,
      Victor

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

        Hi,

        I'm currently investigation VRRP issue and it works as expected on my devices. Could you please provide more information about your devices? I'm interesting in vendor/model information, are you using SNMP or agent for monitoring, for SNMP devices result of SNMP walk on .1.3.6.1.2.1.2.2.1, for agents - content of Net.InterfaceList list.

        Best regards,
        Victor

        1 Reply Last reply
        0
        • T
          T
          Tursiops
          wrote on last edited by
          #4

          Hi Victor,

          The devices are WatchGuard firewalls (XTM870, XTM330 and M200) and monitoring is done via SNMP.
          I've attached the snmpwalk output.

          Cheers


          M200.txt

          M330.txt

          XTM870.txt

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

            Hi,

            so those devices really reports VRRP virtual MAC address as interface's MAC address. Currently I've changed server to ignore VRRP and HSRP MAC addresses, so it won't try to use them for building L2 topology. However, because those devices do not provide real MAC addresses for interfaces (at least not through standard MIB) they won't appear on L2 topology map. It is actually a bug in WatchGuard's SNMP agent - it should return interface's own MAC instead of VRRP MAC even if VRRP is configured on interface.

            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