This section provides the procedures to restore the USB key Complete System Backup onto the new AMC121 CPU. This process comprises the following procedures:
To install the O/S on the new AMC121 CPU using the USB key
Tip
In this example, the Carrier blade slot is 14 and the new AMC121 CPU is in subslot 4.
From the VSE CLI interface, deactivate the new AMC121 CPU, if the new AMC121 CPU is not deactivated yet.
hardware app-blade deactivate <frame shelf slot subslot>
For example,
ha app-blade deactivate 0 0 14 4
If not already done so, insert the USB key into the USB port on the new AMC121 CPU.
From the VSE CLI, activate the new AMC121 CPU.
hardware app-blade activate <frame> <shelf> <slot> <subslot>
For example,
ha app-blade activate 0 0 14 4
Press F2 while the AMC121 CPU is powering up to enter the BIOS.
If the AMC121 CPU starts to lilo boot, you have missed the chance to press F2. In this case, try again to deactivate, and then re-activate the card using the VSE CLI interface by entering the following.
For example,
ha app-blade deactivate 0 0 14 4
ha app-blade activate 0 0 14 4
Navigate to the Main window and make sure that the System Time and the System Date are set to the local time and date on the working CPU and the other CPU in the operation regardless of timezone.
Caution
You must set the System Time and the System Date to the local time and date on the working CPU and the other CPU in operation regardless of timezone in this step even if you have done this task before. Otherwise, the system will not function as expected.
For example, if the local time on the working CPU is 07:30:25 EST, the time entered in the BIOS on the new AMC121 CPU and the other working CPU has to be 07:30:25 even though the timezone is not entered.
- Navigate to the Exit window, select Load Custom/Optimal Defaults, and press ENTER.
- Select OK, and press ENTER.
- Navigate to the Boot window and select Hard Disk Drives.
- Select the 1st Drive, highlight the device that corresponds to the USB key and press ENTER.
Select 2nd Drive, highlight the device that corresponds to the AMC121 CPU's SD card, and press ENTER.
The second boot drive should be the AMC121 CPU's SD card (USB: Single Flash Reader) and the third boot drive should be the AMC121 CPU's hard drive, which should be in the format SATA: <hd manufacturer/model>. In the following example, the hard drive entry is SATA:PM-FUJITSU MH.
Navigate to the Exit window, select Save Changes and Exit, and press ENTER.
Enter root and press ENTER.
CentOS Linux 7 (Core)
Kernel 3.10.0-693.21.1.el7.sonus06.x86_64 on an x86_64
usb-os-installer login:
Enter y and press ENTER. The following appears on your screen.
+-------------------------------------+
| USB OS Installation |
+-------------------------------------+
Installation Details
================================================================================
Card Type: AMC121
Target Shared Storage Device:
Node: /dev/sda
Transport: ata
Description: ATA Hitachi HTE54322
Installer Key Device:
Node: /dev/sdb
Transport: usb
Description: Generic Flash Disk
Target Root File System Device:
Node: /dev/sdc
Transport: usb
Description: Single Flash Reader
Do you wish to repartition/reformat the logs/stats device /dev/sda (y/n)?
Enter y and press ENTER.
The system will be installed on device sdc.
Confirm (y/n)?
When prompted, remove the USB key and press ENTER to reboot the AMC121 CPU.
Please remove the USB key. Upon reboot into the OS installed on the permanent
drive there will be additional automated installation steps and a second reboot.
When this reboot has completed:
- for new install the login banner will indicate when system initialization
steps are required.
- for restore the data will be applied to the system and applications will
start.
Manual installation sanity checks can be performed at that time.
Please remove the USB key and press ENTER to continue (reboot).
<PRESS ENTER>
- If the AMC121 CPU does not boot without the USB key, go to the BIOS settings and make sure that the SD card is set as the first boot device.
- The screen output for Boot > Hard Disk Drive should appear as follows.
- The screen output for Boot >Boot Device Priority should appear as follows.
After the system reboots and the following prompts appear, go to the next step.
Enter root for login and the same password for the working CPU, and then press ENTER.
If the root password from the working CPU is not working, try to use password changeme instead.
Verify the OS version by running following command at Linux prompt on the new AMC121 CPU.
- Make sure that the Chassis Type is set to 13U or 14SLOT on the new AMC121 CPU. If unsure about which setting to use, refer to the output of the /usr/sbin/getChassisType command on the working CPU.
On the working AMC121 CPU, query the chassis type by entering the following:
# /usr/sbin/getChassisType
On a 13U 16slot system, this command will return 13U. On a 13U 14slot system, this command will return 14SLOT.
On the new AMC121 CPU, query the chassis type by entering the following:
# /usr/sbin/getChassisType
If the working CPU chassis type is 13U, and the new CPU does not match, on the new AMC121 CPU enter the following:
# /usr/sbin/setChassisType -c 13U
Set Chassis Type to 13U
If the working AMC121 CPU chassis type is 14SLOT, and the new AMC121 CPU does not match, on the new CPU enter the following:
# /usr/sbin/setChassisType -c 14SLOT
Set Chassis Type to 14SLOT
From the new AMC121 CPU, make sure that this CPU can ping its carrier card.
# ping -c 3 169.254.100.31
PING 169.254.100.31 (169.254.100.31) 56(84) bytes of data.
64 bytes from 169.254.100.31: icmp_seq=1 ttl=64 time=0.160 ms
64 bytes from 169.254.100.31: icmp_seq=2 ttl=64 time=0.154 ms
64 bytes from 169.254.100.31: icmp_seq=3 ttl=64 time=0.143 ms
--- 169.254.100.31 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.143/0.152/0.160/0.012 ms
To restore the data configuration on the new AMC121 CPU
Login to the new CPU.
echo (slot number) > /opt/restore_identity
For example, if the new CPU is supposed to be slot 24, type the following:
echo 24 > /opt/restore_identity
Enter the following, and press ENTER.
systemctl restart sonus-system
The CPU restores the data and then itself.
Tip
The CPU restore can take up to 15 minutes.