Applies To:

Show Versions Show Versions

sol13965: Overview of the automated process of joining a newly installed or RMA replacement VIPRION blade to the cluster
OverviewOverview

Original Publication Date: 11/05/2012
Updated Date: 08/14/2014

Summary

The following information should provide assistance when monitoring the status of the newly installed or Return Materials Authorization (RMA) replacement blade as it becomes a member of the cluster.

Description

The slots in a VIPRION chassis work together as a single, powerful unit. This entity is called a cluster. The size of the cluster depends on the number of running blades installed in the chassis. When a blade is installed in a slot and is turned on, the blade automatically becomes a member of the cluster. For the newly installed blade to become a member of a cluster, the following automated events occur without user interaction:

The system boots the newly inserted blade

If you monitor the newly inserted blade by way of the blade's console port, a login prompt is displayed when the system completes this initial boot. However, the blade is not yet an online or active member of the cluster. The system places the newly inserted blade into 'quorum' status.

You can view the status of the newly inserted blade at this time, using the tmsh show sys cluster command on the primary blade. The output of the command displays the quorum status, which appears similar to the following example:

---------------------------------------
Sys::Cluster: default
---------------------------------------
Address                 172.24.24.42/24
Availability            available
State                   enabled
Reason                  Cluster Enabled
Primary Slot ID         1
Primary Selection Time  0

  -----------------------------------------------------------------------
  | Sys::Cluster Members
  | ID  Address       Availability  State     Licensed  HA       Clusterd
  -----------------------------------------------------------------------
  | 1   172.24.24.41  available     enabled   true      active   running
  | 2   172.24.24.40  available     enabled   true      active   running
  | 3   172.24.24.39  unavailable   enabled   false     active   quorum
  | 4   ::            unknown       disabled  false     unknown  shutdown

Note: The BIG-IP system's Traffic Management Microkernel (TMM) can take an additional 30 seconds to begin processing traffic after the high availability (HA) status becomes active. To verify TMM's availability, run the tail -f /var/log/ltm | grep command when you are able to log in, and then wait for the HA reports tmm ready message. The confirmation message appears similar to the following example: slot1/VIP4400 notice sod[5611]: 01140044:5: HA reports tmm ready

The system copies software images from the primary blade to the newly inserted blade

The system automatically copies software images from the primary blade to the newly inserted blade to ensure that the software images for each boot location match the other blades in the cluster.

You can use the tmsh show sys software status command on the primary blade to determine if the newly inserted blade needs a software image from the primary blade. The command displays the waiting for product image status for each boot location needing a new software image. The output of the command appears similar to the following example:

--------------------------------------------------------------------------------
Sys::Software Status
Volume  Slot  Product  Version   Build  Active                                     Status
--------------------------------------------------------------------------------
HD1.1      1   BIG-IP   11.1.0  1943.0      no                                   complete
HD1.1      2   BIG-IP   11.1.0  1943.0      no                                   complete
HD1.1      3   BIG-IP   11.1.0  1943.0     yes                                   complete
HD1.2      1   BIG-IP   11.2.1   797.0     yes                                   complete
HD1.2      2   BIG-IP   11.2.1   797.0     yes                                   complete
HD1.2      3   BIG-IP   11.1.0  1943.0      no  waiting for product image (BIG-IP 11.2.1)
HD1.3      1   BIG-IP   10.2.4   577.0      no                                   complete
HD1.3      2   BIG-IP   10.2.4   577.0      no                                   complete
HD1.3      3   BIG-IP   11.2.0  2446.0      no  waiting for product image (BIG-IP 10.2.4)

No user interaction is required; the system automatically copies the software images from the primary blade. However, it may take several minutes for this to occur.

The system installs software images on the newly inserted blade to match the boot locations of the primary blade

Once the software images are copied from the primary blade to the proper boot location of the newly installed blade, the installation of the software begins.

You can monitor the status of the software installation using the tmsh show sys software status command on the primary blade. The command output indicates the installation completion percentage. The output of the command appears similar to the following example:

--------------------------------------------------------------------------------
Sys::Software Status
Volume  Slot  Product  Version   Build  Active                                     Status
--------------------------------------------------------------------------------
HD1.1      1   BIG-IP   11.1.0  1943.0      no                                   complete
HD1.1      2   BIG-IP   11.1.0  1943.0      no                                   complete
HD1.1      3   BIG-IP   11.1.0  1943.0     yes                                   complete
HD1.2      1   BIG-IP   11.2.1   797.0     yes                                   complete
HD1.2      2   BIG-IP   11.2.1   797.0     yes                                   complete
HD1.2      3   BIG-IP   11.1.0  1943.0      no  waiting for product image (BIG-IP 11.2.1)
HD1.3      1   BIG-IP   10.2.4   577.0      no                                   complete
HD1.3      2   BIG-IP   10.2.4   577.0      no                                   complete
HD1.3      3   BIG-IP   10.2.4   577.0      no                      installing 90.000 pct

You can continue to monitor the status of the software installation by repeating the command on the primary blade.

---------------------------------------------------------------------
Sys::Software Status
Volume  Slot  Product  Version   Build  Active                 Status
---------------------------------------------------------------------
HD1.1      1   BIG-IP   11.1.0  1943.0      no               complete
HD1.1      2   BIG-IP   11.1.0  1943.0      no               complete
HD1.1      3   BIG-IP   11.1.0  1943.0     yes               complete
HD1.2      1   BIG-IP   11.2.1   797.0     yes               complete
HD1.2      2   BIG-IP   11.2.1   797.0     yes               complete
HD1.2      3   BIG-IP   11.2.1   797.0      no  installing 10.000 pct
HD1.3      1   BIG-IP   10.2.4   577.0      no               complete
HD1.3      2   BIG-IP   10.2.4   577.0      no               complete
HD1.3      3   BIG-IP   10.2.4   577.0      no               complete

The newly inserted blade reboots to complete the software installation

Once the software installation is complete, the newly inserted blade displays messages that appear similar to the following example, and then reboots:

slot3/VIP4400-R24-S42 emerg overdog[4097]: 01140043:0: Ha feature software_update reboot requested.
INIT: Switching to runlevel: 6 (reboot)
INIT: Sending processes the TERM signal
INIT: Sending processes the KILL signal
Shutting down smartd: [  OK  ]
Using bigstart to shutdown Big-IP:

The system may reboot the newly inserted blade an additional time to update the firmware

As the blade boots up following the software installation, it may require an additional reboot to update the firmware. If the firmware requires an update, the system displays messages that appear similar to the following on the blade's console:

Checking for firmware updates:
...
Updating HSB on mezzanine to version 1.4.2.0... DO NOT INTERRUPT
Erasing flash... (may take up to 30 secs)
Programming flash...
HSB firmware update: the system will automatically reboot to activate slot 1.
Updating HSB on main to version 1.4.2.0... DO NOT INTERRUPT
Erasing flash... (may take up to 30 secs)
Programming flash...
HSB firmware update: the system will automatically reboot to activate slot 1.
INIT: Sending processes the TERM signal
Using bigstart to shutdown Big-IP:

Following this reboot, the blade boots to the same active boot location as the primary blade. As the blade boots back up following the firmware update, the system displays messages that appear similar to the following, to the blade's console:

Checking for firmware updates:
...
Successful update to HSB v1.4.2.0
Successful update to HSB v1.4.2.0

The system activates the newly inserted blade's license

Once the blade has finished the required reboots, the system automatically activates the new blade's license. You can verify that the blade's license has been activated using the tmsh show sys cluster command on the primary blade. The Licensed column in the output of the command shows a status of true for the newly inserted blade. The output of the command appears similar to the following example:

---------------------------------------
Sys::Cluster: default
---------------------------------------
Address                 172.24.24.42/24
Availability            available
State                   enabled
Reason                  Cluster Enabled
Primary Slot ID         1
Primary Selection Time  0

  -----------------------------------------------------------------------
  | Sys::Cluster Members
  | ID  Address       Availability  State     Licensed  HA       Clusterd
  -----------------------------------------------------------------------
  | 1   172.24.24.41  available     enabled   true      active   running
  | 2   172.24.24.40  available     enabled   true      active   running
  | 3   172.24.24.39  offline       enabled   true      offline  running
  | 4   ::            unknown       disabled  false     unknown  shutdown

The system places the newly inserted blade online and it becomes active

A short time after the system activates the blade's license, the system places the blade online and it is active. You can verify that the blade is online and active using the tmsh show sys cluster command on the primary blade. The output of the command appears similar to the following example:

---------------------------------------
Sys::Cluster: default
---------------------------------------
Address                 172.24.24.42/24
Availability            available
State                   enabled
Reason                  Cluster Enabled
Primary Slot ID         1
Primary Selection Time  0

  -----------------------------------------------------------------------
  | Sys::Cluster Members
  | ID  Address       Availability  State     Licensed  HA       Clusterd
  -----------------------------------------------------------------------
  | 1   172.24.24.41  available     enabled   true      active   running
  | 2   172.24.24.40  available     enabled   true      active   running
  | 3   172.24.24.39  available     enabled   true      active   running
  | 4   ::            unknown       disabled  false     unknown  shutdown

Recommendations

None

Supplemental Information

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)