Risoluzione dei problemi di Control Plane per ambienti FabricPath

Introduzione

In questo documento viene descritto come risolvere i problemi relativi a FabricPath.

Prerequisiti

Requisiti

Cisco NXOS® raccomanda la conoscenza dei seguenti argomenti:

• FabricPath
• Intermediate System to Intermediate System (IS-IS)
• STP (Spanning Tree Protocol)
• Modulo ELAM (Embedded Logic Analyzer Module)

Componenti usati

Il documento può essere consultato per tutti i componenti hardware, ad esempio Nexus 7000.

Le informazioni discusse in questo documento fanno riferimento a dispositivi usati in uno specifico ambiente di emulazione. Su tutti i dispositivi menzionati nel documento la configurazione è stata ripristinata ai valori predefiniti. Se la rete è operativa, valutare attentamente eventuali conseguenze derivanti dall'uso dei comandi.

Premesse

FabricPath è una tecnologia Cisco che mira a migliorare le funzionalità di rete Ethernet, in particolare negli ambienti di centri dati su larga scala.

Di seguito sono elencate le caratteristiche principali e i vantaggi di FabricPath su Cisco Nexus serie 7000:

1. Scalabilità: FabricPath è progettato per consentire un numero elevato di canali di porte virtuali (vPC) e per fornire una rete di livello 2 altamente scalabile in grado di gestire un numero elevato di host senza le limitazioni tipiche associate allo Spanning Tree Protocol (STP).

2. Topologia senza loop: FabricPath elimina la necessità di STP all'interno del dominio di rete FabricPath. A tale scopo, viene utilizzata una tecnologia simile al routing per inoltrare i frame Ethernet, denominata TRILL (Transparent Interconnection of Lots of Links), che impedisce i loop e consente a tutti i percorsi di essere attivi.

3. Alta disponibilità: FabricPath consente di gestire in modo più efficiente le modifiche alla topologia di rete, riducendo i tempi di convergenza. Ciò migliora la stabilità complessiva della rete e fornisce una migliore disponibilità della rete.

4. Facilità d'uso: la tecnologia semplifica la progettazione della rete consentendo un'architettura Layer 2 flessibile e scalabile. Ciò semplifica la gestione della rete e riduce la complessità operativa.

5. Equal-Cost Multipath (ECMP): FabricPath supporta ECMP, consentendo l'utilizzo di più percorsi paralleli tra due punti qualsiasi della rete. In questo modo l'utilizzo della larghezza di banda viene ottimizzato mediante il bilanciamento del carico del traffico su tutti i percorsi disponibili.

6. Supporto della virtualizzazione: FabricPath fornisce un'infrastruttura ideale per i centri dati virtualizzati e le installazioni di cloud privati. La capacità di gestire un numero elevato di ambienti virtuali lo rende adatto a questo tipo di applicazioni.

È inoltre importante notare che, sebbene FabricPath offra numerosi vantaggi, è ideale per gli ambienti in cui i vantaggi specifici si allineano agli obiettivi di progettazione della rete, ad esempio i centri dati che richiedono domini Layer 2 grandi, dinamici e scalabili.

Topologia

Per semplicità, in questa topologia vengono presentate solo una colonna vertebrale e due foglie.

ID switch emulato foglia A: 3101

ID switch emulato foglia D: 3102

 

 

 

 

 

 

Risoluzione dei problemi

L'host 1 non può comunicare con l'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) Verificare che la tabella degli indirizzi MAC sia compilata correttamente per i due host.

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) Verificare la configurazione per ciascuna interfaccia e vlan coinvolta nel percorso. FabricPath deve essere abilitato.

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) Verificare gli ID degli switch per ogni dispositivo che partecipa a 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) Verificare che siano configurati i percorsi corretti con l'ID switch di ciascun 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) Verificare l'adiacenza IS-IS tra foglie e aculei.

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) Verificare che i conflitti non siano presenti nella distribuzione corrente.

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) Verificare che le VLAN siano state aggiunte all'intervallo di 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)Verificare se un ELAM è attivato nella spina 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) Aggiungere 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)#

Verifica

1) Verificare la tabella degli indirizzi 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) Verificare se un ELAM è attivato nella spina 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) Verificare la connettività da foglia A all'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#

Informazioni correlate

Cisco FabricPath

Guida di riferimento ai comandi di Cisco Nexus serie 7000 NX-OS FabricPath

Procedura ELAM del modulo Nexus 7000 M3