Solución de problemas del plano de control para entornos FabricPath

Introducción

Este documento describe los pasos básicos para resolver problemas de FabricPath.

Prerequisites

Requirements

Cisco NXOS® recomienda que conozca estos temas:

• FabricPath
• Sistema intermedio a sistema intermedio (IS-IS)
• Spanning Tree Protocol (STP)
• Módulo analizador de lógica integrada (ELAM)

Componentes Utilizados

Este documento está restringido a hardware específico como Nexus 7000.

La información que contiene este documento se creó a partir de los dispositivos en un ambiente de laboratorio específico. Todos los dispositivos que se utilizan en este documento se pusieron en funcionamiento con una configuración verificada (predeterminada). Si tiene una red en vivo, asegúrese de entender el posible impacto de cualquier comando.

Antecedentes

FabricPath es una tecnología de Cisco cuyo objetivo es mejorar las capacidades de red Ethernet, especialmente en entornos de Data Center a gran escala.

A continuación se indican las características y ventajas clave de FabricPath en Cisco Nexus serie 7000:

1. Escalabilidad: FabricPath está diseñado para admitir un gran número de canales de puertos virtuales (vPC) y para proporcionar una red de capa 2 altamente escalable que pueda gestionar un gran número de hosts sin las limitaciones asociadas normalmente al protocolo de árbol de extensión (STP).

2. Topología sin bucles: FabricPath elimina la necesidad de STP en el dominio de red FabricPath. Esto se hace mediante el uso de una tecnología similar al ruteo para reenviar tramas Ethernet, llamada Interconexión transparente de muchos links (TRILL), que evita los loops y permite que todas las trayectorias estén activas.

3. Alta disponibilidad: con FabricPath, los cambios en la topología de red se gestionan de forma más eficaz, lo que reduce el tiempo de convergencia. Esto mejora la estabilidad de la red en general y proporciona una mejor disponibilidad de la red.

4. Facilidad de uso: esta tecnología simplifica el diseño de la red al permitir una arquitectura de capa 2 flexible y escalable. Esto facilita la gestión de la red y reduce la complejidad operativa.

5. Equal-Cost Multipath (ECMP): FabricPath admite ECMP, lo que permite el uso de varias rutas paralelas entre dos puntos cualesquiera de la red. Esto optimiza la utilización del ancho de banda al equilibrar la carga del tráfico en todas las rutas disponibles.

6. Compatibilidad con la virtualización: FabricPath proporciona una infraestructura ideal para Data Centers virtualizados e implementaciones de nube privada. Su capacidad para gestionar un gran número de entornos virtuales lo convierte en una buena opción para este tipo de aplicaciones.

También es importante tener en cuenta que, aunque FabricPath ofrece muchas ventajas, es mejor utilizarlo en entornos en los que sus ventajas específicas están en consonancia con los objetivos de diseño de red, como los Data Centers que requieren dominios de capa 2 grandes, dinámicos y escalables.

Topología

Para simplificar, en esta topología solo se presentan una columna vertebral y dos hojas.

Hoja A de ID de switch emulado: 3101

Hoja D de ID de switch emulado: 3102

 

 

 

 

 

 

Troubleshoot

El Host 1 no se puede comunicar con el 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) Compruebe que la tabla de direcciones MAC está correctamente cumplimentada para los dos 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 la configuración para cada interfaz y vlan involucradas en la trayectoria. FabricPath debe estar 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 los ID de switch para cada dispositivo que participe en 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 que las rutas correctas estén configuradas con el ID de 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) Verificar la adyacencia IS-IS entre hojas y espinas.

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) Compruebe que no haya conflictos en la implementación actual.

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) Verificar que las VLAN se agregan al rango 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)Compruebe si se activa un ELAM en la columna 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) Agregue la VLAN 409 a 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)#

Verificación

1) Verifique la tabla de direcciones 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 si se activa un ELAM en la columna 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 la conectividad de la Hoja A al 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#

Información Relacionada

Cisco FabricPath

Referencia de Comandos de Cisco Nexus 7000 Series NX-OS FabricPath

Procedimiento ELAM del módulo Nexus 7000 M3