9124 and VSANs

Hi, I am new to SANs and have what is hopefully a simple question. Our current setup is very simple, two 9124 switches licensed for 16 ports each, no interconnection between the two. On switch 1 all ports are configured as VSAN 1, on switch 2 they are all VSAN 2. All devices in our small SAN connect to each of the 9124's.
We would like to expand the SAN to another building on our campus, the devices in the other building are not "critical" so redundancy is not necessary.
For this other building I was thinking we could get one more 9124 with 16 active ports and configure 8 ports with VSAN 1 and 8 ports with VSAN 2, then connect the small number of devices to each VSAN.
Is it really this simple, I am assuming I'm missing something...

What you propose is just fine. If the 3rd site with the 9124 with 8 ports in VSAN 1 and 8 ports in VSAN 2 need to communicate with the devices back in the original 2 switches, you will need to use 1 port from each VSAN as an ISL back to the original swtich. It will also mean that you need to use of the 16 ports in those switches for the ISL as well.
If the devices in the new switch do not need connectivity back to the original switches, then set port 1-8 in VSAN 1, and port 9-16 in VSAN 2 and your done.
Hope this helps,
Mike

Similar Messages

Vfc and vsan on nexus 5K interface

Hi,
I am seeing the following configuration on one of the 5K interfaces & related subsequent configs follow;
int eth1/2
description test1 vfc-1030
switchport mode trunk
spanning-tree port type edge trunk
spanning-tree bpduguard enable
sh run int vfc 1003
version 5.2(1)N1(3)
interface vfc1030
bind interface Ethernet1/2
switchport trunk allowed vsan 120
switchport description test1
no shutdown
sh vsan 120
vsan 120 information
         name:VSAN-120 state:active
         interoperability mode:default
         loadbalancing:src-id/dst-id/oxid
         operational state:up
Now the vfc1030 interface says only allow vsan 120 over the trunk, whereas eth1/2 switch port status tells me that all vlans(1-4094) are allowed on this interface.
So , how does this work here? which one takes precedence and what vlans actually flow over this.
I am confused by this linkages, appreciate if some one can shed some light on the above please.
Thanks in advance!

What NX-OS version are you using? It is available starting NX-OS 5.1(3)N2(1) on the Nexus 5500:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/qos/521_n1_1/b_5k_QoS_Config_521N11_chapter_01000.html#topic_93B8067633394356B790D6F1E522CC61
HTH,
jerry

Initial UCS Setup: Ethernet Uplink and VSAN

Hi All,
I'm beginner with UCS and had received my loan unit yesterday. I've connected all the cables and have two question:
1. My loan unit come with a Catalyst 3750X with expansion module of 10GE (C3KX-NM-10GE). I've configure the port 5 in both FI and the Catalyst TE port as trunk but UCSM detected it down (noconnect). Do I have to create a service profile first before the link went up?
2. We dont have any MDS and plan to directly connect the Netapp storage using the uplink FC port. Can we still use the VSAN features? (as per understanding the far-end port device must has NPIV support like MDS switch)
Thanks!
Rgds,
Nazri

On the UCS Fabric Interconnect (FI) make sure the port is confiugred as an uplink port not a server port. Make sure you created all the vlans on both the 3750 and the FI. Since you have just a single port do not try to use port-channels. Other than that its a connectivity problem so troubleshoot it as you normally would. Try isolating the issue to the FI or the 3750.
You can't use VSANs if you are going to directly connect the netapp to the FI. I'm pretty sure the Netapp does not understand VSAN tagging. You'll need an MDS or N5K if you want something more complex.

EVO:RAIL and VSAN

Are there VSAN benchmarks on EVO:RAIL compared with traditional server based VSAN?

Sorry, I'm a bit confused about the question - you mean a comparison between EVO:RAIL and VMware Virtual SAN - or do you mean benchmarks between EVO:RAIL/VSAN - and conventional Storage Array connected over ethernet (iSCIS/NFS) or FC block storage?
For VSAN there's been a number of articles about performance which you might find useful - one caveat. In this release EVO:RAIL supports 16 nodes per cluster whereas Virtual SAN supports 32-nodes per cluster - so some of the sliding scale doesn't apply...
http://blogs.vmware.com/performance/2014/09/microsoft-exchange-server-shows-great-performance-vmware-virtual-san.html
http://blogs.vmware.com/performance/2014/08/web-2-0-applications-vmware-virtual-san.html
http://blogs.vmware.com/performance/2014/03/vdi-performance-benchmarking-vmware-virtual-san-5-5.html
My colleague Duncan Epping has written extensively on some of the considerations around VSAN:
http://www.yellow-bricks.com/2013/11/14/vsan-performance-many-sas-low-capacity-vs-sata-high-capacity/
and there's been some independent work too:
http://www.storagereview.com/vmware_vsan_posts_2_million_iops

Cisco 9124 and alert manager - showing sensor alerts

I currently have 2 Cisco Fiber 9124 switches in my environement. Everything seems to be working fine except I'm receiving these warnings every so often:
9/26/2013 01:25 PM
Sensor 26195
Alert me when any hardware component goes into a warning or critical state
9/26/2013 01:25 PM
Sensor 26196
Alert me when any hardware component goes into a warning or critical state
9/26/2013 01:25 PM
Sensor 26164
Alert me when any hardware component goes into a warning or critical state
9/26/2013 01:25 PM
Sensor 26186
Alert me when any hardware component goes into a warning or critical state
9/26/2013 01:25 PM
Sensor 26132
Alert me when any hardware component goes into a warning or critical state
I can't find anything in the logs stating there is a failure and when I check the power everything shows ok. Anybody have an idea what this is about? Could it just be a power fluctuation and by the time I get in to see the switch everything is ok?
Thanks

Hi All,
-check the load on the IPS module cpu/mem
-disable unwanted signatures..
run it to clear the signature statistics in peak hours
" show statistics virtual-sensor clear "
run it after 5 mins in peak hours
"show statistics virtual-sensor "
you can confirm by checking the signature details using below link, there by disable unwanted sigs.
http://tools.cisco.com/security/center/search.x
regards
rajesh

Cisco MDS9216i VSAN not merging and FCIP up but not trunking

I have configured FCIP between DC and DR IPSAN switches. FCIP is up but not trunking. On both switches trunk mode is on. Hence my VSAN (id 20 on both switches) not merging.
See below FCIP interface status...
fcip1 is up
Hardware is GigabitEthernet
Port WWN is 20:10:00:0d:ec:35:68:40
Peer port WWN is 20:10:00:0d:ec:34:d6:80
Admin port mode is auto, trunk mode is on
snmp traps are enabled
Port mode is E, FCID is 0x9a0002
Port vsan is 1
Speed is 1 Gbps
Using Profile id 1 (interface GigabitEthernet1/1)
Peer Information
Peer Internet address is 10.128.1.95 and port is 3225
Write acceleration mode is configured off
Tape acceleration mode is configured off
Tape Accelerator flow control buffer size is automatic
Ficon Tape acceleration configured off for all vsans
IP Compression is disabled
Special Frame is disabled
Maximum number of TCP connections is 2
Time Stamp is disabled
QOS control code point is 0
QOS data code point is 0
B-port mode disabled
TCP Connection Information
2 Active TCP connections
Control connection: Local 10.132.1.95:65260, Remote
10.128.1.95:3225
Data connection: Local 10.132.1.95:65262, Remote 10.128.1.95:3225
138 Attempts for active connections, 16 close of connections
TCP Parameters
Path MTU 1420 bytes
Current retransmission timeout is 200 ms
Round trip time: Smoothed 22 ms, Variance: 4 Jitter: 661 us
Advertized window: Current: 2412 KB, Maximum: 2412 KB, Scale: 5
Peer receive window: Current: 2047 KB, Maximum: 2047 KB, Scale: 5
Congestion window: Current: 1170 KB, Slow start threshold: 1950 KB
Current Send Buffer Size: 2412 KB, Requested Send Buffer Size: 0 KB
CWM Burst Size: 50 KB
5 minutes input rate 328 bits/sec, 41 bytes/sec, 0 frames/sec
5 minutes output rate 256 bits/sec, 32 bytes/sec, 0 frames/sec
3551 frames input, 419612 bytes
3443 Class F frames input, 406076 bytes
108 Class 2/3 frames input, 13536 bytes
8 Reass frames
0 Error frames timestamp error 0
3572 frames output, 324264 bytes
3464 Class F frames output, 312996 bytes
108 Class 2/3 frames output, 11268 bytes
0 Error frames
I have one more pair of IPSAN switches. I configured them which are working fine. FCIP interface is showing "trunking". I have compared the configuration of working and non-working pairs and both are same (except the IP address of locate and remote and VSAN ids).
Please suggest what can be done. If I get the FCIP port in trunking, I hope VSAn will start merging.

The problem is here -
Port mode is E, FCID is 0x9a0002
Port vsan is 1
What it says is yes, it is a trunk , but only an E port. So it is only trunking the port VSAN 1. What you want to do is change it to a Trunking E port, which allows it to carry multiple vsans over the link.
The other option is to change the port VSAN to 20. That will get you up, but if you need to trunk more vsans in the future you will still have to change the FCIP to a TE port.
When everything is right it should look something like this -
P28-MDS-9216# sho interface fcip 2
fcip2 is trunking
Hardware is GigabitEthernet
Port WWN is 20:42:00:0d:ec:0c:e6:40
Peer port WWN is 20:42:00:0d:65:6a:18:40
Admin port mode is auto, trunk mode is on
snmp traps are enabled
Port mode is TE
Port vsan is 1
Speed is 1 Gbps
Trunk vsans (admin allowed and active) (1,20)
Trunk vsans (up) (1,20)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
Using Profile id 1 (interface GigabitEthernet2/1)
Peer Information
Peer Internet address is 10.2.28.2 and port is 3225
Write acceleration mode is configured off
Tape acceleration mode is configured off
Tape Accelerator flow control buffer size is automatic
Ficon Tape acceleration configured off for all vsans
IP Compression is disabled
Special Frame is disabled
Maximum number of TCP connections is 2
Time Stamp is disabled
The document for configuring FCIP trunks on the MDS is available here -
http://www.cisco.com/univercd/cc/td/doc/product/sn5000/mds9000/3_0/clicnfg/part6/cfcip.htm
If you found this helpful please rate it -
-- Colin McNamara

Changing VSAN ID and FCoE VLAN ID

Currently our VSAN ID and FCoE VLAN ID are exactly the same, 1. In order to update the firmware on our fabric interconnects, I need to change one or the other with the FCoE VLAN ID being the most likely choice. When our VSAN was created in UCSM, it was created as 1 shared VSAN rather than one VSAN for fabric A and another for fabric B. I was told that if I change the FCoE VLAN ID, it's going to cause a short blip due to the way the VSAN was created. Has this ever happened to anyone and if so, what was your experience? How long of an outage can I expect from this change?

There are misc. aspects that you should consider
- Vlan 1 and Vsan 1 should never be used for any operational purposes (eg. caveats with disjoint vlans)
- Same vlan should be defined in both fabric a and b (nic teaming !)
- vsan's should be different for fabric a and b; a cable connecting fabric a and b will not result in a fabric merge, and therefore a possible disaster
- FCoE vlans for vsan #x are best placed with a high offset + #x
As you said, changing the FCoE vlan is disruptive, link initialization, flogi... have to be done; usually a OS should survive such a short interrupt.
However, changing the Vsan # might also require zoning changes (if you use fc alias which are per vsan; device alias are global, and therefore don't have this problem).
Changing vsan # might also require a modification of the FI FC uplink ports
Good luck

Shoul I upgrade MDS 9222i and MDS 9124 both have SANOS 3.3.2 to 3.3.5?

Hi guys,
I have 2 MDS 9222i, 2 MDS 9124 and 10 MDS Blades Switches (IBM Blades) all have SANOS 3.3.2.
All those swicthes are attached to external drives (IBM DS4800) IBM requested to upgrade this DS4800 firmware level but in order to do that they told me that I need a new SANOS I plan to upgrade it to SANOS 3.3.5 can someone tell me if this SANOS works alright? or What SANOS do yoy recommend me?
Thanks in advance

The Cisco TAC will always defer to your Original Storage provided when asked which
image to run, as they (the Original Storage providers) qualify our images for use with their
devices.
Regards,
Ken

Merging together two different VSANs

Hi all.
I need to migrate an actual fabric based on Cisco 9124 and 9134, to a brand new Cisco Director 9506. Actually I have two fabric (fabric 1 and 2) which are not currently merging together. VSAN are not in use in the actual scenario.
I would like to move to a VSAN topology. In order to proceed with migration from actual fabric, my idea would be to create two separate VSANs on the 9506 (VSAN 10 and VSAN20). Then I could merge fabric 1 with VSAN 10 and fabric2 witrh VSAN20. Unfortunately I can't use IVR, then the idea would be to disable trunking on ISLs so I could migrate zones to new directors but maintaining the separation between fabric 1 and 2 (from actual physical separation to new logical one). I am aware merging different VSANs is discouraged, but it is documented by Cisco ("In some cases, you may need to merge traffic from different port VSANs across a non-trunking ISL. If so, disable the trunking protocol. "). Idea would be maintain the ISL for the time required to migrate all the gears (servers and disk arrays) to the new directors. My question then: have you got any experiences or suggestions ? Could I proceed with this unusual merge hoping not encounter any outages ? Many thanks !

Let me get this straight, today you have 2 physical switches each is a separate fabric, they do not talk to eachother. You are moving to a single 9506 director. The current switches do not use VSAN's, but you are asking if you can create VSAN 10 and 20 on the director.
Yes, this is fine. You should create VSAN 10 and 20 on the director. Connect fabric 1 to VSAN 10. You should use an E-port and disable trunking protocol like you suggested. You can do the same with fabric 2 and VSAN 20. Then copy over all the zones and move the stuff over one port at a time if you like.
There is no issue with what you are discussing. Keep in mind normal fabric "rules" apply, such as timers matching, and other parameters to avoid an isolation. Good luck!
Brian

How to Connect a 9124 to another 9124

Hey all,
I'm hoping someone can help me with this. I have two 9124's Im trying to connect to each other. One is a 9124blade in a HP c7000 chassis and the other is a standalone 9124. I have 4 ports configured on each switch in a port channel with port mode "E" on the individual ports and on the port channel. Following Cisco documentation the trunk mode on the blades are set to trunk mode "trunk" and the standalone are set to trunk mode "auto" The port channel ID's are unique on each switch, and the speed it set to auto on both switches
The standalone 9124 have our existing zone config and I need to keep that, the blade 9124's dont need any zoning I just want them to pass the wwid's of the HP blades to the standalone switches.
The problem is when I admin up the ports they do not link I get link down on both switches on all ports. Can anyone help with any ideas?
Thanks in advance

Thanks for the reply Ken
so far I have gotten the links to come up as TE ports, but what seems to be happening is that the existing 9124 that has all of the zoning info becomes unmanageable as soon as I bring up the link. I have to delete the new switch and the existing one from fabric manager and re-add them again.
I simply want to connect the new "edge 9124" to the existing "core" 9124 and have the edge do nothing but pass wwid's to the core(existing) 9124 that has the zone config.
Both switches have different domain ID's
Both Domain ID are allowed the the domain Manager
The core existing 9124 has a higher priority the the new switch
the link(s) are configed as E ports and trunking is on (shows up as a TE port)
all vsans are allowed across the link
Thanks in advance

Renaming default Datacenter, Cluster, and Datastore object names in EVO:RAIL

Hello,
The Datacenter, Cluster, and vSAN Datastore objects in my newly-installed EVO:RAIL appliance all default to a label of "MARVIN-...". Is it safe to rename these labels appropriate to my environment, such as a geographic location for my Datacenter object? I suspect that it is okay because the underlying UID will not change, but am looking for confirmation from someone who has successfully done this in a lab or production environment and who has also been successful in applying EVO:RAIL patches afterward.
Thanks in advance.

Just to close the loop, I successfully renamed the datacenter, cluster, and vSAN objects in vCenter Server.
I kept a close watch on Log Insight at each step, and did log one error that I found suspicious following the object rename of the vSAN datastore:
2015-01-29T19:03:27.158Z <My 4th Host's FQDN> Hostd: [783C2B70 info 'DiskLib'] DISKLIB-LINK :DiskLinkGetSpaceUsedInfo: Failed to get the file system unique id for file vsan://118eb054-f123-469a-d542-XXXXXXXXXXXX, using id as "remote"
Where in my case the 4th host happens to currently be the HA master. I'm guessing this was just a transient error as it hasn't reappeared in the last 30 minutes, but I'll keep an eye out for it. There was no corresponding error viewed in vCenter Server, and I seem to be able to refresh the vSAN storage counter without issue.
Thanks again.

Best Way To Connect 6120 FICs And B250/200M2s To 2 SANs

We have x2 6120 FICs connected currently to an EMC CX4 via x4 FC links in the expansion module of each FIC. We have x2 FC links in each FIC left over. We have a new VNX SAN and in order to migrate our vSphere infrastructure from the old SAN to the new SAN, I need some advice on the best manner in which to have the B250 M2s and B200 M2s with their M81KRs be able to 'see' & communicate with both SANs in order to accomplish the migration. I have seen some discussion on adding HBA's and 'pinning' them to the appropriate FC links & I have also seen some discussion about using VSANs. The last time we did this, we just daisy chained the new SAN via the old but we were keeping the same SAN switches. In our current scenario, we will need to hook the FIC's to the new SAN switches regardless. Any thoughts or help will be greatly appreciated.
Thank you.

The following procedure has been done many times with success
- don't use pinning, it's a management nightmare
- use separate physical links and VSAN's to connect the new SAN
- create additional vhba in the service profile, and move them to the new VSAN
This allows you to migrate, read from the old storage, and write to the new one (e.g. with storage vmotion)

UCS FCoE VSAN 1 down

Any way to clear these faults?
F1081 2013-02-21T15:04:24.658 157614 san Member 1/31 of Port-Channel 8 on fabric interconnect A is down, membership: down
F1081 2013-02-21T15:04:24.658 157613 san Member 1/32 of Port-Channel 8 on fabric interconnect A is down, membership: down
Have FCoE setup between 6248s and Nexus 5548s. Using VSAN 20 on Fabric A and VSAN 40 on Fabric B.
Why is VSAN 1 trying to initialize when I have the FCoE port-channel mapped to VSAN 20 in UCSM? Any way to set the allowed trunk vsan list?
Everything is working just would like the anoying faults to go away

Hi,
This sounds like:
FCoE Uplink vsan membership fault for any vsan not configured upstream
Symptom:
Fabric Vsan Membership Down fault message on FCoE uplink portsSeverity: Major
Code: F1083
Name: Fabric Vsan Membership Down
Conditions:
Observed with UCSM 2.1 and when FCoE uplink port is configured on the Fabric Interconnect
Workaround:
None.Error message is cosmetic.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCud81857
I'd open a case on it and have them link it to the bug if it is indeed the case

5548UP VSAN Flogi Info

We are working with a Nexus 5548UP connected to a EMC VNX5500 and four Dell R610 servers
We created VSAN 332 and VLAN 330
Here is the config.
class-map type qos class-fcoe
class-map type queuing class-fcoe
match qos-group 1
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type network-qos class-fcoe
match qos-group 1
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy
slot 1
port 1-32 type ethernet
vlan 330
fcoe vsan 332
vsan database
vsan 332
fcdomain fcid database
vsan 332 wwn 50:06:01:69:3e:e4:00:d6 fcid 0x320000 dynamic
vsan 332 wwn 50:06:01:61:3e:e4:00:d6 fcid 0x320001 dynamic
vsan 332 wwn 21:00:00:c0:dd:1a:69:c7 fcid 0x320002 dynamic
vsan 332 wwn 21:00:00:c0:dd:1a:6a:4f fcid 0x320003 dynamic
vsan 332 wwn 21:00:00:c0:dd:1a:68:07 fcid 0x320004 dynamic
vsan 332 wwn 21:00:00:c0:dd:1a:67:db fcid 0x320005 dynamic
interface vfc17
bind interface Ethernet1/17
switchport trunk allowed vsan 332
switchport description HS-XEN-1
no shutdown
interface vfc18
bind interface Ethernet1/18
switchport trunk allowed vsan 332
switchport description HS-XEN-2
no shutdown
interface vfc19
bind interface Ethernet1/19
switchport trunk allowed vsan 332
switchport description HS-XEN-3
no shutdown
interface vfc20
bind interface Ethernet1/20
switchport trunk allowed vsan 332
switchport description HS-XEN-4
no shutdown
interface vfc31
bind interface Ethernet1/31
switchport trunk allowed vsan 332
no shutdown
interface vfc32
bind interface Ethernet1/32
switchport trunk allowed vsan 332
no shutdown
vsan database
vsan 332 interface vfc17
vsan 332 interface vfc18
vsan 332 interface vfc19
vsan 332 interface vfc20
vsan 332 interface vfc31
vsan 332 interface vfc32
interface Ethernet1/17
description HS-XEN-1
switchport mode trunk
switchport access vlan 330
switchport trunk allowed vlan 34,300,310,320,330
spanning-tree port type edge trunk
interface Ethernet1/18
description HS-XEN-2
switchport mode trunk
switchport access vlan 330
switchport trunk allowed vlan 34,300,310,320,330
spanning-tree port type edge trunk
interface Ethernet1/19
description HS-XEN-3
switchport mode trunk
switchport access vlan 330
switchport trunk allowed vlan 34,300,310,320,330
spanning-tree port type edge trunk
interface Ethernet1/20
description HS-XEN-4
switchport mode trunk
switchport access vlan 330
switchport trunk allowed vlan 34,300,310,320,330
spanning-tree port type edge trunk
interface Ethernet1/31
description VNX (B8) B1-P0
switchport mode trunk
switchport access vlan 330
switchport trunk allowed vlan 330
spanning-tree port type edge trunk
interface Ethernet1/32
description VNX (A8) A1-P0
switchport mode trunk
switchport access vlan 330
switchport trunk allowed vlan 330
spanning-tree port type edge trunk
When we change the VSAN and VLAN, the flogi information dissapears for the EMC VNX5500. The Flogi information is still present for the four Dell servers
changed VSAN and VLAN
vlan 102
fcoe vsan 1002
vlan 300,310,320,330
vpc domain 100
vsan database
vsan 1002
fcdomain fcid database
vsan 1002 wwn 21:00:00:c0:dd:1a:69:c7 fcid 0xae0000 dynamic
vsan 1002 wwn 21:00:00:c0:dd:1a:67:db fcid 0xae0001 dynamic
vsan 1002 wwn 21:00:00:c0:dd:1a:6a:4f fcid 0xae0002 dynamic
vsan 1002 wwn 21:00:00:c0:dd:1a:68:07 fcid 0xae0003 dynamic
interface vfc17
bind interface Ethernet1/17
switchport trunk allowed vsan 1002
switchport description HS-XEN-1
no shutdown
interface vfc18
bind interface Ethernet1/18
switchport trunk allowed vsan 1002
switchport description HS-XEN-2
no shutdown
interface vfc19
bind interface Ethernet1/19
switchport trunk allowed vsan 1002
switchport description HS-XEN-3
no shutdown
interface vfc20
bind interface Ethernet1/20
switchport trunk allowed vsan 1002
switchport description HS-XEN-4
no shutdown
interface vfc31
bind interface Ethernet1/31
switchport trunk allowed vsan 1002
no shutdown
interface vfc32
bind interface Ethernet1/32
switchport trunk allowed vsan 1002
no shutdown
vsan database
vsan 1002 interface vfc17
vsan 1002 interface vfc18
vsan 1002 interface vfc19
vsan 1002 interface vfc20
vsan 1002 interface vfc31
vsan 1002 interface vfc32
interface Ethernet1/17
description HS-XEN-1
switchport mode trunk
switchport access vlan 102
switchport trunk allowed vlan 34,300,310,320,330
spanning-tree port type edge trunk
interface Ethernet1/18
description HS-XEN-2
switchport mode trunk
switchport access vlan 102
switchport trunk allowed vlan 34,300,310,320,330
spanning-tree port type edge trunk
interface Ethernet1/19
description HS-XEN-3
switchport mode trunk
switchport access vlan 102
switchport trunk allowed vlan 34,300,310,320,330
spanning-tree port type edge trunk
interface Ethernet1/20
description HS-XEN-4
switchport mode trunk
switchport access vlan 102
switchport trunk allowed vlan 34,300,310,320,330
spanning-tree port type edge trunk
interface Ethernet1/31
description VNX (B8) B1-P0
switchport mode trunk
switchport access vlan 102
switchport trunk allowed vlan 102
spanning-tree port type edge trunk
interface Ethernet1/32
description VNX (A8) A1-P0
switchport mode trunk
switchport access vlan 102
switchport trunk allowed vlan 102
spanning-tree port type edge trunk
Is there a set procedure for changing VLAN and VSAN's ?
Thanks!

We found the problem. The VNX uses VLAN tagging. The original install team set the wrong vlan. We changed the VNX vlan and the FLOGI's are now visible.
Regards
JG

Nexus 5000 and MDS 9509 FC

Greetings Everyone,
I have been beating my head on the desk for the last few days tring to get a FC connection established between a NX5010 and a MDS9509. The 9509 is running the legacy storage systems but we are moving to FCoE on the NEXUS. I am not getting link on the fiber between the 2 devices. I have checked and verified the MM cable both SFP units have been swapped out.
I keep getting the following on the MDS when I bring up the interface.
2011 Apr 22 20:39:42 MDS9509_01 %PORT-5-IF_DOWN_INACTIVE: %$VSAN 1%$ Interface fc1/9 is down (Inactive)
fc1/9 is down (Inactive)
    Port description is Connection to Nexus 5kSW01 [FC2/1]
    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
    Port WWN is xxxxxxxxxxxxxxx
    Admin port mode is auto, trunk mode is on
On the NX 5010 I have
fc2/1 is down (Link failure or not-connected)
    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
    Port WWN is xxxxxxxxxxxxxxxxx
    Admin port mode is auto, trunk mode is on
    snmp link state traps are enabled
    Port vsan is 1
    Receive data field Size is 2112
I dont have anything really configured I am just tring to get a link to establish. If someone has a sample configuration for this or a suggestion, I would certainly appreciate it.
Cheers
Mike

Yes, the trunk interfaces must be assigned into active VSAN, even though they are trunk (TE) ports and might not even be trunking that VSAN.
There is no concept of Spanning-Tree in Fibre Channel. Don't confuse Ethernet with FC, a lot of things a different. VSANs are similar to VLANs and they allow you to segregate traffic, and VSAN trunking also has the same goal as VLAN trunking, but that's where the similarity with Ethernet ends.
The loop prevention is achieved through FSPF (FC shortest path first) algorithm. Think of it as OSPF. Each VSAN runs its own FSPF process. Each FC switch has a unique Domain ID (value from 1 to 254) assigned by the FC Domain process in each VSAN. FSPF process is automatically on, it detects other switches and determines a best path between domain IDs based on FSPF interface costs (per VSAN). So it's actually more like IP routing than Ethernet STP. FC addresses are 3-byte FCID addresses where the first byte is the domain ID of the switch that the node (storage or HBA) is connected to. You are probably familiar with WWN's, but WWN's are not actually used in fibre channel frame headers, instead they are mapped to FCIDs.
FC/SANOS is a fun topic, consider becoming CCIE Storage expert (http://www.iementor.com/ccie-storage-workbook-walkthrough-bundle-p-338.html)
I'm not sure why it took 2 minutes for interface to come up, it should have been instanteneous, are you saying the actual interfaces didn't go Up for two minutes after changes were made?
There's no VPC concept in fibre channel. There is a regular port channel that Cisco has on MDS/NX-OS FC switches. Yes, you can configure Port channel between NX-OS on N5K and SAN-OS/NX-OS on MDS9K. It must be configured between two switches and can't span multiple switches.

9124 and VSANs

Similar Messages

Maybe you are looking for