- Preface
- Information About Cisco DFA
- Troubleshooting Platform and Software Requirements
- Troubleshooting Your Cable Plan
- Troubleshooting the DCNM OVA Installation
- Troubleshooting Power-on Auto Provisioning Issues
- Troubleshooting Post-POAP, Autoconfiguration, and Device Discovery Issues
- Troubleshooting Prime Network Services Controller Issues
- Decoding Leaf-Spine Traffic
- Debugging Tenant Traffic
Debugging Tenant
Traffic
This chapter contains the following sections:
Debugging Tenant Traffic
To verify the VLAN to VN-Segment mapping use the show platform fwm info vdc all verbose | begin fwm_avl_vlan_tree_by_vni command.
To verify the if programming works fine, use the show platform fwm info qinq-xlate-table <asic-num> command as this will show the mapping from the internal VLAN to VN-Segment mapping and vice-versa.
switch# show platform fwm info xlate-vlan-table 1 | grep " 200 " Dir Xlate-idx Key-vlan Res-vlan Ref-count Masked Location is_l2_if Ig 17 200 199 1 no 1.784.0 1 Eg 17 199 200 1 no 1.3262.0 1 switch# show platform fwm info qinq-xlate-table 1 | grep “ 200 " Number of xlate containers pending PSS: 0 Dir Xlate-idx Key-vlan Res-vlan Ref-count Masked Location is_l2_if Eg 17 199 20000 1 no 1.3024.0 1 Ig 17 20000 199 1 no 1.3189.0 1
For certain VLAN and VN-Segment mapping, the VLAN is seen from the server-side and hence it is xlate-vlan-table and QinQ is seen from the fabric-side and hence it is qinq-xlate-table.
In the above example of xlate-vlan-table, 'Res-vlan' in the Ig direction is the internal context that ASIC uses to forward server traffic of a tenant. In the CLI output of qinq-xlate-table, 'Res-vlan' in the Ig direction is the forwarding context that ASIC uses to forward FabricPath traffic of a tenant. It is required that, for a VLAN with VN-Segment, both the VLAN in the Ig direction and VN-Segment in the Ig direction should point to the same 'Res-vlan'.
switch# show platform fwm info pif ethernet 1/1 | grep asic Eth1/1 pd: slot 0 logical port num 0 slot_asic_num 1 global_asic_num 1 fw_ins t 0 phy_fw_inst 0 fc 0
The global_asic_num value is 1 for ethernet 1/1 in the above example.
Note | The VLAN and VN-Segment programming will be global and will be programmed symmetrically in all the ASICs. |