The September 1999 release of firmware for the SilkWorm 1000-family of FC Switches (Silkworm and Silkworm Express) is named V1.6c3.
This chapter contains the following sections:
ATTENTION On DYNIX/ptx V4.5.x, all FC switches must have a license key enabled. Otherwise, EES events, which are captured by in-band communication with the FC switch, will not be logged.
When running on a SilkWorm 1000-family FC Switch, version 1.6c3 of this OEM firmware is compatible with the following:
DYNIX/ptx V4.5.1 and V4.5.2, and other members of system-software release sets as listed in "'Best Recipe' FC-Firmware Release Sets for DYNIX/ptx V4.5.x System," Table 1-1, in Chapter 1.
IBM 2109 and SilkWorm 2000-family FC Switches, set up in their "address-compatibility mode," when:
A SilkWorm 1000 is paired in the same fabric with an IBM 2109 or a SilkWorm 2000 (cascaded)
A SilkWorm 1000 is used as a single-switch fabric in a dual-fabric resource domain where the opposite fabric is an IBM 2109 or a SilkWorm 2000
ATTENTION SilkWorm 1000-family switches are not compatible with the hardware enforcement required by IBM when zoning is employed. A zoned fabric cannot include a SilkWorm 1000-family switch.
The non-OFC versions of the FC Bridge (Model Numbers FCB-1000-02 and -05)
The non-OFC versions of the FC-P Host Adapter board (Model Numbers IOC-0210-52 and -54)
EMC Symmetrix Storage Subsystems with only SA Director cards and running at least V5264.34.32 firmware.
EMC Symmetrix Storage Subsystems with only FC Director cards and running at least V5265.11.11 firmware.
EMC Symmetrix Storage Subsystems with mixed SA Director and FC Director cards and running at least V5265.11.11 firmware.
CLARiiON DASS Storage Subsystems running at least LIC firmware V9.55.01.
Starting with FC Switch firmware version V1.4b, the naming requirements for FC Switches have changed.
ATTENTION Previous versions of switch firmware allowed several special characters in the switch name that are no longer supported, for example, the colon (:) and space ( ). Any existing switches that contain invalid characters must be renamed as soon as possible. If a name must be changed on a switch to be upgraded, it must be done before the upgrade takes place. Otherwise, the switch will not boot to the new firmware and will have to be returned to the factory resulting in unplanned downtime. To display or set the switch's name, telnet to the switch and use the switchName command.
If a name is changed, remember to update the name in the /etc/hosts and .rhosts files on the host system before starting a download.
Specifically, the name of the switch:
Must have the first character be among 'a-z' or 'A-Z'.
Can only contain the characters 'a-z', 'A-Z', '0-9', or the underscore (_). No other punctuation is allowed.
Cannot exceed 19 characters in length.
Additionally, it is suggested that switch names be unique in a cascaded environment.
See the SilkWorm 1000 FC Switch Administration Guide for instructions on setting the name of a switch.
Version 1.6c3 has the same capabilities as V1.4b, plus the following improvements and new features:
Fabric Name Service enabled
Support for Class 2 FCP
Interoperability with IBM 2109 and SilkWorm 2000-family switches
Default Domain ID changed from 0 to 1
New shell commands or command content added:
Renamed the "DEADNPORT" error message to a more port-generic "PORTNOTPRESENT."
Deleted the following options from the flashSet shell command:
vc_loop_c2
vc_loop_c3
Deleted the uPathShow shell command.
Moved the errDisplayFilter shell command to the root account level.
Deleted local control-panel commands:
VC Loop Class 3
VC Loop Class 2
Added new local control-panel commands:
Since NUMA-Q's license keys authorize all three licenses, the value should always be reported as 7.
G stands for G_port type. An unconnected, generic port that can operate as an E_port or an F_port, depending on the type of device when it is connected.
F stands for F_port, the fabric access port used to connect an N_port.
E stands for E_port, an interswitch expansion port used to connect to another E_port of another switch to create a cascade.
x stands for no GBIC installed.
The sequence of the two-line display mirrors the physical port numbering. The first line lists Port 0 on the left and Port 7 on the right. The second line lists Port 8 through Port 15.
S for shortwave laser media
L for longwave laser media
C for copper media
A dash (-) for no GBIC installed
The sequence of the two-line display mirrors the physical port numbering. The first line lists Port 0 on the left and Port 7 on the right. The second line lists Port 8 through Port 15.
ATTENTION See the Fibre Channel Switch Administration Guide for explanations of all the menu items and telnet commands listed in these release notes.
NUMA-Q FC Switch models do not use the following list of specific commands and switch management features available in the V1.6c3 firmware:
The following critical or serious problems have been reported against the FC Switch V1.6c3 firmware. See "FC I/O Subsystem-Level Problem Reports," Chapter 2 for possible I/O subsystem-level problems involving FC Switches.
When a SilkWorm 1000 port receives a Class 2 FLOGI from DYNIX/ptx V4.5.x, it fails to login more than half the time.
Workaround: The well-known addresses of SilkWorm 1000 ports require a Class 3 FLOGI. Install FP255111 to make the OS revert to a Class 3 probe and retry whenever a normal Class 2 probe fails.
When preparing to investigate problems with a specific port, a common practice has been to clear the current port log to give a handy visual checkpoint for viewing diagnostic data sets during manual troubleshooting exercises. However, if the port log was previously halted, the command portLogClear will clear the port log, but it cannot reenable it.
Workaround: Before issuing portLogClear, determine if the port log is halted. Do so by examining the last line of the port log, which should give some indication of the error condition if the port log is halted. Furthermore, the timestamp of that last line will not change. If the port log is not halted, you can use the portLogClear command to clear the port log and continue to log new events. If the port log is halted, you must reboot the switch to reenable the port log.
Use the distribution CD-ROM labeled "DYNIX/ptx V4.5.1 OS and Layered Products Software, Mar 2000, Rev A."
Insert the distribution CD-ROM into the CD-ROM drive in the Bootbay connected to Quad 0 of a system.
Log in to the host as root.
Use the ptx/ADMIN menu system and the ptx/INSTALL utility to load the V1.6c3 file for a SilkWorm-1000 family FC Switch.
ATTENTION There are two versions of FC Switch firmware listed during the installation process, one for the SilkWorm 1000 family and another for the SilkWorm 2000 family. Be sure to read the descriptions and load only the switch software package labeled "V1.6.3" in the installation menus.
Remove the distribution CD-ROM.
Upgrade all SilkWorm 1000 FC Switches in the system with the downloading procedure described in Section 6.7.
ATTENTION If the switch name needs to be changed per FC Switch Naming Requirements," Section 6.2, it must be changed before downloading the new firmware and rebooting or else the new firmware will not boot and the switch will become disabled and must be returned to the factory.
If the switch name is changed, its name in the /etc/hosts and .rhosts files must be changed as well in order to have a successful download.
ATTENTION The following procedures will require the system to be at the single-user level during the firmware upgrade.
The following information is required before beginning the downloading procedure:
Switch symbolic name, such as "sw9" (switchName)
Severity level for displaying error messages (errDisplayFilter)
Collect this list before beginning the upgrade.
Software downloading is by TCP connection between the Switch and the host system containing the source file. Before attempting to download software to a Switch, use the following checklist to make sure that the host system was properly configured when the system or Switch was initially installed. If these host-system files are not configured as described, you may get "Permission denied" and the "rcmd fails" error messages. The configuration procedures are described in Section 8.5 of the Fibre Channel Subsystem Installation Guide. Here is the checklist
[ ] | On the host system containing the new distribution software file, the /etc/hosts file must contain a name and IP address for each Switch to be upgraded.
| ||
[ ] | On the host system, there must be a user account set up, with a password and a basic login shell, for administering FC Switches. | ||
[ ] | On the host system, the .rhosts file in that user's account must contain IP address entries for each Switch to be upgraded. | ||
[ ] | On the host system, permissions for all to read and execute must be set for all the directories and the binary file in the path /usr/ssw/fw/fc_switch/brocade1000/fc_sw1k.bin. For instance: $cd /usr/ssw | ||
[ ] | On the host system, test the reshd daemon from the user account set up to administer Switches: username$ resh localhost ls -a If the resh command fails, and the OS is V4.4.2 or later, check the shell entry in the /etc/inetd.conf file and make sure that it is set up to be a stream socket and not a tli socket. If the /etc/inetd.conf file must be modified, kill and restart the inetd daemon. | ||
[ ] | On each Switch, the Switch name and Ethernet IP address must match the name and IP address entered for it in the host system's /etc/hosts file. |
From the host system, verify that it can communicate with each Switch to be upgraded. Issue the following command:
username$ /etc/ping Switch_IP_address
Do the upgrade procedures with the host system at the single-user level.
The following procedure is performed from the VCS PTX Console window via a remote login (telnet) over the Ethernet LAN connected to the FC Switch to be upgraded.
Warn all users and then use the shutdown command to bring the host system down to the single-user level .
Enable basic networking and the inetd daemon from the single-user level with the following commands:
# /etc/ifconfigall 2
# /etc/inetd
Verify network operation. For example:
# netstat -in
Name Mtu Network Address Ipkts Opkts Odrop
loop 0 <Link> 0 0 0
loop 0 127/8 127.0.0.1 0 0 0
pe0 1502 <Link>00.00.bc.0f.04.ee 57 12 0
pe0 1502 138.95.103./24 138.95.103.77 57 12 0
If the Switch is not on the same side of a network router as the host, use the route command on the host system. For example:
# route fill
add net default: gateway 138.95.103.215
Initiate a telnet login session with the first Switch to be upgraded and log in as admin. For example:
(Host_prompt): telnet switch_IP_address
(Switch_name) login: admin
Password: admin_password
Switch_name:admin>
If this switch is one of a cascaded pair making up a fabric, determine its current domain ID at this time. The domain ID is the first item in the field named "Switch ID" in the following display:
sw3:admin> fabricShow
Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
------------------------------------------------------------------
0: fffc41 10:00:00:60:69:00:0a:12 192.168.1.2 0.0.0 >"sw2"
1: fffc42 10:00:00:60:69:00:01:b4 192.168.1.3 0.0.0 "sw3"
After the firmware has been upgraded, the ID must be restored to this value before returning the switch to service.
ATTENTION The ">" in the display indicates the Principal switch in the fabric.
Put the Switch into its offline state with the following command:
Switch_name:admin>switchDisable
Observe that the yellow LEDs of all the ports flash steadily, indicating all ports unavailable.
Download the new software into the Switch's flash memory with the following flashDownload command:
ATTENTION The username in the following command is the user account set up on the host system for administering Switches. The syntax of double quotes and commas to separate each argument is important. Do not enter the angle brackets.
Switch_name:admin>flashDownload <"host_IP_address">, <"username">,
"/usr/ssw/fw/fc_switch/brocade1000/fc_sw1k.bin"
1159644+195092+876080
writing flash 0 ................
writing flash 1 ................
download complete
value 0 = 0x0
=>
Make the new firmware effective at this time by rebooting the Switch.
=>reboot
Observe that the green LEDs of all the cabled ports glow steadily, indicating ports available.
ATTENTION During the reboot, the telnet session will time out and be closed by the remote host.
Start a new telnet session with the Switch and log in as admin.
Verify the currently-executing firmware version with the following command:
Switch_name:admin>version
VxWorks version: 5.3
Firmware version: v1.6c3
Made on: Fri Jun 18 08:42:05 PDT 1999
where:
Since the reboot cycle enables the Switch, you must disable it again before issuing a configuration command:
sw3:admin> switchDisable
value = 0 = 0x0
Issue the flashDefault command to ensure that all configuration values are operational.
sw3:admin> flashDefault
value = 0 = 0x0
If this switch comprises the fabric itself, set the Domain ID to zero. If this switch is one of a cascaded pair, make sure that the domain ID is the same as before the upgrade. The new V1.6c3 default domain ID is 1. Use the following command to change the ID to 0, if needed. A Ctrl-C command will write the new value and exit the command:
sw3:admin> flashSet
changing flash configuration...
domain_id [1]: 0
b_to_b credit [16]: Ctrl-C
Updating flash ...
done
sw3:admin>
Check the switchDomain: value with the following command to verify that the new domain ID is correct:
sw3:admin> switchShow
Other switch configuration values such as site-specific passwords and usernames, for instance, can be restored at this time.
Power cycle the Switch at this point to enable it and to put the restored values into effect:
ATTENTION Since Switches do not get power cycled very often in a customer production environment, it is a good idea to take advantage of the upgrade opportunity to make a switch go through its entire POST sequence.
Repeat this process for each Switch in the system.
When all Switches in a system have been upgraded, boot the system back up to the multiuser level with the following command:
# init 6
Verify that all cabled port LEDs on the upgraded Switches show a steady green, indicating that the upgraded Switch has re-established FC links to the system's host adapters and to FC Bridges and EMC Symmetrix FC-ported storage susbsystems connected to the Switch.