Packeteer Home Page Choose a PacketGuide version   

 Feedback

 Search

 Index

 Contents

What's New?


 Overviews

 Solutions

   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   

 Reference
 



 

Move Units between Groups

When 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:

  • Relocate a newly added unit from the default group into its intended destination group.

  • Move a unit from one location on the network to another. For example, if you relocated a PacketShaper from the San Francisco branch office to the Chicago branch office, you would also want to move that unit's configuration in PolicyCenter; moving it from the San Francisco group into the Chicago group.

  • Change how a unit functions at its current location. Suppose you had a PacketShaper on your network whose sole function was use partitions to assign specific amounts of bandwidth to users at the branch offices. If you wanted to change the function of that PacketShaper to control unwanted traffic on the network, that PacketShaper could be moved into a group with never-admit or discard policies for many types of peer-to-peer traffic.

To move one or more units to another group:

  1. From the configurations, manage, setup or info tab, select the group of the unit to be moved from the Group: drop-down list.

  2. Select a unit to be moved from the Unit: drop-down list.  show screen

  3. Click move. The Move Unit screen appears.  Show screen

  4. Select the unit you wish to move from the Move Unit drop-down list. Hold down the control (Ctrl) key and click multiple unit names to select and move several units at once.

  5. Select the destination group.

  6. Click move unit.

  7. A popup window will appear and ask you to confirm that you want to move the units. Click OK.

  8. In PolicyCenter 1.4.1 and above: A status window will show which unit move operations have been processed, and which are still pending.  Show screen This window will automatically close after all the move operations have been processed. Do not close the window or make any other changes in the PolicyCenter browser interface while unit moves are still pending, as this may result in incorrect or failed unit move operations.

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