The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The following commands, listed in alphabetical order, are introduced or modified for the Cisco SAMI, and are supported at a SAMI LCP console:
•boot eobc: (LCP ROM monitor command)
•clear daughtercard fpga statistics
•dir
•processor config-register (LCP ROM monitor command)
•show daughtercard fpga statistics
To boot the SAMI from the image on the supervisor engine, use the boot eobc: ROM-monitor command.
boot eobc:
This command has no keywords or arguments.
No default behavior or values exist.
ROM monitor
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
Use the boot eobc: command to boot the SAMI using the image on the supervisor engine.
The following example shows how to boot the SAMI from the image on the supervisor engine:
rommon 1> boot eobc:
|
|
---|---|
boot device module |
Sets the boot variable for the SAMI LCP. (This is supervisor console command.) |
To clear the classification and distribution engine (CDE) statistics and interrupt counts, use the clear cde command.
clear cde {interrupt | stats}
interrupt |
Clears the CDE interrupt counts. |
stats |
Clears the CDE statistics. |
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
This command clears the statistics and counts that display using the show cde command.
Note This command is for use by trained personnel for troubleshooting purposes only.
To clear the CDE interrupt counts, enter:
switch# clear cde interrupt
|
|
---|---|
show cde |
Displays CDE statistics and counts. |
To clear all of the core dumps stored in the core file system, use the clear cores command.
clear cores
This command has no keywords or arguments.
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
To view the list of core files in the core file system, use the dir core command.
To save a copy of a core dump to a remote server before clearing it, use the copy capture command.
To delete a specific core dump file from the core file system, use the delete core command.
Note The SAMI creates a core dump when it experiences a fatal error. Core dump information is for Cisco Technical Assistance Center (TAC) use only. We recommend that you contact TAC for assistance in interpreting information in a core dump.
To clear all core dumps, enter:
switch# clear cores
|
|
---|---|
delete |
Deletes core dumps stored in the core. |
dir |
Displays core dumps stored in the core. |
To clear all field programmable gate array (FPGA) statistics for a SAMI daughter card, use the clear daughtercard fpga statistics command.
clear daughtercard card_number fpga statistics
card number |
Number of the card for which you want to clear FPGA-related statistics. A valid value is 1 or 2. |
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
This command clears the statistics displayed by the show daughtercard fpga statistics command.
To clear all FPGA statistics on SAMI daughter card 1, enter:
switch# clear daughtercard 1 fpga statistics
|
|
---|---|
show daughtercard fpga statistics |
Displays the FPGA statistics for a SAMI daughter card. |
To change the configuration register settings of the SAMI LCP, use the config-register command.
config-register value
This command has no default.
Configuration
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
The config-register command affects only the configuration register bits that control the boot field and
leaves the remaining bits unaltered.
To configure the SAMI LCP to autoboot the system image identified in the boot environment variable, use the config-register command and set the configuration register to 1.
The following example sets the boot field in the configuration register to boot the system image identified in the Boot environment variable upon reboot:
switch(config)# config-register 1
|
|
---|---|
boot system image |
Specifies the system image that the router loads at startup. |
processor config-register |
Sets the configuration register for the SAMI PPCs. |
To change the configuration register settings while in ROM monitor mode, use the confreg command in ROM monitor mode.
confreg value
This command has no default.
ROM monitor
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
The config-register command affects only the configuration register bits that control the boot field and
leaves the remaining bits unaltered.
The following example sets the boot field in the configuration register to boot the system image identified in the Boot environment variable upon reboot:
rommon 1># confreg 1
|
|
---|---|
boot eobc: |
Boots the SAMI from the image on the supervisor engine. |
To configure a SAMI powerPC (PPC) on daughter card 1 to be accessible from the console port on the SAMI front panel, use the console-select db1 command.
console-select {db1 processor_number | db2 processor_number}
Daughter card 1—Console 3 is connected to the daughter card 1 console port on the SAMI front panel.
Daughter card 2—Console 6 is connected to the daughter card 2 console port on the SAMI front panel.
Configuration
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to configure one of the three PPCs on daughter card 1 of a SAMI to be accessible externally using the daughter card console port on the SAMI front panel.
By default, PPC 3 can be accessed by console port for db1 and PPC 6 can be accessed by console port of db2. After a different PPC is configured to be accessible from the console port on the SAMI front panel using the console-select commands, the newly configured PPC will continue to be accessible across router reloads.
To configure the PPC4 on daughter card 1 to be accessible from the daughter 1 console port on the SAMI front panel, enter:
switch(config)# console-select db1 4
To display information on bouncer svc daemon processing, use the debug sami bouncer_svc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sami bouncer {errors | events | packets}
no debug sami bouncer {errors | events | packets}
errors |
Displays errors. |
events |
Displays events. |
packet |
Displays information per-packet. |
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use the debug sami bouncer_svc command to view bouncer svc daemon debugging information.
The following example shows events that occur during bouncer svc daemon processing.
switch# debug sami bouncer_svc events
To display information on sami cd health daemon processing, use the debug sami dc_health command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sami dc_health {errors | events}
no debug sami dc_health {errors | events}
errors |
Displays errors. |
events |
Displays events. |
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use the debug sami dc_health command to view sami cd health daemon debugging information.
The following example shows events that occur during sami cd health processing.
switch# debug sami dc_health events
To display information on ppc download daemon processing, use the debug sami ppc_download command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sami ppc_download {errors | events}
no debug sami ppc_download {errors | events}
errors |
Displays errors. |
events |
Displays events. |
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use the debug sami ppc_download command to view ppc download daemon debugging information.
The following example shows errors that occur during ppc download daemon processing.
switch# debug sami ppc_download errors
To display information on session agent daemon processing, use the debug sami session_agent command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sami session-agent {errors | events | packets}
no debug sami session-agent {errors | events | packets}
errors |
Displays errors. |
events |
Displays events. |
packet |
Displays information per-packet. |
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use the debug sami session-agent command to view session agent daemon debugging information.
The following example shows errors that occur during session agent processing.
switch# debug sami session_agent errors
To delete a specific file in the LCP file system, use the delete command.
delete {core:filename | disk0:[path/]filename | image:filename | volatile:filename}
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
To delete a specific file from the LCP file system, use the delete command.
If you do not specify a filename with the file system keyword, the SAMI LCP prompts you for a filename.
To display the list of files that reside in a file system, use the dir sami# command.
The following example shows how to delete a file named "0x401_VSH_LOG.25256.TAR.GZ" from the core file system:
switch# delete core:0x401_VSH_LOG.25256.TAR.GZ
|
|
---|---|
dir |
Displays the contents of a specified SAMI LCP file system. |
To list files in the various file systems on the LCP, use the dir command.
dir {core: | disk0: | image: | volatile}
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
Use the dir command to list the files in the various file systems on the SAMI LCP.
To delete a file from a file system, use the delete command. To delete all core dumps, use the clear cores command.
The following example shows how to display the contents of the disk0 file system:
switch# dir disk0:
|
|
---|---|
delete |
Deletes a specified file in the SAMI LCP file system. |
more |
Displays the contents of a file. |
To erase the ROM monitor area of a SAMI powerPC (PPC) boot flash and program ROM monitor using the default image in the SAMI software bundle, use the erase ppc-flash command.
erase ppc-flash [image_name:] {ppc_number | all-ppc}
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use the erase ppc-flash command to erase the ROM monitor area of the PPC boot flash and program ROM monitor using the default image in the SAMI software bundle.
To erase the ROM monitor area of the boot flash on PCC 6 and program ROM monitor using the image in the SAMI software bundle, enter:
switch# erase ppc-flash image_name 6
This command has no related commands.
To enable a coredump to be collected from IXP, use the exception ixp command in configuration mode. Use the no form of the command to disable collecting coredump information.
exception ixp IXP-Proc
no exception ixp
IXP-Proc |
IXP processor number ( 1 or 2 ). |
none
Configuration
|
|
---|---|
SAMI Release 4.0 |
This command was introduced in conjunction with Cisco CSG2 Release 6.0, and LTE Release 2.0. |
The coredump gets stored under "crashinfo_collection-XXXXX-YYYY.tar", which resides on LCP "dir:core". The naming convention for the coredump file is as below :-
coredump_proc<Num>- XXXXX-YYYY.gz
where
Num -- Represents either 1 or 2 depending on IXP1 or IXP2 respectively
XXXXX-YYYY-- Represents the timestamp
To change the hostname of the SAMI LCP from host1 to SAMI1-LCP, enter:
switch(config)# hostname SAMI1-LCP
SAMI_LCP(config)# exception ixp 1
exception ixp 2
To change the hostname of the SAMI LCP, use the hostname command. Use the no form of this command to reset the hostname to the default of switch.
hostname name
no hostname name
name |
New hostname for the SAMI LCP. Enter a case-sensitive text string that contains from 1 to 32 alphanumeric characters. |
The hostname is host1.
Configuration
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
By default, the hostname for the SAMI LCP is host1.
The hostname is used for the command line prompts and default configuration filenames. If you establish sessions to multiple devices, the hostname helps you track where you enter commands.
To change the hostname of the SAMI LCP from host1 to SAMI1-LCP, enter:
switch(config)# hostname SAMI1-LCP
SAMI_LCP(config)#
This command has no related commands.
To create a bridge-group virtual interface (BVI) or VLAN interface, use the interface command. To remove the interface, use the no form of this command.
interface {bvi group_number | vlan number}
no interface {bvi group_number | vlan number}
Note If a VLAN interface is configured on the LCP, then a sub-interface for the same VLAN should not be configured on the PPCs.
No default behavior or values exist.
Configuration
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
Use the interface command to create a BVI or VLAN interface.
When entered, the command prompt changes to (config-if).
To assign VLAN interface 100 to the Admin context and access interface configuration mode, enter:
switch(config)# interface vlan 100
switch(config-if)#
|
|
---|---|
clear interface |
Resets the hardware logic on an interface. |
show interface |
Displays statistics for all interfaces configured on the router or access server. |
To configure a default or static IP route, use the ip route command. Use the no form of this command to remove a default or static IP route from the configuration.
ip route dest_ip_prefix netmask gateway_ip_address
no ip route dest_ip_prefix netmask gateway_ip_address
No default behavior or values exist.
Configuration
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
The default route identifies the router IP address to which the SAMI LCP sends all IP packets for which it does not have a route.
Dynamic routing is not supported. You must use static routes for any networks to which the SAMI LCP is not directly connected; for example, use a static route when there is a router between a network and the SAMI LCP.
The SAMI LCP supports up to eight equal cost routes on the same interface for load balancing.
Routes that identify a specific destination address take precedence over the default route.
To configure a default route, set the IP address and the subnet mask for the route to 0.0.0.0. For example, if the SAMI LCP receives traffic that it does not have a route, it sends the traffic out the interface to the router at 192.168.4.8, enter:
switch(config)# ip route 0.0.0.0 255.255.255.0 192.168.4.8
To change the configuration register settings of a SAMI PPC, use the processor config-register configuration command.
processor {proc_number | all-ppc} config-register value
no processor {proc_number | all-ppc} config-register value
0—The front panel connection rather than the on-the-board connection will make the PPCs automatically load the Cisco software application image upon startup.
Configuration
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
You can modify the boot method that a SAMI PPC uses at the next startup by setting the boot field in the software configuration register. The configuration register identifies how the PPC should boot and where the system image is stored. You can modify the boot field to force a PPC to boot a particular system image at startup instead of using the default system image.
The processor config-register command affects only the configuration register bits that control the boot field and leaves the remaining bits unaltered.
The following example sets the boot field in the configuration register to boot the system image identified in the BOOT environment variable upon reboot for PPC 5:
switch(config)# processor 5 config-register 1
|
|
---|---|
confreg |
Set the configuration register settings of a SAMI PPC. |
To reload the configuration on the SAMI LCP, use the reload command.
reload
This command has no keywords or arguments.
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
The reload command reboots the SAMI LCP and performs a full power cycle of both the hardware and software. The reset process can take several minutes. Any open connections with the SAMI are dropped after you enter the reload command.
To execute a soft reboot, enter:
switch# reload
This command will reboot the system
Save configurations for all the contexts. Save? [yes/no]: [yes]
|
|
---|---|
show running-config |
Displays the running configuration information on the SAMI LCP. |
show startup-config |
Displays information about the startup configuration on the SAMI LCP |
To reload a specific SAMI powerPC (PPC), use the reload sami processor command.
reload sami processor {ppc_num | all-ppc}
ppc_num |
Specifies the specific PPC. Enter a value 3 through 8. |
all-ppc |
Specifies that the ROM monitor image on all PPCs be upgraded. |
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
The reload sami processor command reboots a single SAMI PPC. The reload process can take several minutes. Any open connections with the SAMI PPC are dropped after you enter the reload sami processor command.
Note This command is not available for distributed Cisco software applications such as the Cisco Content Services Gateway - 2nd Generation.
To reload processor 4 on a SAMI, enter:
switch# reload sami processor 4
|
|
---|---|
show running-config |
Displays the running configuration information on the SAMI LCP. |
show startup-config |
Displays information about the startup configuration on the SAMI LCP |
To reprogram the Field Upgradable (FUR) partition of the rommon image on the LCP, use the reprogram bootflash command with the fur-image keyword specified.
reprogram bootflash fur-image
fur-image |
Reprograms the rommon image FUR partition. |
|
|
---|---|
Release 2.0 |
This command was introduced. |
The reprogram bootflash command is for use by trained Cisco personnel only. Entering this command may cause unexpected results. Do not attempt to use the reprogram bootflash command without guidance from Cisco support personnel.
To reprogram the rommon image FUR partition on the image: file system, enter:
switch# reprogram bootflash fur-image
This command has no related commands.
To set the destination index table from index x to y to one of several options, use the set cde destindex command in EXEC configuration mode. Use the no form of the command to disable this feature.
set cde destindex x [to y] [cp | ixp0 | ixp1 | nitrox | dc1 | dc2 | invalid]
no set cde destindex
The default value is invalid..
|
|
---|---|
Release 3.4 |
This command was introduced. |
This command is only available with the debug plugin for the LCP.
Here is an example of the set cde destindex command:
SAMI-slot8# set cde destindex 0 to 4 dc2
dest index 3 lsb 0 - 4 dest dc2
To configure vlan destinations for packets in a VLAN(s) to one of several options, use the set cde vlan command in privileged EXEC mode.
set cde vlan x [cp | ixp0 | ixp1 | nitrox | dc1 | dc2 | invalid | gtpipdesthash | ipsrchash ]
By default, CDE destinations in enhanced CDE (version 406 onwards) is set to gtpipdesthash. For previous versions of CDE, the CDE destination is set to ixp0 by default.
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in conjunction with the CSG2 Release 5.0, and the Cisco LTE Release 1.0. |
Here is an example of the set cde vlan command:
SAMI-LCP# set cde vlan 100 ixp1
This can drastically affect the way system behaves.Are you sure? [yes/no] [no] yes
vlan 100 dest ixp1
SAMI-LCP# set cde vlan 101 gtpipdesthash
This can drastically affect the way system behaves.Are you sure? [yes/no] [no] yes
vlan 101 dest gtpipdesthash
SAMI-LCP#set cde vlan 102 to 105 ipsrchash
This can drastically affect the way system behaves.Are you sure? [yes/no] [no] yes
vlan 102 - 105 dest ipsrchash
If a vlan in the range is being used by the LCP (proc 0), a warning is issued that the particular vlan is being used by the LCP and that VLAN is dropped from the configuration. The sample output of the command is as follows:
SAMI-LCP# set cde vlan 7 to 12 ixp1
vlan 7 - 12 dest ixp1
Warning: vlan 10 is being used by proc 0 and this CLI will not update it.
Please use 'set cde vlan 10' to override.
SAMI-LCP# set cde vlan 10 ixp1
To display the classification and distribution engine (CDE) register values, use the show cde command.
show cde {all | count | dist | hash index_number | health | interrupts | reg cde_number register | stats {cumulative | stats} | vlan vlan_number} [|] [>]
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
This command is for use by trained Cisco personnel for troubleshooting purposes only. You can also use the show cde vlan command to verify if the CDE is programmed correctly for the subscriber VLAN.
To display all of the CDE register values, enter:
switch# show cde all
|
|
---|---|
clear cde |
Clear the CDE statistics and interrupt counts. |
To display the destination index table for all indices x to y, use the show cde destindex command in EXEC mode.
show cde vlan x [to y]
There are no arguments or keywords.
0 <= x <= y <= 7
EXEC
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in conjunction with the CSG2 Release 5.0, and the Cisco LTE Release 1.0. |
To display destinations for all vlans from x to y enter:
slot8# show cde destindex 0 to 7
Destination index & 0x7 == 0 --> daughter card 2
Destination index & 0x7 == 1 --> daughter card 2
Destination index & 0x7 == 2 --> daughter card 2
Destination index & 0x7 == 3 --> daughter card 2
Destination index & 0x7 == 4 --> daughter card 2
Destination index & 0x7 == 5 --> ixp1
Destination index & 0x7 == 6 --> ixp0
Destination index & 0x7 == 7 --> ixp1
To display destinations for the specified VLANs, use the show cde vlan command in EXEC mode.
show cde vlan vlan_id [ to vlan_id ]
vlan_id |
VLAN id, or a range of VLAN ids for which output is needed. |
No default behavior or values exist.
EXEC
|
|
---|---|
SAMI Release 3.4 |
This command was introduced in conjunction with the CSG2 Release 5.0, and the Cisco LTE Release 1.0. |
To display destinations for all vlans from x to y enter:
SAMI-LCP# show cde vlan 7 to 12
Vlan 7 --> ixp1
Vlan 8 --> ixp0
Vlan 9 --> gtpipdesthash
Vlan 10 --> ipsrchash
Vlan 11 --> cp
Vlan 12 --> ixp1
To display the field programmable gate array (FPGA) statistics for a daughter card on the SAMI, use the show daughtercard fpga statistics command.
show daughtercard card_number fpga statistics
card number |
Number of the daughter card for which you want to display FPGA-related statistics. A valid value is 1 or 2. |
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
If a daughter card number is not specified, the FPGA statistics for both daughter cards will display.
To display the FPGA statistics for daughter card 2, enter:
switch# show daughtercard 2 fpga statistics
To display the field programmable gate array (FPGA) or complex programmable logic device (CPLD) registers for a daughter card on the SAMI, use the show daughtercard registers command.
show daughtercard card_number [fpga | cpld] registers
card number |
Daughter card for which you want to display registers. Enter 1 or 2. |
fpga |
(Optional) Displays FPGA-related registers. |
cpld |
(Optional) Displays CPLD registers. |
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
If a daughter card number is not specified, the FPGA and/or CPLD registers for both daughter cards will display.
To display the FPGA counters for daughter card 2, enter:
switch# show daughtercard 2 fpga registers
|
|
---|---|
clear daughtercard fpga statistics |
Clears all FPGA statistics for a SAMI daughter card |
show daughtercard fpga statistics |
Displays FPGA statistics for a SAMI daughter card. |
To display the amount of time, a session can remain inactive before it is ended (the login session idle timeout value), use the show login timeout command.
show login timeout
This command has no keywords or arguments.
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
To configure the login timeout value, use the login timeout command in configuration mode.
To display the login timeout value, enter:
switch#
show login timeout
|
|
---|---|
login timeout |
Modifies the length of time that a user can be idle before the LCP terminates the console, Telnet, or SSH session. |
To display the running configuration information on the SAMI LCP, use the show running-config command.
show running-config [aaa | access-list | action-list | class-map | context | dhcp | domain | ft | interface | object-group | parameter-map | policy-map | probe | resource-class | role | rserver | serverfarm | sticky] [|] [>]
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
The show running-config command is a context-sensitive command.
Use the copy capture command to do the following:
•Save a copy of the running configuration to a file on one or more destination locations.
•Save the running configuration as the startup configuration.
•Save the startup configuration as the running configuration.
To display the entire running configuration, enter:
switch# show running-config
To display information about the startup configuration on the SAMI LCP, use the show startup-config command.
show startup-config [|] [>]
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
To clear the startup configuration, use the clear startup-config command. To copy the running configuration to the startup configuration, or copy the startup configuration to the running configuration, use the copy running-config command.
To display information about the startup configuration, enter:
switch# show start-config
|
|
---|---|
clear startup-config |
Clears the startup configuration. |
show running-config |
Displays information about the running configuration on the SAMI LCP. |
To display information that is useful to technical support when reporting a problem with your SAMI LCP, use the show tech-support command.
show tech-support [details] [|] [>]
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
The show tech-support command is useful when collecting a large amount of information about your SAMI LCP for troubleshooting purposes with Cisco technical support. The output of this command can be provided to technical support representatives when reporting a problem.
The show tech-support command displays the output of several show commands at once. The output from this command varies depending on your configuration. The default output of the show tech-support command includes the output of the following commands:
•show environment—See the show environment command.
•show hardware—See the show hardware command.
•show interface—See the show interface command.
•show process—See the show processes command.
•show running-config—See the show running-config command.
•show version—See the show version command.
Explicitly set the terminal length command to 0 (zero) to disable autoscrolling and enable manual scrolling. Use the show terminal command to view the configured terminal size. After obtaining the output of this command, reset your terminal length as required.
You can save the output of this command to a file by appending > filename to the show tech-support command. If you save this file, verify that you have sufficient space to do so as each of these files may take about 1.8 MB.
To display the summary version of the technical support report, enter:
switch# show tech-support
To display the version information of system software that is loaded in flash memory and currently running on the SAMI LCP, use the show version command.
show version| >
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
The show version command also displays information related to the following SAMI hardware components:
•Slot number—Slot number that the SAMI LCP occupies on the Cisco 7600 series chassis.
•CPU—Number of CPUs and type and model
•Memory—Total and shared volatile memory
•Flash memory—Total and used flash memory
Use the show version command to verify the software version on the SAMI LCP before and after an upgrade.
To display the software version information, enter:
switch# show version
To upgrade the ROM monitor of one or more of the SAMI PPCs with a specific ROM monitor image, use the upgrade-rommon command.
upgrade-rommon rommon_image {ppc_num | all-ppc}
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to upgrade the ROM monitor of one or more of the SAMI PPCs with a specific ROM monitor image.
To upgrade the ROM monitor image on SAMI PPC 3, enter:
switch# upgrade-rommon image_name 3
This command has no related commands.
To manage persistent and nonpersistent configuration information, use the write command.
write {erase | memory [all] | terminal}
No default behavior or values exist.
EXEC
|
|
---|---|
Release 1.0 |
This command was integrated into Cisco SAMI Release 1.0. |
The different versions of this command require the following user role or feature in your user role:
•write erase—Admin user
•write mem—config-copy feature
•write all—Admin user
To write the running configuration to the startup configuration, you can also use the copy running-config startup-config command. To erase the startup configuration, you can also use the clear startup-config command. To display the running configuration, you can also use the show running-config command.
To write running configuration to the startup configuration, enter:
switch# write memory
|
|
---|---|
clear startup-config |
Command to clear the startup configuration. |
show running-config |
Command to display information about the running configuration on the SAMI LCP |
The following command is supported at the IXP console:
To shut down the network processor (IXP) on the SAMI, use the shutdown command.
shutdown
shutdown |
Specifies shutdown. |
No default behavior or values exist.
|
|
---|---|
Release 1.0 |
This command was introduced. |
Use this command to shutdown the network processor (IXP) on the SAMI.
The following examples illustrates how to use the shutdown command.
shutdown