Cisco Cisco Nexus 7000 F1-Series 32-Port 1 and 10 Gigabit Ethernet Module Guía Para Resolver Problemas

Traffic is expected to ingress the switch on port Eth3/18. When you check the modules in the system, you see
that Module 3 is an F1 module. It is important to remember that the N7K is fully−distributed, and that the
modules, not the supervisor, make the forwarding decisions for dataplane traffic.

N7K# show module 3

Mod  Ports  Module−Type                Model              Status

−−−  −−−−−  −−−−−−−−−−−−−−−−−−−−−−−−−− −−−−−−−−−−−−−−−−−− −−−−−−−−−−

3    32     1/10 Gbps Ethernet Module  N7K−F132XP−15      ok

For F1 modules, perform the ELAM on the Layer 2 (L2) Forwarding Engine (FE) with internal codename
Orion. The N7K F1 has 16 FEs per module, so you must determine the Orion ASIC that is used for the FE on
port Eth3/18. Enter this command in order to verify:

module−3# show hardware internal dev−port−map 

(some output omitted)

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

CARD_TYPE:         DCE 32 port 10G 

>Front Panel ports:32

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

 Device name             Dev role              Abbr num_inst:

−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−

> Orion Fwding Driver    DEV_LAYER_2_LOOKUP     L2LKP  16

+−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−+

+−−−−−−−−−−−+++FRONT PANEL PORT TO ASIC INSTANCE MAP+++−−−−−−−−+

+−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−+

FP port |  PHYS | MAC_0 | L2LKP | QUEUE |SWICHF 

...

   18      8       8       8       8       1 

In the output, you can see that port Eth3/18 is on Orion (L2LKP) instance 8. 

module−3# elam asic orion instance 8 

module−3(orion−elam)#

The Orion ASIC has a very limited set of ELAM triggers when compared to the other FEs on the N7K
platform. This is because the F1 is an L2−only module. Therefore, it makes switching decisions based on the
MAC address information (or SwitchID in FabricPath environments).

With Nexus Operating Systems (NX−OS), you can use the question mark character in order to separate 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

  vlan

For this example, the frame is captured based on the source and destination MAC addresses on the ingress
decision block.

Note: The F1 module does not require separate DBUS and RBUS triggers.

Here is the trigger:

module−3(orion−elam)# trigger di field sa 0050.56a1.1a01 da 0050.56a1.1aef