Wired Intelligent Edge

 View Only

  • 1.  Netedit 2.9 and prior, cannot discover routed devices.

    Posted Nov 27, 2023 05:01 AM

    Non devices, other the one on the local VLAN as the server, is reachable ?

    Ping/dns/ntp from linux console works fine.

    Anyone ?



    ------------------------------
    Steinar
    ------------------------------


  • 2.  RE: Netedit 2.9 and prior, cannot discover routed devices.

    Posted Nov 27, 2023 10:54 AM

    Hello Steinar, AFAIK I don't see any issue on my Aruba NetEdit 2.9.0 (and I updated it exactly today from Aruba NetEdit 2.8.0): the Aruba NetEdit 2.9.0 is still able to reach the registered switches (currently I've just a pair of VSX Clusters) hosted on a different network (routed) segment, as usual. So no issue so far. Have you troubleshooted at the Debian OS level looking for any relevant log?


    Original Message


  • 3.  RE: Netedit 2.9 and prior, cannot discover routed devices.

    Posted Nov 27, 2023 11:02 AM

    Thanks; but not

    I have only checked ping/dns/..

    Not fluent in LinuxL

    ps, it has been (long time) since 2.1

    Dusins of routed destination is not reachable  L

     

     

     




    Original Message


  • 4.  RE: Netedit 2.9 and prior, cannot discover routed devices.

    Posted Nov 28, 2023 04:46 AM

    If I were you I would login through SSH into the Aruba NetEdit server (as neadmin user) and perform just few basic checks, as example:

    Linux netedit.datafarm.local 4.19.0-24-amd64 #1 SMP Debian 4.19.282-1 (2023-04-29) x86_64

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.
    Last login: Mon Nov 27 03:31:45 2023 from <Logged-Workstation-IP>

    You may re-configure the network by typing 
    'sudo python netedit_config.py -f yes' .

    neadmin@netedit:~$ ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether 00:50:56:xx:xx:xx brd ff:ff:ff:ff:ff:ff
        inet <NetEdit-IP>/24 brd <Gateway-IP> scope global eth0
           valid_lft forever preferred_lft forever

    neadmin@netedit:~$ ip r
    default via <Gateway-IP> dev eth0 onlink 
    <NetEdit-Subnet>/24 dev eth0 proto kernel scope link src <NetEdit-IP> 

    neadmin@netedit:~$ cat /etc/resolv.conf
    search datafarm.local
    nameserver <NS-Resolver-1-IP>
    nameserver <NS-Resolver-2-IP>

    neadmin@netedit:~$ cat /etc/hosts
    127.0.0.1     localhost
    127.0.1.1     netedit
    <NetEdit-IP>  netedit.domain.local netedit


    Original Message


  • 5.  RE: Netedit 2.9 and prior, cannot discover routed devices.

    Posted Nov 28, 2023 09:03 AM

    Thank you, it looks exactly the same, with own values in bold

     

     

    Steinar Grande




    Original Message


  • 6.  RE: Netedit 2.9 and prior, cannot discover routed devices.
    Best Answer

    Posted Nov 28, 2023 02:49 PM

    Perfect! so - simply speaking - if your Aruba NetEdit 2.9.0 Server is able to reach its default gateway (and all hosts belonging to its newtowkr segment) then the culprit could be found at routing level (or when the routing happens or at switching level, VLAN membership).


    Original Message


  • 7.  RE: Netedit 2.9 and prior, cannot discover routed devices.

    Posted Nov 29, 2023 05:27 AM

    Thanks, after allerting the firewall duds, they fixed :)



    ------------------------------
    Steinar
    ------------------------------

    Original Message


Related Content