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 |

| 5 UP Enforcing Security 09Jan14 11:30 |

| 6 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 |

| 5 UP Enforcing Security 09Jan14 11:30 |

| 6 UP Enforcing Security 09Jan14 11:30 |

-----------------------------------------------------------------------------

This output shows that:

Chassis 1 is STANDBY with 5 SGMs UP
Chassis 2 is ACTIVE with 6 SGMs UP

Notes

SGM ID is the Identifier of the SGM. (local) is the SGM on which you ran the command.

State is the state of the SGM. This can be:

UP - The SGM is processing traffic
DOWN - The SGM is not processing traffic

Detached - 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.

Process is the status of the SGM security enforcement:
- Enforcing Security - UP and works properly.
- Inactive - DOWN and is experiences some problem. It is not handling traffic.
- Initial policy - 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 5 / 6 (!) 6 / 6 (!) 6 |

| Ports |

| Standard 0 / 0 0 / 0 11 |

| Bond 2 / 2 2 / 2 11 |

| Other 0 / 0 0 / 0 6 |

| Sensors |

| Fans 9 / 9 9 / 9 5 |

| SSMs 2 / 2 2 / 2 11 |

| CMMs 2 / 2 2 / 2 6 |

| Power Supplies 4 / 4 4 / 4 6 |

| |

| Chassis Grade 133 / 139 139 / 139 - |

--------------------------------------------------------------------------------

| Minimum grade gap for chassis failover: 11 |

| Synchronization |

| Within chassis: Enabled (Default) |

| Between chassis: Enabled (Default) |

| Exception Rules: (Default) |

--------------------------------------------------------------------------------

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, 6/6 means that 6 SGMs are UP and 6 must be UP.
Chassis grade is the sum of the grades of all components. In a Dual-Chassis deployment, the Chassis with a higher grade (by at least the Minimum grade gap) 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 show 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.
Minimum threshold for traffic processing - The minimum grade required for the Chassis to become ACTIVE.
Minimum grade gap for chassis failover - 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.
Synchronization - The status of synchronization:
- Within chassis - Between SGMs located in the same Chassis.
- Between chassis - Between SGMs located in different Chassis.
- Exception Rules - User configured exception rules. To configure, run: asg_sync_manager.
Distribution Control blade - 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.

Compact Output for Selected Virtual Systems

Syntax

> asg stat -v -vs <VSID1>,<VSID2>,<VSID3>,...,<VSIDn>

Example output:

> asg stat -v -vs 0,1,2

------------------------------------------------------------------------------

| Chassis 1 STANDBY |

------------------------------------------------------------------------------

|SGM |1 |2 |3 |4 | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

|State | UP | UP |DOWN | UP | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

| VS ID |

------------------------------------------------------------------------------

| 0 | ES | ES | ES | ES | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

| 1 | ES | ES | ES | ES | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

| 2 | ES | ES | ES | ES | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

| Chassis 2 ACTIVE |

------------------------------------------------------------------------------

|SGM |1 (l)|2 |3 |4 | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

|State | UP | UP | UP | UP | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

| VS ID |

------------------------------------------------------------------------------

| 0 | ES | ES | ES | ES | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

| 1 | ES | ES | ES | ES | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

| 2 | ES | ES | ES | ES | - | - | - | - | - | - | - | -|

------------------------------------------------------------------------------

| Chassis Parameters

------------------------------------------------------------------------------

| Unit Chassis 1 Chassis 2 Unit Weight |

| |

| SGMs 3 / 4 (!) 4 / 4 6 |

| Ports |

| Standard 0 / 0 0 / 0 50 |

| 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 6 / 6 6 / 6 6 |

| |

| Chassis Grade 118 / 124 124 / 124 - |

------------------------------------------------------------------------------

| Minimum grade gap for chassis failover: 11 |

| Synchronization |

| Within chassis: Enabled (Default) |

| Between chassis: Enabled (Default) |

| Exception Rules: (Default) |

| Distribution |

| Control Blade: Disabled (Default) |

| Chassis HA mode: Active Up |

---------------------------------------------------------------

Output State Acronyms

To see a list of the acronyms that show in the reports:

> asg stat -l

Example output:

> asg stat -l

Legend:

SGM States:

ACT - ACTIVE DTC - DETACHED

DWN - DOWN NSG - NOT IN SECURITY GROUP

VS States:

ES - Enforcing Security FSC - FullSync Client

FSS - FullSync Server IAC - Inactive

IF - Iteration Finished IPO - Initial Policy

IS - Iteration Started NPO - No Policy

PC - Policy Completed PRF - Policy Ready2Finish

PS - Policy Started