The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to configure the Backhaul Manager to monitor backhauls in order to maximize backhaul uptime, and to take corrective behavior when a backhaul is down on the Cisco 1000 Series Connected Grid Routers (hereafter referred to as the Cisco CG-OS router).
When configured on the Cisco CG-OS router, the Backhaul Manager actively monitors the backhaul between the Cisco CG-OS router and the head-end router.
When a catastrophe affects the backhaul, the Backhaul Manager automatically initiates its configured policies to attempt to recover the backhaul. The first action taken is a reset of interfaces (such as cellular, WiMax, Ethernet) and tunnels on the backhaul. When a reset of the interfaces or tunnels does not restore the backhaul, then a reload of the Cisco CG-OS router occurs.
The following Backhaul Manager policies can be configured on all Cisco CG-OS router interfaces and tunnels.
Note To define actions to address the backhaul flap beyond reporting a syslog event, add those actions (such as backhaul rest or backhaul reload) to the script (see Defining Backhaul Manager Applets, Track Objects and Scheduler Script).
For detailed configuration steps and examples for the Backhaul Manager policies, see Configuring Backhaul Manager.
The Backhaul Manager must be configured in the default VDC of the Cisco CG-OS router. No other VDCs are supported on the Cisco CG-OS router.
When you want to collect syslog events locally on the Cisco CG-OS router, you must enable syslog
(see Chapter 2, “Configuring System Message Logging”).
Enable the Scheduler on the Cisco CG-OS router (see Defining Backhaul Manager Applets, Track Objects and Scheduler Script).
This section includes the following topics:
Defines environment and threshold policies that the Backhaul Manager can execute to monitor or reset interfaces or tunnels (connections) within the backhaul or to reload the Cisco CG-OS router.
Review the “Information About Backhaul Manager” section and “Prerequisites” section.
event manager environment bh_iflist { “interface slot/port”| “ tunnel number” } ... [ “interface slot/port”| “ tunnel number” ] |
Creates an environment variable named bh_iflist , that defines all the interfaces (such as cellular, Ethernet, or WiMax) or tunnels that the Backhaul Manager monitors (and resets, if necessary) within the backhaul that connects the Cisco CG-OS router and the head-end router. Note : Cisco recommends that you list all active interfaces and tunnels within the backhaul. Both the interface type and slot/port number must be enclosed in quotations as well as the tunnel and tunnel number. Note : Do not provide a space between the interface type and slot/port (such as “ cellular3/1 ”). Likewise, define the tunnel and its number with no space (such as “ tunnel1 ”). Note : Environment variables have a length limit of 39 characters. To ensure that you can define as many backhaul lists as necessary, the Cisco CG-OS software allows you to define multiple bh_iflists such as bh_iflist1 , bh_iflist2 , bh_iflist3 , and so on. Later, the Cisco CG-OS software concatenates the lists. |
|
Creates an environment variable named bh_flap_thresh_cnt that monitors the backhaul flaps on the Cisco CG-OS router and generates a backhaul-down syslog event when the backhaul-down events exceed the defined count ( cnt value ) within a certain duration. value –Enter any numeric value; however, it must be enclosed with quotation marks. Note : The event manager environment bh_flap_thresh_duration command in Step 4 defines the duration. |
||
Defines the maximum period of time (in mins) that a backhaul can remain down before the Cisco CG-OS software generates a backhaul-down syslog event. value –Enter any numeric value; however, it must be enclosed with quotation marks. |
||
Creates an environment variable named bh_down_reset_thresh that defines the maximum allowed backhaul outage (in mins) before the Cisco CG-OS software resets defined interfaces and tunnels on the backhaul. value –Enter any numeric value; however, it must be enclosed with quotation marks. Note : The event manager environment bh_iflist command in Step 6 defines which interfaces and tunnels the Cisco CG-OS software resets. |
||
event manager environment
bh_iflist {
“interface slot/port”| “
tunnel
number”
} |
Creates an environment variable named bh_iflist that defines the interfaces and tunnels that the Cisco CG-OS software resets when the bh_down_reset_thresh value set in Step 5 is exceeded. |
|
Creates an environment variable named bh_down_reload_thresh that defines the maximum allowed backhaul outage (in mins) before the Cisco CG-OS software reloads the Cisco CG-OS router. value –Enter any numeric value; however, it must be enclosed with quotation marks. |
||
This example shows how to configure the supported Backhaul Manager policies to monitor the backhaul between the Cisco CG-OS router and a head-end router.
The script reads and applies all the defined event manager environments each time it is invoked by either the scheduler or an event manager environment variable.
Define all the event manager environments listed in the Defining Event Manager Environments section.
At the Cisco CG-OS router command-line prompt, enter the following commands.
Note For more details on the commands and their syntax, refer to the Command Lookup Tool on Cisco.com.
To define the router to monitor (in this case the loopback address of the head-end router), enter the following commands.
To define the objects to track and report backhaul up and down states, enter the following commands.
Note Object tracking ignores any intermediate state changes before the delay timer expires. The address specified in the ip route command is the loopback address of the head-end router and the delay up and down values are noted in seconds.
To define a job (a set of commands or tcl script) to be executed on a regular schedule enter the following commands.
System message logging allows you to configure the destination device of the system messages and to filter system messages by severity level. For more information on the syslog, see Configuring System Message Logging .
Listed below is an example of the critical events reported to the syslog when a backhaul down condition occurs.
To display event manager configuration information, enter the following commands.
Displays information about the event manager environment variables. |
|
Displays all the logged syslog events for the Backhaul Manager. |