PCI Hot Plug User's Guide I/O device edition - for Solaris(TM) Operating System -

4.2.2 Extension of PCI cards with new redundant system

This subsection describes extension procedure of a new redundant system with the following redundant configuration software.

• SynfinityLink 2.2
• PRIMECLUSTER GLS 4.0 or later

The replacement and extension of PCI cards are supported only on Redundant Line Control Function of SynfinityLink.

Notes:
Because of the dynamic exteinsion, if the environment of SynfinityLink or PRIMECLUSTER GLS was newly added, system reboot is not required.

When using other redundant software, please refer to manuals of each product.

1. Stop the hardware monitoring of the Machine Administration

   The hardware monitoring of the Machine Administration is stopped by using the following command.

   # /usr/sbin/FJSVmadm/prephp <Return>

2. Add PCI cards
   1. Before extending the PCI card, please save the result (current configuration information) of the prtpicl (1M) command.

      # prtpicl -v > /tmp/prtpicl.pre <Return>

   2. Check the status of the slot.

      Subsequent examples describe extension of PCI cards to the slot "R0B01-PCI#slot02." The "R0B01-PCI#slot02" indicates the I/O cabinet number : 0, the PCI / Disk Box number : 1, physical slot number : 02.

      In the extension of a new redundant system, although two or more PCI cards are extended, whenever you add a PCI card, please perform from procedure "2.b" to "3. Connect PCI cards."

      The relationship of the position of a PCI card and format of "Ap_Id" is shown below. (N: an integral number)

      Location of PCI slot	Element	Format of "Ap_Id"
      Cabinet of PRIMEPOWER 900/1500/2500	Cabinet Number : X System Board Number : Y Physical Slot Number : ZZ	Solaris 8 OS and Solaris 9 OS pcipsyN:CXM0Y-PCI#slotZZ Solaris 10 OS CXM0Y-PCI#ZZ
      PCI / Disk Box	I/O Cabinet Number : X PCI / Disk Box Number : Y Physical Slot Number : ZZ	Solaris 8 OS and Solaris 9 OS pcipsyN:RXB0Y-PCI#slotZZ Solaris 10 OS RXB0Y-PCI#ZZ
      other than those above	Physical Slot Number : ZZ	Solaris 8 OS and Solaris 9 OS pcipsyN:PCI#slotZZ Solaris 10 OS PCI#ZZ

      Please confirm that the PCI slot status which extended PCI cards is "empty unconfigured" by using cfgadm (1M) command.

      # cfgadm | grep R0B01-PCI#slot02 <Return>
      pcicsy18:R0B01-PCI#slot02 unknown empty unconfigured unknown

   3. To confirm the slot position at extension operation, blink the ALARM LED of Ap_Id displayed in procedure 2.b.

      # cfgadm -x led=fault,mode=blink pcipsy18:R0B01-PCI#slot02 <Return>

   4. Please confirm that READY LED of the PCI bus slot that extends a PCI card has gone out, and extend a PCI card. This operation is performed by our customer support.
   5. Please confirm that the PCI slot status which extended PCI cards is "disconnected unconfigured" by using cfgadm (1M) command.

      # cfgadm pcipsy15:R0B01-PCI#slot02 <Return>
      Ap_Id Type Receptacle Occupant Condition
      pcicsy18:R0B01-PCI#slot02 unknown disconnected unconfigured unknown

3. Connect PCI cards

   The cfgadm command is executed with the "configure" option to "Ap_Id," or the push button of the PCI bus slot is pushed. Then a extended PCI card is connected.

   In addition, a push button is valid only in multiple user mode.

   Please confirm that the slot status is "connected configured" by using the cfgadm (1M) command after the above-mentioned procedure.

   # cfgadm -c configure pcipsy18:R0B01-PCI#slot02 <Return>
   # cfgadm pcipsy18:R0B01-PCI#slot02 <Return>
   Ap_Id Type Receptacle Occupant Condition
   pcipsy18:R0B01-PCI#slot02 pci-pci/hp connected configured ok

4. Start the hardware monitoring of the Machine Administration

   Please execute the following command in order to update configuration information, and restart the hardware monitoring of the Machine Administration.

   # /usr/sbin/FJSVmadm/postphp <Return>

5. Connect equipment to PCI cards

   The extended PCI card is connected with network equipment by the cable.

6. Setup driver

   The driver configuration is added by following operations.

   1. The interface name is investigated in order to configure drivers and high layer products.

      Please save the result of the prtcicl (1M) command, and obtain the difference information between current result and the result taken at "2.a." Then, the driver instance number for the extended PCI card is obtained.

      In the following example, since the instance number is 1, it can be determined that the interface name of the extended PCI card is "hme1."

      # prtpicl -v > /tmp/prtpic.post <Return>
      # diff /tmp/prtpicl.pre /tmp/prtpicl.post | more <Return>
      :
      > :status okay
      > :devfs-path /pci@8d,2000/network@1
      > :driver-name hme
      > :binding-name SUNW,hme
      > :bus-addr 1
      > :instance 1
      > :_class obp-device
      > :name network
      :

   2. It confirms that the interface name that obtained above-mentioned procedure is an interface name that corresponds to the PCI bus slot of the added PCI card.

      Please carry out this procedure, when it cannot identify relationship between an interface name and PCI bus slot by expanding two or more PCI cards especially.

      # /usr/sbin/FJSVmadm/inst2comp hme1 <Return>
      pcicsy18:R0B01-PCI#slot02

   3. The configuration of each driver is added.

      Please refer to each driver manual for details.

7. Setup redundant system

   When establishing the redundant configuration system, it is necessary to configure the environmental configuration of the Redundant Line Control Function or the Multipath Function, and to activate the redundant configuration system.

   For details of environmental configuration and activation, please refer to each function manual of SynfinityLink or PRIMECLUSTER GLS.

8. Setup applications

   The configuration of high layer product (services, applications) is added.

   Please refer to the manual of each high layer product for details.

9. Start applications

   By following operations, please start the high layer product.

   1. When using TCP/IP interface

      The high layer product (services, applications) using the TCP/IP interface is started.

      For details of starting the high layer products, please refer to the manual of each product.

   2. When using FNA/SNA communication protocol over Ethernet

      It is necessary to start all interfaces of Netcompo FNA-LAN, and all high layer applications that are using Netcompo FNA-LAN. When using the Multipath Function, the FNA (Fujitsu Network Architecture) /SNA (System Network Architecture) communication protocol over Ethernet is valid.

      For details, please refer to the manual of Netcompo FNA-LAN and high layer applications.