Auto-Deployment Overview
For network administrators with experience using PacketShapers, installing
and configuring one or two individual units is a relatively simple and
straightforward process. But what if you want to install a unit at a remote
site where no network administrators are available? Or what if you want
to deploy several dozen units all at once? The simple solution for these
types of deployments is the PolicyCenter auto-deployment feature.
With this feature, network administrators no longer have to travel to
remove sites to configure standard PacketShaper units—
they only need to enter the unconfigured units' names, IP addresses, subnet
mask(s), and gateway and target addresses into PolicyCenter. Once the
staff at the remote sites connect the units to the network with the two
provided cables and power the unit on, PolicyCenter will contact all
the unconfigured units and give each unit its IP address and other unit-specific
information. After the units are configured with their basic network settings,
they will subscribe to the PolicyCenter directory server and receive their
complete configurations.
Important: If you send auto-deploy messages to an entire subnet
with a single unconfigured unit, only that one unconfigured unit will
see the auto-deploy message. If, however, a subnet on your network has
multiple unconfigured units, more than one unit may try to configure itself
with a single auto-deployment message, causing instability or duplicate
IP addresses in those units. Avoid this problem by removing from that
subnet all but one unconfigured unit.
What Type of Information is Sent in an Auto-Deployment Message?
Using the RSVP protocol, the PolicyCenter auto-deployment feature sends auto-deploy messages
to all the units that are still in an unconfigured state. Each RSVP message
contains the following information:
| Information type |
Description |
| IP address |
The IP address to assign to the unit |
| Netmask |
The subnet mask of the unit |
| Unit Name |
The name for the unconfigured unit. This will help identify the
unit when it subscribes to PolicyCenter. A unit name can only be
set on units running PacketWise version 7.2 and later. Auto-deployed
units running PacketWise 7.1.0 /7.1.1 will display a unit name based
upon the unit's serial number. |
| Gateway |
The unit's gateway address |
Target Host IP*
|
The IP address of a host that sits behind the unit to
be configured. PolicyCenter sends the auto-deploy message directly
to the specified address, thereby ensuring that the unconfigured unit
sees the auto-deploy message and avoiding the potential problem of
a router not forwarding the packets sent to the subnet. If no target
is specified, the auto-deploy message will be sent to the subnet of
the unconfigured unit. (See Configure Network Routers for important details on
auto-configuring units without a target host IP.) |
DNS Server*
|
The DNS server for the unit. Though this information
is not required, Packeteer highly recommends you specify a DNS server
for each unit you auto-deploy. |
Domain *
|
The domain name for the unit. Though this information
is not required, Packeteer highly recommends you specify a domain
name for each unit you auto-deploy. |
Configuration Path*
|
The PolicyCenter configuration to which the unit will
be assigned. If no value is specified, the unit will remain assigned
to its own, unique configuration. |
*Optional
Auto-Deployment Workflow
Follow these steps to use Packeteer's auto-deploy feature:
- Connect the PacketShapers to the network. See Install PacketShapers.
- Make sure network routers are properly configured to work with Packeteer's auto-deployment feature. See Configure Network Routers.
- Configure the auto-deployment server.
- Define the network identities of the units you want to auto-deploy. See Add an Auto-Deploy Unit Entry.
Auto-Deployment Feature Requirements
Before implementing the PolicyCenter auto-deployment feature, verify
that you have the following:
- PolicyCenter 7.2 or later
- PacketWise 7.1.0 or later on standard unconfigured units (the auto-deployment
feature will not configure PacketShaper ISP units)
- The unconfigured units are already correctly
connected to the network.
- Network routers are properly
configured for auto-deployment. The PacketShaper will only recognize a auto-deploy message received through the unit's OUTSIDE port.
|
