Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Before You Begin

...

Before you add a new monitored device to DPOD, ensure to perform the following:

  1. Check routing and access from a monitored device:
    The DataPower Gateway needs to route packets to DPOD Agents through the desired interface. Validate through the DataPower's [control panel->Troubleshooting->TCP Connection Test]
  2. Log-in to DPOD Web Console

Device Level Configuration

...

Warning

Adding a device with a locale other than EN may cause some DPOD features to not work as expected

...

make sure to Prepare your Monitored Devices.

Adding a Gateway to DPOD

Inside DPOD's Web Console, navigate to

...

the gateways page [Manage → Topology → Gateways] and click on “New”.

Info

If you wish to add a gateway tenant device, please review the “partial support for tenant feature” section in the Known Limitations page.

Enter the following information:

Field

Description

Name

The gateway name in DPOD (must be identical to the System Identifier

...

of the gateway).
It must meet the requirements detailed in 

...

...

gateway tenant device, enter the landlord's name

...

. DPOD will display the tenant's name as tenant@landlord.

...

Host Address

IP Address used to access the gateway.
If you

...

Info

When updating the "Log Target Source Address" after the device was added and syslog was setup for the device , the user must setup the syslog for device again (see below) in order for the change to take effect on the monitored device (see next item "Setup Syslog For The New Monitored Device" ).

Configure The New Monitored Device

Tip

If you change DPOD's or the monitored device's IP address, you will need to repeat the setup

Info
If you wish to monitor transactions in the default domain, please follow the instructions in Monitoring Transactions in the Default Domain

Right after adding the device, the "Setup" tab will be displayed, the tab is divided into six parts.
Image Removedwing sections 'inside'?

...

Setup Syslog for All Domains  -

Tip

This section will apply the same setup too all domains in the device, to select a different configuration for each domain, see the section "Domain Level Configuration" later on this page.

...

Domains WS-M Setup (Optional)

Tip

This section will apply the same setup too all domains in the device, to select a different configuration for each domain, see the section "Domain Level Configuration" later on this page.

...

Extended Transaction Setup (Optional, Deprecated)

Warning

This feature is deprecated and was replaced by a non-intrusive method.

Please do not use the button unless advised by L2/L3 support.

Domain Level Configuration (Optional)

if your architectural design dictates a different configuration for domains on the same machine, you can configure them separately:

  1. Navigate to the domain setup page  [Manage→ Devices→ Monitored Devices]
  2. Click the device name
  3. Click the domain name
  4. Click "Setup”
     
Tip

Domains may be redirected to different Syslog agents according to the architecture design. Additionally, you may choose to enable WS-M on specific domains only etc. If this is required, follow the steps below to configure specific domains. Otherwise you may skip this section

Syslog setup (Optional)

Under "Syslog Setup", select the desired Analysis Level, select the desired Syslog Agent according to the architecture design, click "Setup Syslog" and wait until the action completes successfully.

Domain WS-M setup (Optional)

Select the desired WS-M Agent according to the architecture design. Click "Setup WS-M” and wait until the action completes successfully.
For supported WS-M payload capture services see IDG WS-M payload capture support.
Click on "Record Payload" to open the payload capture page where you can start capturing payloads

Extended Transaction setup for all services (Optional, Deprecated)

...

wish to add a gateway tenant device, enter the tenant's host.

SOMA port

The SOMA port configured on this gateway.
If you wish to add a gateway tenant device, enter the tenant's SOMA port.

SOMA User Name

The user name used to access the monitored devices via SOMA.

SOMA Password

The password of the user name used to access the monitored devices via SOMA.

Log Target Source Address

IP Address of the gateway's log target source.
This should be the IP address of the ethernet interface of the gateway from which Syslog records should be sent to DPOD.
Usually, this IP address is the same as the IP address used for the Host field mentioned above, unless the gateway is in a different network than DPOD (e.g behind NAT).
If link aggregation interface is configured in the gateway, you may define its IP address as the log target source address to take advantage of the link aggregation benefits when sending Syslog records to DPOD.

Device Resources Monitoring

Whether Device resources monitoring is enabled on this gateway.
It is highly recommended to enable device resources monitoring. Disabling it will cause this device's health to be missing in System Health dashboard, as well as provide unexpected results in dashboards, reports and alerts that are based on this data.

Service Resources Monitoring

Whether Service resources monitoring is enabled on this gateway.

Once you click the Add button, DPOD will make sure it can connect to the monitored device and if successful, the gateway will be added to DPOD as a new monitored device.

Info

Each monitored gateway needs to be configured to send information to DPOD after added to DPOD. To configure the gateway, see Configuring Monitored Devices.