This post is more than 5 years old
234 Posts
0
1999
Zone configuration doubt
Hi All,
We have noticed that cisco MDS 9509 configuration show a mix of dynamic and other set of configurations..these configurations were done by EMC CE and one of our support contractors.
What we have noticed is that EMC configuration has dynamic and other support contractor doesnt reflect that its dynamic.
What are the implications involved with such a configuration? whether we still have portability on switches by just moving the FC cables from one port to another on MDS?
Checked config on mds 9509 some have zone members with pWWN (EMC configured) and other (support contractor) configuration with fc interface. What are best recommendations while configuring the zones on mds 9509, because there are many options of adding/configuring the member with pWWN, or interface or sWWN or fcalias?
Please provide your feedback on above questions raised.
regards,
Samir
We have noticed that cisco MDS 9509 configuration show a mix of dynamic and other set of configurations..these configurations were done by EMC CE and one of our support contractors.
What we have noticed is that EMC configuration has dynamic and other support contractor doesnt reflect that its dynamic.
What are the implications involved with such a configuration? whether we still have portability on switches by just moving the FC cables from one port to another on MDS?
Checked config on mds 9509 some have zone members with pWWN (EMC configured) and other (support contractor) configuration with fc interface. What are best recommendations while configuring the zones on mds 9509, because there are many options of adding/configuring the member with pWWN, or interface or sWWN or fcalias?
Please provide your feedback on above questions raised.
regards,
Samir
AranH1
2.2K Posts
0
August 27th, 2009 08:00
First write out your current startup config to a text file. In the text file you will see how zones are written. Use the same format and pWWN entries (or Device Alias entries) from the startup config text file and copy and paste them to a new text file. This will be your new zone configuration that you want to add to the switch. Ensure that you use unique names for the zones.
When you have your text file complete that contains all the new zones you want to create it is very easy to add to the running config. For example say my new zones are in a file called new_zones.txt and I have them in the ftp root of my ftp server (I run mozilla FTP server on my SAN management server) I would add them to the running config using this method:
switch# copy ftp:new_zones.txt running-config
Follow the prompts for the ftp ip address and username and the contents of the text file will be added to the running-config.
Issue a 'show run' to ensure the changes you added are what you want and then save the running-config to the startup-config.
Let me know if you have any more questions.
AranH1
2.2K Posts
0
August 13th, 2009 12:00
I personally prefer pWWN zoning as the zone is created between the pWWN of the Storage Array port and a specific host HBA. If you use port zoning, then a cable plugged into the wrong port can affect your zoning.
I would not recommend fcalias zoning as they are limited. Instead read up on device aliases and using them for zoning. A device alias is simply an alias that is global to the fabric and is an alias for a pWWN. All of my zones use device alias for the members. This allows me to change the pWWN of a host if the HBA is replaced without manually editing a lot of zones.
I recommend you read through the section on Zoning in the Cisco MDS 9000 Family Fabric Manager Config Guide. It's under the section on Fabric Configuration.
http://cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/fm_3_4_x/fmguide.html
guy009
9 Posts
1
August 13th, 2009 12:00
Zones done by WWN will have flexibility in nature, via you can pull your fibre cable to place in any available port without modifying an existing zone.
Zones done by port# will have less-flexibility in nature, if you need to place your fibre cable into a new port becz a physical switch port fail or other reason, you need to modify existing zone to reflect new port#.
Best practice: create single Initiator zones, keep one HBA WWN in each zone along with storage member port WWN.
AranH1
2.2K Posts
0
August 13th, 2009 13:00
I disagree though about the flexibility versus security argument. I am familiar with the argument and it is an old one, but in my opinion if someone has unauthorized physical access to your switch then it dosn't matter if you have soft or hard zoning in effect. That individual can wreck all sorts of damage.
guy009
9 Posts
0
August 15th, 2009 07:00
all modern applications/technology pushing towards WWN zones, port/area based zones may disappear from discussion very soon.
Best Practice2: persistent disable all un-used ports.
If you do more swapping cables/re-organize time to time (looks you want) use WWN for flexibility, not the case use zone with WWN or port# as members.
alias is just our ease if you add meaningful names to your zone members, you can remember or work easy with zoning.
sasamir1
234 Posts
0
August 16th, 2009 02:00
Our systems are currently in production what would be the best approach to configure all zones based on pWWN with low downtime or disruption to services and what impact would it have while configuring this? (all servers have 2 HBA's installed on them)
regards,
Samir
AranH1
2.2K Posts
1
August 19th, 2009 12:00
If you are comfortable with editing the startup config file, you can use a text editor to create all the new zones and upload them to the switch in one big batch.
sasamir1
234 Posts
0
August 23rd, 2009 22:00
Thanks a lot,
Samir
modaslam
217 Posts
0
August 26th, 2009 10:00
how do we do this, I mean editing the startup config file to upload zones in one batch.
because I used to manualy create zones one by one.
modaslam
217 Posts
0
August 27th, 2009 09:00
Thanks for the post. It looks too complicated, making zone one by one was easily....
anyway right now I dont have any zoning changes to be done. May be next month or so we have a SAN refresh so I will start posting about this...
I have cisco cli guide but nothing is mentioned about this...any Great Idea. saves lots of time...