Blog‎ > ‎

CCIE DC UCS LAB LAN Connectivity

posted Jun 13, 2014, 7:10 PM by Rick McGee   [ updated Jun 18, 2014, 4:15 PM ]
802.3ap 
    Backplane Ethernet 
    IEEE Started task force in 2004 and Ratified standard in 2007
    Allows for 1GE (single lane) and 10GE (single and 4 lane) over printed circuit boards

10BASE-KR
    Operates over a single backplane lane     
    Uses same physical layer coding as 10BASE-LA/ER/SR
    You see "KR" suffix in oder mezzanine card models 

VN-Link
    Marketing term
    How to get traffic from one location to another via a virtual device that doesn't 
    have direct physical connectivity 

VN-TAG
    The actual act of populating the Ethernet header (6 bytes) with a tag to denote what 
    vEth/Eth port to send traffic 
    Became 801.1Qbh and finally standardized as 802.1br

VN-TAG Format

UCS LAN Connectivity 
    No Local switching on the IOM/FEX in chassis, local server switching on the FI's 

Fabric Interconnect Modes
    End Host Mode (NIV) (Default, recommended)
        Presented to upstream switches as a host, not a switch

    Ethernet Switching Mode 
        DON'T USE
        Participates in Spanning-Tree 
        Used to need this for disjointed L2 networks, but that's supported in EHM

LAN Connectivity -EHM
    No upstream MAC learning, only MAC learning is from southbound blades
    
    No STP
    
    Designated Broadcast/Multicase Uplink ports    
        Single Port as the Broadcast Listener and Receiver
            All other uplink interfaces that BC/MC heard ----> Go to the bit bucket

    Reverse Path Forwarding (RPF) Check
        Is this coming in an uplink port but not on that a downstream blade is pinned to? 
        It will drop it.



    Deja-Vu Check 
        Have I already seen this packet before? If so DROP IT
        Applies to BC/MC traffic 

Pinning
    Uplink Pinning, 
        Where a vNIC/Vfc and how it transverses the UCS system

    Static 
        Specify LAN Pin Group's
        We can still failover over to the other FI if primary fails if configured 

    Dynamic
        Automatic pinning, if pinned uplink fails, auto failover to uplink on FI, then to the 
        other FI (if VIC supported and configured)

    Pinning allows all 10GE uplinks to be active, even if not using port channeling
    

UCS LAN TAB Configuration 

UCS Topology 

Step 1 
Click on LAN Tab then LAN Uplinks Manager

Step 2 Configure Port-Channels in the LAN Uplinks Manager
 Step 3 Define a Name
Step 4 Choose Uplinks Ports Nexus
Ports eth 1/7-10 are part of a PO to N5K1 and N5K2
Finish and Click OK

You'll see the Port-Channel 1 for Fabric A listed.

Now setup the same for Fabric Interconnect B

Step 1
Step 2 Give it a Name

Step 3 Assign Port
Ports eth 1/7-10 are part of a PO to N5K1 and N5K2
Click Finish and OK

Final Step Enable all Port-Channels 

This configuration should be done previous to the FI configuration.


N5K1 Uplinks ports
conf t
int eth 1/21 - 22
switchport mode trunk
switchport trunk allowed vlan 1,100-200,4093
channel-group 21 mode active 

int po21
switchport mode trunk 
switchport trunk allowed vlan 1,100-200,4093
vpc 21 

int po22
switchport mode trunk
switchport trunk allowed vlan 1,100-200,4093
vpc 22

conf t
int eth 1/23-24
switchport mode trunk
switchport mode trunk allowed vlan 1,100-200,4093
channel-group 22 mode active 


N5K2 Uplink Ports
conf t
int eth 1/21-22
switchport mode trunk
switchport trunk allowed vlan 1,100-200,4093
channel-group 22 mode active 

int eth 1/23-24
switchport mode trunk
switchport trunk allowed vlan 1,100-100,4093
channel-group 21 mode active 


int po21
switchport mode trunk
switchport trunk allowed vlan 1,100-200,4093
vpc 21

int po22
switchport mode trunk
switchport trunk allowed vlan 1,100-200,4093
vpc 22

show vpc (after you enable the Port-Channels on the FI's)
As you can see, PO21 and PO22 are up with no consistency errors with the appropriate VLAN's 

Create VLAN's 



Hints:
Disabled any unused ports.

In this example I have 12 port license but 32 ports are active. You would want to disable the 20 extra ports that have no licensing associated with them so you don't go past the grace period.

You should see license Ok as in this example

Once you create a VLAN you cannot rename a VLAN,  you'll have to delete and recreate it. 
Pre-Planning is very important!

Comments