Chassis Status Details
> asg stat -v
Output (Top Section)
-----------------------------------------------------------------------------
| VSX System Status |
-----------------------------------------------------------------------------
| VS ID: 0 VS Name: Athens |
-----------------------------------------------------------------------------
| Chassis 1 STANDBY |
-----------------------------------------------------------------------------
| SGM ID State Process Policy Date |
| 1 (local) UP Enforcing Security 09Jan14 11:30 |
| 2 UP Enforcing Security 09Jan14 11:30 |
| 3 DOWN Inactive NA |
| 4 UP Enforcing Security 09Jan14 11:30 |
-----------------------------------------------------------------------------
| Chassis 2 ACTIVE |
-----------------------------------------------------------------------------
| SGM ID State Process Policy Date |
| 1 UP Enforcing Security 09Jan14 11:30 |
| 2 UP Enforcing Security 09Jan14 11:30 |
| 3 UP Enforcing Security 09Jan14 11:30 |
| 4 UP Enforcing Security 09Jan14 11:30 |
-----------------------------------------------------------------------------
This output shows that:
- Chassis 1 is STANDBY with 3 SGMs UP
- Chassis 2 is ACTIVE with 4 SGMs UP
Notes
is the Identifier of the SGM. is the SGM on which you ran the command. - is the state of the SGM. This can be:
- - The SGM is processing traffic
- - The SGM is not processing traffic
- - No SGM has been detected in a slot.
|
Note - To manually change the state of an SGM, use the asg sgm_admin command. This command administratively changes the state to UP or DOWN. An SGM that is down because of a software or hardware problem cannot be changed to UP using this command.
|
- is the status of the SGM security enforcement:
- - UP and works properly.
- - DOWN and is experiences some problem. It is not handling traffic.
- - The SGM is UP but the policy is not installed on the SGM.
Output (Bottom Section)
--------------------------------------------------------------------------------
| Chassis Parameters |
--------------------------------------------------------------------------------
| Unit Chassis 1 Chassis 2 Unit Weight |
| |
| SGMs 4 / 4 3 / 4 (!) 6 |
| Ports |
| Standard 0 / 0 0 / 0 11 |
| Bond 2 / 2 2 / 2 11 |
| Other 0 / 0 0 / 0 6 |
| Sensors |
| Fans 6 / 6 6 / 6 5 |
| SSMs 2 / 2 2 / 2 11 |
| CMMs 2 / 2 2 / 2 6 |
| Power Supplies 3 / 3 3 / 3 6 |
| |
| Chassis Grade 134 / 134 122 / 134 - |
--------------------------------------------------------------------------------
| Minimum grade gap for chassis failover: 11 |
| Synchronization |
| Within chassis: Enabled (Default) |
| Between chassis: Enabled (Default) |
| Exception Rules: (Default) |
--------------------------------------------------------------------------------
| Chassis HA mode: Active Up |
| Chassis HA in Freeze (5 seconds left) |
--------------------------------------------------------------------------------
Notes
- The X/X notation shows the number of components that are UP and the components must be UP. For example, on the SGMs line, 4/4 means that 4 SGMs are UP and 4 must be UP.
- is the sum of the grades of all components. In a Dual-Chassis deployment, the Chassis with a higher grade (by at least the ) becomes ACTIVE. The grade of each component is the Unit Weight multiplied by the number of components that are UP.
You can configure the Unit Weight of each component to reflect the importance of the component in the system. To configure the Unit Weight run:
> set chassis high-availability factors <sensor_name>
For example, to change the weight of the SGM to 12, run:
> set chassis high-availability factors sgm 12
If you run asg stat -v, the output shows a higher unit weight and Chassis grade:
- - The minimum grade required for the Chassis to become
ACTIVE. - - Chassis failover occurs to the Chassis with the higher grade only if its grade is greater than the other Chassis by more than the minimum gap.
- - The status of synchronization:
- - between SGMs located in the same Chassis.
- - between SGMs located in different Chassis.
- - user configured exception rules. To configure, use the command
g_sync_exception.
- - Shows if this option is enabled. When enabled, the SMO handles only management traffic. You always have access immediately to the system with an SSH connection.
|
