Management High Availability Synchronizaton failure - Revision history

Nighthawk: /* Solution */

2013-05-21T07:09:13Z

‎Solution

Nighthawk: /* Solution */

2013-05-21T07:08:44Z

‎Solution

Nighthawk: /* Solution */

2013-05-21T07:08:10Z

‎Solution

Nighthawk: /* Solution */

2013-05-21T07:06:47Z

‎Solution

Nighthawk: /* Solution */

2013-05-21T07:05:55Z

‎Solution

Nighthawk: /* Problem description */

2013-05-21T07:04:20Z

‎Problem description

Nighthawk: /* Solution */

2013-05-21T07:03:30Z

‎Solution

Nighthawk: /* Solution */

2013-05-21T07:02:29Z

‎Solution

Nighthawk at 07:01, 21 May 2013

2013-05-21T07:01:22Z

Nighthawk: Created page with " == Problem description == * Management HA is failing to sync the secondary CMA via SmartDashboard > Policy > Management High Availability * Error message: "Failed to receiv..."

2013-05-21T07:00:51Z

Created page with " == Problem description == * Management HA is failing to sync the secondary CMA via SmartDashboard > Policy > Management High Availability * Error message: "Failed to receiv..."

New page

== Problem description ==
* Management HA is failing to sync the secondary CMA via SmartDashboard > Policy > Management High Availability
* Error message: "Failed to receive current status. Reason: 'Management High Availability feature is not enabled.
[[file: chkp_mgmt_ha_sync_error.png]]
* The smart_center_backup parameter in the objects_5_0.C is false when it should be true
[Expert@provider-1]# mdsenv cma-primary
[Expert@provider-1]# cpmiquerybin attr "" network_objects "management='true'" -a __name__,smart_center_backup
cma-primary true
cma-secondary false
* The secondary CMA is newly created and has never been synchronized. Synchronization during the CMA creating failed.
* Error messages from cpca.elg of the secondary cma:
main: could not initiate the Certificate Authority. No Certificate Authority existing
* The cpca process on the secondary CMA is down and fails to start.
[Expert@provider-1]# mdsstat |
+-----+----------------+-----------------+------------+----------+----------+----------+
| Type| Name | IP address | FWM | FWD | CPD | CPCA |
+-----+----------------+-----------------+------------+----------+----------+----------+
| MDS | - | 171.178.7.1 | up 3421 | up 3420 | up 3419 | up 3956 |
+-----+----------------+-----------------+------------+----------+----------+----------+
| CMA | cma-primary | 171.155.44.74 | up 21716 | up 21715 | up 21705 | '''down''' |

== Solution ==
* <p>Change the smart_center_backup parameter to true using dbedit, gui-dbedit or by editing the objects_5_0.C file.
One the primary cma...
1. stop cma
2. mdsenv cma-primary
3. rm $FWDIR/conf/mgha/*
4. start cma
5. Manually synchronized the secondary via SmartDashboard > Policy > Management HighAvailability

After the sync was successful, the cpca on the secondary cma should start on its own.

← Older revision		Revision as of 07:09, 21 May 2013
Line 33:		Line 33:


−	After the sync ~~was~~ successful, the cpca on the secondary cma should start on its own.	+	After the sync is successful, the cpca on the secondary cma should start on its own.

	[Expert@provider-1]# mdsstat \|		[Expert@provider-1]# mdsstat \|

@@ Line 43: / Line 43: @@
   | CMA | cma-primary    |  192.168.1.2    | up 21716   | up 21715 | up 21705 | '''up 21785''' |
- +-----+----------------+-----------------+------------+----------+----------+----------+
+Problem solved.
- | Type| Name           | IP address      | FWM        | FWD      | CPD      | CPCA     |
- +-----+----------------+-----------------+------------+----------+----------+----------+
- | MDS |        -       | 192.168.1.1     | up 3421    | up 3420  | up 3419  | up 3956  |
-  +-----+----------------+-----------------+------------+----------+----------+----------+
- | CMA | cma-primary    |  192.168.1.2    | up 21716   | up 21715 | up 21705 | '''down'''     |
-−
 [[category:check point]]
 [[category:smartcenter]]

@@ Line 42: / Line 42: @@
   +-----+----------------+-----------------+------------+----------+----------+----------+
   | CMA | cma-primary    |  192.168.1.2    | up 21716   | up 21715 | up 21705 | '''up 21785''' |
 [[category:check point]]
 [[category:smartcenter]]

@@ Line 41: / Line 41: @@
   | MDS |        -       | 192.168.1.1     | up 3421    | up 3420  | up 3419  | up 3956  |
   +-----+----------------+-----------------+------------+----------+----------+----------+
-  | CMA | cma-primary    |  192.168.1.2    | up 21716   | up 21715 | up 21705 | '''up 21785'''  |
+  | CMA | cma-primary    |  192.168.1.2    | up 21716   | up 21715 | up 21705 | '''up 21785''' |
 [[category:check point]]
 [[category:smartcenter]]

@@ Line 31: / Line 31: @@
 # start cma
 # Manually synchronized the secondary via SmartDashboard > Policy > Management HighAvailability
 After the sync was successful, the cpca on the secondary cma should start on its own.

@@ Line 24: / Line 24: @@
 * <p>Change the smart_center_backup parameter to true using dbedit, gui-dbedit or by editing the objects_5_0.C file.
-[['''One the primary cma''']]
+'''One the primary cma'''
 # stop cma

@@ Line 23: / Line 23: @@
 == Solution ==
 * <p>Change the smart_center_backup parameter to true using dbedit, gui-dbedit or by editing the objects_5_0.C file.
-One the primary cma...
-. stop cma
+[['''One the primary cma''']]
-. mdsenv cma-primary
-. rm $FWDIR/conf/mgha/*
+# stop cma
-. start cma
+# mdsenv cma-primary
-. Manually synchronized the secondary via SmartDashboard > Policy > Management HighAvailability
+# rm $FWDIR/conf/mgha/*
 After the sync was successful, the cpca on the secondary cma should start on its own.

@@ Line 8: / Line 8: @@
   [Expert@provider-1]# cpmiquerybin attr "" network_objects "management='true'" -a __name__,smart_center_backup
   cma-primary true
-  cma-secondary       false
+  '''cma-secondary       false'''
 * The secondary CMA is newly created and has never been synchronized.  Synchronization during the CMA creating failed.
 * Error messages from cpca.elg of the secondary cma: