Sun Microsystems 6900, 3900 Sun Proprietary/Confidential Internal Use Only, # ps -ef grep slicd

Models: 6900 3900

1 204
Download 204 pages 8.57 Kb
Page 147
Image 147
4. To restart the slicd for the v1 virtualization engine, type:

4. To restart the slicd for the v1 virtualization engine, type:

#/opt/SUNWsecfg/bin/startslicd -n v1 (or v2, depending on configuration)

5.Confirm that the slicd daemon is running:

# ps -ef grep slicd

 

root 16132 16130

0

11:45:00 ?

0:00 ./slicd

root 16135 16130

0

11:45:00 ?

0:00 ./slicd

root 16130

1

0

11:45:00 ?

0:00 ./slicd

root 16131

16130

0

11:45:00 ?

0:00 ./slicd

root 16189

15877

0

11:48:49 pts/1

0:00 grep slicd

root 16143

16130

0

11:45:00 ?

0:00 ./slicd

 

 

 

 

 

If the slicd daemon is running, it resets the virtualization engine. If the process fails, the slicd daemon changes the IP address to that of the second virtualization engine and attempts to restart the slicd process.

6.If the second virtualization engine fails, power cycle the virtualization engines and make sure they are not in an ERROR HALT 50 condition.

An ERROR HALT 50 condition requires that you visually inspect the virtualization engines with firmware revision 8.14 or earlier.

For virtualization engines with firmware revision 8.17 or later, you can determine error conditions with the following steps:

a.Open a Telnet session into v1_hostname.

b.Display the Vital Product Data (VPD) by entering .1 at the prompt.

The last line of the output displays any error codes, as shown in the following example.

Chapter 9 Troubleshooting Virtualization Engine Devices 127

Sun Proprietary/Confidential: Internal Use Only

Page 147
Image 147
Sun Microsystems 6900, 3900 manual Sun Proprietary/Confidential Internal Use Only, Confirm that the slicd daemon is running