Cisco IOS IP Application Services Command Reference
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
D through H
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Contents D through H default (tracking)To set the de fault values for a tracked list, use the default command in tracking configuration mode. To disable the defaults, use the no form of this command.
default
{delay | object object-number | threshold percentage}
no
default
{delay | object object-number | threshold percentage}
Syntax Description
Command History
Usage GuidelinesAs of Cisco IOS Release 15.1(3)T, a maximum of 1000 objects can be tracked. Although 1000 tracked objects can be configured, each tracked object uses CPU resources. The amount of available CPU resources on a router is dependent upon variables such as traffic load and how other protocols are configured and run. The ability to use 1000 tracked objects is dependent upon the available CPU. Testing should be conducted on site to ensure that the service works under the specific site traffic conditions. ExamplesThe following example shows how to configure a default threshold percentage: Router(config)# track 3 list Router(config-track)# default threshold percentage Related Commands
default-stateTo set the default state for a stub object, use the default-state command in tracking configuration mode. To reset the default state to its internal default state, use the no form of this command. Command History
Usage GuidelinesUse the default-state command to set the default state of a stub object that has been created by the track stub command. The stub object can be tracked and manipulated by an external process, Embedded Event Manager (EEM). EEM is a distributed, scalable, and customized approach to event detection and recovery offered directly in a Cisco IOS device. EEM offers the ability to monitor events and take informational or corrective action when the monitored events occur or when a threshold is reached. An EEM policy is an entity that defines an event and the actions to be taken when that event occurs. delay (tracking)To specify a period of time to delay communicating state changes of a tracked object, use the delay command in tracking configuration mode. To disable the delay period, use the no form of this command.
delay
{up seconds | [down seconds] | up seconds | [down seconds] }
no
delay
{up seconds | [down seconds] | up seconds | [down seconds] }
Command History
Usage GuidelinesThis command is available to all tracked objects. If you specify, for example, delay up 10 down 30, then if the object state changes from down to up, clients tracking that object are notified after 10 seconds. If the object state changes from up to down, then clients tracking that object are notified after 30 seconds. ExamplesIn the following example, the tracking process is tracking the IP-route threshold metric. The delay period to communicate the changes of a down event of the tracked object to the client process is set to 30 seconds. Router(config)# track 1 ip route 10.22.0.0/16 metric threshold Router(config-track)# threshold metric up 16 down 20 Router(config-track)# delay down 30 forwarding-agentTo specify the port on which the forwarding agent will listen for wildcard and fixed affinities, use the forwarding-agent command in CASA-port configuration mode. To disable listening on that port, use the no form of this command. Syntax Description
Command DefaultThe default password timeout is 180 seconds. The default port for the services manager is 1637. Command History
glbp authenticationTo configure an authentication string for the Gateway Load Balancing Protocol (GLBP), use the glbp authentication command in interface configuration mode. To disable authentication, use the no form of this command.
gglbp
authentication
commandlbp
group-number
authentication
{text string | md5 {key-string [ {0 | 7} ] key | key-chain name-of-chain} }
no
glbp
group-number
authentication
{text string | md5 {key-string [ {0 | 7} ] key | key-chain name-of-chain} }
Syntax Description
Command History
Usage GuidelinesThe same authentication method must be configured on all the routers that are configured to be members of the same GLBP group, to ensure interoperation. A router will ignore all GLBP messages that contain the wrong authentication information. If password encryption is configured with the service password-encryption command, the software saves the key string in the configuration as encrypted text. ExamplesThe following example configures stringxyz as the authentication string required to allow GLBP routers in group 10 to interoperate: Router(config)# interface fastethernet 0/0 Router(config-if)# glbp 10 authentication text stringxyz In the following example, GLBP queries the key chain âAuthenticateGLBPâ to obtain the current live key and key ID for the specified key chain: Router(config)# key chain AuthenticateGLBP Router(config-keychain)# key 1 Router(config-keychain-key)# key-string ThisIsASecretKey Router(config-keychain-key)# key-string ThisIsASecretKey Router(config-keychain-key)# exit Router(config-keychain)# exit Router(config)# interface Ethernet0/1 Router(config-if)# ip address 10.0.0.1 255.255.255.0 Router(config-if)# glbp 2 authentication md5 key-chain AuthenticateGLBP glbp client-cache maximumTo enable the Gateway Load Balancing Protocol (GLBP) client cache, use the glbp client-cache command in interface configuration mode. To disable a GLBP client cache, use the no form of this command.
glbp
group
client-cache
maximum
number
[timeout minutes]
no
glbp
group-number
client-cache
maximum
number
[timeout minutes]
Syntax Description
Command History
Usage GuidelinesThis command enables a GLBP client cache on a single group only. To enable the client cache on multiple GLBP groups, you must apply this command to each group for which a client cache is required. You must specify a maximum number of clients that the client cache will hold for a GLBP group to limit the size of the cache. If a GLBP client cache already exists when this command is entered and there are already more clients in the cache than the required number, all of the existing cache entries are discarded. If you enter the no form of this command when there are already client entries in the cache, all of the client entries are discarded before the GLBP client cache is disabled.
glbp forwarder preemptTo configure a router to take over as active virtual forwarder (AVF) for a Gateway Load Balancing Protocol (GLBP) group if the current AVF falls below its low weighting threshold, use the glbp forwarder preempt command in interface configuration mode. To disable this function, use the no form of this command.
glbp
group
forwarder
preempt
[delay minimum seconds]
no
glbp
group
forwarder
preempt
[delay minimum]
Command History
ExamplesThe following example shows a router being configured to preempt the current AVF when the current AVF falls below its low weighting threshold. If the router preempts the current AVF, it waits 60 seconds before taking over the role of the AVF.
Router(config-if)# glbp 10 forwarder preempt delay minimum 60
glbp ipTo activate the Gateway Load Balancing Protocol (GLBP), use the glbp ip command in interface configuration mode. To disable GLBP, use the no form of this command. Command History
Usage GuidelinesThe glbp ip command activates GLBP on the configured interface. If an IP address is specified, that address is used as the designated virtual IP address for the GLBP group. If no IP address is specified, the designated address is learned from another router configured to be in the same GLBP group. For GLBP to elect an active virtual gateway (AVG), at least one router on the cable must have been configured with the designated address. A router must be configured with, or have learned, the virtual IP address of the GLBP group before assuming the role of a GLBP gateway or forwarder. Configuring the designated address on the AVG always overrides a designated address that is in use. When the glbp ip command is enabled on an interface, the handling of proxy Address Resolution Protocol (ARP) requests is changed (unless proxy ARP was disabled). ARP requests are sent by hosts to map an IP address to a MAC address. The GLBP gateway intercepts the ARP requests and replies to the ARP on behalf of the connected nodes. If a forwarder in the GLBP group is active, proxy ARP requests are answered using the MAC address of the first active forwarder in the group. If no forwarder is active, proxy ARP responses are suppressed. ExamplesThe following example activates GLBP for group 10 on Fast Ethernet interface 0/0. The virtual IP address to be used by the GLBP group is set to 10.21.8.10. Router(config)# interface fastethernet 0/0 Router(config-if)# ip address 10.21.8.32 255.255.255.0 Router(config-if)# glbp 10 ip 10.21.8.10 The following example activates GLBP for group 10 on Fast Ethernet interface 0/0. The virtual IP address used by the GLBP group will be learned from another router configured to be in the same GLBP group. Router(config)# interface fastethernet 0/0 Router(config-if)# glbp 10 ip glbp load-balancingTo specify the load-balancing method used by the active virtual gateway (AVG) of the Gateway Load Balancing Protocol (GLBP), use the glbp load-balancing command in interface configuration mode. To disable load balancing, use the no form of this command.
glbp
group
load-balancing
[ {host-dependent | round-robin | weighted} ]
no
glbp
group
load-balancing
Syntax Description
Command History
Usage GuidelinesUse the host-dependent method of GLBP load balancing when you need each host to always use the same router. Use the weighted method of GLBP load balancing when you need unequal load balancing because routers in the GLBP group have different forwarding capacities. glbp nameTo enable IP redundancy by assigning a name to the Gateway Load Balancing Protocol (GLBP) group, use the glbp name command in interface configuration mode. To disable IP redundancy for a group, use the no form of this command. Syntax Description
Command History
Usage GuidelinesThe GLBP redundancy client must be configured with the same GLBP group name so that the redundancy client and the GLBP group can be connected. ExamplesThe following example assigns the abccomp name to GLBP group 10:
Router(config-if)# glbp 10 name abccomp
Related Commands
glbp preemptTo configure the gateway to take over as active virtual gateway (AVG) for a Gateway Load Balancing Protocol (GLBP) group if it has higher priority than the current AVG, use the glbp preempt command in interface configuration mode. To disable this function, use the no form of this command. Syntax Description
Command DefaultA GLBP router with a higher priority than the current AVG cannot assume the role of AVG. The default delay value is 30 seconds. Command History
ExamplesThe following example shows a router being configured to preempt the current AVG when its priority of 254 is higher than that of the current AVG. If the router preempts the current AVG, it waits 60 seconds before assuming the role of AVG. Router(config-if)# glbp 10 preempt delay minimum 60 Router(config-if)# glbp 10 priority 254 glbp priorityTo set the priority level of the gateway within a Gateway Load Balancing Protocol (GLBP) group, use the glbp priority command in interface configuration mode. To remove the priority level of the gateway, use the no form of this command. Syntax Description
Command History
Usage GuidelinesUse this command to control which virtual gateway becomes the active virtual gateway (AVG). After the priorities of several different virtual gateways are compared, the gateway with the numerically higher priority is elected as the AVG. If two virtual gateways have equal priority, the gateway with the higher IP address is selected. glbp ssoTo enable Gateway Load Balancing Protocol (GLBP) support of Stateful Switchover (SSO) if it has been disabled, use the glbp ssocommand in global configuration mode. To disable GLBP support of SSO, use the no form of this command. Command History
glbp timersTo configure the time between hello packets sent by the Gateway Load Balancing Protocol (GLBP) gateway and the time that the virtual gateway and virtual forwarder information is considered valid, use the glbp timers command in interface configuration mode. To restore the timers to their default values, use the no form of this command. Syntax Description
Command History
Usage GuidelinesRouters on which timer values are not configured can learn timer values from the active virtual gateway (AVG). The timers configured on the AVG always override any other timer settings. All routers in a GLBP group should use the same timer values. If a GLBP gateway sends a hello message, the information should be considered valid for one holdtime. Normally, holdtime is greater than three times the value of hello time, (holdtime > 3 * hellotime). The range of values for holdtime force the holdtime to be greater than the hello time. ExamplesThe following example shows the GLBP group 10 on Fast Ethernet interface 0/0 timers being configured for an interval of 5 seconds between hello packets, and the time after which virtual gateway and virtual forwarder information is considered to be invalid to 18 seconds: Router(config)# interface fastethernet 0/0 Router(config-if)# glbp 10 ip Router(config-if)# glbp 10 timers 5 18 glbp timers redirectTo configure the time during which the active virtual gateway (AVG) for a Gateway Load Balancing Protocol (GLBP) group continues to redirect clients to a secondary active virtual forwarder (AVF), use the glbp timers redirect command in interface configuration mode. To restore the redirect timers to their default values, use the no form of this command. Syntax DescriptionCommand History
Usage GuidelinesA virtual forwarder that is assigned a virtual MAC address by the AVG is known as a primary virtual forwarder. If the virtual forwarder has learned the virtual MAC address from hello messages, it is referred to as a secondary virtual forwarder. The redirect timer sets the time delay between a forwarder failing on the network and the AVG assuming that the forwarder will not return. The virtual MAC address to which the forwarder was responsible for replying is still given out in Address Resolution Protocol (ARP) replies, but the forwarding task is handled by another router in the GLBP group.
The timeout interval is the time delay between a forwarder failing on the network and the MAC address for which the forwarder was responsible becoming inactive on all of the routers in the GLBP group. After the timeout interval, packets sent to this virtual MAC address will be lost. The timeout interval must be long enough to allow all hosts to refresh their ARP cache entry that contained the virtual MAC address. ExamplesThe following example shows the commands used to configure GLBP group 1 on Fast Ethernet interface 0/0 with a redirect timer of 1800 seconds (30 minutes) and timeout interval of 28,800 seconds (8 hours): Router# config terminal Router(config)# interface fastEthernet 0/0 Router(config-if)# glbp 1 timers redirect 1800 28800 glbp weightingTo specify the initial weighting value of the Gateway Load Balancing Protocol (GLBP) gateway, use the glbp weighting command in interface configuration mode. To restore the default values, use the noform of this command. Syntax Description
Command DefaultThe default gateway weighting value is 100 and the default lower weighting value is 1. Command History
Usage GuidelinesThe weighting value of a virtual gateway is a measure of the forwarding capacity of the gateway. If a tracked interface on the router fails, the weighting value of the router may fall from the maximum value to below the lower threshold, causing the router to give up its role as a virtual forwarder. When the weighting value of the router rises above the upper threshold, the router can resume its active virtual forwarder role. Use the glbp weighting track and track commands to configure parameters for an interface to be tracked. If an interface on a router goes down, the weighting for the router can be reduced by a specified value. ExamplesThe following example shows the weighting of the gateway for GLBP group 10 being set to a maximum of 110 with a lower weighting limit of 95 and an upper weighting limit of 105: Router(config)# interface fastethernet 0/0 Router(config-if)# ip address 10.21.8.32 255.255.255.0 Router(config-if)# glbp 10 weighting 110 lower 95 upper 105 glbp weighting trackTo specify a tracking object where the Gateway Load Balancing Protocol (GLBP) weighting changes based on the availability of the object being tracked, use the glbp weighting track command in interface configuration mode. To remove the tracking, use the no form of this command.
glbp
group
weighting
track
object-number
[decrement value]
no
glbp
group
weighting
track
object-number
[decrement value]
Syntax Description
Command History
Usage GuidelinesThis command ties the weighting of the GLBP gateway to the availability of its interfaces. It is useful for tracking interfaces that are not configured for GLBP. When a tracked interface goes down, the GLBP gateway weighting decreases by 10. If an interface is not tracked, its state changes do not affect the GLBP gateway weighting. For each GLBP group, you can configure a separate list of interfaces to be tracked. The optional value argument specifies by how much to decrement the GLBP gateway weighting when a tracked interface goes down. When the tracked interface comes back up, the weighting is incremented by the same amount. When multiple tracked interfaces are down, the configured weighting decrements are cumulative. Use the track command to configure each interface to be tracked. As of Cisco IOS Release 15.1(3)T, a maximum of 1000 objects can be tracked. Although 1000 tracked objects can be configured, each tracked object uses CPU resources. The amount of available CPU resources on a router is dependent upon variables such as traffic load and how other protocols are configured and run. The ability to use 1000 tracked objects is dependent upon the available CPU. Testing should be conducted on site to ensure that the service works under the specific site traffic conditions. ExamplesIn the following example, Fast Ethernet interface 0/0 tracks two interfaces represented by the numbers 1 and 2. If interface 1 goes down, the GLBP gateway weighting decreases by the default value of 10. If interface 2 goes down, the GLBP gateway weighting decreases by 5. Router(config)# interface fastethernet 0/0 Router(config-if)# ip address 10.21.8.32 255.255.255.0 Router(config-if)# glbp 10 weighting track 1 Router(config-if)# glbp 10 weighting track 2 decrement 5 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||