| Dynamic Reconfiguration User's Guide I/O device edition - for Solaris (TM) Operating System - |
|
Contents
|
| Chapter 4 Network Devices | > 4.1 Replacement Procedure |
When the PCI cards are needed to be replaced in non-redundant configuration without using redundant software, it is necessary to stop all the high-level products (services) as applications that are using these PCI cards.
The replacement procedures of PCI cards for non-redundant configuration are below.
Using the following procedures, locate the system boards equipped with the faulty PCI cards and the connected interfaces.
| # /opt/FJSVhwr/sbin/drcstat -device | grep hme <Return> 00-ONBOARD "/pci@83,4000/network@1,1" 0 "hme" 01-PCI#3B "/pci@87,4000/SUNW,hme@2,1" 2 "hme" 01-ONBOARD "/pci@87,4000/network@1,1" 1 "hme" # /opt/FJSVhwr/sbin/drcstat -device sb01 <Return> 01-PCI#0B "/pci@84,4000/scsi@2" 2 "glm" 01-PCI#0B "/pci@84,4000/scsi@2,1" 3 "glm" 01-PCI#0B "/pci@84,4000/scsi@2/sd@1,0" 1 "sd" 01-PCI#0B "/pci@84,4000/scsi@2/sd@3,0" 20 "sd" 01-PCI#3B "/pci@87,4000/SUNW,hme@2,1" 2 "hme" 01-ONBOARD "/pci@87,4000/ebus@1/FJSV,scfc@14,200000" 1 "FJSVscf2" 01-ONBOARD "/pci@87,4000/ebus@1/FJSV,se@14,400000" 1 "se" 01-ONBOARD "/pci@87,4000/network@1,1" 1 "hme" |
The above example shows the relevant interface is hme2("/pci@87,4000/SUNW,hme@2,1" 2 "hme"), and so the faulty PCI card is equipped with the PCI slot#3B of the system board#01.
And it is understood that the hme1 and SCSI devices excluding hme2 exist on the relevant system board from the results of execution of the second command.
It is possible to ignore about se driver and scf driver (FJSVscfx) with the redundant configuration automatically.
Refer to "Enhanced Support Facility User's Guide" for details of se driver and scf driver.
Stop the high-level applications that are using the interfaces located in step 1.
When connecting SCSI devices that are using as the above example, refer to "Chapter 3 File Devices" about how to stop them.
When using Quad 10/100 Ethernet Card(PW008QE1/2) or Quad GigabitEthernet card(PW008QG1), it is necessary to stop all high layer applications that are using four ports of the card for the replacement. Please refer to the reference guide of each driver product to specify the port numbers of the card.
1) Checking the IP address and host name of the interface to be stopped.
For example, run the ifconfig(1M) command, see the files /etc/hostname.interface and /etc/inet/hosts.
# ifconfig hme2 <Return>hme2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.10.1 netmask ffffff00 broadcast 192.168.10.1 ether 0:0:e:25:0:d6
# grep 192.168.10.1 /etc/inet/hosts <Return>
192.168.10.1 kscl05
2) Stopping the use of the relevant interface of high-level applications.
Check the remote hosts communicating with the relevant interface by the netstat(1M) command.
# netstat | grep kscl105 <Return> (If the host name is ksc105)kscl105.32790 kscl103.9798 24820 0 24820 0 ESTABLISHED
kscl105.telnet kscl103.56528 24820 0 24820 0 ESTABLISHED
kscl105.32945 kscl105.fjwv_s 32768 0 32768 0 ESTABLISHED
kscl105.fjwv_s kscl105.32945 32768 0 32768 0 ESTABLISHED
kscl105.33075 kscl105.32776 32768 0 32768 0 TIME_WAIT
kscl105.33076 kscl105.32776 32768 0 32768 0 TIME_WAIT
kscl105.33077 kscl105.32776 32768 0 32768 0 TIME_WAIT
kscl105.33078 kscl105.32776 32768 0 32768 0 TIME_WAIT
kscl105.telnet kscl101.1888 63949 3 24820 0 ESTABLISHED
kscl105.33079 kscl105.32776 32768 0 32768 0 TIME_WAIT
kscl105.33080 kscl105.32776 32768 0 32768 0 ESTABLISHED
kscl105.32776 kscl105.33080 32768 0 32768 0 ESTABLISHED
Stop communication with checked remote hosts. If a connection has been established from the remote host side, stop the communication from the remote host side to stop access to the relevant interface.
3) Inactivating the high-level drivers.
Inactivate the relevant interface of TCP/IP.
# ifconfig hme2 down <Return># ifconfig hme2 unplumb <Return>
When using the FNA or SNA interface as a high-level protocol for non-redundant configuration, it is impossible to replace the located interface only, and so it is necessary to inactivate all interfaces of the system.
To replace the located interface only, it is required to be redundant configuration using the multipath function of SynfinityLink or PRIMECLUSTER GLS.
1) Stopping the high-level applications.
Stop the high-level applications using the FNA or SNA interface as Netcompo application conversation service etc.
Refer to the manual for each high-level application product about how to stop them.
2) Inactivating the high-level drivers.
Inactivate the high-level drivers as Netcompo FNA-BASE etc.
Refer to the manual for each high-level driver product about how to inactivate them.
3) Inactivating the low-level drivers.
Inactivate the low-level drivers as Netcompo FNA-LAN etc.
Refer to the manual for each low-level driver product about how to inactivate them.
When using PCI card drivers on target system boards, the drc(1M) command terminates abnormally. So go back to the stopping the high-level products.
| # /opt/FJSVhwr/sbin/drc -disconnect sb01 -keep <Return> |
Notes
When the ATM cards (GP7B8AT1) are mounted on more than one system board, the operation below cannot be performed for the system boards on which the ATM cards are mounted.
Performing this operation will also disable communication by the ATM card.
1) Detaching the system board during configuration modification via system reboot
# drc -connect sb01 -reset <Return><System reboot>
2) Moving a system board to another partition
# drc -disconnect sb01 -next 1 -reset <Return><System reboot>
| # /opt/FJSVhwr/sbin/drcstat -board sb01 SB BN Status (Detail) PID Next_PID Board_Type CPU(MHz) -- -- --------------- --- -------- ---------- -------- 01 0 Unconfigured 00 00 10 300 |
Pull out the detached system boards and replace the faulty PCI cards located in step 1 to replacement parts, then mount back the system boards. A certified service engineer takes charge of this work.
| # /opt/FJSVhwr/sbin/drc -connect sb01 <Return> |
| # /opt/FJSVhwr/sbin/drcstat -board sb01 SB BN Status (Detail) PID Next_PID Board_Type CPU(MHz) -- -- --------------- --- -------- ---------- -------- 01 0 Configured 00 00 10 300 |
1) Activating the high-level drivers.
Activate the relevant interface of TCP/IP.
# ifconfig hme2 plumb <Return># ifconfig hme2 hostname netmask netmask up <Return>
2) Restarting the high-level applications.
Restart high-level applications using the relevant interface.
Using the steps below, restart the stopped high-level products.
1) Activating the low-level drivers.
Activate the low-level drivers as Netcompo FNA-LAN etc.
Refer to the manual for each low-level driver product about how to activate them.
2) Activating the high-level drivers.
Activate the high-level drivers as Netcompo FNA-BASE etc.
Refer to the manual for each high-level driver product about how to activate them.
3) Restarting the high-level applications.
Restart the high-level applications using the FNA or SNA interface as Netcompo application conversation service etc.
Refer to the manual for each high-level application product about how to start them.
|
Contents
|