Difference between revisions of "Cpinfo for cma or mds on provider-1"

 (Created page with "SOLUTION  To generate a cpinfo for the Provider-1/ SiteManager-1 CMA or MDS, proceed as follows.   To collect cpinfo from the relevant CMA that manages the Security Gateway : ...")  | 
			|||
| (2 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | ||
| + | == CMA cpinfo ==  | ||
| + | |||
To generate a cpinfo for the Provider-1/ SiteManager-1 CMA or MDS, proceed as follows.    | To generate a cpinfo for the Provider-1/ SiteManager-1 CMA or MDS, proceed as follows.    | ||
| Line 11: | Line 13: | ||
Look at the list of all Customers (CMAs) by running:    | Look at the list of all Customers (CMAs) by running:    | ||
| − | mdsstat  | + |  mdsstat  | 
Set the environment for the Customer by running:    | Set the environment for the Customer by running:    | ||
| − | mdsenv <customer_name>    | + |  mdsenv <customer_name>    | 
For example, for the Customer "test" the syntax is:    | For example, for the Customer "test" the syntax is:    | ||
| − | mdsenv test    | + |  mdsenv test    | 
(This sets the environment specifically for the Customer "test", a setting that is different from the MDS environment settings.)  | (This sets the environment specifically for the Customer "test", a setting that is different from the MDS environment settings.)  | ||
| Line 27: | Line 29: | ||
Verify the correct environment by running:    | Verify the correct environment by running:    | ||
| − | echo $FWDIR    | + |  echo $FWDIR    | 
This displays the correct path for the CMA. For example, the response will be:    | This displays the correct path for the CMA. For example, the response will be:    | ||
| − | /opt/CPmds-R65/customers/<customer_name>/CPsuite-R65/fw1/  | + |  /opt/CPmds-R65/customers/<customer_name>/CPsuite-R65/fw1/  | 
Collect cpinfo by using exactly this syntax:    | Collect cpinfo by using exactly this syntax:    | ||
| − | cpinfo -c <cma_name> -z -n -o /var/cma.cpinfo  | + |  cpinfo -c <cma_name> -z -n -o /var/cma.cpinfo  | 
Please send Check Point Support this file:    | Please send Check Point Support this file:    | ||
| − | /var/cma.cpinfo.gz  | + |  /var/cma.cpinfo.gz  | 
| − | |||
| + | == MDS cpinfo==  | ||
| + | |||
Log into the MDS as "superuser".  | Log into the MDS as "superuser".  | ||
| Line 51: | Line 54: | ||
Set the environment for the entire MDS by running:    | Set the environment for the entire MDS by running:    | ||
| − | mdsenv  | + |  mdsenv  | 
Verify the correct environment by running:    | Verify the correct environment by running:    | ||
| − | echo $FWDIR    | + |  echo $FWDIR    | 
For example, the response will be:    | For example, the response will be:    | ||
| − | /opt/CPmds-R65/  | + |  /opt/CPmds-R65/  | 
Collect cpinfo:    | Collect cpinfo:    | ||
| − | cpinfo -z -n -o /var/mds.cpinfo  | + |  cpinfo -z -n -o /var/mds.cpinfo  | 
Please send Check Point Support this file:    | Please send Check Point Support this file:    | ||
| − | /var/mds.cpinfo.gz  | + |  /var/mds.cpinfo.gz  | 
[[category:cpinfo]]  | [[category:cpinfo]]  | ||
Latest revision as of 14:54, 22 July 2014
CMA cpinfo
To generate a cpinfo for the Provider-1/ SiteManager-1 CMA or MDS, proceed as follows.
To collect cpinfo from the relevant CMA that manages the Security Gateway :
Login to the MDS as "superuser".
Look at the list of all Customers (CMAs) by running: 
mdsstat
Set the environment for the Customer by running: 
mdsenv <customer_name>
For example, for the Customer "test" the syntax is:
mdsenv test
(This sets the environment specifically for the Customer "test", a setting that is different from the MDS environment settings.)
Verify the correct environment by running: 
echo $FWDIR
This displays the correct path for the CMA. For example, the response will be:
/opt/CPmds-R65/customers/<customer_name>/CPsuite-R65/fw1/
Collect cpinfo by using exactly this syntax: 
cpinfo -c <cma_name> -z -n -o /var/cma.cpinfo
Please send Check Point Support this file: 
/var/cma.cpinfo.gz
MDS cpinfo
Log into the MDS as "superuser".
Set the environment for the entire MDS by running: 
mdsenv
Verify the correct environment by running: 
echo $FWDIR
For example, the response will be:
/opt/CPmds-R65/
Collect cpinfo: 
cpinfo -z -n -o /var/mds.cpinfo
Please send Check Point Support this file: 
/var/mds.cpinfo.gz