Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Design question around VSANs

We are leveraging the Nexus 5K for our FC switching to boot our UCS blades. I am wondering what the best design is for the following situation.

Active / Active NetApp HA pair.

2 FC target ports from each NetApp head in the HA pair to the SAN switches (Nexus 5K in our case).

1 port from each NetApp head to each of the Nexus 5010s.

Should I have 1 VSAN on each 5010 with a port from each NetApp head in it or should I have 1 common VSAN between the 5010s?

Any feedback on this would be appreciated.

Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Design question around VSANs

A good best practice is to use different VSAN numbering on each fabric.

For Fabric A (or 1) use odd numbered VSANs (3, 5, etc.)

For Fabric B (or 2) use even mumbered VSANs (2, 4, etc.)

It provides a visual cue for the operator to let them know which fabric they are making changes to. Additionally, in the case of an inadvertent ISL connect between the two fabrics you won't merge your A and B fabric zonesets (I've seen it happen). Dont' put any active traffic in VSAN 1 for the same reason.

2 REPLIES
Cisco Employee

Re: Design question around VSANs

A good best practice is to use different VSAN numbering on each fabric.

For Fabric A (or 1) use odd numbered VSANs (3, 5, etc.)

For Fabric B (or 2) use even mumbered VSANs (2, 4, etc.)

It provides a visual cue for the operator to let them know which fabric they are making changes to. Additionally, in the case of an inadvertent ISL connect between the two fabrics you won't merge your A and B fabric zonesets (I've seen it happen). Dont' put any active traffic in VSAN 1 for the same reason.

New Member

Re: Design question around VSANs

Thanks. That is how I had it setup while testing with our LAB equipment but its not an HA pair so I wanted to make sure I wasn't missings something before rolling towards production usage.

498
Views
0
Helpful
2
Replies