|
|
|
System Administration | showfailover(1m) |
| showfailover - display system controller
(SC) failover status or role |
SYNOPSIS
|
showfailover(1M) enables you to monitor the state of the SC failover mechanism. This command displays the current status of the failover mechanisms. If you do not specify a -r option, then the following information is displayed:
|
SC Failover Status: state
|
The failover mechanism can be in one of four states: ACTIVATING, ACTIVE, DISABLED, or FAILED. See the EXTENDED DESCRIPTION section.
|
|
The following options are supported:
- -h
- Help. Displays usage descriptions. Note Use alone. Any option specified in addition to -h is ignored.
- -r
- Displays the SC's role as either MAIN, SPARE, or UNKNOWN.
- -v
- Verbose. Displays all available command information.
|
|
The failover mechanism states are as follows:
-
ACTIVATING
- Indicates that the failover mechanism is preparing to transition to the ACTIVE state. Failover becomes active when all tests have passed and files have been synchronized.
-
ACTIVE
- Indicates that the failover mechanism is enabled and is functioning normally.
-
DISABLED
- Indicates that the failover mechanism has been disabled due to a failover or an operator request (for example, setfailover
off).
-
FAILED
- Indicates that the failover mechanism has detected a failure that prevents a failover.
In addition, if the external network has been configured, showfailover displays the state of each of the external network interface links monitored by the failover processes. The display format is as follows:
external community name: [UP|DOWN]
A failure string is returned, describing the failure condition. Each failure string has a code associated with it. The codes and associated failure strings are defined in the following table.
String | Explanation |
None | No failure. |
S-SC EXT NET | The spare SC external network interface has failed. |
S-SC CONSOLE BUS | A fault has been detected on the spare SC's console bus path. |
S-SC LOC CLK | The spare SC's local clock has failed. |
S-SC DISK FULL | The spare SC's system is full. |
S-SC IS DOWN | The spare SC is down and/or unresponsive. If this message results from the I2 network/HASRAMs being down then the spare SC could still be running. Login to the spare SC to verify. |
S-SC MEM EXHAUSTED | The spare SC's memory/swap space has been exhausted. |
S-SC SMS DAEMON | At least one SMS daemon could not be started/restarted on the spare SC. |
S-SC INCOMPATIBLE SMS VERSION | The spare SC is running a different version of SMS software. Both SCs must be running the same version. |
I2 NETWORK/HASRAMS DOWN | Both interfaces for communication between the SCs are down. The main cannot tell what version of SMS is running on the spare nor what its state is. It declares the spare SC down and logs a message to that effect. Dependent services, including file propagation, are unavailable. |
Group Privileges Required
|
You must have platform administrator, platform operator, or platform service privileges to run this command.
Refer to Chapter 2, "SMS Security Options and Administrative Privileges" in the System Management Services (SMS) 1.4 Administrator Guide for more information.
|
|
| Example 1. Displaying a Failover Status That Indicates That Everything is OK
|
|
sc0:sms-user:> showfailover
SC Failover Status: ACTIVE
C1: UP
|
|
Example 2. Displaying a Failover Status That Indicates That the Spare SC System is Full
|
|
sc0:sms-user:> showfailover
SC Failover Status: FAILED
S-SC DISK FULL
C1: UP
|
|
Example 3. Displaying the SC Role
|
|
sc0:sms-user:> showfailover -r
SPARE
|
|
Example 4. Displaying the Status of All Monitored Components
|
|
sc0:sms-user:> showfailover -v
SC Failover Status: ACTIVE
Status of Shared Memory: HASRAM (CSB at CS0): ......................................Good HASRAM (CSB at CS1): ......................................Good
Status of xc30p13-sc0: Role: .....................................................MAIN SMS Daemons: ......................... ....................Good System Clock: .............................................Good Private I2 Network: .......................................Good Private HASRAM Network:....................................Good Public Network.......................................NOT TESTED System Memory: ...........................................38.9% Disk Status: /: ..................................................17.4%
Console Bus Status: EXB at EX1: ..........................................Good EXB at EX2: ..........................................Good EXB at EX4: ..........................................Good
Status of xc30p13-sc1: Role: ....................................................SPARE SMS Daemons: ..............................................Good System Clock: .............................................Good Private I2 Network: .......................................Good Private HASRAM Network:....................................Good Public Network: .....................................NOT TESTED System Memory: ...........................................34.2% Disk Status: /: ..................................................17.1%
Console Bus Status:
EXB at EX1: .........................................Good
EXB at EX2: .........................................Good
EXB at EX4: .........................................Good
|
|
|
|
The following exit values are returned:
-
0
- Successful completion.
- >0
- An error occurred.
|
|
See attributes(5) for descriptions of the following attributes:
Attribute Types | Attribute Values |
Availability | SUNWSMSop |
Interface Stability | Evolving |
Command Output | Unstable |
|
SMS 1.4 | Go To Top | Last Changed 19 September 2003 |
Company Info
|
Contact
|
Copyright 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 USA. All rights reserved.
|