Re: Gateway reset on reboot (was: xnptd insane after reboot)

From: Dave Stewart (dstewart_at_AQUAFLO.COM)
Date: 05/20/05

  • Next message: jeff barratt-mccartney: "veritas foundation suites (vxvm/vxfs) and database edition on aix"
    Date:         Thu, 19 May 2005 17:25:25 -0700
    To: aix-l@Princeton.EDU
    
    

    On May 18, 2005, at 9:04 PM, hercom offered this insight:

    > I had a similar issue... I had to flush the table and remove all the
    > network
    > interfaces (smitty-further configuration), cfgmgr and put the values
    > again.

    Oh oh, now I've done it. :-(

    I thought this sounded good, so I:

    1. flushed the routing tables
    2. smitty tcpip -> further configuration -> network interfaces ->
    network interface selection -> remove a network interface (done for all
    network interfaces; trying to blast out the old gateway value that just
    won't die).
    3. cfgmgr
    4. try to reconfigure the interfaces with smitty tcpip -> minimum
    configuration & startup ...

    Here's the output that smitty is giving me (note this isn't good):

    en2
    rusty
    inet0 changed
    method error (/usr/lib/methods/chgif):
    0514-068 cause not known
    0821-510 ifconfig: error calling entry point /usr/lib/drivers/if_en:
    the specified device does not exist
    0821-002 chgif: getting records from CuAt
    0821-007 chgif: ifconfig command failed
    the status of "en2" interface in the current running system is uncertain
    0821-223 chgif: can not get records from CuAt
    0821-510 ifconfig: error calling entry point /usr/lib/drivers/if_en:
    the specified device does not exist
    0821-223 chgif: can not get records from CuAt
    0821-229 chgif: ifconfig command failed
    the status of "en2" interface in the current running system is uncertain
    mktcpip: problem with command chdev:
    return code = 1

    Fortunately, this particular machine isn't used by anyone currently
    (I'm trying to fix that by making it a time server and DNS server for
    internal corporate use). Unfortunately I have no idea how to recover
    from this. This machine was working fine (when you reconfigured the
    network interfaces after a reboot) and now it's still running, but I
    can't connect to it anymore (fortunately it's right behind me, not 6
    feet away:).

    Robert Miller was kind enough to mention that if I used smitty tcpip to
    set the gateway, it should persist across reboots. Unfortunately for us
    it does not and that's the issue I'm trying to address (at least it was
    before I screwed the pooch).

    So, anyone have any ideas what I can do or say to get over this? Any
    insight is welcome and greatly appreciated, except for the obvious "now
    you've done it, dummy". (I'll be thrilled if someone can show me this
    isn't as bad as it feels!)

    >
    > Also check on the scripts in /etc/rc.d/ for the "routeadd" statement.

    I checked for this, there is no routeadd statement anywhere in those
    scripts. I did notice that the old gateway value *STILL* shows up in
    smitty tcpip, even though the device is now dead and unconfigurable (so
    it seems not only have I broke it worse than it was, but I also haven't
    fixed the issue I'm trying to attack vehemently).

    >
    >
    > -----Original Message-----
    > From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf
    > Of Dave
    > Stewart
    > Sent: Wednesday, May 18, 2005 3:37 PM
    > To: aix-l@Princeton.EDU
    > Subject: Gateway reset on reboot (was: xnptd insane after reboot)
    >
    > Hi folks!
    >
    > ...
    >
    > Disclaimer: I don't know what I'm doing. OK, that may be a little
    > drastic, but I'm not a studied AIX admin yet so please be a little
    > patient with me.
    > ;-)
    >
    > On Apr 7, 2005, at 9:02 PM, Bob Booth - CITES offered this insight:
    >
    >>>
    >>> Next question, why does this server (IBM E20 running AIX 5.1) keep
    >>> resetting it's gateway on a reboot? Where *could* it be caching this
    >>> old gateway value?
    >>
    >> How exactly is the gateway being set through smit? If done correctly,
    >> the
    >> gateway information is stored in the ODM and set when the machine
    >> comes up.
    >
    > smitty tcpip
    > Minimum Configuration & Startup
    > en2 (desired network interface; we also have en1 configured with a
    > different address, but with the same issue)
    > new default gateway is set in the "Default Gateway" entry and I hit
    > <enter> to make it happen.
    >
    > Note at this point I usually have to flush the routing tables, as the
    > old gateway is often littered throughout it.
    >
    >>
    >> You can check what value is stored in the ODM to make sure it is
    >> correct:
    >>
    >> odmget -q name="inet0" CuAt
    >
    > Gee, this gives me a bunch of stuff. Some of it looks right, but most
    > of it looks just wrong. I show 26 entries similar to the following:
    >
    > CuAt:
    > name = "inet0"
    > attribute = "route"
    > value = "net,-hopcount,5,,0,192.168.2.253"
    > type = "R"
    > generic = "DU"
    > rep = "s"
    > nls_index = 0
    >
    > CuAt:
    > name = "inet0"
    > attribute = "route"
    > value = "net,-hopcount,0,,0,192.168.12.2"
    > type = "R"
    > generic = "DU"
    > rep = "s"
    > nls_index = 0
    >
    > Above, the first example is just wrong (old network value), the second
    > example shows the new (correct) gateway value.
    >
    > Sorry, I just don't know what this means or how to deal with it. I can
    > handle smitty OK and have man-handled the routing tables before, but
    > here I feel like I'm drowning here (well over my head). I feel like I
    > want to blast all these CuAt entries away and start over, but I don't
    > know how to do that or if it would even fix my issue.
    >
    > If there is a chapter in the docs I should be reading, please feel free
    > to direct me there.

    Dave Stewart
    Aqua~Flo Supply (Goleta CA)
    dstewart at aquaflo dot com

    There are 10 kinds of people in the world:
    Those who understand binary and those who don't.


  • Next message: jeff barratt-mccartney: "veritas foundation suites (vxvm/vxfs) and database edition on aix"

    Relevant Pages

    • RE: Using Fedora as firewall.
      ... configuring two network interfaces. ... This sounds like you specified a default gateway on the eth1 interface. ... network interfaces. ... Just make sure you edit the eth1 config and make ...
      (Fedora)
    • Re: Gateway reset on reboot (was: xnptd insane after reboot)
      ... I had to flush the table and remove all the network ... interfaces (smitty-further configuration), cfgmgr and put the values again. ... Subject: Gateway reset on reboot ... smitty tcpip ...
      (AIX-L)
    • IPSec (i.e. Freeswan 2.x), Linux kernel 2.6 no longer masquerading (NATing) connections
      ... kernel and thus the virutal ipsecN interfaces once used for IPSec ... Cisco IPSec clients for Linux have done this for a while now), ... makes NAT'ing VPN traffic on a gateway difficult - if not impossible. ... network across an IPSec tunnel? ...
      (comp.os.linux.networking)
    • Re: network parameters
      ... > Is there a way to get network parameters (number of network ... - number of network interfaces, ip address, gateway: ... The problem with the world is stupidity. ...
      (comp.lang.python)
    • Re: PIX 506E Multiple LAN-Areas...
      ... :> 192.168.100.128/25 Gateway should be 100.129 on the PIX ... :network per interface with current OS versions. ... The 506E with current software allows two virtual interfaces, ...
      (comp.dcom.sys.cisco)