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     |

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

Notes

This output shows that:

• Chassis 1 is STANDBY with 3 SGMs up.
• Chassis 2 is in ACTIVE state with 4 SGMs up
• 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. 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 state of the SGM security enforcement:
  • Enforcing Security - UP and working properly.
  • Inactive - DOWN, and is experiencing some problem. It is not handling any 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                            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 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 = Unit Weight x the number of components that are UP. The Unit Weight of each component can be configured 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 if you wish to change the weight of the SGM from 6 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, use the command g_sync_exception.
• Distribution Control blade - Shows if this option is enabled. When enabled, the SMO handles only management traffic. You always have immediate access to the system with an SSH connection.