failover on PIX

Discussion in 'Cisco' started by Salus, Nov 4, 2003.

  1. Salus

    Salus Guest

    Hello,

    Can anybody have a look at my issue? Everything seems ok but I can not
    make the failover running properly...

    You have here the show fail and show interface.

    With the hope it will help to fix the issue,

    Many thanks,

    Seb

    pix# sh fail
    Failover On
    Cable status: Normal
    Reconnect timeout 0:00:00
    Poll frequency 15 seconds
    failover replication http
    This host: Secondary - Active
    Active time: 936660 (sec)
    Interface sync (10.10.10.1): Normal (Waiting)
    Interface intf4 (127.0.0.1): Link Down (Shutdown)
    Interface intf3 (127.0.0.1): Link Down (Shutdown)
    Interface dmz (203.27.5.12.245): Link Down (Waiting)
    Interface external (203.27.9.10.245): Normal (Waiting)
    Interface inside (203.27.2.11.245): Normal (Waiting)
    Other host: Primary - Standby (Failed)
    Active time: 300 (sec)
    Interface sync (10.10.10.2): Normal (Waiting)
    Interface intf4 (0.0.0.0): Link Down (Shutdown)
    Interface intf3 (0.0.0.0): Link Down (Shutdown)
    Interface dmz (203.27.5.12.246): Link Down (Waiting)
    Interface external (203.27.9.10.246): Failed (Waiting)
    Interface inside (203.27.2.11.246): Normal (Waiting)

    Stateful Failover Logical Update Statistics
    Link : sync
    Stateful Obj xmit xerr rcv rerr
    General 39 0 41 0
    sys cmd 39 0 39 0
    up time 0 0 2 0
    xlate 0 0 0 0
    tcp conn 0 0 0 0
    udp conn 0 0 0 0
    ARP tbl 0 0 0 0
    RIP Tbl 0 0 0 0

    Logical Update Queue Information
    Cur Max Total
    Recv Q: 0 1 41
    Xmit Q: 0 1 39

    pix# sh interface

    interface ethernet0 "external" is up, line protocol is up
    Hardware is i82559 ethernet, address is 000d.bdbb.b648
    IP address 203.27.9.10.245, subnet mask 255.255.255.0
    MTU 1500 bytes, BW 100000 Kbit full duplex
    4685983 packets input, 698378593 bytes, 0 no buffer
    Received 4688021 broadcasts, 0 runts, 0 giants
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    62485 packets output, 3750772 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 babbles, 0 late collisions, 0 deferred
    0 lost carrier, 0 no carrier
    input queue (curr/max blocks): hardware (128/128) software
    (0/16)
    output queue (curr/max blocks): hardware (0/10) software (0/9)

    interface ethernet1 "inside" is up, line protocol is up
    Hardware is i82559 ethernet, address is 000d.bdbb.b64a
    IP address 203.27.2.11.245, subnet mask 255.255.255.0
    MTU 1500 bytes, BW 100000 Kbit full duplex
    3828506 packets input, 654332063 bytes, 0 no buffer
    Received 3829563 broadcasts, 0 runts, 0 giants
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    62485 packets output, 3750772 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 babbles, 0 late collisions, 0 deferred
    0 lost carrier, 0 no carrier
    input queue (curr/max blocks): hardware (128/128) software
    (0/15)
    output queue (curr/max blocks): hardware (0/10) software (0/9)

    interface ethernet2 "dmz" is up, line protocol is down
    Hardware is i82559 ethernet, address is 0005.5d18.84f8
    IP address 203.27.5.12.245, subnet mask 255.255.255.0
    MTU 1500 bytes, BW 100000 Kbit full duplex
    0 packets input, 0 bytes, 0 no buffer
    Received 0 broadcasts, 0 runts, 0 giants
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    62485 packets output, 3750772 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 babbles, 0 late collisions, 0 deferred
    0 lost carrier, 0 no carrier
    input queue (curr/max blocks): hardware (128/128) software
    (0/0)
    output queue (curr/max blocks): hardware (0/10) software (0/9)

    interface ethernet3 "intf3" is administratively down, line protocol is
    down
    Hardware is i82559 ethernet, address is 0005.5d18.84f9
    IP address 127.0.0.1, subnet mask 255.255.255.255
    MTU 1500 bytes, BW 100000 Kbit full duplex
    0 packets input, 0 bytes, 0 no buffer
    Received 0 broadcasts, 0 runts, 0 giants
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    0 packets output, 0 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 babbles, 0 late collisions, 0 deferred
    0 lost carrier, 0 no carrier
    input queue (curr/max blocks): hardware (128/128) software
    (0/0)
    output queue (curr/max blocks): hardware (0/0) software (0/0)

    interface ethernet4 "intf4" is administratively down, line protocol is
    down
    Hardware is i82559 ethernet, address is 0005.5d18.84fa
    IP address 127.0.0.1, subnet mask 255.255.255.255
    MTU 1500 bytes, BW 100000 Kbit full duplex
    0 packets input, 0 bytes, 0 no buffer
    Received 0 broadcasts, 0 runts, 0 giants
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    0 packets output, 0 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 babbles, 0 late collisions, 0 deferred
    0 lost carrier, 0 no carrier
    input queue (curr/max blocks): hardware (128/128) software
    (0/0)
    output queue (curr/max blocks): hardware (0/0) software (0/0)

    interface ethernet5 "sync" is up, line protocol is up
    Hardware is i82559 ethernet, address is 0005.5d18.84fb
    IP address 10.10.10.1, subnet mask 255.255.255.252
    MTU 1500 bytes, BW 100000 Kbit full duplex
    13 packets input, 7158 bytes, 0 no buffer
    Received 3 broadcasts, 0 runts, 0 giants
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    62486 packets output, 3754282 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 babbles, 0 late collisions, 0 deferred
    0 lost carrier, 0 no carrier
    input queue (curr/max blocks): hardware (128/128) software
    (0/3)
    output queue (curr/max blocks): hardware (0/10) software (0/9)

    pix#
    Salus, Nov 4, 2003
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Mike Harrison

    Pix 535 Failover bundle/DSL question

    Mike Harrison, Jul 12, 2003, in forum: Cisco
    Replies:
    2
    Views:
    1,063
  2. Alec Waters
    Replies:
    0
    Views:
    1,486
    Alec Waters
    Jun 9, 2004
  3. Replies:
    1
    Views:
    518
    Walter Roberson
    Sep 11, 2005
  4. Tom Pouce
    Replies:
    6
    Views:
    6,095
  5. Pit
    Replies:
    0
    Views:
    1,113
Loading...

Share This Page