Move Units between GroupsWhen you first add PacketShapers and PacketSeekers to PolicyCenter, they are always placed in the group default. You can move a Packeteer unit from the default group to another group at any time. Because each unit in a group must have a unique name, PolicyCenter does not allow you to move a unit into a group that already has a unit with the same name. Rename the unit you wish to move before placing it into its new group. Move units from one PolicyCenter group to another when you want to:
To move one or more units to another group:
See examples of traffic class behavior as a unit moves from group to group. Notes: Only local classes and configuration attributes are moved with the unit. Shared classes and attributes inherited from the group configuration are not moved; the unit will leave these behind, and inherit a shared configuration from its new group. See also PolicyCenter Configuration Management for more information on local and inherited traffic classes. Because the shared group configuration attributes are not moved with a unit configuration, if a unit has a local classes that use a host list inherited from its group, moving or copying this unit configuration to a new group will causes an error if the associated host list does not exist in the new group as well. To work around this, ensure that the host list exists in the target group, or add the host list on the unit to be moved, creating a local version of the host list that will be moved with the unit. If you see the message "The configuration has changed" in a popup window, close this window and refresh the browser information. To refresh the browser, either select the configurations tab in PolicyCenter or click Refresh or Reload in the browser. The browser will now display the current configuration. |
PacketGuide for PacketWise® Version 6.0