Synchronizing the Physical and Database Environment
After you have made changes to the physical state of the chassis, for example, removing or adding a blade, use the /opt/terraspring/sbin/shelfsync command to synchronize the CPDB with the physical state of the chassis. Synchronization is preceded by the task of discovering the device to be synchronized. This task is common to adding, removing, moving, and exchanging server blades. Therefore the discovery process and the related example is only shown once in the Adding, Moving, and Deleting Chassis Components section. Subsequent synchronization sections show only the recommended action and synchronization processes and related examples.
To Add Server Blades and Switch and System Controllers
Steps
-
Begin synchronization of the CPDB with the discovery of the chassis's physical state by entering the server blade's IP address or device ID when prompted to do so.
-
At the prompt, type your system controller username.
-
At the prompt, type your system controller password.
You are asked whether the system controller user name and password are the same as the switch user name and password.
-
Indicate whether the user names and passwords are the same.
When the discovery process has completed successfully, the actual synchronization process begins.
-
-
When prompted to either type q for exiting or the line number for the recommended action, enter the line number.
-
When asked whether to add the device, type y
-
When all recommended actions are completed or you do not want to complete the remaining recommended actions, type q to exit.
-
When prompted to either resynchronize the shelf with its saved state, to synchronize another chassis, or to exit, make the appropriate selection for synchronizing all the chassis you want to have synchronized.
-
Type 3 at the prompt to exit.
Example 2–2 Sample Actions for Adding Server Blades and SSCs
/opt/terraspring/sbin/shelfsync
Begining synchronization of the I-Fabric's database with an SFB1600's
physical state.
Enter SFB1600 management IP address or the device ID: 10.5.132.65
Database query in progress. Please wait.
Found: ipaddr="10.5.132.65" shelfid="50200" powerid="50260"
Checking network connectivity to 10.5.132.65....Done. Network connectivity:
OK
Attempting discovery of the specified SFB1600 device.
Management interface user name: admin
Password:
Are the switch user name and password the same as the management user name
and password? [yY/nN]y
Is there any new switch added to the shelf that you want to bench
configure? [yY/nN]n
Device discovery for 10.5.132.65 in progress. Please wait.
Writing WML output to /var/tmp/deviceWML.29789
Device discovery succeeded.
Fetching database state.....Please Wait.....Done!!
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0 Discovered ADD 50211 00:03:BA:26:91:AD
1 Discovered ADD 50251 sw_50251_SSC1
* = action has been run, entering -y will suppress acknowledgement prompts
Enter line number(s) from above or q for quit: 1
ADD device 50251 (Identification: sw_50251_SSC1)? [y/n] y
Adding device 50251 by running /var/tmp/add.withtype.50251:
<segment>
<device-type name="sun-b1600-shelf" parent="bls" desc="Sun B1600 Shelf">
</device-type>
...
Processing WML file /var/tmp/add.withtype.50251 ...
**WARNING** Skipping device type 'sun-b1600-shelf'. It is already defined.
**WARNING** Updating device '50001'. It is already defined.
File '/var/tmp/add.withtype.50251' processed successfully
Password set : 50251
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0 Discovered ADD 50250 sw_50250_SSC0
1 Discovered *ADD 50251 sw_50251_SSC1
* = action has been run, entering -y will suppress acknowledgement prompts
Enter line number(s) from above or q for quit: 0
ADD device 50211 (Identification: 00:03:BA:26:91:AD? [y/n] y
Adding device 50211 by running /var/tmp/add.withtype.50211:
<segment>
<device-type name="sun-b1600-shelf" parent="bls" desc="Sun B1600 Shelf">
</device-type> ...
Processing WML file /var/tmp/add.withtype.50211 ...
**WARNING** Skipping device type 'sun-b1600-shelf'. It is already defined.
File '/var/tmp/add.withtype.50211' processed successfully
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0 Discovered *ADD 50211 00:03:BA:26:91:AD
1 Discovered *ADD 50251 sw_50251_SSC1
* = action has been run, entering -y will suppress acknowledgement prompts
Enter line number(s) from above or q for quit: q
What do you want to do next:
#1. Re-sync the current SFB1600 device with its saved state.
#2. Synchronize another SFB1600 device with its saved state.
#3. Exit.
Make selection (1-3): 3
bash-2.03#
|
To Delete Server Blades and Switch and System Controllers
The following steps describe how to delete server blades and SSCs in an I-Fabric that are not being used in a farm.
Before You Begin
Before physically removing server blades and SSCs, run the removefru blade command from the system controller. See the Sun Fire™ B1600 Blade System Chassis documentation for details on how to use this command.
All blades to be deleted must be in FREE or NEW state. You can change device states by executing the device command. See the device man page for details on how to use that command.
Caution – Do not remove the SSC0 component, otherwise N1 Provisioning Server software will fail.
Steps
-
When prompted to either type q for exiting or type the line number for the recommended action, type the line number to delete the device.
-
When prompted whether to delete the device, type y.
You are prompted to confirm the deletion.
-
Type y again.
-
When all recommended actions are completed or you do not want to complete the remaining recommended actions, type q to exit.
You are asked whether you want to resynchronize the chassis with its saved state, synchronize another chassis, or exit.
-
Make the appropriate selection for synchronizing all the chassis you want to have synchronized.
-
Type 3 at the prompt to exit.
Example 2–3 Sample Actions for Deleting server Blades and SSCs
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: Removed DELETE 50110 00:03:BA:26:91:AD
1: Removed DELETE 50151 sw_50151_SSC1
* = action has been run
Enter line number from above or q for quit: 0
DELETE device 50110 (Identification 00:03:BA:26:91:AD)? [y/n] y
/opt/terraspring/sbin/device -d 50110
Are you sure to delete (y/n)? y
Deleted device 50110
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: Removed *DELETE 50110 00:03:BA:26:91:AD
1: Removed DELETE 50151 sw_50151_SSC1
* = action has been run
Enter line number from above or q for quit: 1
DELETE device 50151 (Identification sw_50151_SSC1)? [y/n] y
/opt/terraspring/sbin/device -d 50151
Are you sure to delete (y/n)? y
Deleted device 50151
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0 Removed *DELETE 50110 00:03:BA:2A:14:4A
0 Removed *DELETE 50151 sw_50151_SSC1
* = action has been run, entering -y will suppress acknowledgement prompts
Enter line number(s) from above or q for quit: q
What do you want to do next:
#1. Re-sync the current SFB1600 device with its saved state.
#2. Synchronize another SFB1600 device with its saved state.
#3. Exit.
Make selection (1-3): 3
[root@idb1:2]#
|
To Move a Server Blade From One Slot to Another
This scenario describes moving a server blade from one slot to another one within a chassis.
Caution – In this procedure, the order in which tasks are performed is important, otherwise a conflict might occur if the server blade removed from the chassis is still in the CPDB. Ensure that you delete the server blade first from its current slot, then add it to the new one. See the example following the steps for details.
Before You Begin
Before physically removing server blades, execute the removefru blade command from the system controller. See the Sun Fire B1600 Blade System Chassis documentation for details on how to use this command.
All server blades to be deleted must be in FREE or NEW state. You can change device states by executing the device command. See the device man page for details on how to use that command.
Steps
-
When prompted to either type q for exiting or the line number for the recommended action, type the line number.
-
When prompted whether to delete or add a device, type y.
You are prompted to confirm the deletion.
-
Type y again.
Note –Do delete operations first to avoid getting error messages.
Example 2–4 Sample Actions for Moving a Blade Between Slots
In the following example, a server blade was physically moved from slot S10 to S14 of a shelf. The shelfsync discovery process recommended two actions: an addition to slot S14 (device ID 50114) and a deletion from slot S10 (device ID 50110).
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: CONFLICT ADD 50114 00:03:BA:26:91:F5 50110
1: CONFLICT DELETE 50110 00:03:BA:26:91:F5 50114
* = action has been run
Enter line number from above or q for quit: 1
DELETE device 50110 (Identification 00:03:BA:26:91:F5)? [y/n] y
/opt/terraspring/sbin/device -d 50110
Are you sure to delete (y/n)? y
Deleted device 50110
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: CONFLICT ADD 50114 00:03:BA:26:91:F5 50110
1: CONFLICT *DELETE 50110 00:03:BA:26:91:F5 50114
* = action has been run
Enter line number from above or q for quit: 0
ADD device 50114 (Identification=oo:03:BA:26:91:F5) [y/n] y
Adding device 50114 by running /var/tmp/add.withtype.50114:
<segment>
,device-type name="sun-b1600-shelf" parent="bls" desc="Sun B1600 Shelf">
</device-type>
...
Processing WML file /var/tmp/add.withtype.50114
**WARNING** Skipping device type 'sun-b1600-shelf'. It is already defined.
File '/var/tmp/add.withtype.50114' processed successfully
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: CONFLICT *ADD 50114 00:03:BA:26:91:F5 50110
1: CONFLICT *DELETE 50110 00:03:BA:26:91:F5 50114
* = action has been run
Enter line number from above or q for quit: q
What do you want to do next:
#1. Re-sync the current SFB1600 device with its saved state.
#2. Synchronize another SFB1600 device with its saved state.
#3. Exit.
Make selection (1-3): 3
[root@idb1:2]#
|
To Exchange Server Blades Within a Chassis
The following scenario describes the exchange of two server blades within a chassis.
Caution – In this procedure, the order in which tasks are performed is important, otherwise a conflict may occur if the server blade removed from the chassis is still in the CPDB. Ensure that you delete the server blade first from its current slot, then add it to the new one. See the example following the steps for details.
Before You Begin
Before physically removing server blades, execute the removefru blade command from the power controller. See the Sun Fire B1600 Blade System Chassis documentation for details on how to use this command.
All server blades to be deleted must be in FREE or NEW state. You can change device states by executing the device command. See the delete man page for details on how to use that command.
Steps
-
When prompted to either type q for exiting or the line number for the recommended action, type the line number.
-
When prompted whether to delete the device, type y.
You are prompted to confirm the deletion.
-
Type y again.
Example 2–5 Sample Action for Exchanging Server Blades in a Chassis
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: CONFLICT DELETE 50114 00:03:BA:26:91:F5 50110
1: CONFLICT ADD 50110 00:03:BA:26:91:F5 50114
2: CONFLICT ADD 50114 00:03:BA:26:91:AD 50110
3: CONFLICT DELETE 50110 00:03:BA:26:91:AD 50114
* = action has been run
Enter line number from above or q for quit: 0
DELETE device 50114 (MAC address 00:03:BA:26:91:F5)? [y/n] y
/opt/terraspring/sbin/device -d 50114
Are you sure to delete (y/n)? y
Deleted device 50114
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: CONFLICT *DELETE 50114 00:03:BA:26:91:F5 50110
1: CONFLICT ADD 50110 00:03:BA:26:91:F5 50114
2: CONFLICT ADD 50114 00:03:BA:26:91:AD 50110
3: CONFLICT DELETE 50110 00:03:BA:26:91:AD 50114
* = action has been run
Enter line number from above or q for quit: 3
DELETE device 50110 (Identification 00:03:BA:26:91:AD)? [y/n] y
/opt/terraspring/sbin/device -d 50114
Are you sure to delete (y/n)? y
Deleted device 50110
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: CONFLICT *DELETE 50114 00:03:BA:26:91:F5 50110
1: CONFLICT ADD 50110 00:03:BA:26:91:F5 50114
2: CONFLICT ADD 50114 00:03:BA:26:91:AD 50110
3: CONFLICT *DELETE 50110 00:03:BA:26:91:AD 50114
* = action has been run
Enter line number from above or q for quit: 1
ADD device 50110 (Identification=00:03:BA:26:91:F5)? [y/n] y
Adding device 50110 by running /var/tmp/add.withtype.50110:
<segment>
,device-type name="sun-b1600-shelf" parent="bls" desc="Sun B1600 Shelf">
</device-type>
...
Processing WML file /var/tmp/add.withtype.50110...
File '/var/tmp/add.withtype.50110' processed successfully
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: CONFLICT *DELETE 50114 00:03:BA:26:91:F5 50110
1: CONFLICT *ADD 50110 00:03:BA:26:91:F5 50114
2: CONFLICT ADD 50114 00:03:BA:26:91:AD 50110
3: CONFLICT *DELETE 50110 00:03:BA:26:91:AD 50114
* = action has been run
Enter line number from above or q for quit: 2
ADD device 50114 (Identification=00:03:BA:26:91:AD)? [y/n] y
Adding device 50114 by running /var/tmp/add.withtype.50114:
<segment>
,device-type name="sun-b1600-shelf" parent="bls" desc="Sun B1600 Shelf">
</device-type>
...
Processing WML file /var/tmp/add.withtype.50114...
File '/var/tmp/add.withtype.50114' processed successfully
Recommended actions:
Recommended
# Cause Action Identification Conflicting IDs
-- ----------- ------- ----------------------- ---------------
0: CONFLICT *DELETE 50114 00:03:BA:26:91:F5 50110
1: CONFLICT *ADD 50110 00:03:BA:26:91:F5 50114
2: CONFLICT *ADD 50114 00:03:BA:26:91:AD 50110
3: CONFLICT *DELETE 50110 00:03:BA:26:91:AD 50114
* = action has been run
Enter line number from above or q for quit: q
What do you want to do next:
#1. Re-sync the current SFB1600 device with its saved state.
#2. Synchronize another SFB1600 device with its saved state.
#3. Exit.
Make selection (1-3): 3
[root@idb1:2]#
|
Adding a Replacement Server Blade to a Farm
If you exchanged a server blade that was assigned to a farm and you want the newly placed server blade to be assigned to that farm, you need to add the new blade to the farm.
To Add a Replacement Server Blade to a Farm
Steps
-
Delete the replaceFailedDevice request in the database queue.
-
Replace the failed server blade with a new one.
-
Get the media access control (MAC) address for the new blade and update the CPDB by typing:
device -s device-ID -o port-name mac-address
-
Type replacedevice -i
-
Logon to the Control Center and submit a request for an update using the Control Center Editor.
See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details.
- © 2010, Oracle Corporation and/or its affiliates