2. System Administration
ROX™ v2.2 User Guide
52
RuggedBackbone™ RX5000
The CLI commands to execute at the scheduled time. The command or list of commands can be
up to 1024 characters in length. For example, this command saves the running configuration to a
file named 'myconfig': show running-config | save myconfig
Do not use interactive commands or commands that require a manual response or confirmation.
2.8. The Featurekey
2.8.1. Overview
Some ROX™ software features are only available by purchasing an appropriate feature level. Consult
the product datasheet for available feature levels and the specific capabilities they enable.
When specifying a feature level at the time of ordering, the featurekey is entered into the electronic
signature on the Control Module (CM). The featurekey is independent of the compact flash card and is
retained by the Control Module (CM) should the card be replaced. When moving the RX/MX5000 CM
to another chassis, the featurekey follows the CM to the new chassis.
2.8.2. Upgrading Feature Levels in the field
Feature levels can be purchased and upgraded in the field with a file-based featurekey. To update
your featurekey, contact your RuggedCom sales representative. For RX/MX5000 products, you need
to provide the serial number of the CM and the backplane. The upgraded featurekey is licensed for the
serial numbers you provide. For instructions on how to view your serial numbers, see
“Viewing RuggedCom Serial Numbers”
.
To install the featurekey file, use the Install Files form found under that admin menu. You can also use
the file scp-featurekey-from-url command from the ROX™ Command Line Interface. For instructions
on how to upload the featurekey file, see
Section 2.8.5, “Uploading a Featurekey”
The upgraded featurekey resides on the device’s compact flash card. ROX™ evaluates both the CM
featurekey and the file-based featurekey, and then enables the most capable feature level described
by the keys.
When using file-based featurekeys, the feature level follows the compact flash card. Moving the compact
flash card to another CM moves the feature level to the new CM. If you want the upgraded feature
level to be tied to a specific CM, contact your RuggedCom sales representative to arrange for an RMA
(Return to Manufacturer Authorization) to have the featurekey programmed into the CM.
2.8.3. When a File-based featurekey does not Match the Hardware
In rare circumstances, you may need to remove the compact flash card from one CM and transfer it
to another CM. For example: you may have a backup CM to replace a malfunctioning unit, and you
choose to use the upgrade featurekey on the malfunctioning unit’s compact flash card to retain your
configuration in the backup unit.
The file-based featurekey on the compact flash card is licensed for a particular unit, but can be
transferred to another unit to ensure continuity of service. When you transfer the file-based featurekey
from its licensed unit to another unit for which it is not licensed, the CM behaves in the following manner:
1.
The CM enables the higher feature level found on the compact flash card.
2.
The CM raises a non-clearable alarm, indicating a hardware mismatch with the featurekey.
3.
The alarm trips the fail-safe relay and turns on the main alarm LED.
On RX/MX5000 units, if the file-based featurekey matches only one of the CM or backplane
serial numbers, the CM raises an alarm of lower severity. The lower severity alarm can be
configured so that it does not trip the fail-safe relay.
