Qlogic SANbox 2
Re-set credentials and stuff
- Power off switch
- Press and hold "maintenance mode" button
- Power on switch
- Wait 60 seconds
- Telnet to 10.0.0.1 (switch's new IP address)
- Log in as "prom" (password is "prom")
- Choose appropriate re-set option (network, users, ...)
Configuration done to virgin switch
- telnet to 10.0.0.1
- Log in as "admin" (password is "password")
- "admin begin" to start admin mode (think Cisco's "enable" or "su" on UNIXy OSes)
- "set setup system" to do basic configuration (network,
SANbox2 (admin) #> set setup system A list of attributes with formatting and current values will follow. Enter a new value or simply press the ENTER key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the ENTER key to do so. Eth0NetworkDiscovery (1=Static, 2=Bootp, 3=Dhcp, 4=Rarp) [Static ] 3 AdminTimeout (dec value 0-1440 minutes, 0=never) [30 ] InactivityTimeout (dec value 0-1440 minutes, 0=never) [0 ] 60 TempMonitoringWarning (dec value 40-75 degrees Celsius) [65 ] TempMonitoringFailure (dec value 40-75 degrees Celsius) [70 ] TempFailurePortShutdown (True / False) [False ] UserAuthentication (True / False) [False ] LocalLogEnabled (True / False) [True ] RemoteLogEnabled (True / False) [False ] RemoteLogHostAddress (dot-notated IP Address) [10.0.0.254] NTPClientEnabled (True / False) [False ] True NTPServerAddress (dot-notated IP Address) [10.0.0.254] 172.16.0.1 EmbeddedGUIEnabled (True / False) [True ] False Do you want to save and activate this system setup? (y/n): [n] y System setup saved and activated. SANbox2 #>
Firmware updates
Firmware updates are performed by using an FTP client to PUT a new image to the switch. Log in as "images" (password "images"), PUT the file from Qlogic's FTP site and open up a telnet session to the switch.
SANbox2 (admin) #> image list 4.2.0.18_x86 SANbox2 (admin) #> image unpack 4.2.0.18_x86 Processing the command ... A notification with the command result will appear on the screen when the command has completed. SANbox2 (admin) #> image unpack command result: Passed. The firmware will become active after the next switch reset.
Do a "hardreset" to restart the switch with the new firmware.
Who is attached to the fabric?
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 #>
Zoning the fabric
Assuming we're starting from scratch here. All zoning info can be cleared by doing reset zoning.
A naming convention
vendor_model_serialnumber_slot_slotname_port_portnumber
For instance sun_sun_fire_V20z_XG043888262_slot_pci1_port_0
And maybe dell_powervault_128t_5lhfs11_port_0 (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 (
admin start) - Enter zoning edit mode (
zoning edit)
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 alias list and alias members 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
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
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
(This is probably unnecessary, but it won't hurt anything.)
Switch configuration backup
- Log in to the switch and issue the
config backupcommand. - FTP to the switch as user
images(password isimages.) - Make sure binary mode is turned on (FTP client specific)
get configdata- Put your configuration file in a safe place.
Switch configuration restore
This is pretty much inverse of the backup:
- Get your configuration file from your safe place.
- FTP to the switch as user
images(password isimages.) - Make sure binary mode is turned on (FTP client specific)
put configdata- Log in to the switch and issue the
config restorecommand.