Blog‎ > ‎

CCIE DC SAN Virtual SAN's (VSANs)

posted May 12, 2014, 5:41 PM by Rick McGee   [ updated May 12, 2014, 6:45 PM ]
Use to segment Fabric Services into logical "SAN Islands"
    FLOGI, FC Domain, FC Name Server, Zoning, Aliases, etc.
        The above would be per VSAN basis 

Configuration 
    vsan database
    vsan 10 
    vsan 10 interface fc1/1
VSAN doesn't equate to how can talk to how within the SAN, but just creating separate copies of the fabric services

VSAN's and E ISL's 
    All VSAN's allowed on trunk port by default (Similar to Ethernet Bride Assurance)
    Remotely un-configued VSAN's automatically "pruned" off trunk ports is remote device does
    not have a particular VSAN configured.
    To avoid merging fabrics, VSAN's should be pruned manually 
        "switchport trunk allowed vsan"

Design

Configuration 

N5K1 
conf t
vlan database 
vsan 10
vsan 30
vsan 30 interface fc1/31
    It will ask you if you want to continue because it might impact the port (disrupted) have to 
    re-register with the fabric services (send out FLOGI)
vsan 10 interface fc1/32

MDS1 
conf t
vlan database 
vsan 10
vsan 30 (in the transit path for VSAN 30) not assigning to a link 
vsan 40
vsan 10 interface fc1/17
vsan 40 interface fc1/18

MDS2
conf t
vlan database 
vsan 20
vsan 30 
vsan 40 (in the transit path for VSAN 40) not assigning to a link 
vsan 30 interface fc1/14
vsan 20 interface fc1/13

N5K2
conf t
vlan database 
vsan 20
vsan 40 
vsan 20 interface fc1/32
vsan 40 interface fc1/31

Now show int brief | in TE


Show int fc1/13 trunk vsan 
This will show you what VSAN's are passed over the TE trunk

You can dis allow VSAN 10 from port fc1/13 with:
config t
int fc1/13
switchport trunk allowed vsan 30
switchport trunk allowed vsan add 40

Show running-config from N5K1 



In the above example you would usually only have two VSAN's the would denote SAN A and SAN B

Comments