Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Arturxr
Contributor
Jump to solution

The ASG Monitor output shows the Maestro chassis is down.


The ASG Monitor output shows the Maestro chassis is down. For your information, we're still using VSX.

Could you tell me why it's down and if we reboot the chassis, will we have any problems?

0 Kudos
2 Solutions

Accepted Solutions
Vanness_Chen
Explorer

Hi Arturxr:

You can first try running cpstart on the SGM that is in the down state and observe at which stage the synchronization gets stuck. This usually helps provide some clues.

If restarting does not improve the situation, based on past experience, it’s recommended to collect cpinfo and hcp report first, and then open a TAC case for further analysis.

View solution in original post

0 Kudos
Arturxr
Contributor

It seems our problem has been solved. After searching for information on Checkmates, I tried the following solutions:

According to sk177468, I pulled config and restarted the VSX contexts. After that, we haven't seen any problems.

View solution in original post

0 Kudos
5 Replies
Chris_Atkinson
MVP Platinum CHKP MVP Platinum CHKP
MVP Platinum CHKP

Did you mean to attach some useful logs or outputs to review ?

Otherwise suggest capturing cpinfo / HCP and raising a case with TAC...

CCSM R77/R80/ELITE
0 Kudos
Arturxr
Contributor

asg monitor -v shows:

0 Kudos
Arturxr
Contributor

I also noticed the following:
Device Name: VSX
Registration number: 3
Timeout: none
Current state: problem
Time since last report: 0.2 sec
Problematic VSIDs: 1.

Device Name: pull_config
Registration number: 14
Timeout: none
Current state: problem
Time since last report: 56.4 sec

0 Kudos
Vanness_Chen
Explorer

Hi Arturxr:

You can first try running cpstart on the SGM that is in the down state and observe at which stage the synchronization gets stuck. This usually helps provide some clues.

If restarting does not improve the situation, based on past experience, it’s recommended to collect cpinfo and hcp report first, and then open a TAC case for further analysis.

0 Kudos
Arturxr
Contributor

It seems our problem has been solved. After searching for information on Checkmates, I tried the following solutions:

According to sk177468, I pulled config and restarted the VSX contexts. After that, we haven't seen any problems.

0 Kudos