Device-upgrade – Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) User Manual
Page 57
Brocade Mobility RFS Controller CLI Reference Guide
39
53-1003098-01
2
rfs7000-37FABE>crypto key import rsa moto123 url passphrase word background on
rfs7000-37FABE
RSA key import operation is started in background
rfs7000-37FABE>
rfs7000-37FABE>crypto pki generate self-signed word generate-rsa-key word
autogen-subject-name fqdn word
Successfully generated self-signed certificate
rfs7000-37FABE>
rfs7000-37FABE>crypto pki zeroize trustpoint word del-key on rfs7000-37FABE
Successfully removed the trustpoint and associated certificates
%Warning: Applications associated with the trustpoint will start using
default-trustpoint
rfs7000-37FABE>
rfs7000-37FABE>crypto pki authenticate word url background on rfs7000-37FABE
Import of CA certificate started in background
rfs7000-37FABE#>
rfs7000-37FABE>crypto pki import trustpoint word url passphrase word on
rfs7000-37FABE
Import operation started in background
rfs7000-37FABE>
Related Commands:
device-upgrade
Enables firmware upgrade on an adopted device or a set of adopted devices (access points,
wireless controllers, and service platforms)
In an hierarchically managed (HM) network, this command enables centralized device upgradation
across the network.
The Mobility HM network defines a three-tier structure, consisting of multiple wireless sites
managed by a single Network Operations Center (NOC) controller, The NOC controller constitutes
the first and the site controllers constitute the second tier of the hierarchy. The site controllers may
or may not be grouped to form clusters. The site controllers in turn adopt and manage access
points that form the third tier of the hierarchy.
NOTE
Hierarchical management allows the NOC controller to upgrade controllers and access points that
are directly or indirectly adopted to it. However, ensure that the NOC controller is loaded with the
correct firmware version.
All adopted devices (access points and second-level controllers) are referred to as the ‘adoptee’.
The adopting devices are the ‘adopters’. A controller cannot be configured as an adoptee and an
adopter simultaneously. In other words, a controller can either be an adopter (adopts another
controller) or an adoptee (is adopted by another controller).
Removes server certificates, trustpoints and their associated certificates