本文档介绍如何在Nexus 5500交换机上配置、运行适配器交换矩阵扩展器(FEX)功能并排除故障。
本文档没有任何特定的要求。
本文档中的信息基于以下软件和硬件版本:
本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始(默认)配置。如果您的网络处于活动状态,请确保您了解任何命令或数据包捕获设置的潜在影响。
此功能允许Nexus 5500交换机在服务器的VIC上管理虚拟接口(以太网虚拟网络接口控制器(vNIC)和光纤通道虚拟主机总线适配器(FC vHBA))。这独立于服务器上运行的任何虚拟机监控程序。创建的任何虚拟接口都对服务器上安装的主操作系统(OS)可见(前提是操作系统具有相应的驱动程序)。
支持的平台可在Cisco Nexus 5000系列NX-OS适配器FEX操作指南5.1(3)N1(1)版中找到。
适用于适配器 — FEX的支持拓扑可在Cisco Nexus 5000系列NX-OS适配器FEX操作指南5.1(3)N1(1)版中的此部分找到。
支持的拓扑包括:
后续配置部分讨论“通过主用/备用上行链路到一对Nexus 5500交换机的服务器双宿主”,如下所示:
每个vNIC在Nexus 5000上都有相应的虚拟以太网接口。同样,每个vHBA在Nexus 5000上都将有相应的虚拟光纤通道(VFC)接口。
在两台Nexus 5000交换机上完成以下步骤:
(config)# install feature-set virtualization
(config)# feature-set virtualization
(config)# vethernet auto-create
(config)# interface Eth 1/10
(config-if)# switchport mode vntag
(config-if)# no shutdown
端口配置文件是交换机接口可应用(继承)的配置模板。在适配器 — FEX的环境中,端口配置文件可以应用于手动定义的虚拟以太网接口,也可以应用于在UCS C系列思科集成管理控制器(CIMC)GUI接口上配置vNIC时自动创建的虚拟以太网接口。
port-profile的类型为“vethernet”。
端口配置文件配置示例如下所示:(config)# port-profile type vethernet VNIC1
(config-port-prof)# switchport mode access
(config-port-prof)# switchport access vlan 10
(config-port-prof)# no shutdown
(config-port-prof)# state enabled
在UCS C系列服务器上完成以下步骤:
在服务器适配器上创建vHBA时,不会自动创建相应的交换机接口。相反,应手动定义它们。交换机和服务器端的步骤如下所示。
在交换机端完成以下步骤:
示例:
(config)# interface veth 10
(config-if)# switchport mode trunk
(config-if)# switchport trunk allowed vlan 1,100
(config-if)# bind interface eth1/1 channel 3
(config-if)# no shutdown
示例:
(config)# interface vfc10
(config-if)# bind interface veth 10
(config-if)# no shut
此接口的虚拟存储区域网络(VSAN)成员资格在VSAN数据库下定义:
(config)# vsan database
(config-vsan-db)# vsan 100 interface vfc10
(config-vsan-db)# vlan 100
(config-vlan)# fcoe vsan 100
(config-vlan)# show vlan fcoe
在服务器端完成以下步骤:
要定义的主要字段包括:
使用本部分可确认配置能否正常运行。
可使用以下命令显示虚拟以太网接口列表:
n5k1# show interface virtual summary
Veth Bound Channel/ Port Mac VM
Interface Interface DV-Port Profile Address Name
-------------------------------------------------------------------------
Veth32770 Eth1/2 1 UPLINK
Total 1 Veth Interfaces
n5k1#
n5k1# show interface virtual status
Interface VIF-index Bound If Chan Vlan Status Mode Vntag
-------------------------------------------------------------------------
Veth32770 VIF-17 Eth1/2 1 10 Up Active 2
Total 1 Veth Interfaces
自动创建的虚拟以太网接口会显示在运行配置中,并在执行复制运行启动时保存到启动配置:
n5k1# show run int ve32770
!Command: show running-config interface Vethernet32770
!Time: Thu Apr 10 12:56:23 2014
version 5.2(1)N1(4)
interface Vethernet32770
inherit port-profile UPLINK
bind interface Ethernet1/2 channel 1
n5k1# show int ve32770 brief
--------------------------------------------------------------------------------
Vethernet VLAN Type Mode Status Reason Speed
--------------------------------------------------------------------------------
Veth32770 10 virt access up none auto
n5k1#
本部分提供的信息可用于对配置进行故障排除。
使用以下命令验证交换机VNTag接口的数据中心桥接功能交换协议(DCBX)信息:
# show system internal dcbx info interface ethernet <>
检验:
如下所示:
n5k1# show sys int dcbx info interface e1/2
Interface info for if_index: 0x1a001000(Eth1/2)
tx_enabled: TRUE
rx_enabled: TRUE
dcbx_enabled: TRUE
DCX Protocol: CEE <<<<<<<
DCX CEE NIV extension: enabled <<<<<<<<<
<output omitted>
Feature type NIV (7) <<<<<<<
feature type 7(DCX CEE-NIV)sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 1
feature_seq_no 0 remote_feature_tlv_present 1 remote_tlv_aged_out 0
remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
disruptive_error 0 mts_addr_node 0x2201 mts_addr_sap 0x193
Other server mts_addr_node 0x2301, mts_addr_sap 0x193
Desired config cfg length: 8 data bytes:9f ff 68 ef bd f7 4f c6
Operating config cfg length: 8 data bytes:9f ff 68 ef bd f7 4f c6
Peer config cfg length: 8 data bytes:10 00 00 22 bd d6 66 f8
常见问题包括:
n5k1# show sys int vim event-history interface e1/2
>>>>FSM: <Ethernet1/2> has 18 logged transitions<<<<<
1) FSM:<Ethernet1/2> Transition at 327178 usecs after Thu Apr 10 12:22:27 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_DCBX]
Triggered event: [VIM_NIV_PHY_FSM_EV_PHY_DOWN]
Next state: [VIM_NIV_PHY_FSM_ST_WAIT_DCBX]
2) FSM:<Ethernet1/2> Transition at 327331 usecs after Thu Apr 10 12:22:27 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_DCBX]
Triggered event: [VIM_NIV_PHY_FSM_EV_DOWN_DONE]
Next state: [VIM_NIV_PHY_FSM_ST_WAIT_DCBX]
3) FSM:<Ethernet1/2> Transition at 255216 usecs after Thu Apr 10 12:26:15 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_DCBX]
Triggered event: [VIM_NIV_PHY_FSM_EV_RX_DCBX_CC_NUM]
Next state: [VIM_NIV_PHY_FSM_ST_WAIT_3SEC]
4) FSM:<Ethernet1/2> Transition at 250133 usecs after Thu Apr 10 12:26:18 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_3SEC]
Triggered event: [VIM_NIV_PHY_FSM_EV_DCX_3SEC_EXP]
Next state: [VIM_NIV_PHY_FSM_ST_WAIT_ENCAP]
5) FSM:<Ethernet1/2> Transition at 262008 usecs after Thu Apr 10 12:26:18 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_ENCAP]
Triggered event: [VIM_NIV_PHY_FSM_EV_VIC_OPEN_RECEIVED]
Next state: [FSM_ST_NO_CHANGE]
6) FSM:<Ethernet1/2> Transition at 60944 usecs after Thu Apr 10 12:26:19 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_ENCAP]
Triggered event: [VIM_NIV_PHY_FSM_EV_ENCAP_RESP]
Next state: [VIM_NIV_PHY_FSM_ST_UP]
7) FSM:<Ethernet1/2> Transition at 62553 usecs after Thu Apr 10 12:26:19 2014
Previous state: [VIM_NIV_PHY_FSM_ST_UP]
Triggered event: [VIM_NIV_PHY_FSM_EV_VIC_OPEN_ACKD]
Next state: [FSM_ST_NO_CHANGE]
8) FSM:<Ethernet1/2> Transition at 62605 usecs after Thu Apr 10 12:26:19 2014
Previous state: [VIM_NIV_PHY_FSM_ST_UP]
Triggered event: [VIM_NIV_PHY_FSM_EV_VIC_OPEN_DONE]
Next state: [VIM_NIV_PHY_FSM_ST_UP_OPENED]
9) FSM:<Ethernet1/2> Transition at 62726 usecs after Thu Apr 10 12:26:19 2014
Previous state: [VIM_NIV_PHY_FSM_ST_UP_OPENED]
Triggered event: [VIM_NIV_PHY_FSM_EV_PP_SEND]
Next state: [VIM_NIV_PHY_FSM_ST_UP_OPENED_PP]
10) FSM:<Ethernet1/2> Transition at 475253 usecs after Thu Apr 10 12:51:45 2014
Previous state: [VIM_NIV_PHY_FSM_ST_UP_OPENED_PP]
Triggered event: [VIM_NIV_PHY_FSM_EV_PHY_DOWN]
Next state: [VIM_NIV_PHY_FSM_ST_WAIT_VETH_DN]
11) FSM:<Ethernet1/2> Transition at 475328 usecs after Thu Apr 10 12:51:45 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_VETH_DN]
Triggered event: [VIM_NIV_PHY_FSM_EV_DOWN_DONE]
Next state: [VIM_NIV_PHY_FSM_ST_WAIT_DCBX]
12) FSM:<Ethernet1/2> Transition at 983154 usecs after Thu Apr 10 12:53:06 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_DCBX]
Triggered event: [VIM_NIV_PHY_FSM_EV_RX_DCBX_CC_NUM]
Next state: [VIM_NIV_PHY_FSM_ST_WAIT_3SEC]
13) FSM:<Ethernet1/2> Transition at 992590 usecs after Thu Apr 10 12:53:09 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_3SEC]
Triggered event: [VIM_NIV_PHY_FSM_EV_DCX_3SEC_EXP]
Next state: [VIM_NIV_PHY_FSM_ST_WAIT_ENCAP]
14) FSM:<Ethernet1/2> Transition at 802877 usecs after Thu Apr 10 12:53:10 2014
Previous state: [VIM_NIV_PHY_FSM_ST_WAIT_ENCAP]
Triggered event: [VIM_NIV_PHY_FSM_EV_ENCAP_RESP]
Next state: [VIM_NIV_PHY_FSM_ST_UP]
15) FSM:<Ethernet1/2> Transition at 804263 usecs after Thu Apr 10 12:53:10 2014
Previous state: [VIM_NIV_PHY_FSM_ST_UP]
Triggered event: [VIM_NIV_PHY_FSM_EV_VIC_OPEN_ACKD]
Next state: [FSM_ST_NO_CHANGE]
16) FSM:<Ethernet1/2> Transition at 992390 usecs after Thu Apr 10 12:53:11 2014
Previous state: [VIM_NIV_PHY_FSM_ST_UP]
Triggered event: [VIM_NIV_PHY_FSM_EV_VIC_OPEN_RECEIVED]
Next state: [FSM_ST_NO_CHANGE]
17) FSM:<Ethernet1/2> Transition at 992450 usecs after Thu Apr 10 12:53:11 2014
Previous state: [VIM_NIV_PHY_FSM_ST_UP]
Triggered event: [VIM_NIV_PHY_FSM_EV_VIC_OPEN_DONE]
Next state: [VIM_NIV_PHY_FSM_ST_UP_OPENED]
18) FSM:<Ethernet1/2> Transition at 992676 usecs after Thu Apr 10 12:53:11 2014
Previous state: [VIM_NIV_PHY_FSM_ST_UP_OPENED]
Triggered event: [VIM_NIV_PHY_FSM_EV_PP_SEND]
Next state: [VIM_NIV_PHY_FSM_ST_UP_OPENED_PP]
Curr state: [VIM_NIV_PHY_FSM_ST_UP_OPENED_PP] <<<<<<<<<<
n5k1#
如果虚拟以太网接口是固定虚拟以太网,请检查VIC_CREATE是否显示在此命令中:
# show system internal vim info niv msg logs fixed interface e 1/16 ch 1
Eth1/16(Chan: 1) VIF Index: 605
REQ MsgId: 56630, Type: VIC ENABLE, CC: SUCCESS
RSP MsgId: 56630, Type: VIC ENABLE, CC: SUCCESS
REQ MsgId: 4267, Type: VIC SET, CC: SUCCESS
RSP MsgId: 4267, Type: VIC SET, CC: SUCCESS
REQ MsgId: 62725, Type: VIC CREATE, CC: SUCCESS <<<<<<<
RSP MsgId: 62725, Type: VIC CREATE, CC: SUCCESS <<<<<<<
REQ MsgId: 62789, Type: VIC ENABLE, CC: SUCCESS
RSP MsgId: 62789, Type: VIC ENABLE, CC: SUCCESS
REQ MsgId: 21735, Type: VIC SET, CC: SUCCESS
RSP MsgId: 21735, Type: VIC SET, CC: SUCCESS
请注意,固定虚拟以太网接口是不支持跨物理接口迁移的虚拟接口。讨论适配器 — FEX时,范围始终在固定虚拟以太网上,因为适配器 — FEX是指通过单个(即非虚拟化)操作系统使用网络虚拟化。
如果VIC_CREATE未显示:
# show system internal vim log
# attach fex <number>
# test vic_proxy dump trace
版本 | 发布日期 | 备注 |
---|---|---|
1.0 |
04-Sep-2014 |
初始版本 |