N5K with N2K FEX vPC
1. Attach FEX
1.1 Configure FEX on both N5Ks
Since vPC is not enabled yet, N5K-1 configured with FEX will attach the FEX and N5K-2 won’t.
On N5K-2, FEX state is connected. But you can’t check its details which means N5K-1 manages the attached FEX control information. If you check the FEX uplink interface SFP as a test, you can’t get the information.
1.2 FEX Attachment State Change Process
Logs on N5K-1. N5K-2 goes through the same process but doesn’t mange the FEX.
When I shut the port towards FEX, I got the following logs.
The logs on the N5K-2 is as follows. It takes 32 seconds for N2K to be back online on the other N5K.
The FEX 100 is hidden from N5K-1 and shown on N5K-2.
Now I unshut the link towards FEX on N5K-1, I got the following log.
FEX is still attached to N5K-2.
1.3 FEX Show Command Output
Show FEX interface related information.
Show the transceiver info on N5K side and N2K side. They are different if using different SFPs.
Show FEX inventory and environment information.
2. Form vPC
2.1 Configure vPC between N5Ks.
The vPC status is as follows.
2.2 Configure vPC for FEX
Configure the following on both N5Ks.
Now N2Ks can be managed from either of the N5Ks.
I got the following log when I make the configuration change.
Now the FEX interfaces are in the show vpc
output.
2.3 Configure Host vPC
Configure VLAN, SVI interface, HSRP and port-channel towards Host.
The status of Po120 is as follows:
If I configure vPC under Po120, I got this error.