Sun Microsystems StorEdge T3+, Service Manual

Page: 82 / 240

4-12 Sun StorEdge T3 and T3+ Array Field Service Manual • September 2001
Currently, only
code_signature
and
hdr_counter
affects the automatical
selection done by level 1 code or level 2 code. Of course,
code_cksum
and
hdr_cksum
are used to validate the code.
4.3.2.2 Level 1 Controller Firmware
This procedure upgrades the level 1 firmware in only one controller. Therefore, you
must perform it twice for each array partner group.
1. Connect a console to the serial port (the right RJ-45 port) of the array.
See Section 2.1, “Establishing a Serial Port Connection” on page 2-1.
Note –
The serial cables used by the Sun StorEdge T3 and T3+ arrays are different.
Both cables are supplied in the F370-4119-02 Diagnostic Kit. The T3 array uses the
serial cable with RJ-11 connectors and the T3+ array uses the serial cable with RJ-45
connectors.
2. Set up the tftp host.
See Section 2.5, “Configuring a Server for Remote Booting” on page 2-9.
hdr_counter For the file to be downloaded to ROM by the
.ep
command
to RAM through tftp, this field should be -1. But, after the
code is programmed into ROM, the
.ep
command will
change this field automatically. This field is used to identify
which of two copies of level 2 code or level 3 code is newer.
The smaller the value is, the older the code is. Thus,
0xFFFFFFFF is older than 0xFFFFFFFE. The
.ep
command
will automatically update this field by taking the value of
this field from the other copy and add 1 to the value.
code_flags This field is used to identify whether special handling of the
code file is needed. For example, the code file may be
zipped, when it needs to be unzipped before uploading to
RAM.
hdr_cksum This is the checksum for the header portion. Since the
.ep
command will change
hdr_counter
when downloading
code into ROM, this field will be updated accordingly by the
.ep
command.
TABLE 4-4
Channel Active LED Descriptions
Header Description