Why does the PacketShaper reboot when I try to restore the configuration using the "run" command?

book

Article ID: 167537

calendar_today

Updated On:

Products

PacketShaper

Issue/Introduction

The PacketShaper reboots after you try to use the run command on a .cmd file to restore a configuration.

Resolution

You are experiencing this issue because the traffic classes on your PacketShaper has reached their maximum. For example, the class tree below shows the PacketShaper currently has 1698 classes remaining. If you try to load a configuration that has 2000 traffic classes, the moment the tree reaches 2048 classes (the maximum allowed on this model), the appliance will automatically reboot.

PacketShaper# sys limit
 

Statically allocated objects          Current  Remaining      Total
-------------------------------------------------------------------
Traffic classes                           350       1698       2048
Partitions                                 37        987       1024
Dynamic Partitions                          0       1021       1021
Policies                                   27       2021       2048
Matching rules                            414       4708       5122
Classes with worst clients/servers          0          8          8
Classes with top talkers/listeners          0         12         12
TCP flows                                   1       5119       5120
Other IP flows                              1       2559       2560
Legacy flows                                2       1022       1024
Concurrent Hosts                         5120          0       5120
MAC Cache Entries                           5       4091       4096
Fragment Cache Entries                      0         50         50
Command Contexts                            8         22         30
Compression tunnels                         0          5          5
Compression entries                         0         80         80
Tunnels                                     0          5          5

 

To prevent this from happening, execute the class reset CLI command first using the run command. An example is shown below.

PacketShaper# class reset

This operation will clear the configuration's traffic classes, policies
and user event configuration, and revert it to the default traffic
configuration.

Please confirm if you really want to proceed (YES):

PacketShaper# run config.cmd