This document provides the steps to perform an ELAM on the Nexus 7000 F1-Module, explains the most relevant outputs, and how to interpret their results. Please refer to the following document for an overview on ELAM:
In this example a host on Vlan10 (10.1.1.101 with MAC 0050.56a1.1a01) port Eth3/18 sends an ICMP request to a host also on Vlan10 (10.1.1.102 with MAC 0050.56a1.1aef) off port Eth3/26. We will use ELAM to capture this single frame between the hosts. It's important to remember that ELAM allows us to capture a single frame.
To perform an ELAM on the Nexus7000, you need to first attach to the appropriate module. This requires the network-admin privilege.
N7K# attach module 3
Attaching to module 3 ...
To exit type 'exit', to abort type '$.'
Determine the ingress FE
We expect the traffic to ingress the switch on port Eth3/18. Checking the modules in the system we can see that module 3 is an F1 module. Remember, the Nexus 7000 is fully distributed and the modules, not the supervisor, are responsible for making the forwarding decision for dataplane traffic.
For F1 modules, we want to perform the ELAM on the L2 forwarding engine (FE) with internal codename Orion.The F1 has 16 FEs per module. We need to determine which Orion ASIC is the FE for port Eth3/18. We can use the following command to verify:
From the output above, we can see that Eth3/18 is on Orion (L2LKP) instance 8.
module-3# elam asic orion instance 8
Configure the Trigger
The Orion ASIC has a very limited set of ELAM triggers compared to the other FEs on Nexus 7000. This is because the F1 is an L2 only module. It will be switching based off MAC information (or SwitchID in FabricPath environments). For NX-OS you can utilize the question mark to help parse out the ELAM trigger
module-3(orion-elam)# trigger di field ?
da Destination mac-address
mim_da Destination mac-in-mac-address
mim_sa Source mac-in-mac-address
sa Source mac-address
For this example we want to capture the frame based off source and destination MAC address on the ingress decision block. Note that F1 does not require a separate dbus and rbus trigger.
module-3(orion-elam)# trigger di field sa 0050.56a1.1a01 da 0050.56a1.1aef
Start the Capture
Different from the other Nexus7000 modules, the F1 ELAM is started as soon as the triggered is configured. We can check the status of the ELAM via the status command.
Once the frame matching the trigger has been received by the FE we will see the ELAM as triggered:
Interpret the Results
We can display the results via the show capture command. Below is an excerpt of the ELAM data that is most relevant in this example.
module-3(orion-elam)# show capture
(some output omitted)
dc3v4_si[11:0] : 17
vlanx : a
di : 1e or 1f
res_eth_da : 5056a11aef
res_eth_sa : 5056a11a01
Note that the F1 ELAM combines the data used to make the forwarding decision along with the forwarding result within the same output. From the example above we can see the source LTL (dc3v4_si) , the destination LTL (di), the vlan (vlanx), and MAC addresses. Note that the MAC address format in the ELAM output does not include prepending zeros.
Destination MAC (res_eth_da) 5056a11aef = 0050.56a1.1aef
Source MAC (res_eth_sa) 5056a11a01 = 0050.56a1.1a01
The source LTL (dc3v4_si) represents the port in which the frame was received.
N7K# show system internal pixm info ltl 0x17
The above output shows that source LTL of 0x17 maps to port Eth3/18. This confirms that the frame was received on Eth3/18.
Note that the F1 ELAM displays two results for the destination LTL (1e or 1f). This occurs because the ELAM parser is not able to read the least significant bit of the ELAM data resulting in a slight ambiguity. The rule of thumb is to validate the hardware MAC entry for the destination address and cross-check this with the destination LTL in the ELAM
module-3# show hardware mac address-table fe 8 address 0050.56a1.1aef vlan 10 vdc 1
The above output validates that Orion instance 8 (the FE making the forwarding decision for Eth3/18) has a hardware MAC entry for the destination 0050.56a1.1aef of 0x1f. This index is also the destination LTL (di) within the F1 ELAM. Finally, we validated that the LTL 0x1f maps to port Eth3/26. This confirms that the frame was sent out Eth3/26.
Another command to remember is show system internal pixm info ltl-region, which will show how the switch has allocated the pool of LTL's. This is useful to understand the purpose of an LTL if it does not match to a physical port. A good example is a drop LTL:
Hi,The border nodes in our fabric have linknets towards the fusion routers. These linknets are not routable in our core, but they still use them as source for the ping-requests to the DHCP/DNS-servers they have configured for each VN. The pings obviously ...
Hello, Cisco users, and everyone also. I am new to this forum, and this is my first post also. Guys, I have a problem. That is, I bought a new Cisco router (Cisco Linksys E900 Wireless-N300 Router). After configuration of the router, unable to use the int...
Dear all,I want to improve my technical skills in BGP protocol, searched serveral times for BGP doucments but couldn't get the docuement however I had gone through cisco docuements ( officials websites ) but there is I get confused while studying BGP prot...
We have Cisco 350X and Dlink 1210-28 switches working together in our network.Both these switches are inter-operating together and LACP is configured between them.Dlink 1210-28 switch:
Hardware Version: F1
Loopback detect setting