Administer > Monitoring SA Core components > Gateway monitoring

Gateway monitoring

SA Management and Core Gateways allow an SA Core to manage servers that are behind one or more NAT devices or firewalls. Connectivity between gateways is maintained by routing messages over persistent TCP tunnels between the gateway instances.

For information about configuring the Gateways, see the SA 10.50 Key Concepts Guide.

For information about maintaining Satellite Gateways, see Satellite administration.

Gateway ports

By default, the Gateway uses the following ports:

  • 2001—Management Gateway Listener Port
  • 2001—Slice Component Core Gateway Listener Port
  • 3001—Agent Gateway Port
  • 3001—Satellite Gateway Port

Monitoring processes for the Gateway

In all configurations, the Gateway component has two running process—the Gateway process itself and its watchdog process.

On Solaris or Linux, execute the commands on the server running the Gateway component:

# ps -eaf | grep -v grep | grep opswgw | grep cgw

Running this command produces output similar to the following:

root  17092  1  0  Sep21  ?  00:00:00  [opswgw-watchdog-2.1.1: cgw0-C43]

--PropertiesFile /etc/opt/opsware/opswgw-cgw0-C43/opswgw.properties --BinPath /opt/opsware/opswgw/bin/opswgw

root  17094  17092  0  Sep21  ?  02:23:21  [opswgw-gateway-2.1.1: cgw0-

C43] --PropertiesFile /etc/opt/opsware/opswgw-cgw0-C43/opswgw.properties --BinPath /opt/opsware/opswgw/bin/opswgw --Child true

# ps -eaf | grep -v grep | grep opswgw | grep agw

Running this command produces output similar to the following:

root  17207  1  0  Sep21  ?  00:00:00  [opswgw-watchdog-2.1.1: agw0-C43]

--PropertiesFile /etc/opt/opsware/opswgw-agw0-C43/opswgw.properties --BinPath /opt/opsware/opswgw/bin/opswgw

root  17208  17207  0  Sep21  ?  01:18:54  [opswgw-gateway-2.1.1: agw0-

C43] --PropertiesFile /etc/opt/opsware/opswgw-agw0-C43/opswgw.properties --BinPath /opt/opsware/opswgw/bin/opswgw --Child true

In a Satellite facility on Solaris or Linux, execute the command on the server running the Satellite Gateway component:

# ps -eaf | grep -v grep | grep opswgw | grep <gateway-name>

Where <gateway-name> in this example is Sat1.

Running this command produces output similar to the following:

root  17092  1  0  Sep21  ?  00:00:00  [opswgw-watchdog-2.1.1: Sat1]

--PropertiesFile /etc/opt/opsware/opswgw-Sat1/opswgw.properties --BinPath /opt/opsware/opswgw/bin/opswgw

root  17094  17092  0  Sep21  ?  02:23:21  [opswgw-gateway-2.1.1: Sat1]

--PropertiesFile /etc/opt/opsware/opswgw-Sat1/opswgw.properties --BinPath /opt/opsware/opswgw/bin/opswgw --Child true

Gateway URL

Log into the SA Client UI and select Gateway under Administration in the navigation panel.

https://occ.<data_center>/com.opsware.occ.gwadmin/index.jsp

Gateway logs

The Gateway logs are in the following files:

/var/log/opsware/gateway-name/opswgw.log*

Conditions to monitor in the logs:

  • Strings containing “ERROR”
  • Strings containing “FATAL” (indicates that the process will end soon)

Send Help Center feedback