Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
6026
Views
0
Helpful
2
Replies

ESX Host to Nexus 5000 VPC

darkid123
Level 1
Level 1

‎08-23-2010 05:28 PM

Hi,

Can anyone tell me if it's possible to create a VPC directly from a Nexus 5000 to an ESX Host? My host is running 2 Qlogic 8152 CNAs, and i've got them connecting to 2 Nexus 5000 switches. My problem is, when I create the VPC and I bind the VFC to the newly created port channel, everything but the VFC comes up.

See output below:

sh int brie

-------------------------------------------------------------------------------
Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                  Mode   Trunk                          Mode  Speed  Channel
                         Mode                                 (Gbps)
-------------------------------------------------------------------------------
fc2/1      500    auto   auto    trunking         swl    TE      4    --
fc2/2      4094   auto   auto    sfpAbsent        --     --           --
fc2/3      1      auto   on      sfpAbsent        --     --           --
fc2/4      1      auto   on      sfpAbsent        --     --           --

--------------------------------------------------------------------------------
Ethernet      VLAN   Type Mode   Status  Reason                   Speed     Port
Interface                                                                   Ch #
--------------------------------------------------------------------------------
Eth1/1        1      eth  trunk  up      none                        10G(D) 11
Eth1/2        1      eth  trunk  up      none                        10G(D) --
Eth1/3        161    eth  access down    SFP not inserted            10G(D) --
Eth1/4        161    eth  access down    SFP not inserted            10G(D) --
Eth1/5        161    eth  access down    SFP not inserted            10G(D) --
Eth1/6        161    eth  access down    SFP not inserted            10G(D) --
Eth1/7        161    eth  access down    SFP not inserted            10G(D) --
Eth1/8        161    eth  access down    SFP not inserted            10G(D) --
Eth1/9        161    eth  access down    SFP not inserted            10G(D) --
Eth1/10       161    eth  access down    SFP not inserted            10G(D) --
Eth1/11       161    eth  access down    SFP not inserted            10G(D) --
Eth1/12       161    eth  access down    SFP not inserted            10G(D) --
Eth1/13       1      eth  trunk  up      none                        10G(D) --
Eth1/14       1      eth  trunk  up      none                        10G(D) --
Eth1/15       1      eth  trunk  down    SFP not inserted            10G(D) --
Eth1/16       1      eth  trunk  down    SFP not inserted            10G(D) --
Eth1/17       161    eth  access down    SFP not inserted            10G(D) --
Eth1/18       161    eth  access down    SFP not inserted            10G(D) --
Eth1/19       1      eth  trunk  up      none                        10G(D) 100
Eth1/20       1      eth  trunk  up      none                        10G(D) 100
Eth2/1        1      eth  trunk  down    Administratively down       10G(D) --
Eth2/2        1      eth  access down    SFP not inserted            10G(D) --
Eth2/3        1      eth  trunk  up      none                        10G(D) 10
Eth2/4        1      eth  access down    SFP not inserted            10G(D) --

--------------------------------------------------------------------------------
Port-channel VLAN  Type Mode   Status  Reason                    Speed  Protocol
Interface
--------------------------------------------------------------------------------
Po10         1     eth  trunk  up      none                       a-10G(D)  none
Po11         1     eth  trunk  up      none                       a-10G(D)  none
Po100        1     eth  trunk  up      none                       a-10G(D)  none

--------------------------------------------------------------------------------
Port   VRF          Status IP Address                              Speed    MTU
--------------------------------------------------------------------------------
mgmt0  --           up     X.X.X.X                          1000     1500

-------------------------------------------------------------------------------
Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                  Mode   Trunk                          Mode  Speed  Channel
                         Mode                                 (Gbps)
-------------------------------------------------------------------------------
vfc1       500    F      on      down             --     --           --

Only pay attention to VFC 1 in this output. This is the VFC that I have binded to Po11, which relates to physical port e1/1.

The output is the same on both switches.

I was told that if you have 4 ports going out to 1 ESX Host (2 to each switch), I would need to create 2 VPCs with 1 port from each switch. This is what I am trying to do, but the first VPC I'm trying to create is failing.

Any ideas?

Thanks.

Labels:
0 Helpful
2 Replies 2

darkid123
Level 1
Level 1

‎08-24-2010 05:21 PM

Since posting this i've realized that it's Spanning tree that is causing the issue on switch 2.

I created a vpc between my 2 nexus 5000s. Then...
On switch 1 my fcoe vlan is 500 (matching vsan 500). All ports are forwarding in STP because this bridge is the root for vlan 500.
On switch 2 my fcoe vlan is 501 (matching vsan 501). Even though this bridge is root for vlan 501, the port-channel going to my host is in
blocking mode. This is very weird behaviour considering a root bridge shouldn't be blocking any ports...

Here's the output from switch 2.

VLAN0501
  Spanning tree enabled protocol rstp
  Root ID    Priority    33269
             Address     0005.9b73.523c
             This bridge is the root
             Hello Time  2  sec  Max Age 20 sec  Forward Delay 15 sec

  Bridge ID  Priority    33269  (priority 32768 sys-id-ext 501)
             Address     0005.9b73.523c
             Hello Time  2  sec  Max Age 20 sec  Forward Delay 15 sec

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- --------
--------------------------------
Po11             Desg BLK 1         128.4106 (vPC) P2p
Eth1/13          Desg FWD 2         128.141  Edge P2p
Eth1/14          Desg FWD 2         128.142  Edge P2p

On switch 1, all the ports are forwarding, which is why the VFC comes up on that switch. But on switch 2, because Po11 is blocked, the VFC bound to it never comes up.

Anybody have any idea why this port would get blocked?

0 Helpful

Prashanth Krishnappa
Cisco Employee
Cisco Employee
In response to darkid123

‎09-10-2010 05:03 AM

I see STP thinks STP state is P2P. It should be edge P2P. I am suspecting you do not have "spanning-tree port type edge trunk" configured on the interface port-channel 11. I have seen this issue and recently filed a new defect since I believe STP state should not be blocking for missing this configuration or misconfiguring the trunk interface.

http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCti79446

0 Helpful
Customers Also Viewed These Support Documents