Wednesday, August 21, 2013

UCS Unified Storage Ports

Hi Guys!

Well there is no shame in admitting I took my first attempt at CCIE DC and didn't make it this first time, I was very close but not close enough, I am looking to book again ASAP so if you know anyone who is going to cancel let me know if my blog has been helpful at all :).

Anyway back on that horse, today I am going to talk about FCoE Storage ports on UCS, In case you have been living under a rock, UCS 2.1 allows us (finally!) to have northbound FCoE Connectivity!

HIP HIP HOORAY!


There are some good news with it too, you DON'T have to configure it in switch mode for FC or anything funky like that, you can be in NPV mode, you can do port channels and trunking too, so there really are no restrictions with this.


It's also quite easy to configure and works quite well. Let's take a look


So, first thing is first, you have to create your uplink from your FI to your Nexus or other FCoE capable device, this is exactly what you would expect, you just configure your port channel as you normally would:









Nothing special so far, Next, you want to go ahead and create your VSAN like you normally would on both the Nexus (the FCOE Device) and the Fabric Interconnect:

FI:




Nexus 5000:
vsan database
  vsan 88 

vlan 88
 fcoe vsan 88
!



Pretty straight forward so far and nothing special, but now we want to take that lovely port channel we just created, and make an FCoE Port channel uplink from it.

So on our N5k we would have some config like this:
feature fcoe
feature npiv (still have to do feature NPIV since we are still an NPV switch on the FI)

interface port-channel1
  switchport mode trunk
  speed 10000

  switchport trunk allowed vlan 1-10, 88
!
interface vfc1
  bind interface port-channel1
  no shutdown

 !

On the FI, go to the SAN tab, then expand out the FCoE Port Channels branch:



Add a new FCoE Port Channel, you will be asked to enter an ID, be sure to enter the same ID for the port channel as for your actual Ethernet Uplink, this is crucial, so for example if your northbound (to the nexus 5k) PO uplink is Port Channel ID 10, this must also be port channel ID 10 set here and we will find out why later


Since you have used the same port channel number, you now do not need to choose the ports, as the UCS will be smart enough to know that you mean to use those ports already associated with the other port channel.

Here will be your finished product if you where to look at the output produced by NX-OS:

UCS-SB58-B(nxos)# show run int vfc693

!Command: show running-config interface vfc693
!Time: Wed Aug 21 06:53:44 2013

version 5.0(3)N2(2.11a)

interface vfc693
  bind interface port-channel10
  switchport mode NP
  no shutdown



So as you can see, it simply creates a new VFC interface and binds it to whatever port channel number you placed here, this is what it is doing in the background, and is why you don't have to select any ports, if you WHERE to select ports it wouldn't hurt anything it would just make it re-add the ports to the port channel which could interrupt traffic, when there is no real point to doing that. So create your ethernet uplink as normal THEN create your vfc.

Here is an example of it logging in from one i created earlier:



Pod8-5548-B# show int vfc1
vfc1 is trunking (Not all VSANs UP on the trunk)
    Bound interface is port-channel1
    Hardware is Ethernet
    Port WWN is 20:00:54:7f:ee:46:30:bf
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port mode is TF
    Port vsan is 1
    Trunk vsans (admin allowed and active) (1,88)
    Trunk vsans (up)                       (88)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (1)
    1 minute input rate 88 bits/sec, 11 bytes/sec, 0 frames/sec
    1 minute output rate 1432 bits/sec, 179 bytes/sec, 0 frames/sec
      7 frames input, 900 bytes
        0 discards, 0 errors
      53 frames output, 8316 bytes
        0 discards, 0 errors
    last clearing of "show interface" counters never
    Interface last changed at Wed Aug 21 06:51:53 2013


Pod8-5548-B# show flogi database
--------------------------------------------------------------------------------
INTERFACE        VSAN    FCID           PORT NAME               NODE NAME      
--------------------------------------------------------------------------------
vfc1             88    0xd60000  22:b3:00:0d:ec:f0:77:ff 20:58:00:0d:ec:f0:77:c1

Total number of flogi = 1.





Now the only other small thing I wanted to show you was, what if you only wanted a single port to be your FCoE Uplink? Well first of all you might need to go to the doctor and get your head examined for such a risky idea, but assuming your OK with it, here is how to do it:

Go to SAN Uplink Manager, find a port that has been configured as an ethernet uplink port but NOT as a port channel, highlight the port and click "Make FCoE Uplink Port"























This will make NXOS on the FI create a new VFC interface and bind it to the port you highlighted:

UCS-SB58-A(nxos)# show run int vfc694

!Command: show running-config interface vfc694
!Time: Wed Aug 21 06:44:34 2013

version 5.0(3)N2(2.11a)

interface vfc694
  bind interface Ethernet1/14
  switchport mode NP
  no shutdown




I hope this helps someone out there and wish me luck for my second attempt i will get it this time!

8 comments:

  1. Sorry to hear that you've failed with your 1st attempt matey... keep going with this great job and you'll get there!

    D.

    ReplyDelete
  2. This is a great post and the only one I've found which explains about FCoE uplink ports, rather than FCoE storage ports.

    Good luck with next attempt - I'm on the same track, but some months from lab attempt. What do you feel was the problem? Time management???

    ReplyDelete
  3. I have gather much knowledge about UCS Unified storage ports. You discussed everything in details that how to set up it. Your blog really helped me lot. I think it will help me easy to set up.Thanks for your valuable information. Keep it update like this.

    ReplyDelete
  4. Hi! I need a piece of help.
    I've recently installed this new set of diskless UCS enclosures and I must keep them accessing NetApp's LUNs through Fibre Channel (Brocade fabrics - forced to use NPIV) for at least 1 year.
    NetApp has 4 UTA (CNA) ports attached to both FIs (our current 10 Gigabit ports are all on the FIs only...) and I wanted to use them all simultaneously for NFS traffic and FCoE boot.
    Initial deployment consultant configured all NetApp attached ports on both FIs as "Appliance Storage", and if I try to reconfigure them as "FCoE Storage Port", UCS Manager complains about FIs' "end-host mode". Configuring FIs' ports as "FCoE uplink ports" makes no sense at this moment as long as everything as plugged on the FIs.
    I have not tried your post instructions but would you suggest changing current ports' mode from something other than "Appliance Storage"?
    Many thanks!
    Jose

    ReplyDelete
  5. Network hosted storage allows your business to access data anytime, and also make for an easy way to back up data and improve network performance management. Self Storage

    ReplyDelete