Sun Fire E25K Server
 
Sun Fire E20K Server
 
Sun Fire 12K Server
 
Sun Fire 15K Server
 
Sun Enterprise 10000 Server
 

GCS>Sun Microsystems>Servers>High-End Servers
 

Applies to:

Goal

Solution

ok  setenv  dr-max-mem 1
or
# eeprom dr-max-mem=1

ok  setenv  dr-max-mem 1
or
# eeprom dr-max-mem=1

* DR enabled set  kernel_cage_enable=1
* DR entry complete

1. To add a board (ex. SB6):
   
   
   ssp:domain% dr
dr>  init_attach  6
dr> drshow  6  obp (to verify board inventory)
dr> complete_attach 6
dr> exit
   
   
   
2. To remove a board (ex. SB6):
   
   NOTE:  Stop edd so that no Recordstops can occur during a detach DR operation.
   If a Recordstop were to occur during a DR operation, the domain will have to be STOPPED!
   
   Therefore, you should stop 'edd' and then re-start it again after DR is finished with the 'edd_cmd' command:
   
   
   ssp% edd_cmd -x stop
ssp:domain% dr
dr>  drain 6
dr>  drshow 6  IO  (determine if there is active I/O on board being detached)
dr>  complete_detach 6
dr>  reconfig
dr>  exit
Restart edd again:
ssp% edd_cmd -x start
   
   

These automated methods may be used for DR operations:

1. addboard -d <domain> [-f] [-q] {-b board_number | SB<x>}
2. moveboard -d <domain> [-f] [-q] {-b board_number | SB<x>}
3. deleteboard -d <domain> [-f] [-q] {-b board_number | SB<x>}
   

Adding a board (ex. SB6):
ssp% addboard -b 6 -d domain_name -r 2 -t 600
where (-b) is SB#, (-d) is domain name, (-r) is # of retries, (-t) timeout

Removing a board (ex. SB6):
ssp% deleteboard -b 6 -r 2 -t 900

Moving a board (ex. SB6):
ssp% moveboard -b 6 domain_name -r 2 -t 900

If any RT (real-time) processes are running on a domain, it will prevent a DR from completing. These processes must be stopped for DR to work properly, if it complains about them. Use the command:

ssp% ps -eo class | grep RT

to identify which PIDs(Process Ids) to kill if necessary. Be aware of which RT processes are running, and what their exact function is. Be sure to understand any adverse affects that may arise if these processes are killed manually.

1. addboard -d <domain_id|domain_tag> [-q] [-f] <SB 0-17 or IO 0-17>
2. moveboard -d <domain_id|domain_tag> [-q] [-f] <SB 0-17 or IO 0-17>
3. deleteboard [-q] [-f] <SB 0-17 or IO 0-17>
   

Examples:
sms> addboard -d A SB10
sms> moveboard -d B SB7
sms> deleteboard SB0

sc0:sms-user:> rcfgadm -d <domain_id|domain_tag> [-f] [-v] -c <function> <APID>
            function  -  assign | unassign, configure | unconfigure, or connect | disconnect
           APIDs  - can be either logical or physical, and are either static or dynamic.

PHYSICAL EXAMPLES:
/devices/pseudo/dr@0:IO4
/devices/pseudo/dr@0:IO6
/devices/pseudo/dr@0:IO14
/devices/pseudo/dr@0:SB4
/devices/pseudo/dr@0:SB6

LOGICAL EXAMPLES:
IO4, IO6, IO14, SB4, SB6

STATIC AP TYPES:
HPCI, CPU, MCPU, pci-pci/hp

DYNAMIC AP TYPES:
cpu, mem, io

Examples:

sc0:sms-user:> rcfgadm -d a -f -c configure SB6
sc0:sms-user:> rcfgadm -d a -c unconfigure IO14
sc0:sms-user:> rcfgadm -d a -c configure SB6
sc0:sms-user:> rcfgadm -d a -c configure pcisch3:e06B1slot2  <--DR an I/O component (See Below)

Breakdown of specific I/O card to DR:

Example from above: sc0:sms-user:> rcfgadm -d a -c configure pcisch3:e06B1slot2

pcisch<#>:   This represents the pcisch device instance number.  The example shows that the device being configured is pcisch3, the third instance of a pcisch device for this domain.  Prior to configuring a new device instance, you should do a grep pcisch /etc/path_to_inst on the domain to confirm what instances of the device are currently configured.  Choose the next available instance to configure into the domain. 

e<#>:   This indicates the Expander Board location of this device.  The example shows that this is e06, indicating the device is located on Expander 06.

B1:   Indicates a slot1-type board.

NOTE:  The board type will always be B1 on a Sun Fire[TM] 12K/15K/E20K/E25K for the I/O devices, because a slot1 board is the only type of board where these devices can be installed.

Slot<#>:   Indicates the Cassette slot# (1-4) that the device is located in on a slot1 board.  The example above shows slot2.
This is the Bottom Left cassette slot on the I/O Board.

See Technical Instruction Document: 1017493.1 for a diagram. 

rcfgadm -d a        lists all attachment points except dynamic points.
rcfgadm -d a -al    lists all current configurable hardware information (including dynamic).
rcfgadm -d a -avl   lists all current configurable hardware in verbose mode.

cfgadm [-f] [-v] -c <function> <APID>

References

This solution has no attachment