admin
<ROOT>
This command enables the context to configure administrative system commands. Only authorized users can execute the commands in the admin context.
n/a
debug-save file-url
admin
This command saves existing debug configuration. Debug configurations are not preserved in configuration saves.
n/a
the file URL location to save the debug configuration (see Table: URL Types and Syntax for parameter descriptions)
disconnect {address ip-address | username user-name | console | telnet | ftp | ssh | mct}
admin
This command disconnects a user from a console, Telnet, FTP, SSH, SFTP, or MPT craft terminal (MCT) session.
If any of the console, Telnet, FTP, SSH, or MCT options are specified, then only the respective sessions are affected. The ssh keyword disconnects users connected to the node via SSH or SFTP.
If no console, Telnet, FTP, SSH, or MCT options are specified, then all sessions from the IP address or from the specified user are disconnected.
Any task that the user is executing is terminated. FTP files accessed by the user are not removed. A major severity security log event is created, specifying what was terminated and by whom.
n/a — no disconnect options are configured
the IP address to disconnect
the name of the user
disconnects the console session
disconnects the Telnet session
disconnects the FTP session
disconnects the SSH or SFTP session
disconnects the MCT session
display-config [detail | index]
admin
This command displays the system’s running configuration.
By default, only non-default settings are displayed.
Specifying the detail option displays all default and non-default configuration parameters.
displays default and non-default configuration parameters
displays only persistent indexes
reboot [active | standby] | [upgrade] [now]
admin
This command reboots the router including redundant CSMs or upgrades the boot ROMs.
If no options are specified, the user is prompted to confirm the reboot operation. For example:
ALU-1>admin# reboot
Are you sure you want to reboot (y/n)?
If the now option is specified, no boot confirmation messages appear.
keyword to reboot the active CSM
keyword to reboot the standby CSM
enables card firmware to be upgraded during chassis reboot. The 7705 SAR and the boot.ldr support functionality to perform automatic firmware upgrades on CSMs. The automatic upgrade must be enabled in the 7705 SAR Command Line Interface (CLI) when rebooting the system.
When the upgrade keyword is specified, a chassis flag is set for the Boot Loader (boot.ldr) and on the subsequent boot of the 7705 SAR on the chassis, any firmware images on CSMs requiring upgrading will be upgraded automatically.
If a 7705 SAR is rebooted with the ‟admin reboot” command (without the ‟upgrade” keyword), the firmware images are left intact.
Any CSMs that are installed in the chassis will be upgraded automatically. For example, if a card is inserted with down revision firmware as a result of a card hot swap with the latest OS version running, the firmware on the card will be automatically upgraded before the card is brought online.
If the card firmware is upgraded automatically, a CHASSIS ‟cardUpgraded” (event 2032) log event is generated. The corresponding SNMP trap for this log event is ‟tmnxEqCardFirmwareUpgraded”.
During any firmware upgrade, automatic or manual, it is imperative that during the upgrade procedure:
power must NOT be switched off or interrupted
the system must NOT be reset
no cards are inserted or removed
Any of the above conditions may render cards inoperable requiring a return of the card for resolution.
The time required to upgrade the firmware on the cards in the chassis depends on the number of cards to be upgraded. On system reboot, the firmware upgrades can take from approximately 3 minutes (for a minimally loaded 7705 SAR) to 8 minutes (for a fully loaded 7705 SAR chassis), after which the configuration file will be loaded. The progress of the firmware upgrades can be monitored at the console. Inserting a single card requiring a firmware upgrade in a running system generally takes less than 2 minutes before the card becomes operationally up.
forces a reboot of the router immediately without an interactive confirmation
save [file-url] [detail] [index]
admin
This command saves the running configuration to a configuration file. For example:
ALU-1>admin# save ftp://test:test@192.168.x.xx/./100.cfg
Saving configuration .........Completed.
By default, the running configuration is saved to the primary configuration file.
the file URL location to save the configuration file (see Table: URL Types and Syntax for parameter descriptions)
saves both default and non-default configuration parameters
forces a save of the persistent index file regardless of the persistent status in the BOF file. The index option can also be used to avoid an additional boot required while changing your system to use the persistence indexes.
[no] enable-tech
admin
This command enables the shell and kernel commands.
This command should only be used with authorized direction from the Nokia Technical Assistance Center (TAC).
tech-support file-url
admin
This command creates a system core dump.
If the file-url is omitted, and a ts-location has previously been defined, the tech-support file will get an automatic 7705 SAR generated filename based on the system name, date, and time, and the file will be saved to the directory indicated by the configured ts-location.
The format of the auto-generated filename is ts-xxxxx.yyyymmdd.hhmmUTC.dat, where:
xxxxx is the system name with any special characters expanded to avoid problems with file systems (for example, a period (‟.”) is expanded to ‟%2E.”)
yyyymmdd is the date, with leading zeros on year, month, and day
hhmm are the hours and minutes in UTC time (24-hour format, always 4 characters, with leading zeros on the hours and minutes)
This command should only be used with authorized direction from the Nokia Technical Assistance Center (TAC).
the file URL location to save the binary file (see Table: URL Types and Syntax for parameter descriptions)
ts-location file-url
no ts-location
config>system>security>tech-support
This command specifies a location for the auto-generated filename that is created if the file-url parameter is not used in the tech-support command. The file is automatically assigned a name and saved to the configured location only if this ts-location command has first been configured; otherwise, the file-url parameter must be configured in the tech-support command to provide this information. The directory specified for the ts-location is not automatically created by the 7705 SAR; it must already exist.
the file URL location to save the binary file (see Table: URL Types and Syntax for parameter descriptions)
update boot-loader file-url
admin
This command upgrades the boot loader file on the system. The command checks that the new boot.ldr is a valid image and that it is at least a minimum supported variant for the hardware platform on which it is being loaded. Once this has been verified, the command overwrites the boot.ldr file that is stored on the system.
Nokia recommends that the boot loader file on all 7705 SAR platforms be upgraded using this command. This command is mandatory on all 7705 SAR platforms that do not have a removable compact flash drive and is part of a mechanism that protects the boot loader file from accidental overwrites on these platforms.
The file upgrade command takes several minutes to complete. Do not reset or power down the system, or insert or remove cards or modules, while the upgrade is in progress, as this could render the system inoperable.
Refer to the latest 7705 SAR Software Release Notes, ‟Standard Software Upgrade Procedure” section, for complete instructions.
the file URL location to use for upgrading the boot.ldr file (see Table: URL Types and Syntax for parameter descriptions)