Introduction Configuring an Alias
Software Reference for SwitchBlade x3100 Series Switches (Setting Up the Switch)
1-14
contactalarm all severity all state all;
showtraf............... show classifier all full;show trafficdescriptor
all;show arpfilter;show qos;show accesslist all
showuser............... show user;show telnet server;show sessions;show
system userconfig;show log filter;show log
output;show radius;show tacplus;show snmp;show snmp
community all;
showvc................. show vc interface all full;
showvlan............... show vlan all full
-------------------------------------------------------------------------------
The default aliases are created dynamically when the system reboots and no other aliases have been created by
the user. If, for some reason, a default alias or aliases have been deleted, the user can recreate them all using
the
SETDEFAULTS ALIAS command.
1.4.6.2 Configuration Guidelines
•
Command alias allows the user to create a shortcut to a command string, allowing input of the alias instead
of the extended command string. For example, suppose the user types the following, CREATE
ALIAS=reboot STRING=”RESTART CARD ACTCFC COLD”. From this point forward, the user would
only be required to type “reboot” at the CLI to reboot the active CFC.
• When the user inputs an alias that happens to fail for some reason, the failure will be displayed exactly as if
the user entered the full command string.
• The alias must encompass an entire command line. Alias strings cannot be used to substitute a portion of a
command.
• The alias is not case-sensitive; similar to normal CLI commands.
• The system has an upper limit of 200, 255-character long alias entries.
• Alias commands persist between the ACTCFC and INACTCFC. Alias commands are available to all users
and are protected by the user level settings.
• Question mark (?), the CLI help symbol, is not available for aliases. For example, if a user created an alias
called “mkcard” that takes a parameter for card slot and card type, the following would not provide any
useful information: Manager>> mkcard ?.
• If an alias was created using a command whose definition changed as the result of an upgrade or the alias is
associated with a command that no longer exists after the upgrade, the alias will remain after the upgrade,
but will no longer work. Auditing of the aliases over upgrades to ensure that they match any commands in
the current command set is not supported.
• An existing alias cannot be overwritten. To reuse an existing alias name, the user must first destroy and then
create the new definition of the alias using the DESTROY and CREATE commands.
• An alias command name that is all or part of a command verb is not allowed. For example, the alias com-
mand could not be “CREATE”, “CREAT”, “CRE”, “CR” or “C”, because it could potentially overwrite the
command verb “CREATE”.
• All aliases are visible to all user privilege levels. Validation of the user privilege level (to execute a certain
command), is done when attempting to use the alias. If the user does not have the privilege level required
for the command, command execution will fail. This will be discussed in more detail later in this subsection.
• Alias names must be alphanumeric.
To Next Page
Loading...
Need help?
General
