Deployment of Solaris 10 on SPARC Enterprise M5000

Overview of Solaris 10 Jumpstart Server (for SPARC clients)

Jumpstart is Solaris tool for OS installation over the LAN. The installation is faster than using DVD and you can do consistent installation for many clients. It is also unattended.

Jumpstart installation is using:

profile text file (defines software to be installed)
rules text file (defines rules/steps for install)
scripts for pre and post install tasks
sysidcfg (configuration information)

Note: Sun provides 'check' script that you run to verify rules file, if everything is okay, the script will generate rules.ok file.

Basically this works like:

Client boot from the network
The rules.ok file is checked
The profile in rules.ok is used for installation
If rule(s) doesn't match, regular interactive installation occurs.

This deployment uses one server (Solaris 10 x86, say hostname = mgmt_host) as Boot, Install and Profile server, all three in one.
Note: DHCP service is needed only if you need to install Solaris on i386 platform.

Install Solaris 10 bits

Follow the example of procedure how to install Solaris 10 bits from ISO image.

Download Solaris 10 update 11 ISO to /tmp
Run: lofiadm -a /tmp/sol-10-u11-ga-sparc-dvd.iso /dev/lofi/1 (assign device to file)
mount -F hsfs -o ro /dev/lofi/1 /mnt (mount device to /mnt)
cd /mnt/Solaris_10/Tools/ (go to desired dir)
./setup_install_server /export/install/sol_10_u11_sparc ( install jumpstart server)
Once you are done, un-mount /mnt (umount /mnt)
Remove the file /dev/lofi/1 ( command: /usr/sbin/lofiadm -d /dev/lofi/1 )

Setup NFS shares

Make sure that all relevant directories are accessible from clients over NFS. These are ones with Solaris bits, clients’ profiles/rules/finish scripts.

For example, have line in /etc/dfs/dfstab file:

share -F nfs -o ro,anon=0   /export/install/sol_10_u11_sparc

And run the command: shareall

The /etc/ethers file

Populate this file with MAC address of client system (you need MAC address of interface that clients use to boot via network)
Example :

00:03:ba:cf:4b:78    sap01.austin.company.com

Note: one of ways to find server’s MAC address is from Open Boot (ok prompt).

{ok}  show-nets 
a) /pci@0,600000/pci@0/pci@8/pci@0,1/pci@1/network@1
b) /pci@0,600000/pci@0/pci@8/pci@0,1/pci@1/network@0
c) /pci@0,600000/pci@0/pci@8/pci@0/network@2,1
d) /pci@0,600000/pci@0/pci@8/pci@0/network@2
q) NO SELECTION
Enter Selection, q to quit: q

Change directories to the network device and get the MAC address

{ok}   cd /pci@0,600000/pci@0/pci@8/pci@0,1/pci@1/network@0
{ok}    .properties

Look for line like: local-mac-address 00 14 4f 67 b8 7c

The /etc/hosts file

Add IP and host name in the /etc/hosts file
Example:

16.106.64.76      sap01.austin.domain.com     sap01

Note: The RARP protocol will be used for mapping between MAC and IP and for booting client.

Adding SPARC client

Go to mgmt_host:/export/install/sol_10_u11_sparc/Solaris_10/Tools and install client with command add_install_client
Example:

/export/install/sol_10_u11_sparc/Solaris_10/Tools/add_install_client \
-i 16.106.64.76  -e 00:03:ba:cf:4b:78  \
-s 16.106.64.56:/export/install/sol_10_u11_sparc \
-c 16.106.64.56:/jumpstart/sol-refresh/sap01.sol10u11 \
-p 16.106.64.56:/jumpstart/sol-refresh/sap01.sol10u11 \
sap01 sun4u

Note: platform group is sun4u

This command will add below entry to the /etc/bootparams file (used by client for booting over LAN):

sap01.austin.domain.com  root=mgmt_host:/export/install/sol_10_u11_sparc/Solaris_10/Tools/Boot install=16.106.64.56:/export/install/sol_10_u11_sparc boottype=:in sysid_config=16.106.64.56:/jumpstart/sol-refresh/sap01.sol10u11 install_config=16.106.64.56:/jumpstart/sol-refresh/sap01.sol10u11 rootopts=:rsize=8192

The /tftpboot directory

The command add_install_client also adds some entries to /tftpboot directory.

106A404C -> inetboot.SUN4U.Solaris_10-3
106A404C.SUN4U -> inetboot.SUN4U.Solaris_10-3

The 106A404C is hexadecimal representation of client's MAC address and it's symbolic link to inetboot.SUN4U.Solaris_10-3 (this is small net kernel for booting client via LAN).

Services needed on a jumpstart server

Make sure below services are running:

svc:/network/rarp:default
svc:/network/rpc/bootparams:default
svc:/network/tftp/udp6:default

Boot the client

Now all is ready to boot and install client from OpenBoot {ok} prompt.

{ok}  boot net -v – install

Or for example

{ok} boot /pci@0,600000/pci@0/pci@8/pci@0,1/pci@1/network@0  –v – install

Overview of Jumpstart Client (SPARC) setup

The clients' profiles and other relevant files are located in mgmt_host:/jumpstart/sol-refresh/ directory.
Let's take example of client sap03.austin.domain.com
The rules, profile and finish scripts are located in mgmt_host:/jumpstart/sol-refresh/sap03.sol10u11

The rules file

A rules file defines rules/steps for installation, to verify it run the command check

[root@g1o0007]/jumpstart/sol-refresh/sap03.sol10u11# ./check
Validating rules...
Validating profile profile.zfs...
The custom JumpStart configuration is ok.

[root@g1o0007]/jumpstart/sol-refresh/sap03.sol10u11# cat rules.ok
hostname sap03 && arch sparc   -    profile.zfs   finish_script.sh
# version=2 checksum=5648

Here the rules show that profile.zfs and finish_script.sh will be used.

The profile file

A profile file defines what to be installed and how. Some of most important entries are:

# what type of install
install_type    initial_install
system_type     standalone
# zpool setup
pool rpool auto 32g auto mirror any any
bootenv installbe bename zfsroot dataset /var
# what to install 
cluster           SUNWCXall
package SMCperl add nfs://16.106.64.56/export/mvs/software/perl/sparc/5.10
patch 122608-08 nfs 16.106.64.56:/export/mvs/JASS_security-scripts

So here, we can add third-party packages to be installed via NFS. Also patches are installed at this moment via NFS.
See example

The sysidcfg file

This is configuration file unique for each system. It contains hostname, network parameters, encrypted root password, time zone, etc.
See example

The Finish script

A finish script performs tasks after the Solaris software is installed on a system, but before the system reboots.
The Solaris installation program mounts the system's file systems on /a .
The file systems remain mounted on /a until the system reboots. So the finish script performs action to the newly installed file system hierarchy by working on the file systems that are respective to /a.

After the jumpstart installation is completed, the log file of finish script is redirected to /var/sadm/system/logs/finish.log We'll be using finish script to copy RC files to the system and to install Veritas Storage Foundation 6.
See example

The RC files

The idea of RC files is to perform actions that are not easy to be integrated in finish script or even not possible to integrate. The RC scripts are located in mgt_host:/jumpstart/sol-refresh/rc_scripts/

Note that RC scripts will run after very first system reboot upon jumpstart installation. Once RC script finishes, it will add underscore sign (_) in front of its name, so it will not run during future system reboots.

For now, there are three RC scripts and each one does certain groups of actions.

The S99-00-zfs is adjusting ZFS infrastructure, like creating new ZFS and setting quota and reservations.
See example

The S99-01-proto is copying prototype files to the system. These are files that are same on all systems, good examples are configuration files (like ntp.conf and similar ones), and SSH public keys. The prototype directory is in mgmt_host:/jumpstart/sol-refresh/proto
See example

The S99-02-oracle-svcs.sol_10_u11 is adjusting Oracle parameters, disabling/enabling services, installing Dataprotector/OVR, setup App/Users home directories, etc. At the end will send the email report to Multi Vendor Systems (MVS) administrators. This email report has reminder what needs to be done on system manually.
See example

The example of email body:

- Install & configure Powerbroker (binary in /var/tmp)
- Install lftp/proftpd if needed (binary in /var/tmp)
- Install all necessary SMC packages
- Install SSCS for domains that boot from StorEdge 3510 (binary: /var/tmp/2.5_fw_solaris_sparc.pkg)
- Configure/enable multipathing with command (requires reboot): stmsboot -e
- Configure Veritas Storage Foundation (mount mgmt_host:/export/mvs/software/veritas/sparc/6.0.1/dvd1-sol_sparc/sol10_sparc and run: ./installer -configure )
- Verify /etc/passwd /etc/shadow /etc/group /etc/shells /etc/services files (copy from relevant server)
- Setup and test Failover NICs
- Review OpenBoot Environments, check boot devices and test boot from both disks
- Run first JASS pass, reboot, run second JASS pass, check for failures
- If needed, FC Firmware can be upgraded with: luxadm -e forcelip /dev/cfg/c#

Post jumpstart installation setup

The build email report tells you what else is needed to be done on the system.
Here are some additional notes.

FC Firmware upgraded

If needed, FC Firmware can be upgraded with:

luxadm -e forcelip /dev/cfg/c<chunnel#> 

Example: luxadm -e forcelip /dev/cfg/c4

SSCS

The SSCS (Sun Storage Config Software) is very useful tool for monitoring hardware state of StorEdge 3510 JBOD. If below problem occurs:

[root@sap08]/opt/SUNWsscs/sbin# ./sccli
sccli: no manageable devices found
sccli: Type "sccli help" for valid commands.

Add line:

ses "scsiclass,03"

To the file /etc/driver_aliases and run command touch /reconfigure and reboot.

Multipath

Use command stmsboot to enable/disable multipath.

Example when multipath is disabled:

#  stmsboot -L 
stmsboot: MPxIO is not enabled
stmsboot: MPxIO disabled

# zpool status
  pool: rpool
 state: ONLINE
 scan: none requested
config:
        NAME          STATE     READ WRITE CKSUM
        rpool         ONLINE       0     0     0
          mirror-0    ONLINE       0     0     0
            c0t0d0s0  ONLINE       0     0     0  ---> traditional disk name (no multipath) 
            c0t1d0s0  ONLINE       0     0     0

Example after enabling multipath
(there are 4 disks in the system, 2 SAN paths):

#  stmsboot -L 
non-STMS device name                    STMS device name
------------------------------------------------------------------
 /dev/rdsk/c0t123d0      /dev/rdsk/c6t500000E01142FC30d0 
 /dev/rdsk/c0t120d0      /dev/rdsk/c6t500000E0110CB8B0d0 
 /dev/rdsk/c0t114d0      /dev/rdsk/c6t500000E011070DE0d0 
 /dev/rdsk/c0t117d0      /dev/rdsk/c6t500000E011431A00d0 
 /dev/rdsk/c1t117d0      /dev/rdsk/c6t500000E011431A00d0 
  /dev/rdsk/c1t123d0      /dev/rdsk/c6t500000E01142FC30d0 
 /dev/rdsk/c1t120d0      /dev/rdsk/c6t500000E0110CB8B0d0 
 /dev/rdsk/c1t114d0      /dev/rdsk/c6t500000E011070DE0d0 

# zpool status
  pool: rpool
 state: ONLINE
 scan: none requested
config:
        NAME                         STATE     READ WRITE CKSUM
        rpool                        ONLINE     0     0     0
          mirror-0                   ONLINE     0     0     0
             c6t500000E011070DE0d0s0 ONLINE    0   0     0  ---> disk name with multipath enabled 
             c6t500000E011431A00d0s0 ONLINE    0   0     0

Veritas Storage Foundation version 6 Configuration

Mount Veritas source from mgmt_host:

# mount -F nfs 16.106.64.56:/export/mvs/software/veritas/sparc/6.0.1/dvd1-sol_sparc/sol10_sparc /mnt

And start the Veritas configuration

# cd /mnt ; ./installer –configure

The example:

     1)  Veritas Dynamic Multi-Pathing (DMP)
     2)  Veritas Cluster Server (VCS)
     3)  Veritas Storage Foundation (SF) 
     4)  Veritas Storage Foundation and High Availability (SFHA)
     5)  Veritas Storage Foundation Cluster File System HA (SFCFSHA)
     6)  Symantec VirtualStore (SVS)
     7)  Veritas Storage Foundation for Sybase ASE CE (SFSYBASECE)
     8)  Veritas Storage Foundation for Oracle RAC (SF Oracle RAC)
Select a product to configure: [1-8,q] 3 

Verifying systems: 100%
    Estimated time remaining: (mm:ss) 0:00                                                             5 of 5
    Checking system communication ..................................................................... Done
    Checking release compatibility .................................................................... Done
    Checking installed product ........................................................................ Done
    Checking platform version ......................................................................... Done
    Performing product prechecks ...................................................................... Done

 1)  Enter a valid license key
 2)  Enable keyless licensing and complete system licensing later
How would you like to license the systems? [1-2,q] (2)


     1)  SF Standard
     2)  SF Enterprise 
     b)  Back to previous menu
Select product mode to license: [1-2,b,q,?] (2)

Would you like to enable the Veritas Volume Replicator? [y,n,q] (n)

Starting SF: 100%
    Estimated time remaining: (mm:ss) 0:00                                                 15 of 15
    Performing SF configuration ............................................................ Done
    Starting vxdmp ......................................................................... Done
    Starting vxio .......................................................................... Done
    Starting vxspec ........................................................................ Done
    Starting vxconfigd ..................................................................... Done
    Starting vxesd ......................................................................... Done
    Starting vxrelocd ...................................................................... Done
    Starting vxcached ...................................................................... Done
    Starting vxconfigbackupd ............................................................... Done
    Starting vxattachd ..................................................................... Done
    Starting vxportal ...................................................................... Done
    Starting fdd ........................................................................... Done
    Starting vxdbd ......................................................................... Done
    Starting odm ........................................................................... Done
    Performing SF poststart tasks .......................................................... Done

The license file is mgmt_host:/export/mvs/software/veritas/sparc/6.0.1/license.txt

To verify if product is licensed, run installer (without any arguments)

Symantec Product                                   Version Installed    Licensed
===============================================
Veritas File System                                6.0.100.000          yes
Veritas Dynamic Multi-Pathing                      6.0.100.000          yes
Veritas Volume Manager                             6.0.100.000          yes
Veritas Cluster Server                             none                 no
Veritas Storage Foundation                         6.0.100.000          yes
Veritas Storage Foundation and High Availability   none                 no
Veritas Storage Foundation Cluster File System HA  none                 no
Symantec VirtualStore                              none                 no
Veritas Storage Foundation for Sybase ASE CE       none                 no
Veritas Storage Foundation for Oracle RAC          none                 no

At the end, un-mount /mnt

Setup and test Failover NICs

Edit the primary NIC file /etc/hostname. (example: hostname.nxge0) and edit the only line in the file to look as follow

<IP_address> netmask + broadcast + group shared0 up

Where IP_address is the IP address of the host your doing, e.g. 16.140.64.185, so whole file is like:
16.140.64.185 netmask + broadcast + group shared0 up

Edit the secondary NIC file /etc/hostname.nxge1 and place the following in the file as the only line.

group shared0 standby up

Reboot the server for the changes to take effect. . Or, to make the changes by hand, instead of rebooting.

#ifconfig nxge0 group shared0
#ifconfig nxge1 plumb
#ifconfig nxge1 group shared0 standby

Testing NIC Failover:
In order to simulate a failure of the nxge0 interface, do the following.

# if_mpadm -d nxge0

Try pinging the gateway, then try pinging another system outside of the network using the IP address, then doing an nslookup of something to see that name resolution works. If this doesn't work, then you've used the wrong secondary interface or the cabling in wrong.
To simulate nxge0 recovery, do the following.

# if_mpadm -r nxge0

Review OpenBoot Environments, check boot devices and test boot from both disks

SSH to the M5000's XSCF and review Domains on it:

XSCF> showdcl -a
DID   LSB   XSB   Status
00                Running
      00    00-0
      01    00-2
      02    00-3
      03    01-2
---------------------------
01                Running
      00    00-1
---------------------------
02                Running
      00    01-0

Example of connecting to the serial console of Domain 0:

XSCF> console -d 0

Console contents may be logged.
Connect to DomainID 0?[y|n] :y
sap03.austin.domain.com console login:

To disconnect from serial console and return to XCSF press: #.

Determine both disks in zpool (in our case it’s names rpool)

# zpool status
  pool: rpool
 state: ONLINE
 scan: none requested
config:
        NAME                         STATE     READ WRITE CKSUM
        rpool                        ONLINE       0     0     0
          mirror-0                   ONLINE       0     0     0
            c7t5000C50007A7A6D3d0s0  ONLINE       0     0     0
            c7t5000C5000F446FCFd0s0  ONLINE       0     0     0

This disk name tells us that multipathing is enabled, so find traditional name of disks

# stmsboot -L
non-STMS device name                    STMS device name
------------------------------------------------------------------
/dev/rdsk/c0t0d0        /dev/rdsk/c7t5000C50007A7A6D3d0
/dev/rdsk/c0t1d0        /dev/rdsk/c7t5000C5000F446FCFd0

Now find full path of disks:

# cd /dev/dsk
# ls -la | grep c0t0d0s0
lrwxrwxrwx   1 root    root  60 Jan 22 16:50 c0t0d0s0 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0:a
# ls -la | grep c0t1d0s0
lrwxrwxrwx   1 root     root  60 Jan 22 16:50 c0t1d0s0 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0:a

Go to the OpenBoot and create nvalias for boot and mirror disk.
Note that sd will have to be replaced with disk.
And make sure that use-nvramrc? is setup to be true

{5} ok nvalias bootdisk /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk@0,0:a
{5} ok nvalias mirrdisk /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk@1,0:a

{5} ok setenv boot-device bootdisk mirrdisk
boot-device =           bootdisk mirrdisk

{5} ok printenv boot-device
boot-device =           bootdisk mirrdisk

{5} ok devalias
mirrdisk                 /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk@1,0:a
bootdisk                 /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk@0,0:a
cdrom                    /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk@3,0:f
disk                     /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk@0
net                      /pci@2,600000/network@0
name                     aliases

Finally test booting system from both disks:

{ok} boot bootdisk 
And
{ok} boot mirrdisk

Harden the system by performing JASS (JumpStart Architecture and Security Scripts)

Run the first pass.

# cd /opt/SUNWjass/bin/ 
# ./jass-execute -d EDS-HP-NGDC.driver -o /var/tmp/Security/SSTharden-v`date +"%Y%m%d"`

The command may take a while to run. Once it is done, you will need to reboot the system.
After reboot, run the second pass.

# cd /opt/SUNWjass/bin
# ./jass-execute -a EDS-HP-NGDC.driver -V 2 -o /var/tmp/Security/SSTaudit-v`date +"%Y%m%d"`

Powerbroker installation

The jumpstart puts PB bits in the /var/tmp

# cd /var/tmp/pb5
# cp -p pb.settings /etc
# cd powerbroker/powerbroker/v5.0/pbsparc_solarisC-5.0.4-06/install
# ./pbinstall

You may be prompted for an editor. The default editor of "vi" is fine. Once you respond to that prompt, you will be shown configuration options. Go ahead and choose "X" to exit out of the installation. Install the license key ( cp /var/tmp/pb5/pb.key /etc )

Appendix

Example of M5000 configuration

Learn more about XSCF (eXtended System Control Facility) using man pages ...

XSCF> man showhardconf
...

XSCF>  showhardconf -u 
SPARC Enterprise M5000; Memory_Size:256 GB;
    +-----------------------------------+------------+
    |              FRU                  |  Quantity  |
    +-----------------------------------+------------+
    | MBU_B                             |       1    |
    |     Type:1;                       |   (   1)   |
    |     CPUM                          |       4    |
    |         Freq:2.400 GHz;           |   (   8)   |
    |     MEMB                          |       8    |
    |         MEM                       |      64    |
    |             Type:4B; Size:4 GB;   |   (  64)   |
    |     DDC_A                         |       4    |
    |     DDC_B                         |       2    |
    | IOU                               |       2    |
    |     Type:1;                       |   (   2)   |
    |     DDC_A                         |       2    |
    |     DDCR                          |       2    |
    |         DDC_B                     |       2    |
    | XSCFU                             |       1    |
    | OPNL                              |       1    |
    | PSU                               |       4    |
    | FANBP_C                           |       1    |
    |     FAN_A                         |       4    |
    +-----------------------------------+------------+

Example: moving system board 01-3

XSCF>  showdomainstatus -a 
DID         Domain Status
00          Powered Off
01          Powered Off
02          Powered Off
03          -

XSCF>  showboards -a 
XSB  DID(LSB) Assignment  Pwr  Conn Conf Test    Fault
---- -------- ----------- ---- ---- ---- ------- --------
00-0 00(00)   Assigned    y    y    y    Passed  Normal
00-1 02(00)   Assigned    y    y    y    Passed  Normal
00-2 00(01)   Assigned    y    y    y    Passed  Normal
00-3 02(01)   Assigned    y    y    y    Passed  Normal
01-0 01(00)   Assigned    y    y    y    Passed  Normal
01-1 02(02)   Assigned    y    y    y    Passed  Normal
01-2 01(01)   Assigned    y    y    y    Passed  Normal
01-3 02(03)   Assigned    y    y    y    Passed  Normal <-- in domain 2, number 03


XSCF>  showdcl -a 
DID   LSB   XSB   Status
00                Running
      00    00-0
      01    00-2
---------------------------
01                Running
      00    01-0
      01    01-2
---------------------------
02                Running
      00    00-1
      01    00-3
      02    01-1
      03    01-3        <-- in domain 2, number 03


XSCF>  deleteboard  -c unassign 01-3 
XSB#01-3 will be unassigned from domain immediately. Continue?[y|n] :y


XSCF>  showboards -a 
XSB  DID(LSB) Assignment  Pwr  Conn Conf Test    Fault
---- -------- ----------- ---- ---- ---- ------- --------
00-0 00(00)   Assigned    n    n    n    Passed  Normal
00-1 02(00)   Assigned    n    n    n    Passed  Normal
00-2 00(01)   Assigned    n    n    n    Passed  Normal
00-3 02(01)   Assigned    n    n    n    Passed  Normal
01-0 01(00)   Assigned    n    n    n    Passed  Normal
01-1 02(02)   Assigned    n    n    n    Passed  Normal
01-2 01(01)   Assigned    n    n    n    Passed  Normal
01-3 SP       Available   n    n    n    Passed  Normal <---- available

Associate board 01-3 to number 02 in Domain 0:

XSCF>  setdcl -d 0 -a 02=01-3 

XSCF>  showdcl -a 
DID   LSB   XSB   Status
00                Powered Off
      00    00-0
      01    00-2
      02    01-3  <----------- new location
---------------------------
01                Powered Off
      00    01-0
      01    01-2
---------------------------
02                Powered Off
      00    00-1
      01    00-3
      02    01-1
      03    01-3 <------ board still shows in old location

Clear association between board and number

XSCF>  setdcl -d 2 -r 03 

XSCF>  showdcl -a 
DID   LSB   XSB   Status
00                Powered Off
      00    00-0
      01    00-2
      02    01-3  <-------- now only shows in new location
---------------------------
01                Powered Off
      00    01-0
      01    01-2
---------------------------
02                Powered Off
      00    00-1
      01    00-3
      02    01-1

XSCF>  addboard -c assign -d 0 01-3 
XSB #01-3 will be assigned to DomainID 0. Continue?[y|n] :y

XSCF> showboards -a
XSB DID(LSB) Assignment Pwr Conn Conf Test Fault
---- -------- ----------- ---- ---- ---- ------- --------

00-0 00(00) Assigned n n n Passed Normal

00-1 02(00) Assigned n n n Passed Normal

00-2 00(01) Assigned n n n Passed Normal

00-3 02(01) Assigned n n n Passed Normal

01-0 01(00) Assigned n n n Passed Normal

01-1 02(02) Assigned n n n Passed Normal

01-2 01(01) Assigned n n n Passed Normal

01-3 00(02) Assigned n n n Passed Normal <-- now in domain 0

Dumping and restoring M5000 configuration

The M5000 configuration has been saved to mgmt_host, so it can be easily restored in case of disaster. Also if for any reason it's needed to go back to M5000 to factory defaults, this config backup can be used to restore M5000 to previous workable status. The configuration dump contains domain configuration, user accounts, etc.

To dump configuration from XSCF run command (make sure FTP runs on mgmt_host)

XSCF>  dumpconfig -v -V -u root ftp://mgmt_host/root/sap02-c.dumpconfig 

reading database ... .................*done
creating temporary file ... done
starting file transfer ...transfer from '/tmp/dumpconfig.FTdL5I' to 'ftp://mgmt_host/root/sap02-c.dumpconfig'
Password:

The result is ASCII file, with some details about M5000 but actual configuration is not humanly readable.

So let's say you need to revert M5000 to the factory default with:

XSCF> restoredefaults -c factory

First thing to do is to be physically beside M5000, so you can restore XSCF network parameters and allow SSH.

To restore M5000 configuration run:

XSCF> restoreconfig -v -V -u root ftp://mgmt_host/root/sap02-c.dumpconfig

The M5000 power-cycle is needed once this command is finished.

Example: M5000 with 4 domains

The ioxadm manages External I/O Expansion Units

XSCF> ioxadm  list
IOX                      Link 0                   Link 1
IOX@X4M9                 IOU#1-PCI#4              IOU#0-PCI#4

XSCF> ioxadm  -v list
Location                 Type       FW Ver     Serial Num Part Num                 State
IOX@X4M9                 IOX        2.4        XCX4M9     CF00501-6937 07/5016937-07 On
IOX@X4M9/PS0             A195       -          DD6025     CF00300-1701 06/3001701-06 On
IOX@X4M9/PS1             A195       -          DD6046     CF00300-1701 06/3001701-06 On
IOX@X4M9/IOB0            PCIE       -          XE06JF     CF00501-6939 08/5016939-08 On
IOX@X4M9/IOB0/LINK       OP         2.4        XF071M     CF00501-7040 07/5017040-07 On
IOU#1-PCI#4              OP         2.5        XF0FNK     CF00501-7040 08/5017040-08 On
IOX@X4M9/IOB1            PCIE       -          XE06MW     CF00501-6939 08/5016939-08 On
IOX@X4M9/IOB1/LINK       OP         2.4        XF0740     CF00501-7040 07/5017040-07 On
IOU#0-PCI#4              OP         2.4        XF0776     CF00501-7040 07/5017040-07 On

Back to the main page