The PCI card using the PHP function is replaced with the rvnetadm disconnect command and the rvnetadm connect command. These commands are used when disconnecting or reconnecting a physical NIC assigned under the virtual NIC.
Note
When using PHP, execute the following command to enable the hotplug service. For details, refer to the service manuals.
# svcadm enable hotplug
Procedure when disconnecting a NIC
This section describes the procedure for disconnecting a PCI card built into the target system board temporarily from the virtual NIC when replacing a system board due to a failure or other reason.
Figure 6.4 Disconnecting procedure
Disconnect a NIC from a virtual NIC
Disconnect a NIC that is to be replaced from the virtual NIC with the rvnetadm disconnect command.
# /opt/FJSVrvnet/bin/rvnetadm disconnect -n fjvnet0 -i net1
See
For details on the rvnetadm command, see "A.1 rvnetadm command."
Disconnecting the PCI card
Confirm that the slot status of the PCI slot "slot03" to be disconnected is "connected configured."
# cfgadm BB#0-PCI#0 Ap_Id Type Receptacle Occupant Condition BB#0-PCI#0 etherne/hp connected configured ok
Execute the uncfgadm(1M) command with specifying unconfigure to cancel the configuration of the PCI card at Ap_Id.
After that, execute the cfgadm(1M) command to check if the slot status is changed to "connected unconfigured".
# cfgadm -c unconfigure BB#0-PCI#0 <Return> # cfgadm BB#0-PCI#0 <Return> Ap_Id Type Receptacle Occupant Condition BB#0-PCI#0 unknown connected unconfigured unknown
Execute the cfgadm(1M) command with specifying disconnect to disconnect the PCI card from Ap_Id.
After that, execute the cfgadm(1M) command to check if the slot status is changed to "disconnected unconfigured".
# cfgadm -c disconnect BB#0-PCI#0 <Return> # cfgadm BB#0-PCI#0 <Return> Ap_Id Type Receptacle Occupant Condition BB#0-PCI#0 unknown disconnected unconfigured unknown
To indicate the slot position for replacement, specify the obtained "Ap_Id" to "cfgadm" command and blink the ATTENTION LED.
# cfgadm -x led=attn,mode=blink BB#0-PCI#0 <Return>
See
For details on the cfgadm(1M) command, see the Solaris manual.
For details on disconnecting the PCI card, see the service guide.
Procedure when connecting a NIC
This section describes the procedure for embedding the NIC built into the target system board to the virtual NIC again when replacing a system board due to a failure or other reason.
Figure 6.5 Connecting procedure
Reconnecting the PCI card
Execute the uncfgadm(1M) command with specifying connect to connect the new PCI card to Ap_Id.
After that, execute the cfgadm(1M) command to check if the slot status is changed to "connected unconfigured".
# cfgadm -c connect BB#0-PCI#0 <Return> # cfgadm BB#0-PCI#0 <Return> Ap_Id Type Receptacle Occupant Condition BB#0-PCI#0 unknown connected unconfigured unknown
Specify the target Ap_Id and execute the cfgadm(1M) command with specifying configure to install the new PCI card.
After that, execute the cfgadm(1M) command to check if the slot status is changed to "connected configure".
# cfgadm -c configure BB#0-PCI#0 <Return> # cfgadm BB#0-PCI#0 <Return> Ap_Id Type Receptacle Occupant Condition BB#0-PCI#0 etherne/hp connected configured ok
See
For details on the cfgadm(1M) command, see the Solaris manual.
For details on reconnecting the PCI card, see the service guide.
Reconnecting a NIC to the virtual NIC
Reconnect all NICs built into the replaced system board to the virtual NIC with the rvnetadm connect command. If changing the active path through the hot swap, fail back the active path as necessary.
# /opt/FJSVrvnet/bin/rvnetadm connect -n fjvnet0 -i net1
See
For details on the rvnetadm command, see "A.1 rvnetadm command."
