Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 1261)

Brocade Mobility RFS Controller CLI Reference Guide 1253
53-1003098-01
25
Supported in the following platforms:
• Access Points — Brocade Mobility 650 Access Point, Brocade Mobility 6511 Access Point,
Brocade Mobility 1220 Access Point, Brocade Mobility 71XX Access Point, Brocade
Mobility 1240 Access Point
• Wireless Controllers — Brocade Mobility RFS4000, Brocade Mobility RFS6000, Brocade
Mobility RFS7000
• Service Platforms — Brocade Mobility RFS9510
Syntax:
use critical-resource-monitoring
Parameters
use critical-resource-monitoring
Example
rfs7000-37FABE(config-routing-policy-testpolicy)#use
critical-resource-monitoring
rfs7000-37FABE(config-routing-policy-testpolicy)#
Related Commands:
no
routing-policy-commands
Negates a command or sets its defaults
Supported in the following platforms:
• Access Points — Brocade Mobility 650 Access Point, Brocade Mobility 6511 Access Point,
Brocade Mobility 1220 Access Point, Brocade Mobility 71XX Access Point, Brocade
Mobility 1240 Access Point
• Wireless Controllers — Brocade Mobility RFS4000, Brocade Mobility RFS6000, Brocade
Mobility RFS7000
• Service Platforms — Brocade Mobility RFS9510
Syntax:
no [apply-to-local-packets|logging|route-map|use]
Parameters
no [apply-to-local-packets|logging|route-map|use]
Usage Guidelines:
use
critical-resource-monitoring Uses CRM to monitor the status of a link. Selecting this option determines the disposition of the
route-map next hop via monitored critical resources. Link monitoring is the function used to determine a
potential fail over to the secondary next hop. This option is enabled by default.
no Disables CRM link status monitoring
no Negates a command or set its defaults