The thought behind writing a series of blogs on NetScaler Command Center 5.0 enhancements was to put forward the reason behind any enhancement that’s done in bringing up this CC 5.0 release. This is to give the back stage information to bring you closer to the actual NetScaler Command Center product.

This blog will entail the motive behind the two built-in tasks for configuring bandwidth on BR devices, through command center appliance.

In command center 4.x and before releases you will come across just one built-in task ConfigureBandwidth to configure bandwidth on your Branch Repeater (BR) appliances. This is for BR 5.x and before releases. NetScaler Command Center (CC) 5.0 release support a set of features of BR 6.0 Capri release. One of those supports is bandwidth configuration for BR 6.0 Capri release. In CC 5.0 you will notice ConfigureBandwidth-5.xandearlier and ConfigureBandwidth-6.xandlater built-in tasks instead of ConfigureBandwidth.

Why the segregation into two tasks?

ConfigureBandwidth-5.xandearlier is similar to ConfigureBandwidth built-in task. It asks you to define boost mode, bandwidth, minimum send rate, send limit and receive limit as shown in Figure 1. As the names suggests, this task can be executed for BR 5.x and earlier release devices. The send limit and receive limit are essentially the limits we set for the bandwidth limit for the traffic BR device sends and receives.

Figure 1 – ConfigureBandwidth-5.xandearlier built-in task

But, ConfigureBandwidth-6.xandlater built-in task just asks you to define boost mode and receive limit as shown in Figure 2. This task is executed for BR 6.x onwards devices.

Figure 2 – ConfigureBandwidth-6.xandlater built-in task

This is because for BR 6.0 release onwards, there has been an enhancement which defines two limits for send traffic:

  1. The WAN link limit which is set in the ‘Links’ page.
  2. The limit which is on the license installed on the repeater.

With BR 6.0 release, the BR appliances will have WAN and LAN links defined on different ports to segregate both the traffics and do reporting based on these. Initially depending on the “BR options” attached in the request, the opponent BR devices used to segregate the traffic into WAN and LAN traffic and perform reporting based on an algorithm. Now, BR segregates the traffic into WAN and LAN by defining links. These links perform auto-configuration and set the send limit as the lowest amongst the physical WAN link limit and the licensed limit. With this auto-configuration, BR has eradicated the manual configuration of send limit. Defining these links essentially enables the BR appliance’s reporting and traffic shaping.

Therefore, the send limit will be either the licensed limit or the WAN link limit, whichever is lower. Due to this modification in BR 6.0, these configurational changes have also been reflected in Command Center 5.0 GUI and the built-in tasks have been segregated into two separate tasks signifying different releases of BR devices.

The support for BR devices with this CC 5.0 release has been extended to not just device inventory and group configuration level functions. But, it has also been extended to new custom reports, new counter groups and new SNMP traps.

We will be talking more on the CC 5.0 new support for BR devices in upcoming blogs.