Cisco N5K-C5010P-BF Troubleshooting Guide - Page 22

Failover, FCoE Traffic

Get Cisco N5K-C5010P-BF - Nexus 5010 Switch PDF manuals and user guides
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

Failover Chapter 1 Troubleshooting Overview Send document comments to [email protected]. Device ID:TM-6506-1 System Name: Interface address(es): IPv4 Address: 11.1.1.1 Platform: cisco WS-C6506, Capabilities: Router Switch IGMP Filtering Interface: Ethernet1/4, Port ID (outgoing port): TenGigabitEthernet1/2 port connections Holdtime: 133 sec ? Verifies proper Version: Cisco Internetwork Operating System Software IOS (tm) s72033_rp Software (s72033_rp-IPSERVICES_WAN-VM), Version 12.2(18)SXF11, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2007 by cisco Systems, Inc. Compiled Fri 14-Sep-07 23:09 by kellythw Advertisement Version: 2 Native VLAN: 1 ? Sent on Native VLAN Duplex: full Failover FCoE Traffic When the Nexus 5000 experiences loss of fabric connectivity, it brings down all the affected vFC interfaces. The following methods are used to signal the host of loss of connectivity to the FC fabric • FIP Clear Link Virtual Link to the CNA will be signaled to indicate the 'shut' state of vFC. Throughout the 'shut' period FCF Advertisements indicate 'not available for login'. • In case the loss of connectivity is over the FCoE network, FIP keep-alives are used by the FCF and the CNA to timeout the login sessions. The keep-alive timers are configurable. Non-FCoE traffic Under certain failure scenarios where the access switch has lost all uplink connectivity to the aggregation layer, the CNA needs to be signaled of the loss of LAN connectivity. This helps the CNA failover the host traffic to the standby port. Traditionally, such a failure is signaled by bringing down the host facing link. Bringing down the link achieves two purposes: • Host is signaled of loss of connectivity. • The access switch stops forwarding traffic to and from the host-facing link. However, in the converged network, even though the LAN connectivity is lost at the access switch, the SAN connectivity might still be intact. Bringing down the entire host-facing link is not desirable. Instead, the loss of connectivity is signaled over protocols. Loss of SAN connectivity is signaled using the FIP Clear Virtual Link message. Loss of LAN connectivity is signaled using logical link status TLVs defined in DCBX and VIC protocols. 1-14 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
Send document comments to [email protected].
1-14
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 1
Troubleshooting Overview
Failover
Device ID:TM-6506-1
System Name:
Interface address(es):
IPv4 Address: 11.1.1.1
Platform: cisco WS-C6506, Capabilities: Router Switch IGMP Filtering
Interface: Ethernet1/4, Port ID (outgoing port): TenGigabitEthernet1/2
? Verifies proper
port connections
Holdtime: 133 sec
Version:
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-IPSERVICES_WAN-VM), Version 12.2(18)SXF11, RELEASE
SOFTWARE (fc1)
Copyright (c) 1986-2007 by cisco Systems, Inc.
Compiled Fri 14-Sep-07 23:09 by kellythw
Advertisement Version: 2
Native VLAN: 1
? Sent on Native VLAN
Duplex: full
Failover
FCoE Traffic
When the Nexus 5000 experiences loss of fabric connectivity, it brings down all the affected vFC
interfaces.
The following methods are used to signal the host of loss of connectivity to the FC fabric
•
FIP Clear Link Virtual Link to the CNA will be signaled to indicate the ‘shut’ state of vFC.
Throughout the ‘shut’ period FCF Advertisements indicate ‘not available for login’.
•
In case the loss of connectivity is over the FCoE network, FIP keep-alives are used by the FCF and
the CNA to timeout the login sessions. The keep-alive timers are configurable.
Non-FCoE traffic
Under certain failure scenarios where the access switch has lost all uplink connectivity to the aggregation
layer, the CNA needs to be signaled of the loss of LAN connectivity. This helps the CNA failover the
host traffic to the standby port. Traditionally, such a failure is signaled by bringing down the host facing
link. Bringing down the link achieves two purposes:
•
Host is signaled of loss of connectivity.
•
The access switch stops forwarding traffic to and from the host-facing link.
However, in the converged network, even though the LAN connectivity is lost at the access switch, the
SAN connectivity might still be intact. Bringing down the entire host-facing link is not desirable.
Instead, the loss of connectivity is signaled over protocols. Loss of SAN connectivity is signaled using
the FIP Clear Virtual Link message. Loss of LAN connectivity is signaled using logical link status TLVs
defined in DCBX and VIC protocols.