Solucionar problemas do plano de controle para ambientes FabricPath

Introdução

Este documento descreve as etapas básicas para solucionar problemas do FabricPath.

Pré-requisitos

Requisitos

O Cisco NXOS® recomenda que você tenha conhecimento destes tópicos:

• FabricPath
• Sistema intermediário para sistema intermediário (IS-IS)
• STP (Spanning Tree Protocol)
• ELAM (Embedded Logic Analyzer Module, Módulo Analisador Lógico Embutido)

Componentes Utilizados

Este documento é restrito a hardware específico, como o Nexus 7000.

As informações neste documento foram criadas a partir de dispositivos em um ambiente de laboratório específico. Todos os dispositivos utilizados neste documento foram iniciados com uma configuração (padrão) inicial. Se a rede estiver ativa, certifique-se de que você entenda o impacto potencial de qualquer comando.

Informações de Apoio

FabricPath é uma tecnologia da Cisco que tem como objetivo aprimorar os recursos de rede Ethernet, particularmente em ambientes de data center de grande escala.

Estes são os principais recursos e benefícios do FabricPath no Cisco Nexus 7000 Series:

1. Escalabilidade: o FabricPath foi projetado para permitir um grande número de canais de porta virtuais (vPCs) e para fornecer uma rede de Camada 2 altamente escalável que possa lidar com um grande número de hosts sem as limitações normalmente associadas ao Spanning Tree Protocol (STP).

2. Topologia sem loops: o FabricPath elimina a necessidade de STP no domínio de rede do FabricPath. Isso é feito usando uma tecnologia de roteamento para encaminhar quadros Ethernet, chamada de TRILL (Transparent Interconnection of Lots of Links, Interconexão Transparente de Muitos Links), que evita loops e permite que todos os caminhos estejam ativos.

3. Alta disponibilidade: com o FabricPath, as alterações na topologia da rede são tratadas com mais eficiência, reduzindo o tempo de convergência. Isso melhora a estabilidade geral da rede e fornece melhor disponibilidade da rede.

4. Facilidade de uso: a tecnologia simplifica o projeto de rede permitindo uma arquitetura de camada 2 flexível e escalável. Isso facilita o gerenciamento da rede e reduz a complexidade operacional.

5. Equal-Cost Multipath (ECMP): o FabricPath oferece suporte ao ECMP, permitindo o uso de vários caminhos paralelos entre dois pontos na rede. Isso otimiza a utilização da largura de banda, balanceando a carga do tráfego em todos os caminhos disponíveis.

6. Suporte à virtualização: o FabricPath fornece uma infraestrutura ideal para data centers virtualizados e implantações de nuvem privada. Sua capacidade de lidar com um grande número de ambientes virtuais o torna uma boa opção para esses tipos de aplicativos.

Também é importante observar que, embora o FabricPath ofereça muitos benefícios, ele é melhor usado em ambientes em que suas vantagens específicas se alinham com as metas de projeto de rede, como data centers que exigem domínios de camada 2 grandes, dinâmicos e escaláveis.

Topologia

Para simplificar, apenas uma coluna e duas folhas são apresentadas nessa topologia.

ID de switch emulado Folha A: 3101

ID de Switch Emulado Leaf D :3102

 

 

 

 

 

 

Troubleshooting

O Host 1 não pode se comunicar com o Host 2.

Leaf_A# ping 192.168.10.17
PING 192.168.10.17 (192.168.10.17): 56 data bytes
ping: sendto 192.168.10.17 64 chars, No route to host
Request 0 timed out
ping: sendto 192.168.10.17 64 chars, No route to host
^C
--- 192.168.10.17 ping statistics ---
2 packets transmitted, 0 packets received, 100.00% packet loss
Leaf_A# 

1) Verifique se a tabela de endereços MAC está preenchida corretamente para os dois hosts.

Leaf_A# show mac address-table vlan 409
Note: MAC table entries displayed are getting read from software.
Use the 'hardware-age' keyword to get information related to 'Age'

Legend: 
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link,
(T) - True, (F) - False , ~~~ - use 'hardware-age' keyword to retrieve age info 
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
* 409 aaaa.aaaa.aaaa dynamic ~~~ F F Po3
                                                 <------ Leaf A is not learning the mac address of Host 2
Leaf_A#

Leaf_D# show mac address-table vlan 409
Note: MAC table entries displayed are getting read from software.
Use the 'hardware-age' keyword to get information related to 'Age'

Legend: 
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link,
(T) - True, (F) - False , ~~~ - use 'hardware-age' keyword to retrieve age info 
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
* 409 bbbb.bbbb.bbbb dynamic ~~~ F F Po4
409 aaaa.aaaa.aaaa dynamic ~~~ F F 3101.1.65535    <------ Leaf D is correctly learning both Mac Addresses.

Leaf_D#

2) Verifique a configuração de cada interface e vlan envolvida no caminho. FabricPath deve ser habilitado.

Leaf_A# show run fabricpath

!Command: show running-config fabricpath
!Time: Mon Apr 22 23:12:40 2024

version 6.2(12)
install feature-set fabricpath
feature-set fabricpath

vlan 409
mode fabricpath
fabricpath domain default

fabricpath switch-id 301

vpc domain 301
fabricpath switch-id 3101

interface port-channel1
switchport mode fabricpath

interface port-channel2
switchport mode fabricpath

interface Ethernet1/1
switchport mode fabricpath

interface Ethernet1/2
switchport mode fabricpath

Leaf_A#

Leaf_D# show run fabricpath

!Command: show running-config fabricpath
!Time: Mon Apr 22 23:12:40 2024

version 6.2(12)
install feature-set fabricpath
feature-set fabricpath

                         <--------- FabricPath is not enabled for VLAN 409


fabricpath switch-id 101

vpc domain 302
fabricpath switch-id 3102

interface port-channel1
switchport mode fabricpath

interface port-channel2
switchport mode fabricpath 

interface Ethernet1/1
switchport mode fabricpath

interface Ethernet1/2
switchport mode fabricpath


Leaf_D#
Leaf_D#

Spine_A# show run fabricpath

!Command: show running-config fabricpath
!Time: Mon Apr 22 23:12:40 2024

version 6.2(12)
install feature-set fabricpath
feature-set fabricpath

vlan 409
mode fabricpath
fabricpath domain default

fabricpath switch-id 31

vpc domain 101
fabricpath switch-id 1003

interface port-channel1
switchport mode fabricpath

interface port-channel2
switchport mode fabricpath 

interface Ethernet1/1
switchport mode fabricpath

interface Ethernet1/2
switchport mode fabricpath

interface Ethernet1/3
switchport mode fabricpath

interface Ethernet1/4
switchport mode fabricpath 

Spine_A#

3) Verifique as IDs do switch para cada dispositivo que participa do FabricPath.

Leaf_A# show fabricpath switch-id local
Switch-Id: 301
System-Id: aaaa.aaaa.b341
Leaf_A#

Leaf_D# show fabricpath switch-id local
Switch-Id: 101
System-Id: bbbb.bbbb.b342
Leaf_D#

Spine_A# show fabricpath switch-id local
Switch-Id: 31
System-Id: cccc.cccc.b343
Spine_A#

4) Verifique se as rotas certas estão configuradas com a ID do switch de cada dispositivo.

Leaf_A# show fabricpath route switchid 101        
FabricPath Unicast Route Table
'a/b/c' denotes ftag/switch-id/subswitch-id
'[x/y]' denotes [admin distance/metric]
ftag 0 is local ftag
subswitch-id 0 is default subswitch-id


FabricPath Unicast Route Table for Topology-Default

1/101/0, number of next-hops: 1
via Po1, [115/5], 1 day/s 12:21:29, isis_fabricpath-default <------ The route from Leaf A to Leaf D is correctly configured.
Leaf_A

Leaf_D# show fabricpath route switchid 301       
FabricPath Unicast Route Table
'a/b/c' denotes ftag/switch-id/subswitch-id
'[x/y]' denotes [admin distance/metric]
ftag 0 is local ftag
subswitch-id 0 is default subswitch-id


FabricPath Unicast Route Table for Topology-Default

1/301/0, number of next-hops: 1
via Po2, [115/5], 1 day/s 12:21:29, isis_fabricpath-default  <------ The route from Leaf D to Leaf A is correctly configured.
Leaf_D

Spine_A# show fabricpath route switchid 301       
FabricPath Unicast Route Table
'a/b/c' denotes ftag/switch-id/subswitch-id
'[x/y]' denotes [admin distance/metric]
ftag 0 is local ftag
subswitch-id 0 is default subswitch-id


FabricPath Unicast Route Table for Topology-Default

1/301/0, number of next-hops: 1
via Po1, [115/20], 1 day/s 06:13:21, isis_fabricpath-default <------ The route from Spine A to Leaf A is correctly configured.
Spine_A#


Spine_A# show fabricpath route switchid 101
FabricPath Unicast Route Table
'a/b/c' denotes ftag/switch-id/subswitch-id
'[x/y]' denotes [admin distance/metric]
ftag 0 is local ftag
subswitch-id 0 is default subswitch-id


FabricPath Unicast Route Table for Topology-Default

1/101/0, number of next-hops: 1
via Po2, [115/20], 1 day/s 06:13:21, isis_fabricpath-default <------ The route from Spine A to Leaf D is correctly configured.
Spine_A#

5) Verifique a adjacência IS-IS entre folhas e espinhos.

Leaf_A# show fabricpath isis adjacency 
Fabricpath IS-IS domain: default Fabricpath IS-IS adjacency database:
System ID SNPA Level State Hold Time Interface
cccc.cccc.b343 N/A 1 UP 00:00:27 port-channel1

Leaf_A#

Leaf_D# show fabricpath isis adjacency 
Fabricpath IS-IS domain: default Fabricpath IS-IS adjacency database:
System ID SNPA Level State Hold Time Interface
cccc.cccc.b343 N/A 1 UP 00:00:27 port-channel2

Leaf_D#

6) Verifique se não há conflitos na implantação atual.

Leaf_A# show fabricpath conflict all
No Fabricpath ports in a state of resource conflict.


No Switch id Conflicts

No transitions in progress

Leaf_A#

Leaf_D# show fabricpath conflict all
No Fabricpath ports in a state of resource conflict.


No Switch id Conflicts

No transitions in progress

Leaf_D#

Spine_A# show fabricpath conflict all
No Fabricpath ports in a state of resource conflict.


No Switch id Conflicts

No transitions in progress

Spine_A#

7) Verifique se as VLANs foram adicionadas ao intervalo de VLAN IS-IS.

Leaf_A# show fabricpath isis vlan-range
Fabricpath IS-IS domain: default
MT-0
Vlans configured:1,409
Leaf_A#

Leaf_D# show fabricpath isis vlan-range
Fabricpath IS-IS domain: default
MT-0
Vlans configured:1             <------ VLAN 409 is not present
Leaf_D

Spine_A# show fabricpath isis vlan-range
Fabricpath IS-IS domain: default
MT-0
Vlans configured:1, 409
Spine_A#

8) Verifique se um ELAM é acionado na linha A.

module-1# show hardware internal dev-port-map      <------ Determine the F4 ASIC that is used for the FE on port Eth1/2. Enter this command in order to verify this.
--------------------------------------------------------------
CARD_TYPE: 48 port 10G 
>Front Panel ports:48
--------------------------------------------------------------
Device name Dev role Abbr num_inst:
--------------------------------------------------------------
> Flanker Eth Mac Driver DEV_ETHERNET_MAC MAC_0 6
> Flanker Fwd Driver DEV_LAYER_2_LOOKUP L2LKP 6
> Flanker Xbar Driver DEV_XBAR_INTF XBAR_INTF 6
> Flanker Queue Driver DEV_QUEUEING QUEUE 6
> Sacramento Xbar ASIC DEV_SWITCH_FABRIC SWICHF 2
> Flanker L3 Driver DEV_LAYER_3_LOOKUP L3LKP 6
> EDC DEV_PHY PHYS 7
+-----------------------------------------------------------------------+
+----------------+++FRONT PANEL PORT TO ASIC INSTANCE MAP+++------------+
+-----------------------------------------------------------------------+
FP port | PHYS | MAC_0 | L2LKP | L3LKP | QUEUE |SWICHF 
    1       0      0       0       0       0     0,1 
    2       0      0       0       0       0     0,1 
...
module-1#
module-1# 
module-1# elam asic flanker instance 0
module-1(fln-elam)# 
module-1(fln-elam)# elam asic flanker instance 0
module-1(fln-elam)# layer3
module-1(fln-l2-elam)# 
module-1(fln-l2-elam)# trigger dbus ipv4 ingress if source-ipv4-address 192.168.10.17
module-1(fln-l2-elam)# 
module-1(fln-l2-elam)# trigger rbus ingress if trig
module-1(fln-l2-elam)# start
module-1(fln-l2-elam)# 
module-1(fln-l2-elam)# 
module-1(fln-l2-elam)# status
ELAM Slot 1 instance 0: L2 DBUS Configuration: trigger dbus ipv4 ingress if source-ipv4-address 192.168.10.17 
L2 DBUS: Armed
ELAM Slot 1 instance 0: L2 RBUS Configuration: trigger rbus ingress if trig 
L2 RBUS: Armed
module-1(fln-l2-elam)# status
ELAM Slot 1 instance 0: L2 DBUS Configuration: trigger dbus ipv4 ingress if source-ipv4-address 192.168.10.17 
L2 DBUS: Armed
ELAM Slot 1 instance 0: L2 RBUS Configuration: trigger rbus ingress if trig 
L2 RBUS: Armed                                                                                                      <------ ELAM is not triggered. 
module-1(fln-l2-elam)#

9) Adicione a VLAN 409 ao FabricPath.

Leaf_D(config)# vlan 409
Leaf_D(config-vlan)# mode fabricpath
Leaf_D(config-vlan)# show run vlan

!Command: show running-config vlan
!Time: Wed Apr 24 20:27:29 2024

version 6.2(12)
vlan 1,409
vlan 409
mode fabricpath


Leaf_D(config-vlan)#

Verificar

1) Verifique a tabela de endereços mac.

Leaf_A# show mac address-table vlan 409
Note: MAC table entries displayed are getting read from software.
Use the 'hardware-age' keyword to get information related to 'Age'

Legend: 
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link,
(T) - True, (F) - False , ~~~ - use 'hardware-age' keyword to retrieve age info 
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
* 409 aaaa.aaaa.aaaa dynamic ~~~ F F Po3
409 bbbb.bbbb.bbbb dynamic ~~~ F F 3102.1.65535

Leaf_A#

Leaf_D# show mac address-table vlan 409
Note: MAC table entries displayed are getting read from software.
Use the 'hardware-age' keyword to get information related to 'Age'

Legend: 
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link,
(T) - True, (F) - False , ~~~ - use 'hardware-age' keyword to retrieve age info 
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
* 409 bbbb.bbbb.bbbb dynamic ~~~ F F Po4
409 aaaa.aaaa.aaaa dynamic ~~~ F F 3101.1.65535

Leaf_D#

2) Verifique se um ELAM é acionado na linha A.

module-1# elam asic flanker instance 0
module-1(fln-elam)# 
module-1(fln-elam)# elam asic flanker instance 0
module-1(fln-elam)# layer2
module-1(fln-l2-elam)# 
module-1(fln-l2-elam)# trigger dbus ipv4 ingress if source-ipv4-address 192.168.10.17
module-1(fln-l2-elam)# 
module-1(fln-l2-elam)# trigger rbus ingress if trig
module-1(fln-l2-elam)# start
module-1(fln-l2-elam)# 
module-1(fln-l2-elam)# status
ELAM Slot 1 instance 0: L2 DBUS Configuration: trigger dbus ipv4 ingress if source-ipv4-address 192.168.10.17 
L2 DBUS: Armed
ELAM Slot 1 instance 0: L2 RBUS Configuration: trigger rbus ingress if trig 
L2 RBUS: Armed
module-1(fln-l2-elam)# status
ELAM Slot 1 instance 0: L2 DBUS Configuration: trigger dbus ipv4 ingress if source-ipv4-address 192.168.10.17 
L2 DBUS: Triggered             <-------- ELAM triggered
ELAM Slot 1 instance 0: L2 RBUS Configuration: trigger rbus ingress if trig 
L2 RBUS: Triggered             <-------- ELAM triggered
module-1(fln-l2-elam)# 

3) Verifique a conectividade da folha A com o host A.

Leaf_A# ping 192.168.10.17 
PING 192.168.10.17 (192.168.10.17): 56 data bytes
64 bytes from 192.168.10.17: icmp_seq=0 ttl=254 time=1.703 ms
64 bytes from 192.168.10.17: icmp_seq=1 ttl=254 time=1.235 ms
64 bytes from 192.168.10.17: icmp_seq=2 ttl=254 time=1.197 ms
64 bytes from 192.168.10.17: icmp_seq=3 ttl=254 time=3.442 ms
64 bytes from 192.168.10.17: icmp_seq=4 ttl=254 time=1.331 ms

--- 192.168.10.17 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 1.197/1.781/3.442 ms
Leaf_A#

Informações Relacionadas

Cisco FabricPath

Referência de comandos do Cisco Nexus 7000 Series NX-OS FabricPath

Procedimento do módulo ELAM do Nexus 7000 M3