Qlogic SANbox 2 - Revision history

Adj: /* Switch configuration restore */

2012-06-09T03:52:11Z

Switch configuration restore

← Older revision		Revision as of 03:52, 9 June 2012
Line 137:		Line 137:

	== Switch configuration restore ==		== Switch configuration restore ==
	This is pretty inverse of the backup:		This is pretty much inverse of the backup:
	# Get your configuration file from your safe place.		# Get your configuration file from your safe place.
	# FTP to the switch as user '''<code>images</code>''' (password is '''<code>images</code>'''.)		# FTP to the switch as user '''<code>images</code>''' (password is '''<code>images</code>'''.)

Adj: /* Switch configuration backup */

2012-06-08T15:55:06Z

Switch configuration backup

← Older revision		Revision as of 15:55, 8 June 2012
Line 135:		Line 135:
	# '''<code>get configdata</code>'''		# '''<code>get configdata</code>'''
	# Put your configuration file in a safe place.		# Put your configuration file in a safe place.

			== Switch configuration restore ==
			This is pretty inverse of the backup:
			# Get your configuration file from your safe place.
			# FTP to the switch as user '''<code>images</code>''' (password is '''<code>images</code>'''.)
			# Make sure binary mode is turned on (FTP client specific)
			# '''<code>put configdata</code>'''
			# Log in to the switch and issue the '''<code>config restore</code>''' command.

Adj: /* Save your work */

2012-06-07T22:51:57Z

Save your work

← Older revision		Revision as of 22:51, 7 June 2012
Line 128:		Line 128:

	(This is probably unnecessary, but it won't hurt anything.)		(This is probably unnecessary, but it won't hurt anything.)

			== Switch configuration backup ==
			# Log in to the switch and issue the '''<code>config backup</code>''' command.
			# FTP to the switch as user '''<code>images</code>''' (password is '''<code>images</code>'''.)
			# Make sure binary mode is turned on (FTP client specific)
			# '''<code>get configdata</code>'''
			# Put your configuration file in a safe place.

Adj: /* Create a zone, allowing two devices to communicate with each other */

2012-06-06T21:24:08Z

Create a zone, allowing two devices to communicate with each other

← Older revision		Revision as of 21:24, 6 June 2012
Line 105:		Line 105:

	More interesting setups are possible. We could have another HBA in our Sun Fire V20z, or a disk array with several fabric connections. In those cases, create aliases for each port on each device.		More interesting setups are possible. We could have another HBA in our Sun Fire V20z, or a disk array with several fabric connections. In those cases, create aliases for each port on each device.

			As a general rule, you want initiators to see targets and targets to see initiators. You do not want initiators seeing other initiators or targets seeing other targets. Ergo, this zone should really have a name inidicating that it connects the HBA in slot PCI 1 of the V20z to only to the FC port on the PowerVault 128T. I'm not feeling that pedantic today.

			For other, not SCSI sorts of protocols (IP over FibreChannel, maybe), this rule does not hold.

	=== Create a set of zones to activate ===		=== Create a set of zones to activate ===

Adj: /* Create a zone, allowing two devices to communicate with each other */

2012-06-06T21:12:30Z

Create a zone, allowing two devices to communicate with each other

← Older revision		Revision as of 21:12, 6 June 2012
Line 103:		Line 103:
	SANbox2 (admin-zoning) #> zone add sun_fire_v20z_XG043888262_and_dell_powervault_128t_5lhfs11 sun_sun_fire_V20z_XG043888262_slot_pci1_port_0		SANbox2 (admin-zoning) #> zone add sun_fire_v20z_XG043888262_and_dell_powervault_128t_5lhfs11 sun_sun_fire_V20z_XG043888262_slot_pci1_port_0
	SANbox2 (admin-zoning) #> zone add sun_fire_v20z_XG043888262_and_dell_powervault_128t_5lhfs11 dell_powervault_128t_5lhfs11_port_0		SANbox2 (admin-zoning) #> zone add sun_fire_v20z_XG043888262_and_dell_powervault_128t_5lhfs11 dell_powervault_128t_5lhfs11_port_0

			More interesting setups are possible. We could have another HBA in our Sun Fire V20z, or a disk array with several fabric connections. In those cases, create aliases for each port on each device.

	=== Create a set of zones to activate ===		=== Create a set of zones to activate ===

Adj: /* Save your work */

2012-06-06T21:09:17Z

Save your work

← Older revision		Revision as of 21:09, 6 June 2012
Line 120:		Line 120:
	SANbox2 (admin) #> zoning edit		SANbox2 (admin) #> zoning edit
	SANbox2 (admin-zoning) #> zoning save		SANbox2 (admin-zoning) #> zoning save

			(This is probably unnecessary, but it won't hurt anything.)

Adj: /* Zoning the fabric */

2012-06-06T21:01:58Z

Zoning the fabric

← Older revision		Revision as of 21:01, 6 June 2012
Line 78:		Line 78:

	=== A naming convention ===		=== A naming convention ===
			<code>''vendor''_''model''_''serialnumber''_slot_''slotname''_port_''portnumber''</code>
	vendor_model_serialnumber_slot_slotnumber_port_portnumber

			For instance '''<code>sun_sun_fire_V20z_XG043888262_slot_pci1_port_0</code>'''
	For instance sun_sun_fire_V20z_XG043888262_slot_1_port_0

			And maybe '''<code>dell_powervault_128t_5lhfs11_port_0</code>''' (this is a tape library and doesn't really have multiple slots to put cards into.

			=== Getting started ===
			# Log in to the switch
			# Enter admin mode ('''<code>admin start</code>''')
			# Enter zoning edit mode ('''<code>zoning edit</code>''')

			=== Create aliases and put WWNs on them ===
			Create aliases to symbolically reference the world wide '''port''' names (WWPNs or PortWWNs) on the devices attached to the fabric.

			SANbox2 (admin-zoning) #> alias create sun_sun_fire_V20z_XG043888262_slot_pci1_port_0
			SANbox2 (admin-zoning) #> alias add sun_sun_fire_V20z_XG043888262_slot_pci1_port_0 21:00:00:e0:8b:9c:c2:f5

			SANbox2 (admin-zoning) #> alias create dell_powervault_128t_5lhfs11_port_0
			SANbox2 (admin-zoning) #> alias add dell_powervault_128t_5lhfs11_port_0 10:00:00:e0:02:21:f3:0d

			Current aliases and their members can be looked at with the '''<code>alias list</code>''' and '''<code>alias members</code>''' commands.

			=== Create a zone, allowing two devices to communicate with each other ===
			SANbox2 (admin-zoning) #> zone add sun_fire_v20z_XG043888262_and_dell_powervault_128t_5lhfs11 sun_sun_fire_V20z_XG043888262_slot_pci1_port_0
			SANbox2 (admin-zoning) #> zone add sun_fire_v20z_XG043888262_and_dell_powervault_128t_5lhfs11 dell_powervault_128t_5lhfs11_port_0

			=== Create a set of zones to activate ===
			Brocade would call this a "configuration." QLogic calls it a "zoneset."

			SANbox2 (admin-zoning) #> zoneset create fnord_20120606_0
			SANbox2 (admin-zoning) #> zoneset add fnord_20120606_0 sun_fire_v20z_XG043888262_and_dell_powervault_128t_5lhfs11

			With additional servers or devices, more zones will be added to the zoneset.

			=== Activate the zoneset ===
			SANbox2 (admin) #> zoneset activate fnord_20120606_0

			=== Save your work ===
			Activating your zoneset will exits zoning edit mode, you'll need to get back into it.

			SANbox2 (admin) #> zoning edit
			SANbox2 (admin-zoning) #> zoning save

Adj: /* Who is attached to the fabric? */

2012-06-06T20:21:17Z

Who is attached to the fabric?

← Older revision		Revision as of 20:21, 6 June 2012
Line 72:		Line 72:

	SANbox2 #>		SANbox2 #>

			== Zoning the fabric ==

			Assuming we're starting from scratch here. All zoning info can be cleared by doing '''<code>reset zoning</code>'''.

			=== A naming convention ===
			vendor_model_serialnumber_slot_slotnumber_port_portnumber

			For instance sun_sun_fire_V20z_XG043888262_slot_1_port_0

Adj: /* Who is attached to the fabric? */

2012-06-06T19:56:47Z

Who is attached to the fabric?

← Older revision		Revision as of 19:56, 6 June 2012
Line 63:		Line 63:

	== Who is attached to the fabric? ==		== Who is attached to the fabric? ==
	show ns		SANbox2 #> show ns

			Seq Domain Port Port
			No ID ID Type COS PortWWN NodeWWN
			--- ------ ------ ---- --- ------- -------
			1 1 (0x1) 010001 NL 3 10:00:00:e0:02:21:f3:0d 10:00:00:e0:02:01:f3:0d
			2 1 (0x1) 010200 N 3 21:00:00:e0:8b:9c:c2:f5 20:00:00:e0:8b:9c:c2:f5

			SANbox2 #>

Adj: /* Firmware updates */

2012-06-06T19:55:04Z

Firmware updates

← Older revision		Revision as of 19:55, 6 June 2012
Line 61:		Line 61:

	Do a "hardreset" to restart the switch with the new firmware.		Do a "hardreset" to restart the switch with the new firmware.

			== Who is attached to the fabric? ==
			show ns