We were discussing Riverbed Operating System (RiOS) technical concepts. We now look at some of the management streamlining features. As discussed, RiOS is deployed via appliances and clients. By their nature, they have minimal administrative overhead. Deployment is further simplified because it requires no change to servers, clients or routes. In addition, a central management console facilitates enterprise wide reporting, configuration and deployment options.
Let us look at the configuration and management tasks to see how the optimizations we talked about earlier are provisioned. The RiOS devices support management via SSH command line interface or graphical HTTP/S interface. The device needs to know the configuring interface IP, duplex information, subnet and management information, and then the device can be plugged into the network. Every device also supports SNMP traps and email alerts. SNMP traps include accounting and audit alerts such as user login/logout, configuration changes, TCPDump etc. The APIs allow the rest of the reporting and management actions.
RiOS introduces an auto-discovery capability that automates the establishment of optimization peering relationships through the enterprise. This is a scalable approach that can grow with the size of the enterprise. Again, without the use of tunnels, auto-discovery enables easy integration with "any-to-any" networks, which is common to many of today's WAN architectures, thereby circumventing problems specific to tunnel based optimization technologies.
As opposed to the devices, the clients can number in hundreds or even in thousands. Since it requires an installer based deployment, this is easily automated via silent installation mode and mass installations.
The reporting information is not clouded by the application acceleration capabilities. RiOS enables naming and tagging to report the different traffic driving across WAN. Reports can also include per application statistics for traffic that is passed through unoptimized.
#codingexercise
Double GetNthRootProductOddRaisedPPlusQAndEvenRaisedPTimesQ (Double [] A,Double p, Double q)
{
If ( A== null) return 0;
Return A.NthRootProductOddRaisedPPlusQAndEvenRaisedPTimesQ(p, q);
}
Let us look at the configuration and management tasks to see how the optimizations we talked about earlier are provisioned. The RiOS devices support management via SSH command line interface or graphical HTTP/S interface. The device needs to know the configuring interface IP, duplex information, subnet and management information, and then the device can be plugged into the network. Every device also supports SNMP traps and email alerts. SNMP traps include accounting and audit alerts such as user login/logout, configuration changes, TCPDump etc. The APIs allow the rest of the reporting and management actions.
RiOS introduces an auto-discovery capability that automates the establishment of optimization peering relationships through the enterprise. This is a scalable approach that can grow with the size of the enterprise. Again, without the use of tunnels, auto-discovery enables easy integration with "any-to-any" networks, which is common to many of today's WAN architectures, thereby circumventing problems specific to tunnel based optimization technologies.
As opposed to the devices, the clients can number in hundreds or even in thousands. Since it requires an installer based deployment, this is easily automated via silent installation mode and mass installations.
The reporting information is not clouded by the application acceleration capabilities. RiOS enables naming and tagging to report the different traffic driving across WAN. Reports can also include per application statistics for traffic that is passed through unoptimized.
#codingexercise
Double GetNthRootProductOddRaisedPPlusQAndEvenRaisedPTimesQ (Double [] A,Double p, Double q)
{
If ( A== null) return 0;
Return A.NthRootProductOddRaisedPPlusQAndEvenRaisedPTimesQ(p, q);
}
No comments:
Post a Comment