/***FCoE enabled VLAN must be forwarding on operationally UP vlan for a given /*** ethernet interface on N7K, FCoE enabled mapped VSAN should be operationally /*** up on MDS, VLAN should be in BLOCKED state

There are 8 reserved labels ranging from 0x7f0 to 0x7f7, each one corresponding to a FC port-type.

Here’s how to interpret the port-type (the label value)

PORT_FC_PORT_TYPE_TE 0x7f1 // FC Port mode TE (VE port)

PORT_FC_PORT_TYPE_F 0x7f2 // FC Port mode F (VF port)

FIB verification – Verifying routes

Recommended Action:

To verify routes:

module-4# sh fib unicast

IOD Mode: in order mode Mod : #adjacency

All fields in hex except VSAN

Route IOD Fwd | Adj Met Adj Adj

Type Mode VSAN D ID Idx | Mod Idx Idx Mark St VDC FE

---- ---- ---- ------ ---- +--- ----- ----- ---- --- -- ---

wka idle 0 fffff5 b7ea | 1 00000 00059 0009 000 03 00

wka idle 0 fffff5 b7ea | 1 00000 00059 0009 000 03 0b

wka idle 0 fffff6 b7ec | 1 00001 0005a 0009 000 03 00

wka idle 0 fffff6 b7ec | 1 00001 0005a 0009 000 03 0b

wka idle 0 fffff7 b7ee | 1 00002 0005b 0009 000 03 00

wka idle 0 fffff7 b7ee | 1 00002 0005b 0009 000 03 0b

wka idle 0 fffff8 b7f0 | 1 00003 0005c 0009 000 03 00

wka idle 0 fffff8 b7f0 | 1 00003 0005c 0009 000 03 0b

wka idle 0 fffff9 b7f2 | 1 00004 0005d 0009 000 03 00

wka idle 0 fffff9 b7f2 | 1 00004 0005d 0009 000 03 0b

wka idle 0 fffffa b7f4 | 1 00005 0005e 0009 000 03 00

wka idle 0 fffffa b7f4 | 1 00005 0005e 0009 000 03 0b

wka idle 0 fffffb b7f6 | 1 00006 0005f 0009 000 03 00

wka idle 0 fffffb b7f6 | 1 00006 0005f 0009 000 03 0b

wka idle 0 fffffc b7f8 | 1 00007 00060 0009 000 03 00

wka idle 0 fffffc b7f8 | 1 00007 00060 0009 000 03 0b

wka idle 0 fffffd b7fa | 1 00008 00061 0009 000 03 00

wka idle 0 fffffd b7fa | 1 00008 00061 0009 000 03 0b

wka idle 0 fffffe b7fc | 1 00009 00062 0009 000 03 00

wka idle 0 fffffe b7fc | 1 00009 00062 0009 000 03 0b

local idle 1 ceffff .... | 0 00000 deadbeef 0009 000 03

local idle 2 112233 b666 | 1 0000e 00064 0000 000 03 00

local idle 2 112233 b666 | 1 0000e 00064 0000 000 03 0b

local idle 2 c1ffff b5fc | 1 0000a 00063 0009 000 03 00

local idle 2 c1ffff b5fc | 1 0000a 00063 0009 000 03 0b

ucast idle 2 eb0000 b3d6 | 1 0000f 00065 0000 000 03 00

ucast idle 2 eb0000 b3d6 | 1 0000f 00065 0000 000 03 0b

From the given command, the following information can be obtained:

The Route Type indicates the type as before - “wka/local/Remote etc”

The presence of routes in each clipper (FE) as indicated in the FE field. If the FE field is blank, as in the case of FCID 0xceffff with VSAN 1, it is because the route is not programmed in h/w (also note Fwd Idx is “....” and Adj Idx is “deadbeef”

Fwd Idx – Specifies the FIB TCAM address as well as the FIB UC Result DRAM address. The RDRAM stores the LS-MET base address and num paths (-1 actually)

Adj Mod – Specifies the number of paths (VE links / ISLs). This will be 1 for local routes.

Met Idx – Specifies the Multipath base address (similar to Mp table base addr in Orion). One difference with Orion is that there is an additional table which has the “bundle of Adj pointers” called the LS-MET. When there are multiple paths to a destinations, the RDRAM points to the LS-MET base address and a load balance of the link take place at LS-MET level. The LS-MET entry has the “adj_ptr” which tells where the ADJ is in the ADJ Table as well as where the Rewrite Entry is in the RIT table.

Adj Idx – Specifies the Adjacency Index when there is only ONE path to the destination. When there is only one path to destination, the RDRAM directly encodes the “adj_ptr” instead of the LS-MET base address. VDC Id is obtained from VDC field.