Cisco Cisco UCS B440 M1 High-Performance Blade Server 문제 해결 가이드
Appliance Port Troubleshooting
In the majority of implementations, communication between the blade servers and storage controllers that are
plugged into the appliance ports are over the same broadcast domain (Layer 2 of the Open Systems
Interconnect (OSI) model). In order to verify that this Layer 2 communication works correctly, you
must verify whether the UCS Fabric Interconnect has learned the MAC address of the storage controller on
the appliance port and on the correct VLAN.
plugged into the appliance ports are over the same broadcast domain (Layer 2 of the Open Systems
Interconnect (OSI) model). In order to verify that this Layer 2 communication works correctly, you
must verify whether the UCS Fabric Interconnect has learned the MAC address of the storage controller on
the appliance port and on the correct VLAN.
In order to check the MAC address table, log into the UCS CLI console, connect to the NX-OS shell, and
verify the list of allowed VLANs on the appliance port. You can then view the MAC address entries for the
VLAN that are to be used for communication with the appliance port.
verify the list of allowed VLANs on the appliance port. You can then view the MAC address entries for the
VLAN that are to be used for communication with the appliance port.
Here are the commands and output for verification:
F340-31-14-UCS-2-A#
connect nxos a
F340-31-14-UCS-2-A(nxos)#
show run int eth 1/11
!! Command: show running-config interface Ethernet1/11
!! Time: Fri Mar 29 07:02:29 2013
version 5.0(3)N2(2.11b)
interface Ethernet1/11
description A: Appliance
no pinning server sticky
pinning server pinning-failure link-down
no cdp enable
switchport mode trunk
switchport trunk allowed vlan 170
F340-31-14-UCS-2-A(nxos)#
show mac address-table vlan 170
Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link
VLAN MAC Address Type age Secure NTFY Ports
---------+-----------------+--------+-------+------+----+----------
* 170 0025.b500.004f static 0 F F
Veth780
* 170 0025.b500.005f static 0 F F
Veth779
* 170 010a.84ff.e4fe dynamic 0 F F
Eth1/11
In the this output, there are two blade servers, Veth780 and Veth779, and the MAC address of the storage
controller is learned on Eth1/11. These devices should be able to communicate with each other if there are no
other configuration issues on the end devices.
controller is learned on Eth1/11. These devices should be able to communicate with each other if there are no
other configuration issues on the end devices.
If no MAC addresses are learned on the appliance port while the correct VLAN is specified, then return to the
appliance port configuration and re-confirm the trunk configuration. Also, ensure that the communication link
on the storage appliance is in Active mode in the case of an Active/Passive link configuration. You can also
check the MAC address table on fabric interconnect B, dependent on the link that is active on the storage
controller side.
appliance port configuration and re-confirm the trunk configuration. Also, ensure that the communication link
on the storage appliance is in Active mode in the case of an Active/Passive link configuration. You can also
check the MAC address table on fabric interconnect B, dependent on the link that is active on the storage
controller side.
When the MAC addresses of the server and the storage controller are learned on the fabric interconnect within
the same VLAN, the fabric interconnect switches the traffic locally without the use of the upstream switches.
At this juncture, you can use an Internet Control Message Protocol (ICMP) request (ping) in order to test the
communication between the end points.
the same VLAN, the fabric interconnect switches the traffic locally without the use of the upstream switches.
At this juncture, you can use an Internet Control Message Protocol (ICMP) request (ping) in order to test the
communication between the end points.