Add Units to PolicyCenter
Both new and currently operating PacketShapers can be added to PolicyCenter.
Units running software version 5.2 and later can be configured in shared
mode or local mode.
- A unit running in local mode functions independently from other
units, and has all its configuration attributes stored directly on its
flash disk. Once PolicyCenter is installed on a network, units in local
mode can be set to shared mode and added to PolicyCenter by identifying the PolicyCenter directory server and
entering its password. Once done, this unit is subscribed to PolicyCenter.
- Units configured in shared mode are assigned to a PolicyCenter
configuration, and apply settings from their PolicyCenter configuration.
When a unit is in shared mode, PolicyCenter continually synchronizes
the units configuration on the PolicyCenter server with the configuration
files on that units flash disk; therefore, if you switch from
shared mode back to local, (or the network connection to the PolicyCenter
server is lost) the units configuration in local mode will be
the same as its last configuration in shared mode. Units
in shared mode may be returned to local mode at any time.
When a unit running PacketWise version 7.0 or later subscribes to PolicyCenter,
PolicyCenter creates a unique configuration for the unit at the top of
the configuration tree, then assigns the unit to that configuration. The
unique configuration has the unit's serial number for its configuration
name, and is exclusive to the unit for which it was created no other
unit can be assigned to it unless it is renamed or moved to another location
within the configuration tree. If you already have a root-level configuration
named after the unit's serial number, PolicyCenter will add the unit directly
to that existing configuration.
Note: When you subscribe a unit running PacketWise 5.x-6.x to
PolicyCenter, its new configuration appears in the /default folder, instead
of at the top of the configuration tree.
Add a New Unit to PolicyCenter
To add a new, unconfigured unit to PolicyCenter, use the PolicyCenter auto-deployment feature, or select the shared
mode option when you install the unit onto the network. When prompted,
provide the IP address or host name of PolicyCenter and the PolicyCenter
Directory Server password. The PolicyCenter software will create a new PolicyCenter
configuration for the unit, then automatically assign the unit to the
new configuration. This unit is now subscribed to PolicyCenter.
Add a Currently Operating Unit to PolicyCenter
Note: PolicyCenter does not support the Easy Configure feature
available in earlier versions of PacketWise software, and units configured
with Easy Configure cannot be added to PolicyCenter. We recommend that
you
turn off Easy Configure and reset
the class tree before putting a unit into shared mode for PolicyCenter.
To add a unit that is already configured on your network:
- Access the unit's browser interface, using a browser and the IP address
of the unit.
- Click the info tab to verify that the unit is running PacketWise
version 5.2.0 or higher. If the version is not 5.2 or higher, you will
need to upgrade
the software image on that unit.
- Click the setup tab.
- From the Choose Setup Page list, select PolicyCenter access.
(If you do not see the PolicyCenter access option, the PacketShaper is not
running PacketWise version 5.2 or higher.) The PolicyCenter Access
page appears
show screen.
- In the Directory Server Host field, provide the DNS name (recommended)
or IP address of the computer where the PolicyCenter Directory Server is installed.
Note: Packeteer strongly recommends identifying the directory server by
DNS name, rather than by IP address. With this option, if you migrate
PolicyCenter to a different server, you only need to assign the previous
servers DNS name to the new server, and all units will be able
to contact the new PolicyCenter server immediately. If a unit is subscribed
to PolicyCenter via the servers IP address, migrating PolicyCenter
to a different server may require you to access the unit, unsubscribe
it, then resubscribe the unit to the new IP address.
- (Optional for units running PacketWise 7.5 and above) Check the Secure Connection checkbox to establish a secure LDAP connection between the PacketShaper and the PolicyCenter directory server.
- (For units running PacketWise 7.0 and above) In the Unit Name
field, enter a unique name for the unit that will help you to identify
the unit and its configuration within the PolicyCenter Units list. The suggested names are the DNS name of the unit (if present)
or the unit serial number.
- If you want a unit to retain its existing working configuration even after
it has been added to PolicyCenter, select the convert configuration
checkbox. When you select this option, the units existing sharable
attributes will be converted into a new PolicyCenter configuration
with the same attributes and values. Because the units new PolicyCenter
configuration will be based upon its previous configuration, the unit
will continue to operate the same in PolicyCenter as it did in local
mode. If you do not select the convert option, the units new PolicyCenter
configuration is cleared, and will have default settings only.
- Click apply changes. A pop-up window appears and asks you to
confirm your selection.
- Click OK. The unit will be prescribed to PolicyCenter, and you will be logged out of the PacketShaper browser interface.
Confirm that your PacketShaper is installed in PolicyCenter
After you add the unit to PolicyCenter, you should confirm that PolicyCenter
recognizes the new configuration.
- Access PolicyCenter by opening another browser window, and entering
the IP address or DNS name of the PolicyCenter Windows server.
- Click the Units tab. (You may have to wait a few seconds
for a response.)
If PolicyCenter displays information about your unit and its configuration,
you have successfully configured your PacketShaper to work with PolicyCenter.
If your unit isnt listed on the Units tab, refresh the
PolicyCenter browser window or reopen the unit's browser interface and
make sure the unit is in shared mode.
Notes: If you use a secure browser interface with a non-default HTTPS
port setting (that is, a port other than 443) to carry out the convert operation,
you may see a "Page Not Found" error on the secure web page immediately
after you perform this operation. The secure port configuration will be
converted into a PolicyCenter configuration, but it may be a few seconds
before you can refresh the secure browser page to reestablish communication
with the unit.
See also:
PolicyCenter Overview |