PCM+ Agent with ONE zl Module Installation and Getting Started Guide 2009-11

1-28
Getting Started
Example PCM+ Agent Module Deployment
■ If there is a Management VLAN on the private network, the PCM Agent
should be a member of the Management VLAN. Any subnets in the private
network with devices to be managed by the Agent must be accessible from
the Management VLAN, or the VLAB containing the Agent.
■ A subnet can be managed by only one Agent within an Agent Group. If you
have multiple remote sites with a private network protected by a firewall
and you use the same private network for each site, you will need an Agent
Group for each site. Because Agent Groups determine what set of network
devices are displayed using when PCM+ 3.10, you may have created the
necessary Agent Groups already. If so, remember that Agents must be
assigned to an Agent Group before they are activated. Once activated,
there is no way to move an Agent to another Agent Group.
To create an Agent Group, click Agent Groups in the PCM+ 3.10 Navigation
pane to display the Agent Groups dashboard. Select the Agent Groups tab,
then click the “Create Agent Group” icon on the tool bar.
■ Firewalls between an Agent and the devices it manages are not supported.
■ Firewalls between a Clint and the PCM+ 3.10 Server are not supported.
Note You may have a firewall between your PCM+ 3.10 Server and the public
network. This firewall must allow the Agent - Server traffic on port 51111 (by
default) to pass. Also, access the Agent’s Web browser interface requires
communication through port 8080 (by default). In addition, we recommend
allowing ICMP traffic through the firewall, to enable ping operations. The
following example does not address modifying this firewall.
Getting Started
Managing a PCM+ Agent Module through a firewall requires:
■ Firewall policies that allow traffic to be exchanged between the PCM+
3.10 Server and the Agent on port 51111 (by default).
■ Firewall policies for ICMP to enable ping operations to confirm connec-
tions is recommended.
■ Firewall policies to enable access to the Agent Web browser interface for
connection configuration (https://<Agent IP address>:<Port> (the default
port is 8080), if an Agent-initiated connection is required.
■ SNMP, Telnet, and Web browser communication must be available
between the Agent and the devices to be managed in the private network.
Different subnets may be used for devices, so long as the Agent has access
to any subnets with devices to be managed.