N2K Fabric Extender

Creating a Port Channel ===
You can create a port channel before you create a channel group.

The software automatically creates the associated channel group.

2. interface port-channel <channel-number>

3. show port-channel summary

4. copy running-config startup-config

### Adding a Layer 2 Port to a Port Channel

You can add a Layer 2 port to a new channel group or to a channel group that already contains Layer 2 ports.

The software creates the port channel associated with this channel group if the port channel does not already exist.

#### BEFORE YOU BEGIN

Ensure that you are in the correct VDC (or use the switchto vdc command).

All Layer 2 member ports must run in full-duplex mode and at the same speed.

#### SUMMARY STEPS

1. configure terminal

2. interface type slot/port

3. switchport

4. channel-group <channel-number> [ force ] [ mode { on | active | passive }]

5. show interface type slot/port

6. copy running-config startup-config

### Associating a Fabric Extender to a Port Channel

#### BEFORE YOU BEGIN

Ensure that you have installed and enabled the Fabric Extender feature set.

switch# configure terminal

switch(config)# interface ethernet 10/1 - 4

switch(config-if)# channel-group <channel-number>

switch(config-if)# no shutdown

switch(config-if)# exit

switch(config)# interface port-channel <channel-number>

switch(config-if)# switchport

switch(config-if)# switchport mode fex-fabric

switch(config-if)# fex associate 101

####

#### TIP

As a best practice, only enter the fex associate command from the port channel interface, not from the physical interface.

If you try to associate a physical port to a FEX before that physical port is joined to a port channel, the physical port moves to the err-disable state and the Cisco Nexus Series device does not communicate with the FEX on that link.

You must enter the shutdown command and the no shutdown command on the Ethernet interface (not the port channel interface) to clear the err-disable state and bring the link up. (Note that this requirement does not apply if the configuration is performed prior to cabling.)

#### NOTE

When adding physical interfaces to port channels, all configurations on the port channel and physical interface must match.

This example shows how to display the association of the Fabric Extender and the parent device:

switch# show interface port-channel <channel-number> fex-intf

Fabric           FEX

Interface        Interfaces

Po4              Eth101/1/48   Eth101/1/47   Eth101/1/46   Eth101/1/45

Eth101/1/44   Eth101/1/43   Eth101/1/42   Eth101/1/41

Eth101/1/40   Eth101/1/39   Eth101/1/38   Eth101/1/37

Eth101/1/36   Eth101/1/35   Eth101/1/34   Eth101/1/33

Eth101/1/32   Eth101/1/31   Eth101/1/30   Eth101/1/29

Eth101/1/28   Eth101/1/27   Eth101/1/26   Eth101/1/25

Eth101/1/24   Eth101/1/23   Eth101/1/22   Eth101/1/21

Eth101/1/20   Eth101/1/19   Eth101/1/18   Eth101/1/17

Eth101/1/16   Eth101/1/15   Eth101/1/14   Eth101/1/13

Eth101/1/12   Eth101/1/11   Eth101/1/10   Eth101/1/9

Eth101/1/8    Eth101/1/7    Eth101/1/6    Eth101/1/5

Eth101/1/4    Eth101/1/3    Eth101/1/2    Eth101/1/1

Run script 'NEXUS\_N2K.py' OR enter these commands from the proper VDC:

sh inv | begin FEX

show fex

show fex <FEX NUMBER> ver

show fex detail

show environment fex <FEX NUMBER>

show int bri

show int fex-fabric

#### THEN CHECK LOCATOR BEACON LED:

locator-led fex <FEX NUMBER>

no locator-led fex <FEX NUMBER>

PJC3 (talk) 17:07, August 1, 2017 (UTC)