cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
19453
Views
15
Helpful
12
Replies

Adaptor host interface 1/2/1/1 link state down

bosv00001
Level 1
Level 1

Dear All,

can any one help m I have an error  "Adaptor host interface 1/2/1/1 link state down" and none of my nics will come up state "up" F0207 error. I am running 2.2(6f) and the chassis policy as port channel, set the server ports as two for each FI and they are up and working.

Any ideas ?

thanks

2 Accepted Solutions

Accepted Solutions

Actually it is not 4094, we have another VSAN defined in the N5K, and for trouble shooting purpose it is changed to default and forgot to change it back. we have this problem earlier when it was using the same VSAN which is defined in the N5K.

below is the output while it was assigned to the VSAN which is defined in N5K(1100)

show int vfc 709
vfc709 is trunking (Not all VSANs UP on the trunk)
    Bound interface is port-channel80
    Hardware is Ethernet
    Port WWN is 22:c4:8c:60:4f:d2:01:ff
    Admin port mode is NP, trunk mode is on
    snmp link state traps are enabled
    Port mode is TNP
    Port vsan is 1
    Trunk vsans (admin allowed and active) (1,1100)
    Trunk vsans (up)                       (1100)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (1)

You were right about installation.

View solution in original post

If you have non-participating alerts, then those are expected if the OS is not installed, or booted.

Thanks,

Kirk...

View solution in original post

12 Replies 12

Kirk J
Cisco Employee
Cisco Employee

Greetings.

As you have mentioned that you don't have any connectivity alerts for the IOM/chassis link discovery, there are a few things you can try:

  • Decom and reack the Blade (this should rebuild/renegotiate the adapter/iom links)
  • Physical reseat of the Blade

Are all your other blades in this chassis working normally?

Some additional things to try:

Re-ack IOM 1 (this will disrupt connectivity on the A side for this chassis for a few seconds)

Reboot IOM 1 (this will disrupt connectivity on the A side for this chassis for 5-10 min)

The adapter, IOM logs will probably give us some more specific details, but you'll probably need to open a TAC case to get the logs reviewed.

Hopefully some of the suggestions resolve your issue.

Thanks,

Kirk...

Hello Kirk

I am facing exact same issue.

I have two unified up-links to N5Ks port channeled. Created couple of NICs and two HBAs for SAN connectivity. After service profiled assigned, couldn't able to see server WWN numbers in N5K to proceed further with zoning. We have vSAN common in both N5K switches. I have tried to rediscover chassis, server and even IOM modules. please find the vNICs and vHBA state below.  

UCS-A# sh service-profile circuit server 1/1
Service Profile: ESXi01
Server: 1/1
    Fabric ID: A
        Path ID: 1
        VIF        vNIC            Link State  Oper State Prot State    Prot Role   Admin Pin  Oper Pin   Transport
        ---------- --------------- ----------- ---------- ------------- ----------- ---------- ---------- ---------
               804 vNIC0           Error       Error      No Protection Unprotected 0/0        0/0        Ether
               806 vHBA0           Error       Error      No Protection Unprotected 0/0        0/0        Fc
              8998                 Unknown     Unknown    No Protection Unprotected 0/0        0/0        Ether
    Fabric ID: B
        Path ID: 1
        VIF        vNIC            Link State  Oper State Prot State    Prot Role   Admin Pin  Oper Pin   Transport
        ---------- --------------- ----------- ---------- ------------- ----------- ---------- ---------- ---------
               805 vNIC1           Unknown     Unknown    No Protection Unprotected 0/0        0/0        Ether
               807 vHBA1           Error       Error      No Protection Unprotected 0/0        0/0        Fc
              8999                 Unknown     Unknown    No Protection Unprotected 0/0        0/0        Ether

Your help is much appreciated.

You aren't getting any enm pinning errors/faults are you?

From your appropriate FI side (A/B) #connect nxos

#show int veth804 (on A side)

#show int veth805 (on B side)

#show vlan brief (on both sides)

#show npv status

#show run int vfc806

#show run int vfc807

For vhba issues, can you confirm your vsan you have assigned to the vhba, is allowed/assigned to an FC uplink port on each FI?

Also, it sounds like you are using upstream FC switches to provide zoning, in which case you will want to confirm your FI FC switching mode is in 'end host mode' (which is the default).

Thanks,

Kirk...

Please find the output below. 

UCS-A(nxos)# show int veth804
Vethernet804 is down (nonParticipating)
    Bound Interface is --
    Port description is server 1/1, VNIC vNIC0
    Hardware is Virtual, address is 8c60.4fd2.01a0
    Port mode is trunk
    Speed is auto-speed
    Duplex mode is auto
  300 seconds input rate 0 bits/sec, 0 packets/sec
  300 seconds output rate 0 bits/sec, 0 packets/sec
  Rx
    0 unicast packets  0 multicast packets  0 broadcast packets
    0 input packets  0 bytes
    0 input packet drops
  Tx
    0 unicast packets  8 multicast packets  25 broadcast packets
    33 output packets  2172 bytes
    0 flood packets
    0 output packet drops

UCS-A(nxos)# show vlan brief

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Po80, Eth1/3, Eth1/4, Eth1/5
                                                Eth1/6, Eth1/7, Eth1/8, Eth1/9
                                                Eth1/10, Eth1/11, Eth1/12
                                                Eth1/13, Eth1/14, Eth1/15
                                                Eth1/16, Eth1/17, Eth1/18
                                                Eth1/19, Eth1/20, Eth1/21
                                                Eth1/22, Eth1/23, Eth1/24
                                                Eth1/25, Eth1/26, Eth1/27
                                                Eth1/28, Eth1/29, Eth1/30
                                                Eth1/31, Eth1/32, Eth1/1/2
                                                Eth1/1/4, Eth1/1/6, Eth1/1/8
                                                Eth1/1/10, Eth1/1/12, Eth1/1/14
                                                Eth1/1/16, Eth1/1/17, Eth1/1/18
                                                Eth1/1/19, Eth1/1/20, Eth1/1/21
                                                Eth1/1/22, Eth1/1/23, Eth1/1/24
                                                Eth1/1/25, Eth1/1/26, Eth1/1/27
                                                Eth1/1/28, Eth1/1/29, Eth1/1/30
                                                Eth1/1/31, Eth1/1/32

2000 fcoe-vsan-2000                   active    Po80, Eth1/17, Eth1/18
                                                Veth8956, Veth8968, Veth8998
4044 SAM-vlan-management              active    Eth1/1/33
4047 SAM-vlan-boot                    active    
4048 fcoe-vsan-4048                   active    Po80, Eth1/17, Eth1/18

UCS-A(nxos)# show npv status

npiv is enabled

disruptive load balancing is disabled

External Interfaces:
====================
  Interface: vfc798, State: Trunking
        VSAN:    1, State: Waiting For VSAN Up
        VSAN: 2000, State: Up, FCID: 0xa504c1

  Number of External Interfaces: 1

Server Interfaces:
==================
  Interface: vfc764, VSAN: 4094, State: Down
  Interface: vfc776, VSAN: 4094, State: Down
  Interface: vfc806, VSAN: 4094, State: Down

  Number of Server Interfaces: 3

UCS-A(nxos)# show run int vfc806

!Command: show running-config interface vfc806
!Time: Sun Apr  3 05:33:57 2016

version 5.2(3)N2(2.26e)

interface vfc806
  bind interface Vethernet8998
  switchport trunk allowed vsan 2000
  switchport description server 1/1, VHBA vHBA0
  switchport trunk mode on
  no shutdown

UCS-A(nxos)# connect nx b
                        ^
% Invalid command at '^' marker.
UCS-A(nxos)# exit
UCS-A# con nx b
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2015, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
UCS-B(nxos)# show int veth805
Vethernet805 is down (nonParticipating)
    Bound Interface is --
    Port description is server 1/1, VNIC vNIC1
    Hardware is Virtual, address is 8c60.4fd2.5b40
    Port mode is trunk
    Speed is auto-speed
    Duplex mode is auto
  300 seconds input rate 0 bits/sec, 0 packets/sec
  300 seconds output rate 0 bits/sec, 0 packets/sec
  Rx
    0 unicast packets  0 multicast packets  0 broadcast packets
    0 input packets  0 bytes
    0 input packet drops
  Tx
    0 unicast packets  0 multicast packets  0 broadcast packets
    0 output packets  0 bytes
    0 flood packets
    0 output packet drops

UCS-B(nxos)# show vlan brief

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Po8, Eth1/3, Eth1/4, Eth1/5
                                                Eth1/6, Eth1/7, Eth1/8, Eth1/9
                                                Eth1/10, Eth1/11, Eth1/12
                                                Eth1/13, Eth1/14, Eth1/15
                                                Eth1/16, Eth1/17, Eth1/18
                                                Eth1/19, Eth1/20, Eth1/21
                                                Eth1/22, Eth1/23, Eth1/24
                                                Eth1/25, Eth1/26, Eth1/27
                                                Eth1/28, Eth1/29, Eth1/30
                                                Eth1/31, Eth1/32, Eth1/1/2
                                                Eth1/1/4, Eth1/1/6, Eth1/1/8
                                                Eth1/1/10, Eth1/1/12, Eth1/1/14
                                                Eth1/1/16, Eth1/1/17, Eth1/1/18
                                                Eth1/1/19, Eth1/1/20, Eth1/1/21
                                                Eth1/1/22, Eth1/1/23, Eth1/1/24
                                                Eth1/1/25, Eth1/1/26, Eth1/1/27
                                                Eth1/1/28, Eth1/1/29, Eth1/1/30
                                                Eth1/1/31, Eth1/1/32

2000 fcoe-vsan-2000                   active    Po80, Eth1/17, Eth1/18
                                                Veth8957, Veth8969, Veth8999
4044 SAM-vlan-management              active    Eth1/1/33
4047 SAM-vlan-boot                    active    
4048 fcoe-vsan-4048                   active    Po80, Eth1/17, Eth1/18

UCS-B(nxos)# show npv status

npiv is enabled

disruptive load balancing is disabled

External Interfaces:
====================
  Interface: vfc799, State: Trunking
        VSAN:    1, State: Waiting For VSAN Up
        VSAN: 2000, State: Up, FCID: 0xdf04c2

  Number of External Interfaces: 1

Server Interfaces:
==================
  Interface: vfc765, VSAN: 4094, State: Down
  Interface: vfc777, VSAN: 4094, State: Down
  Interface: vfc807, VSAN: 4094, State: Down

  Number of Server Interfaces: 3

UCS-B(nxos)# show run int vfc807

!Command: show running-config interface vfc807
!Time: Sun Apr  3 05:35:36 2016

version 5.2(3)N2(2.26e)

interface vfc807
  bind interface Vethernet8999
  switchport trunk allowed vsan 2000
  switchport description server 1/1, VHBA vHBA1
  switchport trunk mode on
  no shutdown

we are having pinning errors for VIF paths.

Regarding the vHBA issue, i was not able to find the option to assign vSAN to the uplink ports on the FI. Seems that option is not available on GUI. These uplink ports are port channeled.

FIs are in 'end host mode' but not able to see the wwn numbers of the server in N5K.

Server Interfaces:
==================
  Interface: vfc764, VSAN: 4094, State: Down
  Interface: vfc776, VSAN: 4094, State: Down
  Interface: vfc806, VSAN: 4094, State: Down

is VSAN 4094 defined on N5k ?

It seems that you did a fresh install of Cisco UCS, Release 2.0—The FCoE VLAN for the default VSAN uses VLAN 4048 by default. The FCoE storage port native VLAN uses VLAN 4049.

Actually it is not 4094, we have another VSAN defined in the N5K, and for trouble shooting purpose it is changed to default and forgot to change it back. we have this problem earlier when it was using the same VSAN which is defined in the N5K.

below is the output while it was assigned to the VSAN which is defined in N5K(1100)

show int vfc 709
vfc709 is trunking (Not all VSANs UP on the trunk)
    Bound interface is port-channel80
    Hardware is Ethernet
    Port WWN is 22:c4:8c:60:4f:d2:01:ff
    Admin port mode is NP, trunk mode is on
    snmp link state traps are enabled
    Port mode is TNP
    Port vsan is 1
    Trunk vsans (admin allowed and active) (1,1100)
    Trunk vsans (up)                       (1100)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (1)

You were right about installation.

I think one problem is: 

Your port is in VSAN 1, and VSAN 1 in the trunk is not up, but initializing; Please put the peer port on the N5k also in VSAN 1, or 

Best practise: don't use VSAN 1 (and VLAN 1) for any operational ports.

Could you please tell me how to change that VSAN1, we are not able to change that.

Do you have different VSAN on fabric A resp. B, different from 1 ?

Do you have Trunking enabled on UCS (I assume you have EHM for Ethernet and FC) ?

Is f-port-trunking-channel enabled on N5k ?

bosv00001
Level 1
Level 1

Thanks Kirk

I did all of the actions you suggested before I posted the request. Anyway to cut a long story short, this was an old chassis and I had to upgrade the firmware. I normally deploy a service profile and then a OS. But since this was an upgrade I deployed just the service profile and then looked at the uplinks to make sure all was working, i now know that uplink ports only appear when you have an OS installed, i installed an OS and now they are up and working - cheers bosv

If you have non-participating alerts, then those are expected if the OS is not installed, or booted.

Thanks,

Kirk...

nice one

Review Cisco Networking for a $25 gift card

Review Cisco Networking for a $25 gift card