Monday, March 3, 2014

Cisco Nexus: How To Install A 10 Gig FEX On A 5548UP

I really like the data center products.  The Nexus is pretty cool in my opinion.  I had a customer ask me to get another 10 gig FEX ready for them for the next day.  So I went in and did just that.  Two 5548UPs and adding a N2K-C2232PP-10GE.  So I got the fiber in place and wrote out a template on what I would put in on the 5548UPs.  Just FYI, I usually do write a template first.  Its just my personal preference.


Just a note here on air flow.  I had an engineer that the air flow comes from the top of the unit.  He was right, so dont stack these without some space in between them.

The model of the FEX:

Back to the FEX notes.  So when, on the 5548UPs, I do a 'show fex', I get the following (before connecting the new fex):
N5K-1# sh fex
  FEX         FEX           FEX                       FEX
Number    Description      State            Model            Serial
------------------------------------------------------------------------
14  FEX-14                Online    N2K-C2232PP-10GE  SSIxxxxxxxx
15  FEX-15                Online    N2K-C2232PP-10GE   SSIxxxxxxxx
16  FEX-16               Online   N2K-C2248TP-E-1GE  SSIxxxxxxxx
18  FEX-18                Online   N2K-C2248TP-E-1GE   SSIxxxxxxxx
19  FEX-19                Online    N2K-C2232PP-10GE   SSIxxxxxxxx
N5K-1#

Now, for my template for adding a FEX in.  This goes on the 5548UP.  Not just one, but both of them.  We are doing a redundant topology.
n5K-1# config t
Enter configuration commands, one per line.  End with CNTL/Z.
N5K-1(config)#
N5K-1(config)# fex 13
N5K-1(config-fex)#   pinning max-links 1
Change in Max-links will cause traffic disruption.
N5K-1(config-fex)#   description "FEX-13"
N5K-1(config-fex)# exit
N5K-1(config)# interface port-channel13
N5K-1(config-if)#   description **FEX-13**
N5K-1(config-if)#   switchport mode fex-fabric
N5K-1(config-if)#   fex associate 13
N5K-1(config-if)#   vpc 13
N5K-1(config-if)# interface Ethernet2/1
N5K-1(config-if)#   description **FEX-13**
N5K-1(config-if)#   switchport mode fex-fabric
N5K-1(config-if)#   fex associate 13
N5K-1(config-if)#   channel-group 13

Once I got the commands in, I do a 'show fex' to see if the 5548UP can see the FEX:
N5K-1# sh fex
  FEX         FEX           FEX                       FEX
Number    Description      State            Model            Serial
------------------------------------------------------------------------
14  FEX-14                Online    N2K-C2232PP-10GE  SSIxxxxxxxx
15  FEX-15                Online    N2K-C2232PP-10GE   SSIxxxxxxxx
16  FEX-16               Online   N2K-C2248TP-E-1GE  SSIxxxxxxxx
18  FEX-18                Online   N2K-C2248TP-E-1GE   SSIxxxxxxxx
19  FEX-19                Online    N2K-C2232PP-10GE   SSIxxxxxxxx

---       --------             Connected    N2K-C2232PP-10GE   SSIxxxxxxxx

It says above it is connected.  That is good.  Its going to take a little time now for it to come online.  I then moved to the other 5548UP and put in the same config above.
Monitoring the status:
N5K-1# sh fex
  FEX         FEX           FEX                       FEX
Number    Description      State            Model            Serial
------------------------------------------------------------------------
14  FEX-14                Online    N2K-C2232PP-10GE  SSIxxxxxxxx
15  FEX-15                Online    N2K-C2232PP-10GE   SSIxxxxxxxx
16  FEX-16               Online   N2K-C2248TP-E-1GE  SSIxxxxxxxx
18  FEX-18                Online   N2K-C2248TP-E-1GE   SSIxxxxxxxx
19  FEX-19                Online    N2K-C2232PP-10GE   SSIxxxxxxxx
13 FEX-13        Image Download    N2K-C2232PP-10GE   SSIxxxxxxxx

Notice the 'image download' status above.
When I look at the details, just for fun, I see this:
N5K-1# sh fex 13 det
FEX: 13 Description: FEX-13   state: Image Download
  FEX version: 4.2(1)N1(1) [Switch version: 5.1(3)N2(1)]
  FEX Interim version: 4.2(1)N1(0.002)
  Switch Interim version: 5.1(3)N2(1)
  Module Sw Gen: 21  [Switch Sw Gen: 21]
  post level: complete
  Pinning-mode: static    Max-links: 1
  Fabric port for control traffic: Eth2/16
  FCoE Admin: false
  FCoE Oper: true
  FCoE FEX AA Configured: false
  Fabric interface state:
    Po183 - Interface Up. State: Active
    Eth2/16 - Interface Up. State: Active
  Fex Port        State  Fabric Port
Logs:
02/27/2014 18:21:23.196783: Module register received
02/27/2014 18:21:23.197741: Image Version Mismatch
02/27/2014 18:21:23.204499: Registration response sent
02/27/2014 18:21:23.204876: Requesting satellite to download image
N5K-1#

When the image has downloaded, the FEX reboots:
N5K-1# sh fex
  FEX         FEX           FEX                       FEX
Number    Description      State            Model            Serial
------------------------------------------------------------------------
14  FEX-14                Online    N2K-C2232PP-10GE  SSIxxxxxxxx
15  FEX-15                Online    N2K-C2232PP-10GE   SSIxxxxxxxx
16  FEX-16               Online   N2K-C2248TP-E-1GE  SSIxxxxxxxx
18  FEX-18                Online   N2K-C2248TP-E-1GE   SSIxxxxxxxx
19  FEX-19                Online    N2K-C2232PP-10GE   SSIxxxxxxxx
13 FEX-13               Offline    N2K-C2232PP-10GE   SSIxxxxxxxx

When the FEX comes back up, you finally see it come online:
N5K-1# sh fex
  FEX         FEX           FEX                       FEX
Number    Description      State            Model            Serial
------------------------------------------------------------------------
14  FEX-14                Online    N2K-C2232PP-10GE  SSIxxxxxxxx
15  FEX-15                Online    N2K-C2232PP-10GE   SSIxxxxxxxx
16  FEX-16               Online   N2K-C2248TP-E-1GE  SSIxxxxxxxx
18  FEX-18                Online   N2K-C2248TP-E-1GE   SSIxxxxxxxx
19  FEX-19                Online    N2K-C2232PP-10GE   SSIxxxxxxxx
13 FEX-13               Online    N2K-C2232PP-10GE   SSIxxxxxxxx

By the way, below is the fiber module I put in the 10 gig FEX, in case you need to know the part number:

2 comments:

  1. I have been reading your page from time to time and had a question about dual homing your fex to a set of vPC'd 5Ks. I have seen that Cisco doesn't recommend doing this in a data center but to instead attach one FEX to one 5K and another FEX to the other 5K. Then do your VPC via the FEX pair. I would like to have the warm fuzzys about what you are doing with these, but others in my org shy away from it. Do you have any documentation that supports your topology?

    ReplyDelete
    Replies
    1. I don't right off have any documentation, but Cisco is where I got the idea from. It's worked without issue since I put it in.

      Delete

Your comment will be reviewed for approval. Thank you for submitting your comments.