Chinaunix首页 | 论坛 | 认证专区 | 博客 登录 | 注册

ET_cat

may the force be with you

  • 博客访问: 318468
  • 博文数量: 128
  • 博客积分: 265
  • 博客等级: 二等列兵
  • 技术积分: 1414
  • 用 户 组: 普通用户
  • 注册时间: 2011-09-27 20:44
  • 认证徽章:
个人简介

just do it

文章分类

全部博文(128)

文章存档

2017年(6)

2016年(17)

2015年(16)

2014年(43)

2013年(36)

2012年(10)

微信关注

IT168企业级官微



微信号:IT168qiye



系统架构师大会



微信号:SACC2013

订阅
热词专题
友情链接

分类: SOLARIS

The M4000 XSCF firmware upgrade is performed in three steps. The first step – XCP import – involves copying the XSCF Control Package (XCP) previously downloaded to an arbitrary server to the target XSCF; i.e. the XSCF that will be upgraded. Note that copying the XCP to the XSCF does not actually perform the upgrade. That is done in steps 2 and 3.

The XCP comprises two components, the XSCF firmware and the OpenBoot PROM (OBP) firmware. Before updating the firmware, be sure to check that the downloaded XCP is newer than the XCP image file currently stored in the XSCF.

XSCF> getflashimage -l
Existing versions:
       Version                Size  Date
       FFXCP1100.tar.gz   43684331  Thu Apr 28 23:35:12 UTC 2011
XSCF>
XSCF> getflashimage -u ftp_user ftp://ftp_host/FFXCP1102.tar.gz
Existing versions:
       Version                Size  Date
       FFXCP1100.tar.gz   43684331  Thu Apr 28 23:35:12 UTC 2011
Warning: About to delete existing versions.
Continue? [y|n]: y
Removing FFXCP1100.tar.gz.
Password:
  0MB received
  1MB received
  2MB received
:
: {snip}
:
40MB received
41MB received
42MB received
Download successful: 43030 Kbytes in 46 secs (993.703 Kbytes/sec)
Checking file...
MD5: 6002e8c1056b22116ba83606b4a0588e
XSCF>

Ensure that the “Download successful” message and the MD5 checksum are displayed. Check the version of the XCP image again. The downloaded version should now be shown.

XSCF> getflashimage -l
Existing versions:
        Version                Size  Date
        FFXCP1102.tar.gz   44063324  Fri Feb 03 05:43:29 UTC 2012
XSCF>

The second step – XSCF update – downloads the XSCF firmware to the XSCF and updates it. It also downloads the OBP firmware to the domain(s). However, application of the OBP firmware is done in step 3.

Before proceeding, take note of the current XSCF and OBP firmware versions.

XSCF> version -c xcp -v
XSCF#0 (Active )
XCP0 (Current): 1100
OpenBoot PROM : 02.18.0000
XSCF          : 01.10.0000
XCP1 (Reserve): 1100
OpenBoot PROM : 02.18.0000
XSCF          : 01.10.0000
OpenBoot PROM BACKUP
#0: 02.18.0000
#1: --.--.----
XSCF>

Run the flashupdate command to check if the current XCP version can be updated to the new version. If the message “XCP update is possible with domains up” is displayed, it is ok to proceed with theXSCF firmware upgrade without incurring any downtime. Otherwise, you will need to schedule an outage.

XSCF> flashupdate -c check -m xcp -s 1102
XCP update is possible with domains up
XSCF>
XSCF> flashupdate -c update -m xcp -s 1102
The XSCF will be reset. Continue? [y|n] :y
Checking the XCP image file, please wait a minute
XCP update is started (XCP version=1102:last version=1100)
OpenBoot PROM update is started (OpenBoot PROM version=02240000)
OpenBoot PROM update has been completed (OpenBoot PROM version=02240000)
XSCF update is started (XSCFU=0,bank=1,XCP version=1102:last version=1100)
XSCF download is started (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=00:version=01100001:last version=01090003)
XSCF download has been completed (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=00:version=01100001:last version=01090003)
XSCF download is started (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=01:version=01100002:last version=01100000)
XSCF download has been completed (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=01:version=01100002:last version=01100000)
XSCF download is started (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=02:version=01100001:last version=01080001)
XSCF download has been completed (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=02:version=01100001:last version=01080001)
XSCF download is started (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=03:version=01100002:last version=01100000)
XSCF download has been completed (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=03:version=01100002:last version=01100000)
XSCF download is started (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=04:version=01100002:last version=01100000)
XSCF download has been completed (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=04:version=01100002:last version=01100000)
XSCF download is started (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=05:version=01100001:last version=01100000)
XSCF download has been completed (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=05:version=01100001:last version=01100000)
XSCF download is started (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=07:version=01090001:last version=01090001)
XSCF download has been completed (XSCFU=0,bank=1,XCP version=1102:last version=1100, Firmware Element ID=07:version=01090001:last version=01090001)
XSCF update has been completed (XSCFU=0,bank=1,XCP version=1102:last version=1100)
XSCF is rebooting to update the reserve bank
XSCF>

The XSCF reboot may take a while. This is normal. You may tail one of the domain’s /var/adm/messages file to monitor the progress of the XSCF reboot. Check the XCP version once the XSCF is up.

# tail -f /var/adm/messages
Feb  3 15:09:38 domain1 scfd: [ID 556826 kern.warning] WARNING: scfd: SCF went to offline mode. unit=0
Feb  3 15:09:38 domain1 pppd[265]: [ID 702911 daemon.notice] Modem hangup
Feb  3 15:09:38 domain1 sckmd: [ID 889677 daemon.error] failed to receive sckm message: I/O error
Feb  3 15:09:38 domain1 ip: [ID 646971 kern.notice] ip_create_dl: hw addr length = 0
Feb  3 15:09:38 domain1 pppd[265]: [ID 702911 daemon.notice] Connection terminated.
Feb  3 15:12:52 domain1 scfd: [ID 492411 kern.notice] NOTICE: scfd: SCF online.
Feb  3 15:13:12 domain1 pppd[265]: [ID 702911 daemon.notice] Connect: sppp0  /dev/dm2s0
Feb  3 15:13:12 domain1 pppd[265]: [ID 702911 daemon.notice] local  IP address 192.168.2.2
Feb  3 15:13:12 domain1 pppd[265]: [ID 702911 daemon.notice] remote IP address 192.168.2.1
^C
#

XSCF> version -c xcp -v
XSCF#0 (Active )
XCP0 (Reserve): 1102
OpenBoot PROM : 02.24.0000
XSCF          : 01.10.0002
XCP1 (Current): 1102
OpenBoot PROM : 02.24.0000
XSCF          : 01.10.0002
OpenBoot PROM BACKUP
#0: 02.18.0000
#1: 02.24.0000
XSCF>
XSCF> version -c cmu -v
DomainID  0: 02.24.0000
DomainID  1: 02.24.0000
XSB#00-0:  02.18.0000(Current)     00.00.0000(Reserve)
XSB#00-1:  02.18.0000(Current)     00.00.0000(Reserve)
XSB#00-2:  02.18.0000(Current)     00.00.0000(Reserve)
XSB#00-3:  02.18.0000(Current)     00.00.0000(Reserve)
XSCF>

The final step in the XSCF firmware upgrade applies the new OBP firmware to the domain(s). This is accomplished by rebooting the domains(s). Note that this step can be performed at a later time.

To check if the OBP has been updated, keep an eye on the copyright notice as the server boots up. The OBP version should have changed from the last time the domain was booted up.

SPARC Enterprise M4000 Server, using Domain console
Copyright (c) 1998, 2011, Oracle and/or its affiliates. All rights reserved.
Copyright (c) 2011, Oracle and/or its affiliates and Fujitsu Limited. All rights reserved.
OpenBoot 4.33.0.a, 32768 MB memory installed, Serial #01234567.
Ethernet address 01:23:45:67:89:ab, Host ID: 01234567.

XSCF> version -c cmu -v
DomainID  0: 02.24.0000
DomainID  1: 02.24.0000
XSB#00-0:  02.18.0000(Reserve)     02.24.0000(Current)
XSB#00-1:  02.18.0000(Current)     00.00.0000(Reserve)
XSB#00-2:  02.18.0000(Current)     00.00.0000(Reserve)
XSB#00-3:  02.18.0000(Current)     00.00.0000(Reserve)
XSCF>

Note that the new OBP version is now ‘current’ and the old version has become ‘reserve’.

阅读(1179) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~
评论热议
请登录后评论。

登录 注册