Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-2713

Pseudowires Remote Peer Resolving to Hostname

Details

    Description

      The resolving of the remote peer to the hostname/device in the pseudowire table is not working. It only displays the remote peer ipv4 address but if the ipv4 address is present on a device which is in observium it was previously resolving to the specific hostname.

       

      Attachments

        Issue Links

          Activity

            [OBS-2713] Pseudowires Remote Peer Resolving to Hostname

            I've checked with the latest version 9667 and this problem is still present, but I figured out that if you have a VPLS between Extreme <-> Cisco that the Extreme devices resolves the neighbor to hostname and if you view the VPLS on the Cisco site it does not resolve the neighbor to hostname.

            dklimek Denis Klimek added a comment - I've checked with the latest version 9667 and this problem is still present, but I figured out that if you have a VPLS between Extreme <-> Cisco that the Extreme devices resolves the neighbor to hostname and if you view the VPLS on the Cisco site it does not resolve the neighbor to hostname.

            You've mail. I see that on the extreme pseudowire device tab it shows correclty up with the neighbor hostname. In our example a cisco neighbor peer.

            But when I do the same on the cisco pseudowire tab it only shows us the ipv4 address of the extreme device peer. So it's "one way" working.

            And Extreme <-> Extreme is not displaying any resolved hostname :/

            dklimek Denis Klimek added a comment - You've mail. I see that on the extreme pseudowire device tab it shows correclty up with the neighbor hostname. In our example a cisco neighbor peer. But when I do the same on the cisco pseudowire tab it only shows us the ipv4 address of the extreme device peer. So it's "one way" working. And Extreme <-> Extreme is not displaying any resolved hostname :/
            landy Mike Stupalov added a comment - - edited

            dklimek Still not see reasons why not discovered...

            Pls send me 2 debugs, for:

            ./discovery.php -d -m ip-addresses,pseudowires -h <extreme_parent>
            ./discovery.php -d -m ip-addresses,pseudowires -h <extreme_peer>
            

            landy Mike Stupalov added a comment - - edited dklimek Still not see reasons why not discovered... Pls send me 2 debugs, for: ./discovery.php -d -m ip-addresses,pseudowires -h <extreme_parent> ./discovery.php -d -m ip-addresses,pseudowires -h <extreme_peer>

            It's up and the pseudowire itself is also up.

            dklimek Denis Klimek added a comment - It's up and the pseudowire itself is also up.

            even if the peer ipv4 is correctly discovered on a Loopback or routed VLAN interface

            This interfaces in down states?

            landy Mike Stupalov added a comment - even if the peer ipv4 is correctly discovered on a Loopback or routed VLAN interface This interfaces in down states?

            Looks much much better now after a re-discovery of the pseudowires. Only Extreme Pseudowires to other devices are not getting matched even if the peer ipv4 is correctly discovered on a Loopback or routed VLAN interface on the extreme device.

            dklimek Denis Klimek added a comment - Looks much much better now after a re-discovery of the pseudowires. Only Extreme Pseudowires to other devices are not getting matched even if the peer ipv4 is correctly discovered on a Loopback or routed VLAN interface on the extreme device.

            Already thought that a new discovery will be required. I started the process but it will take some minutes :-/

            dklimek Denis Klimek added a comment - Already thought that a new discovery will be required. I started the process but it will take some minutes :-/

            People

              landy Mike Stupalov
              dklimek Denis Klimek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: