We had the wizard create a host for every node in our /24 network and created a group called nwc.syr.edu. We then applied a policy to that group to limit traffic per IP address to 2 Mbps max. No matter what IP address we were assigned by the DHCP server, our test machines got only 2 Mbps.
A downside is that policy changes take effect for new connections only. While running a series of FTP transfers, we enabled a rule to limit FTP to 100 Kbps. But current FTP transfers continued to suck up all the bandwidth for a few minutes until they finished and a new set began.
We also ran into trouble with the streaming video test. We created a channel with 3 Mbps allotted to video at normal priority. However, when the pipe was saturated with Web traffic, our 1.6-Mbps QuickTime movie did not get the guaranteed bandwidth. Only when we increased the priority of the channel did we get the guaranteed bandwidth.
Keeping Track of Users
You can export Data to RADIUS for accounting purposes, a feature Packeteer also supports. ISPs will like this capability because it will help them keep tabs on bandwidth usage. NetEnforcer also provides some protection against DoS (denial of service) attacks in that you can specify a maximum number of connections, and maximum connections per second. Connections beyond these limits can either be admitted without QoS or dropped.
Bob Friday, Chief AI Officer for Juniper Networks, explains how the advanced technology is transforming operations.
Contact center leaders from 8x8, Awaken Intelligence, and 360insight discuss the importance of agent experience.
AI may force enterprises to rewire parts of their data centers so they are fully optimized to run such workloads. The question is do you use Ethernet or InfiniBand?
