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

580 Brocade Mobility RFS Controller CLI Reference Guide
53-1003098-01
7
ip dhcp trust
qos trust dscp
qos trust 802.1p
interface ge4
ip dhcp trust
qos trust dscp
qos trust 802.1p
use firewall-policy default
controller host 1.2.3.4 pool 2
controller group test
service pm sys-restart
rfs4000-229D58(config-profile-testBrocade Mobility RFS4000)#controller
adopted-devices aps controllers
rfs4000-229D58(config-profile-testBrocade Mobility RFS4000)#show context
profile rfs4000 testBrocade Mobility RFS4000
autoinstall configuration
....................................................................
logging on
service pm sys-restart
router ospf
controller adopted-devices aps controllers
rfs4000-229D58(config-profile-testBrocade Mobility RFS4000)#
Related Commands:
critical-resource
Profile Config Commands
Monitors resources that are critical to the health of the service platform, wireless controller, or
access point managed network. These critical resources are identified by their configured IP
addresses. When enabled, the system monitors these devices regularly and logs their status.
A critical resource can be a gateway, AAA server, WAN interface, any hardware, or a service on
which the stability of the network depends. Monitoring these resources is therefore essential.
When enabled, this feature pings critical resources regularly to ascertain their status. If there is a
connectivity issue, an event is generated stating a critical resource is unavailable. By default, there
is no enabled critical resource policy and one needs to be created and implemented.
Critical resources can be monitored directly through the interfaces on which they are discovered.
For example, a critical resource on the same subnet as an Brocade Mobility 1240 Access Point
access point can be monitored by its IP address. However, a critical resource located on a VLAN
must continue to be monitored on that VLAN.
Critical resource monitoring can be enabled on service platforms, wireless controllers, and access
points through their respective device profiles.
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
no Disables or reverts settings to their default