How to Replace/Swap a Oracle Fabric Interconnect Chassis

Asset ID:	1-71-1519032.1
Update Date:	2017-10-19
Keywords:

Solution Type Technical Instruction Sure

Solution 1519032.1 : How to Replace/Swap a Oracle Fabric Interconnect Chassis

Applies to:

Oracle Fabric Interconnect F1-15 - Version All Versions and later
Oracle Fabric Interconnect F1-4 - Version All Versions and later
Information in this document applies to any platform.

Goal

Replace/Swap a Oracle Fabric Interconnect Chassis

Solution

To swap Oracle Fabric Interconnect Chassis follow these steps:

NOTE :: OVN TSEs, please use this internal KB for up-to-date instructions on how to program the midplane WWN and MAC, based upon specific XgOS release. These instructions are internal only and will not be posted in a public facing / accessible KB:

How to Perform Chassis Swap and Retain Failed VP780/VP560 (F1-15 and F1-4) WWN, MAC Addresses and Current Config (Doc ID 1518446.1)

Step 1. On the old director, run the following command (# sign is a place holder for the prompt, not part of the command):

# system export <fabric interconnect name>-<date>

Exported config from command above, is created as a .xml file.

Copy this file down from the director to your local machine via SCP., or use your favorite FTP/SFTP client such as WinSCP, or Filezilla, log into the Fabric Interconnect as user root and traverse to the /var/fsroot/admin folder where you will find the exported config file (date) to pull off to local system for safe keeping. OR from "admin" CLI use the "file copy" command with SCP:

# file copy <exported config filename> scp://<username>@<ip address>:/<path>/

Step 2. Since you will be re-using the existing Front Panel from the failed Fabric Interconnect chassis, you do not have to remove any existing vnics/vhbas from the replacement chassis since it will not have any configuration (replacement chassis only ships with Fabric Board, it does not have Front Panel, fan trays, PSUs, IO modules, or IB cables. All the devices just named will be removed from the failed Fabric Interconnect chassis and put into the new replacement chassis, making sure to put the IO Modules in the exact same slots they were in, in the failed chassis.

The "config" exists on the Gen2 Panel HDD and on the SCP Controller of a Gen1 Front Panel (there aren't many customers who have these anymore as most have been upgraded to Gen2 Front Panel.

Next, run the following steps. Oracle Support will send you the token to use once the serial number and MAC/WWN address pool information from the failed IO Director and the replacement IO Director is obtained.

On the replacement chassis:

Step 3. Program the replacement IO Director with the failed IO Directors MAC and WWN by using the token Xsigo Support sends to you.

# admin@xsigo-001397001256[xsigo] set system mac-wwn <token>

This command will change the base MAC and WWN addresses for this director.

This is a major change that will invalidate any virtual NIC or HBA addresses. You must remove all vNICs and vHBAs after the command completes. Are you sure
you want to do this (y/n)?y

Step 4. Reboot the IO Director:

admin@xsigo-001397001256[xsigo] system cold-restart
Restarting the Director may disrupt IO traffic on attached servers. Are you
sure you want to restart the system (y/n)?y

Step 5. Verify the new base MAC and WWN on the replacement IO Director:

admin@xsigo-001397001256[xsigo] show hardware
#
# Xsigo System Hardware Status
# Model: VP560-CH-DDR
# Serial: 151015603
# Base MAC: 00:13:97:1C:E0:00
# Base WWN: 50:01:39:70:00:1B:F0:00

NOTE :: It has been confirmed that when replacing failed IO Director but using the original SCP/FP from the failed Director, the below step must be completed. If the failed Fabric Director failed hard prohibiting export of current working configuration, use saved configuration from most recent phone-home, or most recent Xsigo problem log bundle (get-log-files -all' bundle includes the config.xml. It may be named something like '<chassis_name>-<date>.xml'.

Step 6. Edit the desired configuration file by replacing the existing serial number with the replacement serial number. If not, the following error will occur:

admin@xsigo-001397001256[xsigo] system import rc5b1
This will import the configuration and commit the changes. Are you sure you
want to import this configuration into the system (y/n)?y
Chassis Serial Number changed, original(151015603), importing(061014817).

OR to avoid editing the config.xml file do this:

NOTE: The'system import' command must use the '-foreign' option since replacement IO Director has different S/N:

# system import rc5b1 -foreign

Attachments

This solution has no attachment