| eG Monitoring |
|---|
|
Measures reported by NSRoutTest By default, the NetScaler has the ability to participate in Layer 3 routing i.e., learning and advertising routes using routing protocols such as Routing Information Protocol (RIP), Open Shortest Path First (OSPF) and Border Gateway Protocol (BGP). BGP is the de facto standard for routing IP traffic across the global Internet. It is a routing protocol designed to share IP network address groups, or prefixes, between multiple different organizations. Each of these organizations (usually an ISP or a large private network) classify their addressing space as an Autonomous System–a network, or group of networks, that has an addressing and routing structure unique from another organizations. BGP is a very complex and powerful routing protocol, which some characteristics that make it quite unique compared to other protocols like RIP or OSPF. All aspects of its configuration are done manually–there is no “auto-discovery” of neighboring routers. Connections to other BGP neighbors, once configured, use a TCP connection to exchange network prefixes. Because of the possibility of mistakenly sending or receiving route information that could bring down the routing tables for neighboring routers, or even the global Internet, there are many methods of screening and applying routing policies to updates sent or received from BGP peers. A NetScaler can run BGP as a routing protocol to learn routes from other BGP routers, as well as advertise routes that the NetScaler knows about (networks downstream, vservers, and so on). Configuring NetScaler for BGP routing involves enabling dynamic routing, adding the BGP process to the routing engine, and configuring the BGP process with the essential BGP settings: peer router addresses and Autonomous System numbers, whether to redistribute routes from the kernel and/or defined static routes, and whether to learn routes from connected BGP peers. When a route is advertised, the BGP peers connected to the network, learns those routes. Frequent advertising of routes indicates that the peers are always kept aware of the routes in the network. If there are any errors that occur when a router advertises a route, then the availability of the router may alternate frwuently between up and down. Due to the instability of the router, the network topology is distorted which forces the routes to be withdrawn. If the instability continues, then the routes that are advertised will decrease and the routes that are withdrawn may subsequently go up resulting in high network latency. The Routing test helps administrators to keep a check on the number of routes that are advertised and the routes that are withdrawn over a period of time. Using this test, administrators can figure out the routes that were advertised and the routes that were relearnt. In addition, this test will help administrators to identify the number of times the routes were withdrawn and the number of times the HA state of the routes was changed. For this test to run and report metrics, the NetScaler device should be configured to create a Syslog file in a remote Syslog server, where the details of all interactions with the NetScaler appliance will be logged. To know how to configure the Syslog server where this Syslog file should be created, Click here. Outputs of the test : One set of results for the NetScaler appliance being monitored The measures made by this test are as follows:
|