FAQ

What are the best practices for swapping out PacketShapers that are IntelligenceCenter data sources?

FAQ ID:    FAQ1100
Version:    1.0
Status:    Published
Published date:    10/26/2010
 

Answer

Background:

When the devices are defined as data sources in IntelligenceCenter, care needs to be taken when replacing one PacketShaper with another. Recycled IP addresses or host names can result in a confusing database or class structure. Furthermore, under rare circumstances, an environment can become corrupted when changing these items while a device is still present as an asset in IntelligenceCenter. (This is more or a risk with the earlier releases of IntelligenceCenter.) IC's DataCollector still has a data map of the old PacketShaper ID, after the steps in this article. The DataCollector would normally reject FDRs from the upgraded PacketShaper. To avoid this behavior, you must restart the DataCollector service after the units have been upgraded. Furthermore, you could end up with a Traffic Class ID Mismatch for user-defined classes. (Standard classes have the same class IDs across all PacketShapers.) This mismatch in the class IDs generated for the old and new PacketShapers can cause the data to show incorrect classes and hence, applications, sites, etc.
 

Answer:

PacketShapers should be upgraded one at a time. Make sure to back up the existing configuration before replacing PacketShapers. Use the setup capture complete <filename> CLI command. This saves the configuration in a .cmd file.  The entire class tree as well as other settings of the unit are saved. Backing up and then restoring ensures that the class information of the new PacketShaper matches that on the old PacketShaper that it is replacing. This is required for reports to match up properly in IntelligenceCenter as well.   For detailed instructions, PacketGuide covers how to back up the configuration on a PacketShaper.

After replacing the PacketShapers, perform the following actions on the IntelligenceCenter Server(s) in which the old PacketShapers participated. This procedure is valid for both IC 2.1.2 and for 3.1.1.

  1.   For each PacketShaper replacement unit: 
    • In IntelligenceCenter, change the IP address and the serial number to the new PacketShaper.
    • Save.
    • Repeat this procedure for every PacketShaper that has been upgraded/replaced.
  2. After all PacketShaper modifications in IntelligenceCenter are complete, restart the DataCollector service (from Windows Control Panel: Administrative Tools > Services).
  3. Transfer the .cmd file created on the original PacketShaper to the new PacketShaper, and then do a run <filename> to load this configuration.
  4. After all configurations have been re-deployed, you may reboot IntelligenceCenter as an optional step.


  Note: The procedure above will work fine whether or not the actual IP address is changed.


Rate this Page

Please take a moment to complete this form to help us better serve you.

Did this document help answer your question?
 
 
If you are finished providing feedback, please click the RATE CONTENT button. Otherwise, please add more detail in the following text box and then click RATE CONTENT.
 
 

Your response will be used to improve our document content.

Ask a Question