Configuring SGM state (asg sgm_admin)
Use this command to manually change the state (UP or DOWN) for one or more SGMs.
Syntax
> asg sgm_admin -b <sgm_ids> up|{down [-a]} [-p]
> asg sgm_admin -h
Parameter
|
Description
|
-b <sgm_ids>
|
Works with SGMs and/or Chassis as specified by <sgm_ids>.
<sgm_ids> can be:
- No <sgm_ids> specified or
all shows all SGMs and Chassis - One SGM
- A comma-separated list of SGMs (
1_1,1_4) - A range of SGMs (
1_1-1_4) - One Chassis (
Chassis1 or Chassis2) - The active Chassis (
chassis_active)
|
-p
|
Persistent. The setting is kept after reboot
|
-a
|
Synchronize accelerated connections to other SGMs
|
-h
|
Show command syntax and help information
|
Example
> asg sgm_admin -b 2_03 -p
You are about to perform blade_admin up on blades: 2_03
Are you sure? (Y - yes, any other key - no) y
Blade_admin up requires auditing
Enter your full name: Fred
Enter reason for blade_admin up [Maintenance]: test
WARNING: Blade_admin up on blades: 2_03, User: Fred, Reason: test
Performing blade_admin up on blades: 2_03
[2_03]Setting blade to normal operation ...
[2_03]pulling configuration from: 192.0.2.16 (may take few seconds)
[2_03]Blade current state is ACTIVE
Notes
- When an SGM is in the state:
- gclish commands do not run on this SGM.
- Traffic is not sent to this SGM.
asg stat shows the SGM as .
- When an SGM is changed to Administrative Up, it automatically synchronizes the configuration from a different SGM that is in the UP state.
- This command generates log entries. To show the logs, run:
> asg log audit
- This command is useful for debugging. We do not recommend that you use it in production environments because it causes performance degradation.
|
