Blue Coat Support asked me to disable this command
I was wondering what the impact would be if I did disable the command from functioning.
I was wondering what the command actually did and if I needed it for future use
Blue Coat Support may have asked to turn off the command so that PacketShaper memory rescources be allocated for other uses. The impact of disabling this command is minimul outside of the Traffic History command removal.
You will not be able to use the Traffic History command until the command is re-enabled from the system settings. However you can continue to use the similar Traffic Flow command that can give you similar outout.
The Traffic History CLI command performs the following functions.
Display recent traffic flows for a specific host or traffic class.
traffic history recent|find<name>
Lists recent flows for a specified traffic class. The output includes the date, time, IP address, port number, and URL of each flow in the specified class.
Lists recent flows for a specified host. The output lists each class that the specified host uses, as well as the date, time, service name, IP address, port number, and URL of each flow in the class.
With therecentargument,<name>is the traffic class name. With thefindargument,<name>is the IP address or name of the host to be tracked.
Thetraffic history findcommand is useful for determining the servers that a specified client IP address is transferring data with, or the clients that are retrieving data from a specific server. It can also be used to determine exactly what type of network applications a specified PC is using.
If you were to disable this command, you can get similar output from using the Traffic Flow command.
Display summary information about some or all currently active TCP connections and/or UDP sessions.
traffic flow -tIo
TCP overview of non-idle flows
traffic flow -uIo
UDP overview of non-idle flows
traffic flow -h
lists help with all options
Thetraffic flow -tLcommand puts two columns in the output: LI (representing the inbound part of the TCP flow) and LO (outbound part of the flow).
Note that some flows do not completely shut down, and are therefore listed until the unit is reset. Therefore, the -t or -u option, combined with the I option, provides a list of non-idle TCP or UDP flows. For example: