NN 20500 260

NN-20500-260
Wireless Service Provider Solutions
WMS
Alcatel-Lucent 9353 Management System

M5000 Firmware Upgrade
NN-20500-260 01.04/EN Standard Sep 2012
WMS

Document number: NN-20500-260

Document issue: 01.04/EN
Document status: Standard
Product release: OAM07 and later
Date: Sep 2012
Alcatel-Lucent – Internal – Proprietary – Use pursuant to Company instruction
Copyright © 2009-2012 Alcatel-Lucent. All rights reserved.
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is “write
protected”; it may be altered only by authorized persons. While copies may be printed, it is not recommended.
Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be
regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent.
Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained
herein confidential, shall disclose the information only to its employees with a need to know, and shall protect
the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by
Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have received
this document in error, please notify the sender and destroy it immediately.
All other trademarks are the property of their owners.

Publication history i
PUBLICATION HISTORY
SYSTEM RELEASE: OAM07 and later
September 2012
Issue 01.04/EN, Standard
Update the Reference Documents
Dec 2009
Issue 01.03/EN, Preliminary
Update taken into account a new method to upgrade the firmware of a ST2540 Disk Array
(linked to the CR 221419.01)
Dec 2009
Update taken into account a new firmware revision (XCP1091) with support of
CPU Jupiter+ @2.53Ghz
August 2009
Update after review
July 2009
Issue 01.00/EN, Draft
Document creation
Copyright © 2009-2012 Alcatel-Lucent Alcatel-Lucent 9353 Management System - M5000 Firmware Upgrade
Publication history iii
TABLE OF CONTENTS
1. INTRODUCTION ................................................................................................1
1.1. APPLICABILITY ..........................................................................................................................1
1.2. AUDIENCE ................................................................................................................................1
1.3. PREREQUISITES........................................................................................................................1
2. REFERENCE DOCUMENTS ....................................................................................2
3. GENERAL DESCRIPTION ......................................................................................3

3.1. UPGRADE METHODOLOGIE ...............................................................................................3
3.2. FIRMWARE RELEASES ................................................................................................................3
4. PROCEDURE DESCRIPTION ...................................................................................4

4.1. OVERVIEW ...............................................................................................................................4
4.2. W HEN TO UPGRADE/DOWNGRADE THE OBP? ............................................................................5
4.3. XCP UPGRADE/DOWNGRADE PROCEDURE .................................................................................5
4.4. ST2540 FIRMWARE UPGRADE PROCEDURE ..............................................................................12
5. QUICK REFERENCE .......................................................................................... 18

5.1. HOW TO GET FIRMWARE REVISION..........................................................................................18
6. ABBREVIATIONS AND DEFINITIONS ...................................................................... 19

6.1. ABBREVIATIONS ......................................................................................................................19
6.2. DEFINITIONS ...........................................................................................................................19
6.3. W HAT’S NEW IN XCP 1090 AND 1091 .....................................................................................19
Publication history v
LIST OF FIGURES
Publication history vii
LIST OF TABLES
Table 1 : XCP Release .............................................................................................................................5
1
1. INTRODUCTION
This document describes the firmware upgrade procedures for the OAM M5000 server
platform. It deals with the following upgrade:
 XCP
 OBP
This document describes the firmware upgrade procedures for the ST2540 Disk Array
controller.
1.1. APPLICABILITY
The procedures described in this document only apply for OAM M5000 just before
any installation/upgrade steps.
It deals with WMS 7.0 and further.
1.2. AUDIENCE
This document is intended for anyone who is responsible for upgrading the firmware
on the M5000.
The instructions provided here are for experienced System or Field Engineers with
Sun/Solaris knowledge.
1.3. PREREQUISITES
2
2. REFERENCE DOCUMENTS
[R1] NN-20500-002 Terminology
SPARC Enterprise M5000 Server Documentation
http://docs.oracle.com/cd/E19580-01/index.html
[R2] Sun SPARC® Enterprise M3000/M4000/M5000/M8000/M9000 Servers
XSCF User’s Guide
Sun Storage 2500-M2 Arrays Documentation
http://docs.oracle.com/cd/E20734_01/index.html
Sun Storage 2500 Arrays Documentation
http://docs.oracle.com/cd/E19508-01/index.html
Sun Storage Common Array Manager (CAM) Software Documentation

NN-20500-260 01.04/EN Standard Sep 2012 Copyright © 2009-2012 Alcatel-Lucent

3
3. GENERAL DESCRIPTION
3.1. UPGRADE METHODOLOGIE

The entire OAM software solution is validated in Alcatel-Lucent labs on M5000
platforms with specific levels of firmware.
A M5000 with a firmware release different from the one tested in Alcatel-Lucent
labs may lead to failures and therefore requires one or more firmware upgrade.
A M5000 with lower firmware release is not supported and therefore requires
upgrade.
All internal disks firmware are supported.
All backplane firmware are supported
3.2. FIRMWARE RELEASES

The following table specifies supported firmware releases for an OAM M5000
platform:
Type of Firmware Supported release

XCP >= 1091
OBP >= 4.24.12
ST2540 - Controller firmware ≥ 07.35.10.10
The following chapters detail the upgrade procedure for the XCP, OBP firmware and
ST2540 Disk array.
4
4. PROCEDURE DESCRIPTION
4.1. OVERVIEW
The version of the XCP/OBP firmware may change regularly for a number of reasons:
To fix hardware bugs or improve compatibility;
To add support for new components (e.g. processors);

To add new functionalities (ASR, dynamic reconfiguration, etc.).
The M5000 firmware contains the following products:
 POST and OpenBoot PROM firmwares (hereafter collectively called the

OpenBoot PROM firmware)
 XSCF firmware

5
4.2. WHEN TO UPGRADE/DOWNGRADE THE OBP?

A M5000 with a lower XCP release must be upgraded using the procedure described
below.
Determine the current XCP release with one of the following commands:
1. Connect through the LAN to the “oam” account:
# ssh oam@< IPAddressXSCF >

oam@< IPAddressSP>'s password: < PTFPasswd >
Last login: Wed Jul ...

XSCF>
2. Display the system status:
XSCF> version -c xcp –v 

XSCF#0 (Active )
XCP0 (Current): 1081
OpenBoot PROM : 02.08.0000
XSCF : 01.08.0004
XCP1 (Reserve): 1081
XSCF : 01.08.0004
OpenBoot PROM BACKUP
#0: 02.08.0000
#1: --.--.----
XSCF> getflashimage –l 
Existing versions:
Version Size Date
FFXCP1081.tar.gz 42413986 Tue Apr 14 17:29:16 CEST 2009
The current XCP Firmware revision here is 1081
3. Use the following array to determine if OBP upgrade is required:
Current XCP release Action

< 1091 Upgrade the XCP (see below)
>= 1091 Nothing to do
Table 1 : XCP Release
4.3. XCP UPGRADE/DOWNGRADE PROCEDURE
4.3.1 CONSTRAINTS
The server MUST BE STOPPED for the XCP upgrade/downgrade. OAM services are
therefore DOWN.
6
Choose a slack period to upgrade/downgrade the XCP. BE SURE TO SCHEDULE DOWN

TIME TO PROCEED WITH THIS PROCEDURE.
The XCP firmware release is available at “My Oracle Support” web site
http://support.oracle.com. After “Sign In” select the tab “Patches & Updates”.
Then search for the product “Sun SPARC Enterprise M5000 Server” on the Platform
“Oracle Solaris on Sparc (64-bit); and download the XCP firmware.
4.3.2 PREREQUISITES
Before proceeding with the upgrade, be sure:
 To know how to retrieve the M5000 firmware.
 That the server has been correctly and entirely backed up.
 That the server has no hardware failure.
 That the server really needs the upgrade/downgrade.
 The OAM application is stopped.
4.3.3 PROCEDURE
The following procedure is applied to perform an upgrade to the 1082 XCP release.
1. Create the directory path to download the patch PE_FWM5000:
When the firmware is available in PE_FWM5000; in the other case follow Oracle
documentation.
<hostname> # rm -rf /opt/nortel/tmp/PE_FWM5000 

If directory does not exist, an error will be displayed.
This error can be ignored.
<hostname> # mkdir -p /opt/nortel/tmp/PE_FWM5000 
2. Retrieve the firmware PE_FWM5000.Vxx_yy.Ezz. As root user:
Retrieve the firmware PE_FWM5000.Vxx_yy.Ezz.tar.* from SRS server or from the

CDROM of patches; when PE_FWM5000 is available. In the other case follow Oracle
documentation.
Get by cp or ftp PE_FWM5000.Vxx_yy.Ezz.tar.* and put it under

/opt/nortel/tmp/PE_FWM5000.
Example:
<hostname> # cd /opt/nortel/tmp/PE_FWM5000 
<hostname> # ftp <SRS_IPaddress> 
name: oamops
password: <OamopsUser_password>

7
ftp> cd /opt/nortel/data/srs/DELIVERY/OAM/ALL/PE_FWM5000/Vxx_yy.Ezz
ftp> binary
ftp> get PE_FWM5000.Vxx_yy.Ezz.tar.*
ftp> bye
<hostname> #
3. Prepare the patch. As root user:
<hostname> # cd /opt/nortel/tmp/PE_FWM5000 
<hostname> # gzip -d PE_FWM5000.Vxx_yy.Ezz.tar.* 
<hostname> # tar xfp PE_FWM5000.Vxx_yy.Ezz.tar 
<hostname> #
The following steps of the procedure are executed with Service

disruption.
The OAM and Solaris will be halted.
All Ethernet connections will be broken.
Warn the users that the OAM server will be halted if this procedure is
applied on an OAM server.
Because Ethernet connections will be broken, the user must, to apply

this procedure works with a ssh client connected to the XSCF NET-
MGT port.
 WARNING: Host will be powered down for automatic firmware update

when download is completed.
The following steps are performed:
- Download System Firmware image
- Power down host
- Update System Firmware
- Reset XSCF
- Power on host
User can continue logon to host or XSCF when system starts up with
new firmware.
If this is an OAM server already installed, this step must be applied:
 As OAM user, stop the OAM server:
<hostname> # su - oamops 
<hostname>(oamops) % /opt/nortel/shell/sysmgt/wam_stopall.sh 
 As root user, stop Sun Management Center:
<hostname># su - 
<hostname># /opt/nortel/shell/sysmgt/wam_stopSunMC.sh 
8
 Create a temporary and dedicated ftp user account. The ftp service
need also to be activated:
<hostname># useradd -d /opt/nortel/tmp/PE_FWM5000 xscfupd 

<hostname># passwd xscfupd 
New Password: <xscfupd pwd>
Re-enter new Password: <xscfupd pwd>
<hostname># svcadm enable ftp 
The user must connect to the server through its XSCF access.
 From any administrative machine on the LAN , get the XSCF prompt
using the “oam” account:
# ssh oam@< IPAddressXSCF >

Last login: Wed Jul ...

XSCF>
 Use the getflashimage command to specify the firmware program

(tar.gz) file and import XCP to the system:
XSCF> getflashimage -u xscfupd ftp://@hostname/FFXCP1090.tar.gz 

Warning: About to delete existing versions.
Continue? [y|n]: y
Password: <xscfupd pwd>
0MB received
1MB received
...
39MB received
40MB received
40MB received
Download successful: 41541 Kbytes in 47 secs (947.646 Kbytes/sec)
Checking file...
MD5: 1f51fecf46c89744a7c1fed98815f611
Note: In case of trouble, use –v ( getflashimage –v –u …) to get some

information about.
 Check the upgrade can be performed with flashupdate. The

message “XCP update is possible with domains up” must be displayed.
As root user:
XSCF> flashupdate -c check -m xcp -s 1091 

XCP update is possible with domains up
XSCF> flashupdate -c update -m xcp -s 1091 

The XSCF will be reset. Continue? [y|n] :y
Checking the XCP image file, please wait a minute
XCP update is started (XCP version=1091:last version=1090)
OpenBoot PROM update is started (OpenBoot PROM version=02130000)
OpenBoot PROM update has been completed (OpenBoot PROM version=02130000)
XSCF update is started (XSCFU=0,bank=0,XCP version=1091:last version=1090)
XSCF download is started (XSCFU=0,bank=0,XCP version=1091:last version=1090,
Firmware Element ID=00:version=01090001:last version=01090000)
XSCF download has been completed (XSCFU=0,bank=0,XCP version=1091:last
version=1090, Firmware Element ID=00:version=01090001:last version=01090000)

9

XSCF update has been completed (XSCFU=0,bank=0,XCP version=1091:last
version=1090)
XSCF is rebooting to update the reserve bank
The connection will disconnect.
4. Go back to the XSCF menu and wait until the showlogs displays a “SCF:XCP
update has been completed“ message:
# ssh oam@< IPAddressXSCF > 

<...please wait for flashupdate complete...>
XSCF>showlogs monitor 
<... this is an example ...>
Dec 3 15:41:25 xxxxxxxx monitor_msg: SCF:XSCF download has been completed
(XSCFU=0, bank=1, XCP version=1091:last version=1090, Firmware Element ID=00,
version=01090001:last version=01090000)
Dec 3 15:41:38 xxxxxxxx monitor_msg: SCF:XSCF download is started (XSCFU=0,
bank=1, XCP version=1091:last version=1090, Firmware Element ID=01,
version=01080001:last version=01080001).../...
XSCF>showlogs monitor 
Dec 3 15:47:49 xxxxxxxx monitor_msg: SCF:XSCF bank apply has been completed
(XSCFU=0, bank=1, XCP version=1091:last version=1090)
10
Dec 3 15:47:50 xxxxxxxx monitor_msg: SCF:XCP update has been completed (XCP
version=1091)
XSCF> version -c xcp -v 

XSCF#0 (Active )
XSCF : 01.09.0001
XSCF : 01.09.0001
#0: 02.13.0000
#1: 02.11.0000
At this step, check the new XCP firmware revision “1091”.
5. Restart the domain to complete the OBP firmware update. Through the XSCF
access, connect as root user on the domain and stop it:
XSCF> console -d 0 
Connect to DomainID 0?[y|n] :y
<hostname># init 0 
...
{1} ok
< #. Allows to go back to the XSCF>
exit from console.
XSCF> poweroff -d 0 
DomainIDs to power off:00
Continue? [y|n] :y
00 :Powering off
*Note*
This command only issues the instruction to power-off.
The result of the instruction can be checked by the "showlogs power".
<... wait one minute ...>
XSCF> poweron -d 0 
DomainIDs to power on:00
Continue? [y|n] :y
00 :Powering on
*Note*
This command only issues the instruction to power-on.
The result of the instruction can be checked by the "showlogs power".
XSCF> console -d 0 

POST Sequence 01 CPU Check
LSB#01 (XSB#01-0): POST 2.12.0 (2009/09/09 15:17)
POST Sequence 02 Banner
LSB#00 (XSB#00-0): POST 2.12.0 (2009/09/09 15:17)
POST Sequence 03 Fatal Check
POST Sequence 04 CPU Register
POST Sequence 05 STICK
POST Sequence 06 MMU
POST Sequence 07 Memory Initialize
POST Sequence 08 Memory
POST Sequence 09 Raw UE In Cache
POST Sequence 0A Floating Point Unit
POST Sequence 0B SC
POST Sequence 0C Cacheable Instruction
POST Sequence 0D Softint
POST Sequence 0E CPU Cross Call
POST Sequence 0F CMU-CH

11
POST Sequence 10 PCI-CH

POST Sequence 11 Master Device
POST Sequence 12 DSCP
POST Sequence 13 SC Check Before STICK Diag
POST Sequence 14 STICK Stop
POST Sequence 15 STICK Start
POST Sequence 16 Error CPU Check
POST Sequence 17 System Configuration
POST Sequence 18 System Status Check
POST Sequence 19 System Status Check After Sync
POST Sequence 1A OpenBoot Start...
POST Sequence Complete.
ChassisSerialNumber BCF092002E
Sun SPARC Enterprise M5000 Server, using Domain console

Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Copyright 2009 Sun Microsystems, Inc. and Fujitsu Limited. All rights
reserved.
OpenBoot 4.24.12, 65536 MB memory installed, Serial #86374034.
Ethernet address 0:21:28:25:f6:92, Host ID: 8525f692.
6. Reboot the domain (if auto-boot? is false):
{0} ok boot 
The system will reboot with the new system firmware installed.
7. Delete the temporary ftp account and disable the ftp service:
<hostname> # userdel xscfupd 

<hostname> # svcadm disable ftp 
If this is an OAM server already installed, this step must be applied:
8. As OAM user, start the OAM server:
<hostname> # su - oamops 
<hostname>(oamops) % /opt/nortel/shell/sysmgt/wam_startall.sh 
4.3.4 OBP POST UPGRADE CHECKS

When the M5000 reboots, check the OBP firmware level:
<hostname># /usr/sbin/prtconf -V 
OBP 4.24.12 2009/10/30 06:59
Or
<hostname># /usr/sbin/prtdiag -v 
...
==================== Hardware Revisions ====================
System PROM revisions:

----------------------
OBP 4.24.12 2009/10/30 06:59...
If OBP revision is not correct, contact Alcatel-Lucent GPS team.
12
4.4. ST2540 FIRMWARE UPGRADE PROCEDURE
4.4.1 CONSTRAINTS
No LUN managements are allowed during the upgrade of the firmware.
This procedure involves a ST2540 system reboot. It is mandatory to stop all OAM
services at the beginning of the firmware upgrade.
The ST2540 system must be fully operational.

The minimum required ST2540 firmware is available with the following product:
 SUNWc2500 package embedded in PE_CAM (Common Array Manager) software
4.4.2 PREREQUISITES
Before proceeding with the upgrade, be sure:
 To know how to retrieve the PE_CAM/SUNWc2500 product.
 That the server has been correctly and entirely backed up.
 That the ST2540 has no hardware failure and there are two active controllers
card.
 That the ST2540 really needs the upgrade.
 To correctly locate the ST2540 to be upgraded.
 To know the password of the storage user

 The OAM application is stopped.
NOTE: Contact Alcatel-Lucent GPS team in case of any prerequisite troubles.
4.4.2.1 CHECK MIRRORING STATUS
<domainA hostname># metastat `cat /etc/vfstab | grep "/data" | awk '{print

$1}'` | grep State: 
CAUTION ! RESULT MUST BE EXACTLY AS FOLLOWS:
State: Okay
State: Okay
State: Okay
State: Okay
4.4.2.2 CHECK REPLICAS STATUS

<domainA hostname># metadb 
CAUTION ! No “flags” must be in uppercase letter.
uctfeam4:/ <4> (root) # metadb

flags first blk block count
a u 16 8192 /dev/dsk/c0t0d0s7
a u 8208 8192 /dev/dsk/c0t0d0s7
a u 16400 8192 /dev/dsk/c0t0d0s7

13
a u 8208 8192 /dev/dsk/c1t0d0s7
a u 16400 8192 /dev/dsk/c1t0d0s7
a u 8208 8192 /dev/dsk/c0t1d0s7
a u 16400 8192 /dev/dsk/c0t1d0s7
a u 8208 8192 /dev/dsk/c1t1d0s7
a u 16400 8192 /dev/dsk/c1t1d0s7
4.4.2.3 CHECK FIBER CHANNEL I/O PATH
<domainA hostname># luxadm display `luxadm probe | grep "Logical Path" | cut
-d: -f2-` | nawk '/Class/ || /State/ {print $0}' 
CAUTION ! FOR ALL “Class” primary, “State” MUST BE “ONLINE”

CAUTION ! FOR ALL “Class” secondary, “State” MUST BE “STANDBY”
Class secondary
State STANDBY
Class primary
State ONLINE
Class primary
State ONLINE
Class secondary
State STANDBY
4.4.2.4 CHECK CONTROLLER STATUS
Check that the ST2540 to be upgraded really needs to be upgraded:
<domainA hostname># /opt/SUNWstkcam/bin/sscs list array 

Array: <ARRAY_NAME>
<domain hostname># $sscs list array <ARRAY_NAME> | grep Firmware 
Firmware Version: 07.35.10.10
<domainA hostname>#
If the current controller firmware is equal to 07.35.10.10 then the ST2540 doesn’t need
to be upgraded.
Caution: If multipathing is not enabled, the system is not configured for a failover
operation. Before continuing with a live firmware upgrade, make sure the configuration
is set up for multipathing support.
4.4.2.5 CHECK ETHERNET
The following actions allow checking that the two LAN links connected to the two
controller of the ST2540 are fully operational:
<domain hostname># /opt/SUNWstkcam/bin/sscs list -a unlabeled controller | grep

IP
IPv4
IP Address: < IPaddressControllerA >
IPv6
IPv4
IP Address: < IpaddressControllerB >
IPv6
<domain hostname># ping <IPaddressControllerA> 

<IPaddressControllerA> is alive
<domain hostname># ping <IpaddressControllerB> 
<IpaddressControllerB> is alive
14
4.4.2.6 CHECK CAM AVAILABILITY
The following actions allow checking that the SUN CAM product is correctly activated
on the server:
<domainA hostname># pkginfo SUNWsesscs

application SUNWsesscs StorEdge Systems Element Manager Command Line Interface
<domainA hostname>#
rd
If not present, activate the CAM product located in /opt/Nortel/3 _party/CAM
<domainA hostname># cd /opt/nortel/3rd_party/CAM

<domainA hostname># ./ptshw_cam_setup.sh
Thursday, December 10, 2009 5:28:32 PM MET : CAM installation...
.../...
SUNWsefmj
SUNWstkcam-dpi-jbod-j4200
SUNWstkcamcd
<domainA hostname>#
Then register the Disk Array:
<domainA hostname># /opt/SUNWstkcam/bin/sscs register –i <DA @ip> storage-

system
4.4.2.7 CHECK FIRMWARE PACKAGE
The following actions allow checking that the SUN package including all necessary
firmware file is installed on the server:
<domainA hostname># pkginfo | grep SUNWc2500 

application SUNWc2500 Sun StorageTek(tm) Array Firmware
<domainA hostname>#
If the package is not present, install it (See the next section)

15
CONTROLLER Procedure
NOTE: In case of failure, contact Alcatel-Lucent GPS team.
1. Retrieve all the IP addresses attached to the OAM server.

2. If not already done, install the CAM firmware package:
<domainA hostname># cd `find /opt -name CAM` 

<domainA hostname># cd HostSoftware*/components 
<domainA hostname># pkgadd -d . SUNWc2500 
Processing package instance

...
Installation of <SUNWc2500> was successful.
<domain hostname>#
3. Verify the controller A and the controller B of the ST2540 are reachable on
the network:
<domainA hostname># ping < IPaddressControllerA > 

<2540 controller A> is alive
<domain hostname># ping < IPaddressControllerB > 
<2540 controller B> is alive
<domain hostname>#
Upgrade the ST2540 system by using the CAM CLI:
4. Check the firmware status of the Disk Array:
<domainA hostname># /opt/SUNWstkcam/bin/sscs list -a <da_name> firmware

Analyzing array xxxxxxxxx,(135.120.xxx.xxx),200300a0b85ae3f8
Controller: Some FRUs not at baseline.

Name Model Current Baseline
Tray.00.Controller.A LCSM100_F 07.xx.xx.xx 07.35.10.10
Tray.00.Controller.B LCSM100_F 07.xx.xx.xx 07.35.10.10
Disk: All FRUs at baseline

Tray.00.Drive.01 ST330056SSUN300G 0A1C 0A1C
Tray.00.Drive.07 HUS1530SBSUN300G SA04 SA04
16
IOM: All FRUs at baseline

Tray.01.IOM.A LCSM100_E 0195 0195
Tray.01.IOM.B LCSM100_E 0195 0195
System/NVSRAM: All FRUs at baseline

xxxxxxxx 2540 N1932-735843-002 N1932-735843-002
Check the highlighted messages: one or several of them may “… not at baseline”
5. Start the firmware upgrade:
<domainA hostname># /opt/SUNWstkcam/bin/sscs modify -a <da name> firmware

WARNING: This command will load new firmware if needed and may impact
array management and data availability.
Do you wish to continue? [y,n] : y
Started firmware upgrade job Install:task4083
And follow the progression of the update thanks to:
<domainA hostname># /opt/SUNWstkcam/bin/sscs list -a <da name> jobs \

Install:task4083
Job ID: Install:task4083
Type: Firmware Upgrade
Status: In progress
% Complete: 46
Time to Completion: 00:00:00
Priority: Unknown
6. When firmware upgrade is completed , check the result:
<domainA hostname># /opt/SUNWstkcam/bin/sscs list -a <da_name> firmware

Analyzing array xxxxxxxxx,(135.120.xxx.xxx),200300a0b85ae3f8
Controller: All FRUs at baseline

Tray.00.Controller.A LCSM100_F 07.35.10.10 07.35.10.10
Tray.00.Controller.B LCSM100_F 07.35.10.10 07.35.10.10
Disk: All FRUs at baseline


17
IOM: All FRUs at baseline

Tray.01.IOM.A LCSM100_E 0195 0195
Tray.01.IOM.B LCSM100_E 0195 0195
System/NVSRAM: All FRUs at baseline

Xxxxxxxxxx 2540 N1932-735843-002 N1932-735843-002
All status must be “All FRUs at baseline”
4.4.3 POST UPGRADE CHECKS

<domainA hostname># luxadm display `luxadm probe | grep "Logical Path" | cut
-d: -f2-` | nawk '/Class/ || /State/ {print $0}' 
CAUTION ! FOR ALL “Class” primary, “State” MUST BE “ONLINE”

CAUTION ! FOR ALL “Class” secondary, “State” MUST BE “STANDBY”
Class secondary
State STANDBY
Class primary
State ONLINE
Class primary
State ONLINE
Class secondary
State STANDBY
<domainA hostname># metadb 
CAUTION ! No “flags” must be in uppercase letter.
uctfeam4:/ <4> (root) # metadb

flags first blk block count
a u 8208 8192 /dev/dsk/c0t0d0s7
a u 16400 8192 /dev/dsk/c0t0d0s7
a u 8208 8192 /dev/dsk/c1t0d0s7
a u 16400 8192 /dev/dsk/c1t0d0s7
a u 8208 8192 /dev/dsk/c0t1d0s7
a u 16400 8192 /dev/dsk/c0t1d0s7
a u 8208 8192 /dev/dsk/c1t1d0s7
a u 16400 8192 /dev/dsk/c1t1d0s7
The following table lists one of the installed firmware release after the upgrade:
Type of Firmware Installed release

ST2540 - Controller firmware >= 07.35.10.10
See $4.4.2.4 for the command to execute to retrieve the firmware releases.
If firmware release mismatch, contact Alcatel-Lucent GPS team.
18
5. QUICK REFERENCE
5.1. HOW TO GET FIRMWARE REVISION

To determine the release of the installed XSCF Firmware and the OBP firmware, the
following commands can be used:
OBP Firmware under OBP prompt:
{1} ok banner
Sun SPARC Enterprise M5000 Server, using Domain console
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Copyright 2009 Sun Microsystems, Inc. and Fujitsu Limited. All rights
reserved.
OpenBoot 4.24.12, 65536 MB memory installed, Serial #86374034.
OBP Firmware under Solaris OS:
<hostname> # /usr/sbin/prtconf –V
OBP 4.24.12 2009/10/30 06:59
<hostname> # /usr/sbin/prtdiag –v
...
==================== Hardware Revisions ====================
System PROM revisions:

----------------------
OBP 4.24.12 2009/10/30 06:59
XCP Firmware under XCSF root access:
XSCF> version -c xcp -v

XSCF#0 (Active )
XSCF : 01.09.0001
XSCF : 01.09.0001
#0: 02.13.0000

19
6. ABBREVIATIONS AND DEFINITIONS
6.1. ABBREVIATIONS
For the purposes of the present document, the following abbreviations apply:
ASR Automatic system Recovery

CAM Common Array Manager
CPU Central Processing Unit
GPS Global Product Support
XSCF eXtended System Control Facility
OBP Open Boot Prom
XCP XSCF Control Package. Contains the control

programs that configure a computing system.
SRS Software Repository Server (located on
Primary Main Server)
WMS Wireless Management System
6.2. DEFINITIONS
For more information refer to [R1].
6.3. WHAT’S NEW IN XCP 1090 AND 1091
 The XCP 1090 firmware is the first XCP release to support the XSCF command
showdateoffset.
 The XCP 1090 firmware is the first XCP release to support the SPARC64 VII 2.53 GHz
processor. Earlier XCP firmware releases do not support this faster version of the processor,
which in other respects is functionally identical to all SPARC64 VII processors
 The XCP 1091 firmware introduces the Active Directory and LDAP over SSL features.
20

WMS

Alcatel-Lucent – Internal – Proprietary – Use pursuant to Company instruction
Copyright © 2009-2012 Alcatel-Lucent. All rights reserved.
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is “write
protected”; it may be altered only by authorized persons. While copies may be printed, it is not recommended.
Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be
regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent.
Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained
herein confidential, shall disclose the information only to its employees with a need to know, and shall protect
the information from disclosure and dissemination to third parties. Except as expressly authorized in writing
by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have
received this document in error, please notify the sender and destroy it immediately.
All other trademarks are the property of their owners.
Document number: NN-20500-260

Document issue: 01.04/EN
Document status: Standard
Product release: OAM07 and later
Date: Sep 2012

NN 20500 260

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NN 20500 260

Uploaded by

Copyright:

Available Formats

NN-20500-260

Wireless Service Provider Solutions

Alcatel-Lucent 9353 Management System

Alcatel-Lucent 9353 Management System

Document number: NN-20500-260

Alcatel-Lucent – Internal – Proprietary – Use pursuant to Company instruction

Copyright © 2009-2012 Alcatel-Lucent. All rights reserved.

All other trademarks are the property of their owners.

2. REFERENCE DOCUMENTS ....................................................................................2

3. GENERAL DESCRIPTION ......................................................................................3

4. PROCEDURE DESCRIPTION ...................................................................................4

5. QUICK REFERENCE .......................................................................................... 18

6. ABBREVIATIONS AND DEFINITIONS ...................................................................... 19

It deals with WMS 7.0 and further.

SPARC Enterprise M5000 Server Documentation

Sun Storage 2500-M2 Arrays Documentation

Sun Storage 2500 Arrays Documentation

Sun Storage Common Array Manager (CAM) Software Documentation

NN-20500-260 01.04/EN Standard Sep 2012 Copyright © 2009-2012 Alcatel-Lucent

3.1. UPGRADE METHODOLOGIE

All internal disks firmware are supported.

All backplane firmware are supported

3.2. FIRMWARE RELEASES

Type of Firmware Supported release

To fix hardware bugs or improve compatibility;

To add support for new components (e.g. processors);

The M5000 firmware contains the following products:

 POST and OpenBoot PROM firmwares (hereafter collectively called the

NN-20500-260 01.04/EN Standard Sep 2012 Copyright © 2009-2012 Alcatel-Lucent

4.2. WHEN TO UPGRADE/DOWNGRADE THE OBP?

1. Connect through the LAN to the “oam” account:

# ssh oam@< IPAddressXSCF >

Last login: Wed Jul ...

2. Display the system status:

XSCF> version -c xcp –v 

3. Use the following array to determine if OBP upgrade is required:

Current XCP release Action

Table 1 : XCP Release

4.3. XCP UPGRADE/DOWNGRADE PROCEDURE

Choose a slack period to upgrade/downgrade the XCP. BE SURE TO SCHEDULE DOWN

 To know how to retrieve the M5000 firmware.

 That the server has no hardware failure.

 That the server really needs the upgrade/downgrade.

 The OAM application is stopped.

1. Create the directory path to download the patch PE_FWM5000:

<hostname> # rm -rf /opt/nortel/tmp/PE_FWM5000 

2. Retrieve the firmware PE_FWM5000.Vxx_yy.Ezz. As root user:

Retrieve the firmware PE_FWM5000.Vxx_yy.Ezz.tar.* from SRS server or from the

Get by cp or ftp PE_FWM5000.Vxx_yy.Ezz.tar.* and put it under

NN-20500-260 01.04/EN Standard Sep 2012 Copyright © 2009-2012 Alcatel-Lucent

3. Prepare the patch. As root user:

The following steps of the procedure are executed with Service

The OAM and Solaris will be halted.

All Ethernet connections will be broken.

Because Ethernet connections will be broken, the user must, to apply

 WARNING: Host will be powered down for automatic firmware update

The following steps are performed:

- Download System Firmware image

- Power down host

- Update System Firmware

If this is an OAM server already installed, this step must be applied:

 As OAM user, stop the OAM server:

 As root user, stop Sun Management Center: