Re: After Patching 4.3.3 disappeared lo0 device, and can't ping my own ip

From: Colin (colin_at_thedomain.co.za)
Date: 06/26/03

  • Next message: fmu_at_OERAG.DE: "strange ICMP - packets from node" 
    Date:         Thu, 26 Jun 2003 15:31:58 +0200
To: aix-l@Princeton.EDU

    What do you get when you execute 'lsattr -El lo0'?

    If the state is down then remove the loopback with 'rmdev -l lo0 -d' and
    then run 'cfgmgr'. This will reconfigure the loopback.

    This also happened to me on 4.3.2 a while ago.

    -----Original Message-----
    From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
    dballester@KERNPHARMA.COM
    Sent: Thursday, June 26, 2003 1:05 PM
    To: aix-l@Princeton.EDU
    Subject: After Patching 4.3.3 disappeared lo0 device, and can't ping my
    own ip

    Hello:
          We have an IBM J45 with Aix 4.3.3 where we have SAP R/3 4.6C +
    Oracle
    8.0.6 ( develop machine ). I have been patching this AIX 'cause we need
    to
    upgrade Oracle to 8.1.7, and some AIX patches are required. Once the
    patches had been installed, with the necessary deps, and after rebooting
    the machine the net seems to not work. With smit, disconnecting and
    enabling en2 ( that's the interface linked to the LAN ) I can ping any
    machine in the LAN, any machine in the LAN can ping me, and can connect
    with telnet or other services, but the same AIX machine can't ping or
    connect to is own ip. Walking trougth smit menus and playing with some
    netstat commands, I can see that lo0 device ( loopback ) doesn't seems
    to
    exist, or at least, is not properly configured. For example: I can't see
    lo0 when netstat -ar reports the routing tables, I can't see lo0 when
    smit->Appl. communication services->TCP/IP->Advanced Conf.->Network
    Interfaces->Network interface controllers, but I can see it when
    smit->Appl. communication services->TCP/IP->Advanced Conf.->Network
    Interfaces->Network Interface Selec->List all network interfaces ( smit
    menus are translated on the fly from spanish ). For more info, here is
    the
    output of netstat -in

    Nom. Mtu Red Direcc. Ipkts Ierrs Opkts Oerrs
    Coll
    lo0* 16896 link#1 0 0 9 0
    0
    en2 1500 link#3 0.4.ac.de.55.e8 19044 0 5540 0
    0
    en2 1500 192.168.26 192.168.26.14 19044 0 5540 0
    0

    Any tip?

    TIA, as always

    David Ballester

  • Next message: fmu_at_OERAG.DE: "strange ICMP - packets from node"

    Relevant Pages

    • Re: newbie openbsd network problem
      ... First thing I did was ifconfig both interfaces and noticed both have ... Flags Refs Use Mtu Interface ... MAC address issues is behind it. ...
      (comp.unix.bsd.openbsd.misc)
    • Re: IPF firewalling
      ... > pass out quick on lo0 all ... > interface ignored ... Btw, this machine is going to be a web, dns, ... I see you have tried to setup ftp also in the above ruleset, ...
      (freebsd-questions)
    • altq and IPsec - queue on incoming interface
      ... Sometimes there is really need for ALTQ on incoming traffic: ... There is problem on queue on $ext_if. ... Use route-to loopback interface ... Then apply queue on outgoing traffic from lo0. ...
      (comp.unix.bsd.openbsd.misc)
    • After Patching 4.3.3 disappeared lo0 device, and cant ping my own ip
      ... and some AIX patches are required. ... enabling en2 (that's the interface linked to the LAN) I can ping any ... netstat commands, I can see that lo0 device doesn't seems to ...
      (AIX-L)
    • Re: AIX ntp.conf problem
      ... create_socketsinterface <en0> OK ignoring en0 - not AF_INET interface OK ... interface <lo0> OK ignoring lo0 - not AF_INET interface OK ... flags for fd 4: 0400006 ...
      (comp.protocols.time.ntp)