VIF Bound Physcial Interface Down

Hi Guys!
We are trying to connect FI 6248 (UCSM 2.1.1a) to Brocade 6510 swtich(One FI to one of the two Brocade switches separately). The ports are configured as FC Uplink port and the FI's work in End-host mode. We created the service profile. After associating the SP to one of the blades the two errors occurs immediately:
VIF <number> Bound Physical Interface Down
VIF <number> Bound Physical Interface Down
and this relates to the 2 vHBAs created in SP. Is this normal situation if OS isn't already installed on the host? We can't configure SAN zone from the brocade side because we don't see any WWPNs of the configured vHBAs in the SP. We see only FI's WWPNs(as I think). NPIV mode is enabled from the Brocade side. 
Can someone explain what can cause this problem?

Sergey,
This is expected if there is no OS installed yet, see the possible reasons for the VIF down in this bug:
https://tools.cisco.com/bugsearch/bug/CSCul99847
Rate ALL helpful answers.
-Kenny

Similar Messages

  • F0283 VIF 1 / 2 B-42/44 down, reason: Bound Physical Interface Down

    Hi
    I have some issues after migrate from CX4 SAN to VNX SAN. Everything is moved from CX4 to VNX and I have disabled FC Uplink port that is connected to CX4. Both my FI's is only connected to VNX.
    We want SAN boot on our ESXi host, and some of them is install on a boot LUN on VNX, and some other is install local at the Blade.
    My issue is that all my host shall boot from SAN. But suddenly this fails.
    I zones the host on our MDS switches, and does everything in VNX, so the host shall see its boot LUN. SAN Boot Target is changed so it sees the VNX SAN.
    In the install I see my boot LUN, and install ESXi without any issues. Remove the installation media and reboots the server.
    When it shall boot back up, it says:
    Reboot and Select proper Boot device
    or Insert Boot Media in selected Boot device and press a key.
    And i gets 8 major error messages like this:
    VIF 1 / 2 B-42/44 down, reason: Bound  Physical Interface Down
    What is wrong. I do the same thing now, as I did when I installed the hosts that is working.

    Can you try to re-ack the Server the Profile is associated to.  The error you're seeing usually means the host Iniitator interface (VIF) is down because it has no uplink to correclty pin to.  You said you shut down the ports the CX4 was previously connected to by disabling it.  Can you re-ack the blade which should re-pinn to the new/remaining uplink.
    If that doesn't correct the problem I'd look into your boot policy.  Double and triple check the boot targets entered in the profile and make sure they match the targets on the VNX, and that each one is online and logged into the MDS ("zone flogi database").  The symptoms you're seeing used to be common with Clariion arrays as they are Active/Passive.  During the installation any available path has access to the LUN for the installation, but they rebooting required the first listed target in the boot policy to be the "owner" of the LUN.  This was easily fixed by trespassing the LUN to the other Storage Processor on the array.  With VNX I'm pretty sure they are Active/Active arrays so this shouldn't matter.
    Regards,
    Robert

  • Unidentified traps and interface down alerts LMS 4.2

    Hi all,
    Sometimes we have unidentified traps in our log, we don't know where they come from.
    In high severity faults we see an active alert with device name “Unidentified” event name unresponsive but with a certain ip address.
    What are these alerts about? Can I filter them?
    A second issue I have is that I get interface down alerts. But when we log on to the device, there is no interface down at all. We can also ping the device from the lms server at that time. I have been told that the admin state and operational state has to be up.
    Thanks,
    Best Regards,
    Joris

    Hi Joris,
    Generic trap support is a new feature introduced in LMS 4.2 release. look at the below
    document also.
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/user/guide/lms_monitor/TrapFwd.html#wpxref13049
    LMS 4.2 release onwards DFM will display any unprocessed traps comming from device in
    fault monitor screen as unidentified trap under Inform alarm.
    For the other issue , it could be a DFM database issue , try to REDISCOVER those devices in
    DFM and see how it works
    Thanks
    Afroz

  • Intermittant radio interface down on 1130 APs

    I am having unified wireless installation, with WiSM on 6500 at central site and around 90 nos of 1130 APs located at remote locations ( over WAN) as well as some APs locate in the same location.
    The APs are configured in WCS, using default AP template.
    Alsomot all APs are showing minor alarms saying " radio interface threshold violated".
    In addition, a major alarm posted frequently on WCS saying "radion interface down".
    Cleints are complaining that they are loosing connectkion momentarily but connected again automatically wo WLAN. But they will have to log in to application programs in such cases.
    a.Does anybody have similar experience, and
    b. What are the best settings for 1130 APs trhat we have to do explicitly in setting up the WCS template ?
    Thanks ,

    Might be due to interference and the fact that RRM is enalbled and the ap's are changing channels causing the radios to shut down temporarily. Either set the channel or try to change the threshold.
    Here is the error info:
    http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcsevent.html#wp1139158

  • Bringing an interface down using a network profile

    I use netcfg to switch between network profiles... but when I switch from a profile using ethernet to a profile using wireless, it just adds the other interface... so that both ethernet and wireless are up.
    The only way I know to bring an interface down (say, ethernet) is to edit NET_PROFILES in /etc/rc.conf and put in a profile using wireless, and do /etc/rc.d/network restart.
    But is there an easier way? Is there some sort of command I can put inside my profile which uses wireless to bring down the ethernet interface?
    Thanks.

    I'm not infront of a Linux box right now, but perhaps if you could run, as root:
    # ifconfig eth0 down;
    of course, replace eth0 with the appropriate interface you wish to take down.
    p.s. - I hope i'm not completely getting your question wrong because I feel I may be.

  • Force dialer interface down

    Can I force dialer interface down until some one dials in?
    Sent from Cisco Technical Support iPhone App

    The router is configured as a hub VPN sever for my mobiles users.
    I don't have the option for dynamic routing due to the remote end.
    Primary connection is ip for mobile users. But if they can't use ip for any reason I want them to come in via Isdn.
    The hub needs to route ip unless it sees that the remote has come in via Isdn. I have considered a gre tunnel on the Isdn but that's over heads I'd prefer to avoid.
    Sent from Cisco Technical Support iPhone App

  • Sdlc interface down very often

    Hello,
    In my customer site, SDLC device connect to 2600. IOS version is 12.0.7T. Then access AS400 through DLSW function. We showed log and found the connected interface down very often. show log as below.
    We checked AS400 log and didn't find the SDLC device inactive ever. And we check SDLC device, the device work well, user didn't find any problem??
    We don't know why always log of message showed the interface down.
    Anyone can help me??
    .Jun 23 08:29:56 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:29:57 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:30:01 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:30:02 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    .Jun 23 08:33:06 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:33:07 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:33:11 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:33:12 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    .Jun 23 08:36:16 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:36:17 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:36:21 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:36:22 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    .Jun 23 08:39:25 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:39:26 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:39:30 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:39:31 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    JSB025a#sh inter se 1/0
    Serial1/0 is up, line protocol is up
    Hardware is CD2430 in sync mode
    Description: connect to SNA pu2.1
    MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation SDLC, loopback not set
    Half-duplex enabled.
    cts-delay 0 milliseconds
    dcd-txstart-delay 100 milliseconds
    dcd-drop-delay 100 milliseconds
    transmit-delay 0 milliseconds
    Errors - 0 half duplex violation
    Router link station role: PRIMARY (DCE)
    Router link station metrics:
    slow-poll 10 seconds
    T1 (reply time out) 3000 milliseconds
    N1 (max frame size) 12016 bits
    N2 (retry count) 20
    poll-pause-timer 10 milliseconds
    poll-limit-value 1
    k (windowsize) 7
    modulo 8
    sdlc vmac: 4000.2625.01--
    sdlc addr 01 state is CONNECT (xid-poll)
    cls_state is CLS_IN_SESSION
    VS 5, VR 0, Remote VR 5, Current retransmit count 0
    Hold queue: 0/200 IFRAMEs 116636/58170
    TESTs 0/0 XIDs 40235/14460, DMs 6784/6736 FRMRs 0/0
    RNRs 7/0 SNRMs 9757/0 DISC/RDs 9733/0 REJs 0/0
    Poll: clear, Poll count: 0, ready for poll, chain: 01/01
    Last input 00:00:00, output 00:00:00, output hang never
    Last clearing of "show interface" counters 9w3d
    Queueing strategy: fifo
    Output queue 0/40, 0 drops; input queue 0/75, 0 drops
    5 minute input rate 0 bits/sec, 50 packets/sec
    5 minute output rate 0 bits/sec, 0 packets/sec
    156063821 packets input, 318338246 bytes, 0 no buffer
    Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
    11 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 11 abort
    155708948 packets output, 337016303 bytes, 0 underruns
    0 output errors, 0 collisions, 43092 interface resets
    0 output buffer failures, 0 output buffers swapped out
    106807 carrier transitions
    DCD=up DSR=up DTR=up RTS=down CTS=down

    Hi,
    I believe that your line keeps bouncing due to Data
    Carrier Detect(DCD) going down. I didn't see a copy
    of the interface config but do you have the following
    command under your interface?
    half-duplex controlled-carrier
    This in conjunction with the dcd-txstart-delay and
    dcd-drop-delay settings will cause the DCE to drop
    DCD frequently.
    These are for very specialized environments which
    probably are not what you have.
    What is your environment, with respect to the
    connection to the AS/400? Is it just a Cisco DCE
    cable connected to an AS/400 cable? Or are there
    other cables/switches/modems involved?
    If you just have the Cisco DCE cable connected to
    the AS/400's cable then you do not need that command.
    Otherwise, it is possible you have a cable or
    physical interface problem.
    Please include your interface's config if this
    information wasn't enough to resolve the problem.
    Thanks and regards,
    Ed Mazurek

  • RRI not removing routes even with outside interface down

    Hi,
    I'm having trouble with RRI and static crypto map.
    If I configure the RRI with the outside interface down the ASA doesn't create the static route to the remote subnet.
    If I bring up the interface it creates the route, but if I shutdown the interface the RRI routes never go away meaning the ASA would turn into a  black hole.
    Any suggestion on how to get it to remove the RRI routes if the interface is down?
    I tested it with two versions with the same problem:
    9.2(2)4 
    9.3(1)

    We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash ID's to help us learn more about your crash.
    #Enter about:crashes in the address bar (that's where you enter your website URL) and press Enter. You should now see a list of submitted crash reports.
    #Copy the 5 most recent crash ID's that you see in the crash report window and paste them into your response here.
    Thank you for your cooperation!
    More information and further troubleshooting steps can be found in the [[Firefox crashes]] article.

  • ASA 5505 Vlan1/Inside Interface Down

    I did an initial setup of an ASA 5505 using the setup wizard.
    The inside interface is showing down/down.  It is not shutdown in the running config.
    The ethernet ports say "available but not configured via nameif."
    Anyone have some ideas for me to check?
    ethernet0/0 is working with no problems.

    Thank you for your question.  This community is for Cisco Small Business products and your question is in reference to a Cisco Elite/Classic product.  Please post your question in the Cisco NetPro forums located here: http://forums.cisco.com/eforum/servlet/NetProf?page=main  This forum has subject matter experts on Cisco Elite/Classic products that may be able to answer your question.
    Brian

  • Link outage in Etherchannel causes interface down and failover Secondary Faild

    Hi,
    I have configured port-channel Firewall ASA5515-X and  stacking switch WS-3750X. Also firewall configured as failover mode. Problem is that my active firewall connected switch port show green and working but standby firewall connected switch port shows orange color. When i inpute show failover command on firewall, secondary is faild. Please assist. Here is the below show command.
    mdbl-int-fw-01# sho port-channel 10
    Ports: 2   Maxports = 16
    Port-channels: 1 Max Port-channels = 48
    Protocol: LACP/ active
    Minimum Links: 1
    Maximum Bundle: 8
    Load balance: src-dst-ip
    mdbl-int-fw-01# sho interface port-channel 10
    Interface Port-channel10 "inside", is up, line protocol is up
      Hardware is EtherChannel/LACP, BW 2000 Mbps, DLY 10 usec
            Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
            Input flow control is unsupported, output flow control is off
            Description: *** Connected to CORE-SW ***
            MAC address 4c00.821d.511f, MTU 1500
            IP address 10.98.8.97, subnet mask 255.255.255.248
      Traffic Statistics for "inside":
            56859 packets input, 3419130 bytes
            148709 packets output, 16063580 bytes
            56858 packets dropped
          1 minute input rate 0 pkts/sec,  46 bytes/sec
          1 minute output rate 2 pkts/sec,  216 bytes/sec
          1 minute drop rate, 0 pkts/sec
          5 minute input rate 0 pkts/sec,  46 bytes/sec
          5 minute output rate 2 pkts/sec,  216 bytes/sec
          5 minute drop rate, 0 pkts/sec
      Members in this channel:
          Active:   Gi0/1 Gi0/2
    mdbl-int-fw-01# sho port
    mdbl-int-fw-01# sho port-channel sum
    mdbl-int-fw-01# sho port-channel summary
    Flags:  D - down        P - bundled in port-channel
            I - stand-alone s - suspended
            H - Hot-standby (LACP only)
            U - in use      N - not in use, no aggregation/nameif
            M - not in use, no aggregation due to minimum links not met
            w - waiting to be aggregated
    Number of channel-groups in use: 1
    Group  Port-channel  Protocol    Ports
    ------+-------------+-----------+-----------------------------------------------
    10     Po10(U)           LACP    Gi0/1(P)   Gi0/2(P)  
    mdbl-int-fw-01#
    mdbl-int-fw-01# sho port-channel ?      
      <1-48>    Channel group number
      brief     Brief information
      detail    Detail information
      port      Port information
      protocol  protocol enabled
      summary   One-line summary per channel-group
      |         Output modifiers
      <cr>
    mdbl-int-fw-01# sho port-channel bri
    mdbl-int-fw-01# sho port-channel brief
                    Channel-group listing:
    Group: 10
    Ports: 2   Maxports = 16
    Port-channels: 1 Max Port-channels = 48
    Protocol: LACP/ active
    Minimum Links: 1
    Maximum Bundle: 8
    Load balance: src-dst-ip
    mdbl-int-fw-01# sho port-channel ?    
      <1-48>    Channel group number
      brief     Brief information
      detail    Detail information
      port      Port information
      protocol  protocol enabled
      summary   One-line summary per channel-group
      |         Output modifiers
      <cr>
    mdbl-int-fw-01# sho port-channel pro
    mdbl-int-fw-01# sho port-channel protocol
                    Channel-group listing:
    Group: 10
    Protocol: LACP
    mdbl-int-fw-01# sho port-channel ?       
      <1-48>    Channel group number
      brief     Brief information
      detail    Detail information
      port      Port information
      protocol  protocol enabled
      summary   One-line summary per channel-group
      |         Output modifiers
      <cr>
    mdbl-int-fw-01# sho port-channel det
    mdbl-int-fw-01# sho port-channel detail
                    Channel-group listing:
    Group: 10
    Ports: 2   Maxports = 16
    Port-channels: 1 Max Port-channels = 48
    Protocol: LACP/ active
    Minimum Links: 1
    Maximum Bundle: 8
    Load balance: src-dst-ip
                    Ports in the group:
    Port: Gi0/1
    Port state    = bndl
    Channel group =   10        Mode = LACP/ active
    Port-channel  = Po10
    Flags:  S - Device is sending Slow LACPDUs   F - Device is sending fast LACPDUs.
            A - Device is in active mode.        P - Device is in passive mode.
    Local information:
                                 LACP port     Admin     Oper    Port        Port
    Port      Flags   State      Priority      Key       Key     Number      State
    Gi0/1     SA      bndl       32768         0xa       0xa     0x2         0x3d 
    Partner's information:
              Partner Partner    LACP Partner  Partner   Partner  Partner     Partner
    Port      Flags   State      Port Priority Admin Key Oper Key Port Number Port State
    Gi0/1     SA      bndl       32768         0x0       0xa      0x118       0x3d 
    Port: Gi0/2  
    Port state    = bndl
    Channel group =   10        Mode = LACP/ active
    Port-channel  = Po10
    Flags:  S - Device is sending Slow LACPDUs   F - Device is sending fast LACPDUs.
            A - Device is in active mode.        P - Device is in passive mode.
    Local information:
                                 LACP port     Admin     Oper    Port        Port
    Port      Flags   State      Priority      Key       Key     Number      State
    Gi0/2     SA      bndl       32768         0xa       0xa     0x3         0x3d 
    Partner's information:
              Partner Partner    LACP Partner  Partner   Partner  Partner     Partner
    Port      Flags   State      Port Priority Admin Key Oper Key Port Number Port State
    Gi0/2     SA      bndl       32768         0x0       0xa      0x119       0x3d 
    mdbl-int-fw-01#
    mdbl-int-fw-01#
    mdbl-int-fw-01#
    mdbl-int-fw-01#
    mdbl-int-fw-01# sho port-channel ?     
      <1-48>    Channel group number
      brief     Brief information
      detail    Detail information
      port      Port information
      protocol  protocol enabled
      summary   One-line summary per channel-group
      |         Output modifiers
      <cr>
    mdbl-int-fw-01# sho fail        
    mdbl-int-fw-01# sho failover st
    mdbl-int-fw-01# sho failover state
                   State          Last Failure Reason      Date/Time
    This host  -   Primary
                   Active         None
    Other host -   Secondary
                   Failed         Ifc Failure              22:03:03 UTC Jan 8 2014
                                  outside: No Link
                                  dmz: No Link
                                  mgt: No Link
                                  inside: No Link
    ====Configuration State===
            Sync Done
    ====Communication State===
            Mac set
    mdbl-int-fw-01#
    mdbl-int-fw-01#
    mdbl-int-fw-01#
    mdbl-int-fw-01# sho failover     
    Failover On
    Failover unit Primary
    Failover LAN Interface: failover GigabitEthernet0/3 (up)
    Unit Poll frequency 200 milliseconds, holdtime 800 milliseconds
    Interface Poll frequency 500 milliseconds, holdtime 5 seconds
    Interface Policy 1
    Monitored Interfaces 4 of 114 maximum
    failover replication http
    Version: Ours 8.6(1)2, Mate 8.6(1)2
    Last Failover at: 02:16:48 UTC Jan 8 2014
            This host: Primary - Active
                    Active time: 74479 (sec)
                    slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
                      Interface outside (118.179.139.4): No Link (Waiting)
                      Interface dmz (10.98.56.3): No Link (Waiting)
                      Interface mgt (10.10.11.1): Unknown (Waiting)
                      Interface inside (10.98.8.97): Normal (Waiting)
                    slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
                      IPS, 7.1(4)E4, Up
            Other host: Secondary - Failed
                    Active time: 0 (sec)
                    slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
                      Interface outside (118.179.139.6): No Link (Waiting)
                      Interface dmz (10.98.56.2): No Link (Waiting)
                      Interface mgt (0.0.0.0): No Link (Waiting)
                      Interface inside (10.98.8.98): No Link (Waiting)
                    slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
                      IPS, 7.1(4)E4, Up
    Stateful Failover Logical Update Statistics
            Link : failover GigabitEthernet0/3 (up)
            Stateful Obj    xmit       xerr       rcv        rerr     
            General         12665      0          9929       0        
            sys cmd         9929       0          9929       0        
            up time         0          0          0          0        
            RPC services    0          0          0          0        
            TCP conn        0          0          0          0        
            UDP conn        0          0          0          0        
            ARP tbl         2735       0          0          0        
            Xlate_Timeout   0          0          0          0        
            IPv6 ND tbl     0          0          0          0        
            VPN IKEv1 SA    0          0          0          0        
            VPN IKEv1 P2    0          0          0          0        
            VPN IKEv2 SA    0          0          0          0        
            VPN IKEv2 P2    0          0          0          0        
            VPN CTCP upd    0          0          0          0        
            VPN SDI upd     0          0          0          0        
            VPN DHCP upd    0          0          0          0        
            SIP Session     0          0          0          0        
            Route Session   0          0          0          0        
            User-Identity   1          0          0          0        
            Logical Update Queue Information
                            Cur     Max     Total
            Recv Q:         0       7       9930
            Xmit Q:         0       30      99581
    mdbl-int-fw-01#
    mdbl-int-fw-01#
    mdbl-int-fw-01# sho failover state     
                   State          Last Failure Reason      Date/Time
    This host  -   Primary
                   Active         None
    Other host -   Secondary
                   Failed         Ifc Failure              22:03:03 UTC Jan 8 2014
                                  outside: No Link
                                  dmz: No Link
                                  mgt: No Link
                                  inside: No Link
    ====Configuration State===
            Sync Done
    ====Communication State===
            Mac set
    mdbl-int-fw-01# sho failover ?   
      descriptor  Show failover interface descriptors. Two numbers are shown for
                  each interface. When exchanging information regarding a
                  particular interface, this unit uses the first number in messages
                  it sends to its peer. And it expects the second number in
                  messages it receives from its peer. For trouble shooting, collect
                  the show output from both units and verify that the numbers
                  match.
      exec        Show failover command execution information
      history     Show failover switching history
      interface   Show failover command interface information
      state       Show failover internal state information
      statistics  Show failover command interface statistics information
      |           Output modifiers
      <cr>
    mdbl-int-fw-01# sho failover inter
    mdbl-int-fw-01# sho failover interface
            interface failover GigabitEthernet0/3
                    System IP Address: 10.98.8.89 255.255.255.248
                    My IP Address    : 10.98.8.89
                    Other IP Address : 10.98.8.90
    mdbl-int-fw-01# sho failover stati    
    mdbl-int-fw-01# sho failover statistics
            tx:995725
            rx:980617
    mdbl-int-fw-01# sho failover hi        
    mdbl-int-fw-01# sho failover history
    ==========================================================================
    From State                 To State                   Reason
    ==========================================================================
    02:16:40 UTC Jan 8 2014
    Not Detected               Negotiation                No Error
    02:16:48 UTC Jan 8 2014
    Negotiation                Just Active                No Active unit found
    02:16:48 UTC Jan 8 2014
    Just Active                Active Drain               No Active unit found
    02:16:48 UTC Jan 8 2014
    Active Drain               Active Applying Config     No Active unit found
    02:16:48 UTC Jan 8 2014
    Active Applying Config     Active Config Applied      No Active unit found
    02:16:48 UTC Jan 8 2014
    Active Config Applied      Active                     No Active unit found
    ==========================================================================
    mdbl-int-fw-01# sho failover        
    Failover On
    Failover unit Primary
    Failover LAN Interface: failover GigabitEthernet0/3 (up)
    Unit Poll frequency 200 milliseconds, holdtime 800 milliseconds
    Interface Poll frequency 500 milliseconds, holdtime 5 seconds
    Interface Policy 1
    Monitored Interfaces 4 of 114 maximum
    failover replication http
    Version: Ours 8.6(1)2, Mate 8.6(1)2
    Last Failover at: 02:16:48 UTC Jan 8 2014
            This host: Primary - Active
                    Active time: 74554 (sec)
                    slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
                      Interface outside (118.179.139.4): No Link (Waiting)
                      Interface dmz (10.98.56.3): No Link (Waiting)
                      Interface mgt (10.10.11.1): Unknown (Waiting)
                      Interface inside (10.98.8.97): Normal (Waiting)
                    slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
                      IPS, 7.1(4)E4, Up
            Other host: Secondary - Failed
                    Active time: 0 (sec)
                    slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
                      Interface outside (118.179.139.6): No Link (Waiting)
                      Interface dmz (10.98.56.2): No Link (Waiting)
                      Interface mgt (0.0.0.0): No Link (Waiting)
                      Interface inside (10.98.8.98): No Link (Waiting)
                    slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
                      IPS, 7.1(4)E4, Up
    Stateful Failover Logical Update Statistics
            Link : failover GigabitEthernet0/3 (up)
            Stateful Obj    xmit       xerr       rcv        rerr     
            General         12676      0          9938       0        
            sys cmd         9938       0          9938       0        
            up time         0          0          0          0        
            RPC services    0          0          0          0        
            TCP conn        0          0          0          0        
            UDP conn        0          0          0          0        
            ARP tbl         2737       0          0          0        
            Xlate_Timeout   0          0          0          0        
            IPv6 ND tbl     0          0          0          0        
            VPN IKEv1 SA    0          0          0          0        
            VPN IKEv1 P2    0          0          0          0        
            VPN IKEv2 SA    0          0          0          0        
            VPN IKEv2 P2    0          0          0          0        
            VPN CTCP upd    0          0          0          0        
            VPN SDI upd     0          0          0          0        
            VPN DHCP upd    0          0          0          0        
            SIP Session     0          0          0          0        
            Route Session   0          0          0          0        
            User-Identity   1          0          0          0        
            Logical Update Queue Information
                            Cur     Max     Total
            Recv Q:         0       7       9940
            Xmit Q:         0       30      99677

    Hi Ganesan,
    I am proposing a design like this. You can have the STP in pvst mode and have a different priority set for the core switch to make it core a as root bridge. There is nothing wrong with your design you have made you core switch which will be physically down to your firewall... but in real it comes on the top of your firewall as well... But spanning tree conf should be done properly to achieve this... I have proposed my design which is pretty simple but easy for troubleshoot....
    You can have your firewalls connected to core switch on the down and can directly connected to router on outside... always core a -->py fw--rtra will be the primary path... if anything goes wrong then secondary line will come in to picture....
    make sure that your hsrp will have high priority to ur core a vlan conf for the access switches.....
    Please do rate for the helpful posts.
    By
    Karthik

  • Ethernet OAM CFM to take interface down

    Hi,
    I'd like to use CFM to take a link down when the remote side is not responding any more as the link is disrupted.
    Platform is CRS-1 w. IOS-XR 4.1:
    Here my configuration:
    ethernet cfm
    domain md0 level 4 id string crs_196_P2
      service ma0 down-meps
       continuity-check interval 100ms loss-threshold 3
       efd
    interface TenGigE0/2/0/2
    description ->t1600_195_P3, xe-1/0/2
    mtu 4474
    service-policy output VF-QOS
    ipv4 address 172.20.23.1 255.255.255.252
    load-interval 30
    ethernet cfm
      mep domain md0 service isis-eoam mep-id 1
    I get an error message that there is an MAID mismatch and the link is being taken down:
    sh eth cfm lo meps
    Defects (from at least one peer MEP):
    A - AIS received                I - Wrong interval
    R - Remote Defect received      V - Wrong level
    L - Loop (our MAC received)     T - Timed out
    C - Config (our ID received)    M - Missing (cross-check)
    X - Cross-connect (wrong MAID)  U - Unexpected (cross-check)
    P - Peer port down
    Domain md0 (level 4), Service ma0
       ID Interface (State)        Dir MEPs/Err RD Defects AIS
        1 Te0/2/0/2 (Down)         Dn     1/1   Y  X
    When I do a debug ethernet cfm packets I see the following messages that do not indicate an error to me:
    LC/0/2/CPU0:Jul  7 23:55:26.424 : cfmd[138]: PKT-RX: IFH TenGigE0/2/0/2 ingress: CCM packet received at level 4 for domain md0, service ma0: length 75, source MAC 28c0.da4e.9900, destination MAC 0180.c200.0034: Packet processed successfully
    LC/0/2/CPU0:Jul  7 23:55:26.480 : cfmd[138]: PKT-TX: IFH TenGigE0/2/0/2 egress: CCM packet sent at level 4 for domain md0, service ma0: length 98, source MAC 0007.0e50.95c5, destination MAC 0180.c200.0034
    LC/0/2/CPU0:Jul  7 23:55:26.524 : cfmd[138]: PKT-RX: IFH TenGigE0/2/0/2 ingress: CCM packet received at level 4 for domain md0, service ma0: length 75, source MAC 28c0.da4e.9900, destination MAC 0180.c200.0034: Packet processed successfully
    From the documentation I see that the MAID is made up of the MDID and the SMAN, but from the debug above they do seem to match.
    Any ideas on what I am missing here?
    TIA

    Wrong Section, You should be asking it in IOS-XR section.

  • Oracle 10g RAC - public network interface down

    Hi all,
    I have a question about Oracle RAC and network interface.
    We're using Oracle 10gR2 RAC with two nodes on Linux Red Hat.
    Let's assume that the public network interface goes down.
    I would like to know what happens with existing connections
    on node with network interface with problems.
    Are connections frozen, actives?
    Can the users continue to use theses existing connections using the another node of RAC?
    I know that the listener goes down and any other connections is allowed.
    Thank you very much!!!!

    Tads wrote:
    Hi all,
    I have a question about Oracle RAC and network interface.
    We're using Oracle 10gR2 RAC with two nodes on Linux Red Hat.
    Let's assume that the public network interface goes down.
    I would like to know what happens with existing connections
    on node with network interface with problems.
    Are connections frozen, actives?
    Can the users continue to use theses existing connections using the another node of RAC?If the interface is down? what do you think? All connections to this node will die. How does your application handle fail-over, does it attempt to reconnect or just have a complete application failure?
    You should spend some time in a test lab where you can test this stuff for yourself. Read the documentation and there are tons of sites out there that purport to have all of your RAC/TAF/FAN/FAF questions. - I would read and trust the documentation first.
    >
    I know that the listener goes down and any other connections is allowed.
    Thank you very much!!!!

  • Static MAC stay if interface down

    Hello,
    Due to business circonstance I need a static mac in my switch.
    However, if the interface releated to this static mac is down the mac entry remain and cause all traffic to be dropped.
    I would, this mac address to be learned only if a specific interface is down. otherwise my static entry should direct of this mac to this specific interface.
    I need a static mac, but this also break redundancy if this specific interface is down :(

    Hi,
    I am not sure whether this answers your specific requirement or not, but have you tried adding the 'auto-learn' option to the static mac-address entry - this seems to cause the switch to ignore the static mac address if the same mac address is learnt on another interface. Is that what you want or do you simply want the static mac address to have precedence over dynamically learnt mac addresses unless the line protocol of the static mac address interface goes down.
    Very best wishess
    Mike

  • Lms 4.2 interface down alert

    Hi
    I receive email when an interface comes down but because i have a lot of routers with a lot of interfaces i can' tell which one came down , is there any way to include the description under the interface in the email ?
    Also can i monitor the existence/not of specific route in the routing table and receive email ?
    I appreciate any reply
    Sent from Cisco Technical Support iPhone App

    yes ,i receive the same alert but the case i have like 60 routers and lots of interfaces on every router so interfacse s0/0/0.1 is meaningless for me so i need the alert includes the description configured under the interfaces via CLI
    Thanks for your reply
    Sent from Cisco Technical Support iPhone App

  • Mgmt 0 Interface Down - HA not ready

    Setting up a new set of 6248 FIs running 2.1(a) – HA never becomes ready – After some investigation within NXOS mgmt 0 reports as down “link not connected”, even though I am connected on that interface to both FIs and the cluster IP - I have changed cabled and switch etc. I did also turn off interface monitoring thinking it could be this, however I still have the issue.
    Any ideas?

    Hi Nael,
    Can you check and confirm if the L1 and L2 cables are connected between 2 FI's?
    Since you are able to connect to both the FI's using the management IP's, that should be fine.
    Also, missed to mention what Robert mentioned. You need to have chassis connected and server links activated for the full HA to be ready.
    -Ganesh

Maybe you are looking for