Table Of Contents
CLI Command Reference
?
aaa accounting commands
aaa authentication attempts
aaa authentication enable default
aaa authentication login default
accelerate-packet-drops
access-list
application slot replace force completion
asymmetric-L2-support
attack-detector default
attack-detector
attack-detector <number>
attack-detector TCP-port-list|UDP-port-list
attack-filter
attack-filter dont-filter | force-filter
attack-filter subscriber-notification ports
bandwidth
blink
boot system
calendar set
cd
clear arp-cache
clear interface linecard counters
clear interface linecard flow-filter
clear interface linecard mac-resolver arp-cache
clear interface linecard subscriber
clear interface linecard subscriber db counters
clear interface linecard traffic-counter
clear logger
clear management-agent notifications counters
clear rdr-formatter
clear scmp name counters
clock read-calendar
clock set
clock summertime
clock timezone
clock update-calendar
configure
connection-mode
copy
copy ftp://
copy-passive
copy running-config startup-config
copy source-file ftp://
copy source-file startup-config
copy startup-config destination-file
default subscriber template all
delete
dir
disable
do
duplex
enable
enable password
erase startup-config-all
exit
external-bypass
failure-recovery operation-mode
flow-capture
flow-capture controllers
force failure-condition
help
history
history size
hostname
interface gigabitethernet
interface linecard
ip access-class
ip address
ip advertising
ip default-gateway
ip domain-lookup
ip domain-name
ip ftp password
ip ftp username
ip host
ip name-server
ip radius-client retry limit
ip route
ip rpc-adapter
ip rpc-adapter port
ip rpc-adaptor security-level
ip ssh
ip ssh key
ip-tunnel IPinIP skip
ip-tunnel IPinIP DSCP-marking-skip
ip-tunnel l2tp skip
l2tp identify-by
line vty
link failure-reflection
link mode
logger add-user-message
logger device
logger device user-file-log max-file-size
logger get support-file
logger get user-log file-name
logout
mac-resolver arp
management-agent sce-api ignore-cascade-violation
management-agent sce-api logging
management-agent sce-api timeout
management-agent system
mkdir
more
more user-log
mpls
no subscriber
no subscriber mappings included-in
ping
pqi install file
pqi rollback file
pqi uninstall file
pqi upgrade file
pwd
queue
rdr-formatter category number
rdr-formatter destination
rdr-formatter destination protocol NetflowV9 template data timeout
rdr-formatter forwarding-mode
rdr-formatter history-size
rdr-formatter protocol NetflowV9 dscp
rdr-formatter rdr-mapping
reload
reload shutdown
rename
rmdir
salt
sce-url-database add-entry
sce-url-database import
sce-url-database protection
sce-url-database remove-all
scmp
scmp keepalive-interval
scmp loss-of-sync-timeout
scmp name
scmp reconnect-interval
scmp subscriber force-single-sce
scmp subscriber id append-to-guid
scmp subscriber send-session-start
script capture
script print
script run
script stop
service-bandwidth-prioritization-mode
service password-encryption
service rdr-formatter
service telnetd
show access-lists
show blink
show calendar
show clock
show environment all
show environment cooling
show environment power
show environment temperature
show environment voltage
show failure-recovery operation-mode
show hostname
show hosts
show interface gigabitethernet
show interface linecard
show interface linecard accelerate-packet-drops
show interface linecard application
show interface linecard asymmetric-L2-support
show interface linecard asymmetric-routing-topology
show interface linecard attack-detector
show interface linecard attack-filter
show interface linecard connection-mode
show interface linecard counters
show interface linecard duplicate-packets-mode
show interface linecard external-bypass
show interface linecard flow-open-mode
show interface linecard ip-tunnel
show interface linecard ip-tunnel IPinIP
show interface linecard l2tp
show interface linecard link mode
show interface linecard link-to-port-mappings
show interface linecard mac-mapping
show interface linecard mac-resolver arp
show interface linecard mpls
show interface linecard physically-connected-links
show interface linecard sce-url-database
show interface linecard sce-url-database protection
show interface linecard service-bandwidth-prioritization-mode
show interface linecard shutdown
show interface linecard silent
show interface linecard subscriber
show interface linecard subscriber aging
show interface linecard subscriber anonymous
show interface linecard subscriber anonymous-group
show interface linecard subscriber db counters
show interface linecard subscriber mapping
show interface linecard subscriber max-subscribers
show interface linecard subscriber name
show interface linecard subscriber properties
show interface linecard subscriber sm-connection-failure
show interface linecard subscriber templates
show interface linecard tos-marking
show interface linecard traffic-counter
show interface linecard traffic-rule
show interface linecard virtual-links
show interface linecard vlan
sshow interface linecard wap
show interface tengigabitethernet
show inventory
show ip access-class
show ip advertising
show ip default-gateway
show ip filter
show ip radius-client
show ip route
show ip rpc-adapter
show ip ssh
show line vty
show log
show logger device
show management-agent
show management-agent sce-api quota
show pqi file
show pqi last-installed
show rdr-formatter
show rdr-formatter connection-status
show rdr-formatter counters
show rdr-formatter destination
show rdr-formatter enabled
show rdr-formatter forwarding-mode
show rdr-formatter history-size
show rdr-formatter protocol NetflowV9 dscp
show rdr-formatter rdr-mapping
show rdr-formatter statistics
show running-config
show scmp
show snmp
show snmp community
show snmp contact
show snmp enabled
show snmp host
show snmp location
show snmp mib
show snmp traps
show startup-config
show system operation-status
show system-uptime
show tacacs
show telnet sessions
show telnet status
show timezone
show users
show version
show version all
show version software
silent
snmp-server
snmp-server community
snmp-server contact
snmp-server enable traps
snmp-server host
snmp-server interface
snmp-server location
speed
subscriber aging
subscriber anonymous-group export csv-file
subscriber anonymous-group import csv-file
subscriber anonymous-group name ip-range
subscriber capacity-options
subscriber export csv-file
subscriber import csv-file
subscriber max-subscribers
subscriber name property name
subscriber sm-connection-failure
subscriber template export csv-file
subscriber template import csv-file
tacacs-server host
tacacs-server key
tacacs-server timeout
telnet
timeout
tracert
traffic-counter
traffic-rule
unzip
username
username privilege
virtual-links index direction
vlan
wap
CLI Command Reference
This chapter contains all the CLI commands available on the SCE platform.
Each command description is broken down into the following sub-sections:
Description
|
Description of what the command does.
|
Command Syntax
|
The general format of the command.
|
Syntax Description
|
Description of parameters and options for the command.
|
Default
|
If relevant, the default setting for the command.
|
Mode
|
The mode (command line) from which the command can be invoked.
|
Usage guidelines
|
Information about when to invoke the command and additional details.
|
Authorization
|
The level of user authorization required for using the command.
|
Example
|
An illustration of how the command looks when invoked. Because the interface is straightforward, some of the examples are obvious, but they are included for clarity.
|
Related Commands
|
Other commands that might be used in conjunction with the command.
|
Syntax and Conventions
The CLI commands are written in the following format:
command required-parameter [optional-parameter]
no is an optional parameter that may appear before the command name.
When typing commands, you may enclose parameters in double-quote marks, and you must do so when there is a space within a parameter name.
?
Lists all of the commands available for the current command mode. You can also use the ? command to get specific information on a keyword or parameter. To obtain a list of commands that begin with a particular character string, enter the abbreviated command entry immediately followed by a question mark (?). This form of help is called partial help, because it lists only the keywords or arguments that begin with the abbreviation you entered.
?
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings
Command Modes
All
Usage Guidelines
To list a command's associated keywords or arguments, enter a question mark (?) in place of a keyword or parameter on the command line. This form of help is called argument help because it lists the keywords or arguments that apply based on the command, keywords, and arguments you have already entered.
Examples
The following example shows ways of requesting help using the ? wildcard.
SCE(config)#ip ?
default-gateway Sets the default gateway
domain-lookup Enables the IP DNS-based host name-to-address translation
domain-name Define a default domain name
host Add a host to the host table
name-server Specify the address of one or more name servers to use for name and
address resolution
route Add IP routing entry
SCE(config)#ip d?
default-gateway domain-lookup domain-name
SCE(config)#ip de?
default-gateway
SCE(config)#ip de
aaa accounting commands
Use the no form of the command to disable TACACS+ accounting.
aaa accounting commands level default stop-start group tacacs+
no aaa accounting commands level default
Syntax Description
level
|
The privilege level for which to enable the TACACS+ accounting
0: User
5: Viewer
10: Admin
15: Root
|
Defaults
By default, TACACS+ accounting is disabled.
Command Modes
Global Configuration
Usage Guidelines
If TACACS+ accounting is enabled, the SCE platform sends an accounting message to the TACACS+ server after every command execution. The accounting message is logged in the TACACS+ server for the use of the network administrator.
The start-stop keyword (required) indicates that the accounting message is sent at the beginning and the end (if the command was successfully executed) of the execution of a CLI command.
Authorization: admin
Examples
The following example enables TACACS+ accounting for the admin privilege level (10).
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)# aaa accounting commands 10 default stop-start group tacacs+
SCE(config)#
Related Commands
Command
|
Description
|
aaa authentication attempts
|
Sets the maximum number of login attempts that will be permitted before a Telnet session is terminated.
|
aaa authentication enable default
|
Specifies which privilege level authentication methods are to be used, and in what order of preference.
|
aaa authentication login default
|
Specifies which login authentication methods are to be used, and in what order of preference.
|
tacacs-server host
|
Defines a new TACACS+ server host that is available to the SCE platform TACACS+ client.
|
tacacs-server key
|
Defines the global default encryption key for the TACACS+ server hosts.
|
aaa authentication attempts
aaa authentication attempts login number-of-attempts
Syntax Description
number-of-attempts
|
the maximum number of login attempts that will be permitted before the telnet session is terminated
|
Defaults
Default number-of-attempts = 3
Command Modes
Global Configuration
Usage Guidelines
The maximum number of login attempts is relevant only for Telnet sessions. From the local console, the number of re-tries is unlimited.
Authorization: admin
Examples
The following example shows how to set the maximum number of logon attempts to five.
SCE>enable 10
Password:<cisco>
SCE#config
product>(config)# aaa authentication attempts login 5
SCE(config)#
Related Commands
Command
|
Description
|
aaa authentication accounting commands
|
Enables TACACS+ accounting.
|
aaa authentication enable default
|
Specifies which privilege level authentication methods are to be used, and in what order of preference.
|
aaa authentication login default
|
Specifies which login authentication methods are to be used, and in what order of preference.
|
aaa authentication enable default
Specifies which privilege level authentication methods are to be used, and in what order of preference. Use the no form of the command to delete the privilege level authentication methods list.
aaa authentication enable default method1 [method2...]
no aaa authentication enable default
Syntax Description
method
|
the privilege level authentication methods to be used. You may specify up to four different methods, in the order in which they are to be used.
|
Defaults
Default privilege level authentication method = enable only
Command Modes
Global Configuration
Usage Guidelines
Use this command to configure "backup" privilege level authentication methods to be used in the event of failure of the primary privilege level authentication method. The following method options are available:
•
group tacacs+ : Use TACACS+ authentication.
•
local : Use the local username database for authentication.
•
enable (default): Use the " enable " password for authentication
•
none : Use no authentication.
If the privilege level authentication methods list is deleted, the default privilege level authentication method only ( enable password) will be used. TACACS+ authentication will not be used.
Authorization: admin
Examples
This example shows how to configure privilege level authentication methods.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)# aaa authentication enable default group tacacs+ enable none
SCE(config)#
Related Commands
Command
|
Description
|
aaa authentication login default
|
|
aaa authentication accounting commands
|
|
aaa authentication attempts
|
|
show tacacs
|
|
aaa authentication login default
Specifies which login authentication methods are to be used, and in what order of preference. Use the no form of the command to delete the login authentication methods list.
aaa authentication login default method1 [method2...]
no aaa authentication login default
Syntax Description
method
|
the login authentication methods to be used. You may specify up to four different methods, in the order in which they are to be used.
|
Defaults
Default login authentication method = enable only
Command Modes
Global Configuration
Usage Guidelines
Use this command to configure "backup" login authentication methods to be used in the event of failure of the primary login authentication method.
The following method options are available:
•
group tacacs+ : Use TACACS+ authentication.
•
local : Use the local username database for authentication.
•
enable (default): Use the " enable " password for authentication
•
none : Use no authentication.
If the login authentication methods list is deleted, the default login authentication method only (enable password) will be used. TACACS+ authentication will not be used.
Authorization: admin
Examples
This example shows how to configure login authentication methods.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)# aaa authentication login default group tacacs+ enable none
SCE(config)#
Related Commands
Command
|
Description
|
aaa authentication enable default
|
|
aaa authentication accounting commands
|
|
aaa authentication attempts
|
|
show tacacs
|
|
accelerate-packet-drops
Enables the drop-wred-packets-by-hardware mode. This improves performance, but prevents the application from being able to count all dropped packets. Use the no form to disable the drop-wred-packets-by-hardware mode, enabling the software to count all dropped packets (at the expense of some loss of performance).
accelerate-packet-drops
no accelerate-packet-drops
Syntax Description
This command has no arguments or keywords.
Defaults
By default, accelerate-packet-drops (the drop-wred-packets-by-hardware mode) is enabled.
Command Modes
Interface Linecard Configuration
Usage Guidelines
By default, the SCE platform hardware drops WRED packets (packets that are marked to be dropped due to BW control criteria). However, this presents a problem for the user who needs to know the number of dropped packets per service.
The user can disable the drop-wred-packets-by-hardware mode. The application can then retrieve the number of dropped packets for every flow and provide the user with better visibility into the exact number of dropped packets and their distribution.
Note that counting all dropped packets has a considerable affect on system performance, and therefore, by default, the drop-wred-packets-by-hardware mode is enabled.
Note
The MIB object tpTotalNumWredDiscardedPackets counts dropped packets. The value in this counter is absolute only in no accelerate-packet-drops mode. When in accelerate-packet-drops mode (default mode), this MIB counter provides only a relative value indicating the trend of the number of packet drops, with a factor of approximately 1:6.
Authorization: admin
Examples
The following example shows how to disable the drop-wred-packets-by-hardware mode so that the application can count all dropped packets.
SCE>enable 10
password:<cisco>
SCE#>config
SCE(config)#interface linecard 0
SCE(config if)#no accelerate-packet-drops
SCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard accelerate-packet-drops
|
|
access-list
Adds an entry to the bottom of the specified access list. Use the no form of the command to remove an entry from the specified access list.
access-list number permission address
no access-list number
Syntax Description
number
|
An access-list number (1-99).
|
permission
|
Indicates whether the IP address should be allowed or denied access permission as described in the Valid Permission Values table in the Usage Guidelines.
|
address
|
Addresses to be matched by this entry as described in the Valid Address Values table in the Usage Guidelines.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
The SCE platform can be configured with Access Control Lists (ACLs), which are used to permit or deny incoming connections on any of the management interfaces. An access list is an ordered list of entries, each consisting of the following:
•
A permit/deny field
•
An IP address
•
An optional wildcard "mask" defining an IP address range
The order of the entries in the list is important. The default action of the first entry that matches the connection is used. If no entry in the Access List matches the connection, or if the Access List is empty, the default action is deny.
Table 2-1 Valid Permission Values
deny
|
Deny access to list member
|
permit
|
Permit access to list member.
|
any
|
All IP addresses are matched by this entry. This is equivalent to specifying the address 0.0.0.0 255.255.255.255
|
ip-address
|
The IP address or range of IP addresses, matched by this entry. This can be one address in the x.x.x.x format or a range of addresses in the format x.x.x.x y.y.y.y where x.x.x.x specifies the prefix bits common to all IP addresses in the range, and y.y.y.y is a mask specifying the bits that are ignored. In this notation, `1' means bits to ignore. For example, the address 0.0.0.0 255.255.255.255 means any IP address. The address 10.0.0.0 0.1.255.255 means IP addresses from 10.0.0.0 to 10.1.255.255. The address 1.2.3.4 0.0.0.255 means IP addresses from 1.2.3.0 to 1.2.3.255 (A more natural way of expressing the same range is 1.2.3.0 0.0.0.255).
|
Authorization: admin
Examples
The following examples illustrate the use of this command.
EXAMPLE 1
The following example adds entries to the bottom of access-list 1. The first entry permits access to 10.1.1.0 through 10.1.1.255. The second entry denies access to any address. Together this list allows access only to addresses 10.1.1.*.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#access-list 1 permit 10.1.1.0 0.0.0.255
SCE(config)#access-list 1 deny any
SCE(config)#
EXAMPLE 2
The following example defines access list 2, a list that denies access to all IP addresses in the range: 10.1.2.0 to 10.1.2.255, permits access to all other addresses in the range 10.1.0.0 to 10.1.15.255, and denies access to all other IP addresses. Note that since the first range is contained within the second range, the order of entries is important. If they had been entered in the opposite order, the deny entry would not have any effect.
SCE>enable 10
Password:<cisco>
SCE#config
SCE (config)#access-list 2 deny 10.1.2.0 0.0.0.255
SCE (config)#access-list 2 permit 10.1.0.0 0.0.15.255
SCE(config)#
Related Commands
Command
|
Description
|
ip access-class
|
|
show access-lists
|
|
application slot replace force completion
Forces the current application replace process to complete and immediately start finalization (killing all old flows).
application slot slot-number replace force completion
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example illustrates how to force the application replace operation to complete immediately.
SCE>enable 10
Password:<cisco>
SCE#application slot 0 replace force completion
SCE#
asymmetric-L2-support
Configures the system to treat flows as having asymmetric layer 2 characteristics (including Ethernet, VLAN, and L2TP), for the purpose of packet injection.
Use the no form of the command to disable asymmetric L2 support.
asymmetric-L2-support
no asymmetric-L2-support
Syntax Description
This command has no arguments or keywords.
Defaults
By default, asymmetric layer 2 support is disabled.
Command Modes
Interface Linecard Configuration
Usage Guidelines
You should enable asymmetric layer 2 support in cases where the following conditions apply for any flows:
•
Each direction of the flow has a different pair of MAC addresses
•
The routers do not accept packets with the MAC address of the other link
Note
'Asymmetric routing topology' support and 'asymmetric tunneling support' are two separate features. Asymmetric routing topology refers to topologies where the SCE platform might see some flows only in one direction (upstream/downstream). Asymmetric tunneling support (asymmetric L2 support) refers to the ability to support topologies where the SCE platform sees both directions of all flows, but some of the flows may have different layer 2 characteristics (like MAC addresses, VLAN tags, and L2TP headers), which the SCE platform must specifically take into account when injecting packets into the traffic (such as in block and redirect operations). Note as well, that in order to support asymmetric layer 2, the SCE platform switches to asymmetric flow open mode, which incurs a certain performance penalty. This is NOT the case for asymmetric routing topology.
Authorization: admin
Examples
The following example shows how to use this command.
SCE>enable 10
Password:<cisco>
SCE#configure
SCE(config)#interface linecard 0
SCE(config if)# asymmetric-L2-support
Related Commands
Command
|
Description
|
show inteface linecard asymmetric-L2-support
|
|
attack-detector default
Defines default thresholds and attack handling action. If a specific attack detector is defined for a particular situation (protocol/attack direction/side), it will override these defaults. Use the no version of this command to delete the user-defined defaults. The system defaults will then be used.
attack-detector default protocol protocol attack-direction attack-direction side side [action
action ] [open-flows open-flows] [ddos-suspected-flows ddos-suspected-flows]
[suspected-flows-ratio suspected-flows-ratio] [notify-subscriber | dont-notify-subscriber]
[alarm |noalarm]
no attack-detector default protocol protocol attack-direction attack-direction side side [action
action] [open-flows open-flows] [ddos-suspected-flows ddos-suspected-flows]
[suspected-flows- ratio suspected-flows-ratio]
Syntax Description
protocol
|
TCP, UDP, IMCP, other
|
attack-direction
|
attack-source, attack-destination, both
|
side
|
subscriber, network, both
|
action
|
report, block
|
open-flows
|
Threshold for concurrently open flows (new open flows per second).
|
ddos-suspected-flows
|
Threshold for DDoS-suspected flows (new suspected flows per second).
|
suspected-flows-ratio
|
Threshold for ratio of suspected flow rate to open flow rate.
|
Defaults
The default values for the default attack detector are:
•
Action = Report
•
Thresholds — Varies according to the attack type
•
Subscriber notification = Disabled
•
Sending an SNMP trap = Disabled
Command Modes
LineCard Interface Configuration
Usage Guidelines
The following arguments must always be specified:
•
protocol
•
attack-direction
•
side
The following arguments are optional:
•
action
•
open-flows
•
ddos-suspected-flows
•
suspected-flows-ratio
Use the optional keywords as follows:
•
Use the notify-subscriber keyword to enable subscriber notification.
•
Use the dont-notify-subscriber keyword to disable subscriber notification.
•
Use the alarm keyword to enable sending an SNMP trap.
•
Use the no-alarm keyword to disable sending an SNMP trap.
Use the attack-detector <number>command to configure a specific attack detector.
Authorization: admin
Examples
The following examples illustrate the use of the attack-detector default command:
EXAMPLE 1
The following example configures a default attack detector for TCP flows from the attack source.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)#attack-detector default protocol TCP attack-direction attack-source side
both action report open-flows 500 ddos-suspected-flows 75 suspected-flows-ratio 50
SCE(config if)#
EXAMPLE 2
The following example enables subscriber notification for the specified default attack detector.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)#attack-detector default protocol TCP attack-direction attack-source side
both notify-subscriber
SCE(config if)#
Related Commands
Command
|
Description
|
attack-detector <number>
|
|
attack-filter subscriber-notification ports
|
|
show interface LineCard attack-detector
|
|
attack-detector
Enables the specified attack detector and assigns an access control list (ACL) to it.
attack-detector number access-list access-list
Syntax Description
number
|
The attack detector number.
|
access-list
|
The number of the ACL containing the IP addresses selected by this detector
|
Defaults
This command has no default settings.
Command Modes
LineCard Interface Configuration
Usage Guidelines
Use the following commands to define the attack detector and the ACL:
•
attack-detector
•
acccess-list
Authorization: admin
Examples
The following example enables attack detector number "2", and assigns ACL "8".
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)#attack-detector 2 access-list 8
SCE(config if)#
Related Commands
Command
|
Description
|
access-list
|
|
attack-detector <number>
|
|
show interface LineCard attack-detector
|
|
show access-lists
|
|
attack-detector <number>
Configures a specific attack detector for a particular attack type (protocol/attack direction/side) with the assigned number. Use the default form of this command to configure the default attack detector for the specified attack type. Use the no form of this command to delete the specified attack detector.
attack-detector number protocol (((TCP|UDP) [dest-port destination port ])|ICMP|other|all)
attack-direction attack-direction side side [action action ] [open-flows open-flows ]
[ddos-suspected-flows ddos-suspected-flows ] [suspected-flows-ratio suspected-flows-ratio ]
[notify-subscriber|dont-notify-subscriber] [alarm|no-alarm]
no attack-detector number
attack-detector default protocol (((TCP|UDP) [dest-port destination port ])|ICMP|other|all)
attack-direction attack-direction side side [action action ] [open-flows open-flows ]
[ddos-suspected-flows ddos-suspected-flows ] [suspected-flows-ratio suspected-flows-ratio ]
[notify-subscriber|dont-notify-subscriber] [alarm|no-alarm]
no attack-detector default protocol (((TCP|UDP) [dest-port destination port ])|ICMP|other|all)
attack-direction attack-direction side side
default attack-detector {all |all-numbered}
default attack-detector number protocol (((all | IMCP | other | TCP | UDP) [dest-port
destination port attack-direction attack-direction side side
Syntax Description
number
|
Assigned number for attack-detector
|
protocol
|
TCP, UDP, IMCP, other
|
destination port
|
{TCP and UDP protocols only): Defines whether the default attack detector applies to specific (port-based) or not specific (port-less) detections.
specific, not-specific, both
|
attack-direction
|
single-side-destination, single-side-both, dual-sided, all
|
side
|
subscriber, network, both
|
action
|
report, block
|
open-flows-rate
|
Threshold for rate of open flows (new open flows per second).
|
suspected-flows-rate
|
Threshold for for rate of suspected DDoS flows (new suspected flows per second)
|
ssuspected-flows-ratio
|
Threshold for ratio of suspected flow rate to open flow rate.
|
Defaults
The default values for the default attack detector are:
•
Action = Report
•
Thresholds = Varies according to the attack type
•
Subscriber notification = Disabled
•
Sending an SNMP trap = Disabled
Command Modes
LineCard Interface Configuration
Usage Guidelines
If a specific attack detector is defined for a particular attack type, it will override the configured default attack detector.
The following arguments must always be specified:
•
protocol
•
attack-direction
•
side
The following arguments are optional:
•
action
•
open-flows
•
ddos-suspected-flows
•
suspected-flows-ratio
Use the appropriate keyword to enable or disable subscriber notification by default:
•
notify-subscriber : Enable subscriber notification.
•
dont-notify-subscriber: Disable subscriber notification.
Use the appropriate keyword to enable or disable sending an SNMP trap by default:
•
alarm : Enable sending an SNMP trap.
•
no-alarm : Disable sending an SNMP trap.
If the selected protocol is either TCP or UDP, specify whether the destination port is specific, not specific, or both. If the destination port or ports are specific, the specific destination ports are configured using the attack-detectorcommand.
Use the attack-detectorcommand to enable a configured attack detector.
Use the attack-detector defaultcommand to configure a default attack detector.
Authorization: admin
Examples
The following examples illustrate the use of the attack-detector <number>command:
EXAMPLE 1
The following example configures the attack detector number "2".
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)# attack-detector 2 protocol UDP dest-port not-specific attack-direction
single-side-destination side both action block open-flows-rate 500 suspected-flows-rate
500 suspected-flows-ratio 50 notify-subscriber alarm
SCE(config if)#
EXAMPLE 2
The following example deletes attack detector number "2".
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)#no attack-detector 2
SCE(config if)#
EXAMPLE 3
The following example disables subscriber notification for attack detector number "2".
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)#attack-detector 2 protocol UDP dest-port not-specific attack-direction
single-side-destination side both dont-notify- subscriber
SCE(config if)#
Related Commands
Command
|
Description
|
attack-detector
|
|
attack-detector TCP-port-list|UDP-port-list
|
|
attack-filter subscriber-notification ports
|
|
attack-detector default
|
|
show interface LineCard attack-detector
|
|
attack-detector TCP-port-list|UDP-port-list
Defines the list of destination ports for specific port detections for TCP or UDP protocols.
attack-detector number (tcp-port-list|udp-port-list) (all | (port1 [port2...]) )
Syntax Description
number
|
Number of the attack detector for which this list of specific ports is relevant
|
port1, port2
|
List of up to 15 specific port numbers.
|
Defaults
This command has no default settings.
Command Modes
LineCard Interface Configuration
Usage Guidelines
TCP and UDP protocols may be configured for specified ports only (port-based). Use this command to configure the list of specified destination ports per protocol.
Up to 15 different TCP port numbers and 15 different UDP port numbers can be specified.
Configuring a TCP/UDP port list for a given attack detector affects only attack types that have the same protocol (TCP/UDP) and are port-based (i.e. detect a specific destination port). Settings for other attack types are not affected by the configured port list(s).
Specify either TCP-port-list or UDP-port-list.
Use the all keyword to include all ports in the list.
Authorization: admin
Examples
This example shows how to configure the destination port list for the TCP protocol for attack detector #10.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)#attack-detector 10 TCP-port-list 100 101 102 103
SCE(config if)#
Related Commands
Command
|
Description
|
attack-detector <number>
|
|
attack-filter (LineCard Interface Configuration)
|
|
attack-filter
Enables specific attack detection for a specified protocol and attack direction. Use the no form of the command to disable attack detection.
attack-filter protocol (((TCP|UDP) [dest-port destination port ])|ICMP|other|all)
attack-direction attack-direction
no attack-filter protocol (((TCP|UDP) [dest-port destination port ])|ICMP|other|all)
attack-direction attack-direction
Syntax Description
protocol
|
TCP, UDP, IMCP, other
|
destination port
|
{TCP and UDP protocols only): Defines whether the default attack detector applies to specific (port-based) or not specific (port-less) detections.
specific, not-specific, both
|
attack-direction
|
single-side-destination, single-side-both, dual-sided, all
|
Defaults
By default, attack-filter is enabled.
Default protocols = all protocols (no protocol specified)
Default attack direction = all directions
Default destination port = both port-based and port-less
Command Modes
LineCard Interface Configuration
Usage Guidelines
Specific attack filtering is configured in two steps:
•
Enabling specific IP filtering for the particular attack type (using this command).
•
Configuring an attack detector for the relevant attack type (using the attack-detector <number>command). Each attack detector specifies the thresholds that define an attack and the action to be taken when an attack is detected.
In addition, the user can manually override the configured attack detectors to either force or prevent attack filtering in a particular situation (using the attack filter force filter | don't-filter command).
By default, specific-IP detection is enabled for all attack types. You can configure specific IP detection to be enabled or disabled for a specific, defined situation only, depending on the following options:
•
For a selected protocol only.
•
For TCP and UDP protocols, for only port-based or only port-less detections.
•
For a selected attack direction, either for all protocols or for a selected protocol.
If the selected protocol is either TCP or UDP, specify whether the destination port is specific (port-based), not specific (port-less), or both. If the destination port or ports are specific, the specific destination ports are configured using the attack-detector TCP-port-list|UDP-port-listcommand.
Authorization: admin
Examples
The following examples illustrate the use of this command.
EXAMPLE 1
The following example shows how to enable specific, dual-sided attack detection for TCP protocol only.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)#attack-filter protocol TCP dest-port specific attack-direction dual-sided
SCE(config if)#
EXAMPLE 2
The following example shows how to enable single-sided attack detection for ICMP protocol only.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)# attack-filter protocol ICMP attack-direction single-side-source
SCE(config if)#
EXAMPLE 3
The following example disables attack detection for all non TCP, UDP, or ICMP protocols.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface LineCard 0
SCE(config if)#no attack-filter protocol other attack-direction all
SCE(config if)#
Related Commands
Command
|
Description
|
attack-detector TCP-port-list|UDP-port-list
|
|
attack-detector <number>
|
|
show interface LineCard attack-filter
|
|
attack-filter dont-filter | force-filter
This command prevents attack filtering for a specified IP address/protocol. If filtering is already in process, it will be stopped. When attack filtering has been stopped, it remains stopped until explicitly restored by another CLI command (either specific or general). Use theno form of this command to restore attack filtering. Theforce-filter keyword forces attack filtering for a specified IP address/protocol. When attack filtering has been forced, it continues until explicitly stopped by another CLI command (either specific or general). Use theno form of this command to stop attack filtering.
attack-filter force-filter action (block|report) protocol ((TCP|UDP) [dest-port (port-number
|not-specific)]|ICMP|other) attack-direction
(((single-side-source|single-side-destination|single-side-both) ip ip-address )|(dual-sided
source-ip ip-address destination-ip ip-address )) side side
attack-filter dont-filter protocol ((TCP|UDP) [dest-port (port-number
|not-specific)]|ICMP|other) attack-direction
(((single-side-source|single-side-destination|single-side-both) ip ip-address )|(dual-sided
source-ip ip-address destination-ip ip-address )) side side
no attack-filter dont-filter protocol ((TCP|UDP) [dest-port (port-number
|not-specific)]|ICMP|other) attack-direction
(((single-side-source|single-side-destination|single-side-both) ip ip-address )|(dual-sided
source-ip ip-address destination-ip ip-address )) side side
no attack-filter force-filter protocol ((TCP|UDP) [dest-port (port-number
|not-specific)]|ICMP|other) attack-direction
(((single-side-source|single-side-destination|single-side-both) ipip-address )|(dual-sided
source-ip ip-address destination-ip ip-address )) side side
no attack-filter force-filter all
no attack-filter dont-filter all
Syntax Description
action (force-filter command only)
|
Specifies the action th e force-filter command should perform:
• block
• report
|
protocol
|
TCP, UDP, ICMP, or Other
|
destination port
|
(TCP and UDP protocols only): Defines whether specific IP detection is forced or prevented for the specified port number or is port-less (non-specific).
port-number, not-specific
|
attack direction
|
Defines whether specific IP detection is forced or prevented for single-sided or dual-sided attacks.
• Single-sided: specify the direction (single-side-source, single-side-destination, single-side-both) and the IP address.
• Dual-sided: Specify 'dual-sided' and both the source and the destination IP addresses.
|
ip-address
|
IP address from which traffic will not be filtered.
• For single-sided filtering, only one IP address is specified.
• For dual-sided filtering, both a source IP address and a destination IP address are specified.
|
side
|
subscriber, network, both
|
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
After configuring the attack detectors, the SCE platform automatically detects attacks and handles them according to the configuration. However, there are scenarios in which a manual intervention is desired, either for debug purposes, or because it is not trivial to reconfigure the SCE attack-detectors properly.
The user can use the CLI attack filtering commands to do the following:
•
Prevent/stop filtering of an attack related to a protocol, direction and specified IP address
•
Force filtering of an attack related to a protocol, direction and specified IP address
Attack filtering can be prevented for a specified IP address/protocol by executing a dont-filter CLI command. If filtering is already in process, it will be stopped. When attack filtering has been stopped, it remains stopped until explicitly restored by another CLI command (either force-filter or no dont-filter).
Attack filtering can be prevented for a specified IP address/protocol by executing a dont-filter CLI command. If filtering is already in process, it will be stopped. When attack filtering has been stopped, it remains stopped until explicitly restored by another CLI command (either force-filter or no dont-filter).
Use the all keyword to restore or stop all filtering.
Authorization: admin
Examples
The following are examples of the attack-filter command:
EXAMPLE 1
The following example prevents attack filtering for the specified conditions.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#attack-filter dont-filter protocol other attack-direction
single-side-source ip 10.10.10.10 side both
SCE(config if)#
EXAMPLE 2:
The following example restores all attack filtering.
SCE>enable 10
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#no attack-filter dont-filter all
SCE(config if)#
Password:<cisco>
EXAMPLE 3:
The following example forces attack filtering.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#attack-filter force-filter protocol TCP dest-port not-specific
attack-direction dual-sided source-ip 10.10.10.10 destination-ip 20.20.20.20 side both
SCE(config if)#
EXAMPLE 4:
The following example stops all forced attack filtering.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#no attack-filter force-filter all
SCE#
Related Commands
Command
|
Description
|
attack-filter
|
|
attack-filter subscriber-notification ports
Specifies a port as subscriber notification port. TCP traffic from the subscriber side to this port will never be blocked by the attack filter, leaving it always available for subscriber notification. Use theno form of this command to remove the port from the subscriber notification port list.
attack-filter subscriber-notification ports port
no attack-filter subscriber-notification ports port
Syntax Description
port
|
Port number. One port can be specified as the subscriber notification port.
|
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
Use this command to configure the port to be used for subscriber notification as configured using the attack-filter and attack-detector <number>commands.
Authorization: admin
Examples
The following example specifies port 100 as the subscriber notification port.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#attack-filter subscriber-notification ports 100
SCE(config if)#
Related Commands
Command
|
Description
|
attack-detector default
|
|
attack-detector <number>
|
|
show interface linecard attack-filter
|
|
bandwidth
Sets Ethernet shaping for the TenGigabitEthernet line interfaces.
bandwidth bandwidth burst-size burstsize
Syntax Description
bandwidth
|
Bandwidth measured in kbps.
|
burstsize
|
Burst size in bytes.
|
Defaults
bandwidth = 100000K (100 Mbps)
burst-size = 5000 (5K bytes)
Command Modes
TenGigabitEthernet Interface Configuration
Usage Guidelines
This command is valid for a specified TenGigabitEthernet line interface only. It must be executed explicitly for each interface.
Authorization: admin
Examples
The following example sets bandwidth and burst size for a 10 Gigabit Ethernet line interface 3/2/0)
SCEconfig
SCE(config)#interface TenGigabitEthernet 3/2/0
SCE(config if)#bandwidth 100000 burstsize 5000
SCE(config if)#
Related Commands
Command
|
Description
|
interface tengigabitethernet
|
|
queue
|
|
blink
Blinks a slot LED for visual identification. Use theno form of this command to stop the slot blinking.
blink slot slot-number
no blink slot slot-number
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
Not blinking
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example configures the SCE platform to stop blinking.
SCE>enable 10
Password:<cisco>
SCE#no blink slot 0
SCE#
Related Commands
Command
|
Description
|
show blink
|
|
boot system
Specifies a new package file to install. The SCE platform extracts the actual image file(s) from the specified package file only during the copy running-config startup-config command.
boot system ftp://username[:password]@server-address[:port]/path/source-file destination-file
no boot system
Syntax Description
ftp://...destination-file
|
The ftp site and path of a package file that contains the new firmware. The filename should end with the.pkg extension.
|
Defaults
The ftp site and path of a package file that contains the new firmware. The filename should end with the.pkg extension.
Command Modes
Global Configuration
Usage Guidelines
Use this command to upgrade the SCE platform embedded firmware. The package file is verified for the system and checked that it is not corrupted. The actual upgrade takes place only after executing the copy running-config startup-config command and rebooting the SCE platform.
Authorization: admin
Examples
The following example upgrades the system.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#boot system ftp://user:1234@10.10.10.10/downloads/SENum.pkg.pkg
Verifying package file...
Package file verified OK.
SCE(config)#do copy running-config startup-config
Backing -up configuration file...
Writing configuration file...
Extracting new system image...
Extracted OK.
Related Commands
Command
|
Description
|
copy running-config startup-config
|
|
calendar set
Sets the system calendar. The calendar is a system clock that continues functioning even when the system shuts down.
calendar set hh:mm:ss day month year
Syntax Description
hh:mm:ss
|
Current local time in hours in 24-hour format, minutes and seconds (HH:MM:SS).
|
day
|
Current day (date) in the month.
|
month
|
Current month (by three-letter abbreviated name).
|
year
|
Current year using a 4-digit number.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Always coordinate between the calendar and clock by using the clock read-calendar command after setting the calendar.
Authorization: admin
Examples
The following example sets the calendar to 20 minutes past 10 AM, January 13, 2006, synchronizes the real-time clock to the calendar time, and displays the result.
SCE>enable 10
Password:<cisco>
SCE#calendar set 10:20:00 13 jan 2006
SCE#clock read-calendar
SCE#show calendar
10:20:03 UTC THU January 13 2006
SCE#show clock
10:20:05 UTC THU January 13 2006
SCE#
Related Commands
Command
|
Description
|
clock read-calendar
|
|
clock set
|
|
clock update-calendar
|
|
cd
Changes the path of the current working directory.
cd new-path
Syntax Description
new-path
|
The path name of the new directory. This can be either a full path or a relative path.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
The new path should already have been created in the local flash file system.
Authorization: admin
Examples
The following example shows the current directory (root directory) and then changes the directory to the log directory located under the root directory.
SCE>enable 10
Password:<cisco>
SCE>enable 10
SCE#pwd
system
SCE#cd log
SCE#pwd
system:log
SCE#
Related Commands
Command
|
Description
|
pwd
|
|
mkdir
|
|
clear arp-cache
Deletes all dynamic entries from the ARP cache. The Address Resolution Protocol (ARP) is a TCP/IP protocol that converts IP addresses to physical addresses. Dynamic entries are automatically added to and deleted from the cache during normal use. Entries that are not reused age and expire within a short period of time. Entries that are reused have a longer cache life.
clear arp-cache
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example clears the ARP cache.
SCE>enable 10
Password:<cisco>
SCE#clear arp-cache
SCE#
Related Commands
Command
|
Description
|
clear interface linecard mac-resolver arp-cache
|
|
clear interface linecard counters
Clears the linecard Interface counters.
clear interface linecard slot-number counters
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example clears the Line-Card 0 counters.
SCE>enable 10
Password:<cisco>
SCE#clear interface linecard 0 counters
SCE#
Related Commands
Command
|
Description
|
show interface linecard counters
|
|
clear interface linecard flow-filter
Clears all flow filter rules for the specified partition.
clear interface linecard slot-number flow-filter partition name name
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
name
|
Name of the partition for which to clear the flow filter rules
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example shows how to use this command.
SCE>enable 15
Password:<cisco>
SCE#>clear interface linecard 0 flow-filter partition name partition_1
SCE#>
Related Commands
Command
|
Description
|
show interface linecard flow-filter
|
|
flow-filter
|
|
clear interface linecard mac-resolver arp-cache
Clears all the MAC addresses in the MAC resolver database.
clear interface linecard slot-number mac-resolver arp-cache
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example shows how to use this command.
SCE>enable 10
Password:<cisco>
SCE#clear interface linecard 0 mac-resolver arp-cache
SCE#
Related Commands
Command
|
Description
|
clear arp-cache
|
|
mac-resolver arp
|
|
show interface linecard mac-resolver arp
|
|
clear interface linecard subscriber
Clears all anonymous subscribers in the system.
clear interface linecard slot-number subscriber anonymous all
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example clears all anonymous subscribers.
SCE>enable 10
Password:<cisco>
SCE#clear interface linecard 0 subscriber anonymous all
SCE#
Related Commands
Command
|
Description
|
no subscriber
|
|
no subscriber anonymous-group
|
|
show interface linecard subscriber anonymous
|
|
clear interface linecard subscriber db counters
Clears the "total" and "maximum" subscribers database counters.
clear interface linecard slot-number subscriber db counters
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example clears all anonymous subscribers.
SCE>enable 10
Password:<cisco>
SCE#clear interface linecard 0 subscriber db counters
SCE#
Related Commands
Command
|
Description
|
show interface linecard subscriber db counters
|
|
clear interface linecard traffic-counter
Clears the specified traffic counter.
clear interface linecard slot-number traffic-counter (name | all)
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
name
|
Name of the traffic counter to be cleared.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Use the all keyword to clear all traffic counters.
Authorization: admin
Examples
The following example clears the traffic counter name counter1.
SCE>enable 10
Password:<cisco>
SCE#clear interface linecard 0 traffic-counter name counter1
SCE#
Related Commands
Command
|
Description
|
traffic-counter
|
|
show interface linecard traffic-counter
|
|
clear logger
Clears SCE platform logger (user log files). This erases the information stored in the user log files.
clear logger [device user-file-log|line-attack-file-log ] [counters|nv-counters]
Syntax Description
device
|
The device name to be cleared, either user-file-log or line-attack-file-log
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
The user log files have a size limit, with new entries overwriting the oldest entries. Therefore, there is no need to regularly clear the log files. Use this operation when you are certain that the information contained in the logs is irrelevant and might be confusing (for example, when re-installing the system at a new site, whose administrators should not be confused with old information).
•
Use the counters keyword to clear the counters of the SCE platform logger (user log files). These counters keep track of the number of info, warning, error and fatal messages.
•
Use the nv-counters keyword to clear the non-volatile counters for the entire log or only the specified SCE platform. These counters are not cleared during bootup, and must be cleared explicitly by using this command.
Authorization: admin
Examples
EXAMPLE 1:
The following example clears the SCE platform user log file.
SCE>enable 10
Password:<cisco>
SCE#clear logger device User-File-Log
Are you sure?Y
SCE#
EXAMPLE 2:
The following example clears the SCE platform user log file counters.
SCE>enable 10
Password:<cisco>
SCE#clear logger device User-File-Log counters
Are you sure?Y
SCE#
EXAMPLE 3:
The following example clears the user log file non-volatile counters.
SCE>enable 10
Password:<cisco>
SCE#clear logger device user-file-log nv-counters
Are you sure?Y
SCE#
Related Commands
Command
|
Description
|
show logger device
|
|
show log
|
|
clear management-agent notifications counters
Clears the counters for the number of notifications sent to the management agent
clear management-agent notifications counters
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example clears the management agent notifications counters.
SCE>enable 10
Password:<cisco>
SCE#clear management-agent notifications counters
SCE#
Related Commands
clear rdr-formatter
Clears the RDR formatter counters and statistics.
clear rdr-formatter
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example clears the RDR-formatter counters.
SCE>enable 10
Password:<cisco>
SCE#clear rdr-formatter
SCE#
Related Commands
Command
|
Description
|
show rdr-formatter counters
|
|
clear scmp name counters
Clears the counters for the specified SCMP peer device.
clear scmp name name counters
Syntax Description
name
|
Name of the SCMP peer device.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example clears the counters for the SCMP peer device named device_1.
SCE>enable 10
Password:<cisco>
SCE#clear scmp name device_1 counters
SCE#
Related Commands
Command
|
Description
|
show scmp
|
|
clock read-calendar
Synchronizes clocks by setting the system clock from the calendar.
clock read-calendar
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example updates the system clock from the calendar.
SCE>enable 10
Password:<cisco>
SCE#clock read-calendar
SCE#
Related Commands
Command
|
Description
|
calendar set
|
|
clock update-calendar
|
|
show calendar
|
|
clock set
Manually sets the system clock.
clock set hh:mm:ss day month year
Syntax Description
hh:mm:ss
|
Current local time in hours in 24-hour format, minutes and seconds (HH:MM:SS).
|
day
|
Current day (date) in the month.
|
month
|
Current month (by three-letter abbreviated name).
|
year
|
Current year using a 4-digit number
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Always coordinate between the calendar and clock by using the clock update-calendar command after setting the clock.
Authorization: admin
Examples
The following example sets the clock to 20 minutes past 10 PM, January 13, 2006.
SCE>enable 10
Password:<cisco>
SCE#clock set 22:20:00 13 jan 2006
SCE#clock update-calendar
SCE#show clock
22:21:10 UTC THU January 13 2006
SCE#show calendar
22:21:18 UTC THU January 13 2006
SCE#
Related Commands
Command
|
Description
|
clock update-calendar
|
|
show calendar
|
|
show clock
|
|
clock summertime
Configures the SCE platform to automatically switch to daylight savings time on a specified date, and also to switch back to standard time. In addition, the time zone code can be configured to vary with daylight savings time if required. (For instance, in the eastern United States, standard time is designated EST, and daylight savings time is designated EDT). Use theno form of this command to cancel the daylight savings time transitions configuration.
clock summertime
Syntax Description
zone
|
The code for the time zone for daylight savings.
|
week1/week2
|
The week of the month on which daylight savings begins (week1) and ends (week2). A day of the week, such as Monday, must also be specified. The week/day of the week is defined for a recurring configuration only.
Default: Not used
|
day1/day2
|
The day of the week on which daylight savings begins (day1) and ends (day2).
For recurrent configuration: day is a day of the week, such as Sunday.
Use the keywords first/last to specify the occurrence of a day of the week in a specified month. For example: last Sunday March.
For non-recurrent configuration: day is a day in the month, such as 28.
Default: day1 = second Sunday, day2 = first Sunday
|
month1/month2
|
The month in which daylight savings begins (month1) and ends (ends2).
Default: month1 = March, month2 = November
|
year1/year2
|
The year in which daylight savings begins (month1) and ends (ends2).
For non -recurring configuration only.
Default = not used
|
time1/time2
|
The time of day (24-hour clock) at which daylight savings begins (time1) and ends (time2).
Required for all configurations. Default: time1/time2 = 2:00
|
offset
|
The difference in minutes between standard time and daylight savings time.
Default = 60
|
Defaults
recurring, offset = 60 minutes
By default, the following recurrent time changes are configured:
•
Daylight savings time begins: 2:00 (AM) on the second Sunday of March.
•
Daylight savings time ends: 2:00 (AM) on the first Sunday of November.
Command Modes
Global Configuration
Usage Guidelines
The format of the command varies somewhat, depending on how the dates for the beginning and end of daylight savings time are determined for the particular location:
•
recurring: If daylight savings time always begins and ends on the same day every year, (as in the United States):
–
Use the clock summer-time recurring command.
–
The year parameter is not used.
•
not recurring: If the start and end of daylight savings time is different every year, (as in Israel):
–
Use the clock summer-time command.
–
The year parameter must be specified.
General guidelines for configuring daylight savings time transitions:
•
Specify the time zone code for daylight savings time.
•
recurring: specify a day of the month (week#|first|last/day of the week/month).
•
not recurring: specify a date (month/day of the month/year).
•
Define two days:
–
Day1 = beginning of daylight savings time.
–
Day2 = end of daylight savings time.
In the Southern hemisphere, month2 must be before month1, as daylight savings time begins in the fall and ends in the spring.
•
Specify the exact time that the transition should occur (24 hour clock).
–
Time of transition into daylight savings time: according to local standard time.
–
Time of transition out of daylight savings time: according to local daylight savings time.
For the clock summer-time recurring command, the default values are the United States transition rules:
•
Daylight savings time begins: 2:00 (AM) on the second Sunday of March.
•
Daylight savings time ends: 2:00 (AM) on the first Sunday of November.
Use the recurring keyword if daylight savings time always begins and ends on the same day every year.
Use the first/last keywords to specify the occurrence of a day of the week in a specified month: For example: last Sunday March.
Use a specific date including the year for a not recurring configuration. For example: March 29, 2004.
Use week/day of the week/month (no year) for a recurring configuration:
•
Use first/last occurrence of a day of the week in a specified month. For example: last, Sunday, March (the last Sunday in March).
•
Use the day of the week in a specific week in a specified month. For example: 4,Sunday, March (the fourth Sunday in March). This would be different from the last Sunday of the month whenever there were five Sundays in the month.
Authorization: admin
Examples
The following examples illustrate the use of this command.
EXAMPLE 1
The following example shows how to configure recurring daylight savings time for a time zone designated "DST" as follows:
•
Daylight savings time begins: 0:00 on the last Sunday of March.
•
Daylight savings time ends: 23:59 on the Saturday of fourth week of November.
•
Offset = 1 hour (default)
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#clock summer-time DST
recurring last Sunday March 00:00 4 Saturday November 23:59
SCE(config)#
EXAMPLE 2
The following example shows how to configure non-recurring daylight savings time for a time zone designated "DST" as follows:
•
Daylight savings time begins: 0:00 on April 16, 2007.
•
Daylight savings time ends: 23:59 October 23, 2007.
•
Offset = 1 hour (default)
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#clock summer-time DST April 16 2005 00:00 October 23 2005 23:59
SCE(config)#
EXAMPLE 3
The following example shows how to cancel the daylight savings configuration.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no clock summer-time
SCE(config)#
Related Commands
Command
|
Description
|
clock set
|
|
calendar set
|
|
show calendar
|
|
show clock
|
|
clock timezone
Sets the time zone. Use the no version of this command to remove current time zone setting. The purpose of setting the time zone is so that the system can correctly interpret time stamps data coming from systems located in other time zones.
clock timezone zone hours [minutes]
no clock timezone
Syntax Description
zone
|
The name of the time zone to be displayed.
|
hours
|
The hours offset from UTC. This must be an integer in the range -23 to 23.
|
minutes
|
The minutes offset from UTC. This must be an integer in the range of 0 to 59. Use this parameter to specify an additional offset in minutes when the offset is not measured in whole hours.
|
Defaults
UTC (hours = 0)
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example sets the time zone to Pacific Standard Time with an offset of 10 hours behind UTC.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#clock timezone PST -10
SCE(config)#
Related Commands
Command
|
Description
|
calendar set
|
|
clock set
|
|
show calendar
|
|
clock update-calendar
Synchronizes clocks by setting the calendar from the system clock.
clock update-calendar
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example updates the calendar according to the clock.
SCE>enable 10
Password:<cisco>
SCE#clock update-calendar
SCE#
Related Commands
Command
|
Description
|
clock set
|
|
calendar set
|
|
clock read-calendar
|
|
configure
Enables the user to move from Privileged Exec Mode to Configuration Mode.
configure
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
After the user enters the configure command, the system prompt changes from <host-name># to <host-name>(config)#, indicating that the system is in Global Configuration Mode. To leave Global Configuration Mode and return to the Privileged Exec Mode prompt, use the exit command.
Authorization: admin
Examples
The following example enters the Global Configuration Mode.
SCE>enable 10
Password:<cisco>
SCE#configure
SCE#(config) #
Related Commands
connection-mode
Sets the connection mode parameters.
connection-mode connection-mode physically-connected-links physically-connected-links
priority priority on-failure on-failure
Syntax Description
connection-mode
|
• inline : single SCE platform inline
• receive-only : single SCE platform receive-only
• inline-cascade : two SCE platforms inline
• receive-only-cascade : two SCE platforms receive-only
|
physically-connected-links
|
The number of the link connected to the SCE platform. (two SCE platform topology only)
• link 0
• link 1
|
priority
|
Defines which is the primary SCE platform.(two SCE platform topologies only).
• primary
• secondary
|
on-failure
|
Determines system behavior on failure of the SCE platform. (inline topologies only)
• bypass
• cutoff
• external-bypass
|
Defaults
connection mode = inline
physically-connected-links =link 0
priority = primary
on-failure:
–
inline mode: external-bypass
–
inline-cascade mode: bypass
Command Modes
Linecard Interface Configuration
Usage Guidelines
This command can only be used if the line card is in either no-application or shutdown mode.
Authorization: admin
Examples
The following example shows how to configure the primary SCE 8000 platform in a two-SCE platform inline topology. Link "0" is connected to this SCE platform, and the behavior of the SCE platform if a failure occurs is "bypass".
SCE>enable 10
Password: <cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#connection-mode inline-cascade physically-connected-links link-0 priority
primary on-failure bypass
SCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard connection-mode
|
|
show interface linecard physically-connected-links
|
|
copy
Copies any file from a source directory to a destination directory on the local flash file system.
copy source-file destination-file
Syntax Description
source-file
|
The name of the original file.
|
destination-file
|
The name of the new destination file.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Both file names should be in 8.3 format, that is, there are a maximum of 8 characters before the period and three characters following it.
Authorization: admin
Examples
The following example copies the local analysis.sli file located in the root directory to the applications directory.
SCE>enable 10
Password:<cisco>
SCE#copy analysis.sli applications/analysis.sli
SCE#
Related Commands
Command
|
Description
|
copy ftp://
|
|
copy-passive
|
|
copy ftp://
Uploads or downloads a file system using FTP.
copy ftp://username[:password]@server-address[:port]/path/source-file destination-file
copy source-file ftp://username[:password]@server-address[:port]/path/destination-file
Syntax Description
username
|
The username known by the FTP server.
|
password
|
The password of the given username.
|
server-address
|
The dotted decimal IP address of the FTP server.
|
port
|
Optional port number on the FTP server.
|
source-file
|
The name of the source file.
When downloading a file, this must be an FTP location.
|
destination-file
|
The name of the destination file.
When uploading a file, this must be an FTP location.
When downloading a file to the local flash file system, this filename should be in 8.3 format.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Use the following syntax for remote upload/download using FTP:
ftp://username[:password]@server-address[:port]/path/file
You can configure keyword shortcuts for the copy command using the following commands:
•
ip ftp password to configure a password shortcut.
•
ip ftp username to configure a username shortcut.
Authorization: admin
Examples
The following example downloads the ftp.sli file from the host 10.10.10.10 with user name "user" and password "a1234".
SCE>enable 10
Password:<cisco>
SCE#copy ftp://user:a1234@10.10.10.10/p:/applications/ftp.sli appl/analysis.sli
SCE#
Related Commands
Command
|
Description
|
copy-passive
|
|
ip ftp password
|
|
ip ftp username
|
|
copy-passive
Uploads or downloads a file using passive FTP.
copy-passive source-file ftp://username[:password]@server-address[:port]/path/destination-file
[overwrite ]
copy-passive ftp://username[:password]@server-address[:port]/path/source-fil destination-file
Syntax Description
source-file
|
The name of the source file. When downloading a file, this must be an FTP location.
|
username
|
The username known by the FTP server.
|
password
|
The password of the given username.
|
server-address
|
The password of the given username.
|
port
|
Optional port number on the FTP server.
|
destination-file
|
The name of the file. When uploading a file, this must be an FTP location.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Use the following format for remote upload/download using FTP: ftp://username[:password]@serveraddress[:port]/path/file
Use the overwrite keyword to permit the command to overwrite an existing file.
You can configure keyword shortcuts for the copy command using the following commands:
•
ip ftp password to configure a password shortcut.
•
ip ftp username to configure a username shortcut.
Authorization: admin
Examples
The following example downloads the analysis.sli file from the host 10.10.10.10 with user name "user" and password "a1234".
SCE>enable 10
Password:<cisco>0
SCE#copy-passive ftp://user:a1234@10.10.10.10/p:/applications/analysis.sli
appl/analysis.sli
SCE#
Related Commands
Command
|
Description
|
copy ftp://
|
|
ip ftp password
|
|
ip ftp username
|
|
copy running-config startup-config
Builds a configuration file with general configuration commands called config.txt, which is used in successive boots.
copy running-config startup-config
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
This command must be entered to save newly configured parameters, so that they will be effective after a reboot. You can view the running configuration before saving it using the more running-config command.
The old configuration file is automatically saved in the /system/prevconf directory.
Authorization: admin
Examples
The following example saves the current configuration for successive boots.
SCE>enable 10
Password:<cisco>
SCE#copy running-config startup-config
Backing-up configuration file...
Writing configuration file...
SCE#
Related Commands
Command
|
Description
|
more
|
|
show running-config
|
|
copy source-file ftp://
Uploads a file to a remote station, using FTP.
copy source-file ftp://username[:password]@server-address[:port]/path/destination-file
Syntax Description
source-file
|
The name of the source file located in the local flash file system.
|
username
|
The username known by the FTP server.
|
password
|
The password of the given username.
|
server-address
|
The dotted decimal IP address.
|
port
|
Optional port number on the FTP server.
|
destination-file
|
The name of the file to be created in the FTP server.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Use the following format for remote upload/download using FTP: ftp://username[:password]@serveraddress[:port]/path/file
You can configure keyword shortcuts for the copy command using the following commands:
•
ip ftp password to configure a password shortcut.
•
ip ftp username to configure a username shortcut.
Authorization: admin
Examples
The following example uploads the analysis.sli file located on the local flash file system to the host 10.1.1.105.
SCE>enable 10
Password:<cisco>
SCE#copy /appl/analysis.sli ftp://myname:mypw@10.1.1.105/p:/applications/analysis.sli
SCE#
Related Commands
Command
|
Description
|
copy ftp://
|
|
copy source-file startup-config
Copies the specified source file to the startup-config file. Use this command to upload a backup configuration file created using the copy startup-config destination-file command. This is useful in a cascaded solution for copying the configuration from one SCE platform to the other.
copy source-file startup-config
Syntax Description
source-file
|
The name of the backup configuration file.
• ftp://user:pass@host/drive:/dir/bckupcfg.txt
• /system/preconf
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
The source file name should be in 8.3 format, that is, there are a maximum of 8 characters before the period and three characters following it.
Authorization: admin
Examples
The following example shows how to upload a backup configuration file.
SCE>enable 10
Password:<cisco>
SCE#copy ftp://user:pass@host/drive:/dir/bakupcfg.txt startup-config
SCE#
Related Commands
Command
|
Description
|
copy startup-config destination-file
|
|
copy startup-config destination-file
Copies the startup-config file to the specified destination file. Use this command to create a backup configuration file. This is useful in a cascaded solution for copying the configuration from one SCE platform to the other. The file created by this command can then be uploaded to the second SCE platform using the copy source-file startup-config command.
copy startup-config destination-file
Syntax Description
destination-file
|
The name of the file to which the configuration is copied.
• ftp://user:pass@host/drive:/dir/bckupcfg.txt
• /system/prevconf
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
The destination file name should be in 8.3 format, that is, there are a maximum of 8 characters before the period and three characters following it.
Authorization: admin
Examples
The following example shows how to create a backup configuration file.
SCE>enable 10
Password:<cisco>
SCE#copy startup-config ftp://user:pass@host/drive:/dir/bckupcfg.txt
SCE#
Related Commands
Command
|
Description
|
copy source-file startup-config
|
|
default subscriber template all
Removes all user-defined subscriber templates from the system. The default template only remains.
default subscriber template all
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
Authorization: admin
Examples
The following example removes all user-defined subscriber templates.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)# default subscriber template all
SCE(config if)#
Related Commands
Command
|
Description
|
subscriber template import csv-file
|
|
show interface linecard subscriber templates
|
|
party template
|
|
delete
Deletes a file from the local flash file system. Use the recursive switch to delete a complete directory and its contents. When used with the recursive switch, the filename argument specifies a directory rather than a file.
delete file-name [/recursive]
Syntax Description
file-name
|
The name of the file or directory to be deleted.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following examples illustrate how to use this command:
EXAMPLE 1:
The following example deletes the oldlog.txt file.
SCE>enable 10
Password:<cisco>
SCE#delete oldlog.txt
SCE#
EXAMPLE 2:
The following example deletes the oldlogs directory.
SCE>enable 10
Password:<cisco>
SCE#delete oldlogs /recursive
3 files and 1 directories will be deleted.
Are you sure? y
3 files and 1 directories have been deleted.
SCE#
Related Commands
Command
|
Description
|
dir
|
|
rmdir
|
|
dir
Displays the files in the current directory.
dir [applications] [-r]
Syntax Description
applications
|
Filters the list of files to display only the application files in the current directory.
|
-r
|
Includes all files in the subdirectories of the current directory as well as the files in the current directory.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example displays the files in the current directory (root).
SCE>enable 10
Password:<cisco>
SCE#dir
File list for /system/
512TUE JAN 01 00:00:00 1980LOGDBG DIR
512TUE JAN 01 00:00:00 1980LOG DIR
7653 TUE JAN 01 00:00:00 1980FTP.SLI
29 TUE JAN 01 00:00:00 1980SCRIPT.TXT
512 TUE JAN 01 00:00:00 1980SYSTEM DIR
SCE#
Related Commands
Command
|
Description
|
pwd
|
|
cd
|
|
disable
Moves the user from a higher level of authorization to a lower user level.
disable [level ]
Syntax Description
level
|
User authorization level (0, 5, 10, 15) as specified in CLI Authorization Levels.
|
Defaults
This command has no default settings.
Command Modes
Privileged Exec and Viewer
Usage Guidelines
Use this command with the level option to lower the user privilege level, as illustrated in the following figure. If a level is not specified, it defaults to User mode.
Figure 2-1 Disable Command
Note that you must exit to the Privileged Exec command mode to use this command.
Authorization: user
Examples
The following example shows how to change from root to admin mode:
SCE>enable 15
Password:<cisco>
SCE#>disable 10
SCE#
Related Commands
Command
|
Description
|
enable
|
|
do
Use the do command to execute an EXEC mode command (such as a show command) or a privileged EXEC command (such as show running-config ) without exiting to the relevant command mode.
do command
Syntax Description
command
|
Command to be executed.
|
Defaults
This command has no default settings.
Command Modes
All configuration modes
Usage Guidelines
Use this command when in any configuration command mode (global configuration, linecard configuration, or any interface configuration) to execute a user exec or privileged exec command.
Enter the entire command with all parameters and keywords as you would if you were in the relevant command mode.
Authorization: admin
Examples
The following example assumes that the on-failure action of the SCE platform has been changed to 'bypass'. The connection mode configuration is then displayed to verify that the parameter was changed. The do command is used to avoid having to exit to the user exec mode.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#connection-mode on-failure bypass
SCE(config if)#do show interface linecard 0 connection-mode
slot 0 connection mode
Connection mode is inline
slot failure mode is bypass
Redundancy status is standalone
SCE(config if)#
Related Commands
duplex
Configures the duplex operation of the GigabitEthernet management interface.
duplex mode
no duplex
Syntax Description
mode
|
Set to the desired duplex mode:
• full : full duplex
• half : half duplex
• auto : auto-negotiation (do not force duplex on the link)
|
Defaults
mode = Auto
Command Modes
GigabitEthernet Interface Configuration
Usage Guidelines
Use this command to configure the duplex mode of the GigabitEthernet management interface.
•
interface designation =1/1
If the speed (see speed ) of the management interface is configured to auto, changing this configuration has no effect.
Authorization: admin
Examples
The following example configures the management port to auto mode.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface GigabitEthernet 1/1
SCE(config if)#duplex auto
SCE(config if)#
Related CommandsE
Command
|
Description
|
speed
|
|
show interface gigabitethernet
|
|
enable
Enables the user to access a higher authorization level.
enable [level ]
Syntax Description
Defaults
level = admin
Command Modes
User Exec
Usage Guidelines
Authorization levels are illustrated in the following figure.
Figure 2-2 Enable Command
If a level is not specified, the level defaults to admin authorization, level 10.
Note that you cannot use the enable command from the Privileged Exec or any of the configuration command modes.
Authorization: User
Examples
The following example accesses the administrator authorization level. Note that the prompt changes from SCE> to SCE#, indicating that the level is the administrator privilege level.
SCE>enable
Password:<cisco>
SCE#
Related Commands
Command
|
Description
|
disable
|
|
enable password
|
|
enable password
Configures a password for the specified authorization level, thus preventing unauthorized users from accessing the SCE platform. Use theno form of the command to disable the password for the specified authorization level.
enable password [level level ] [encryption-type ] password
no enable password [level level ]
Syntax Description
level
|
User authorization level (0, 5, 10, 15) as specified in "CLI Authorization Levels". If no level is specified, the default is Admin (10).
|
encryption-type
|
If you want to enter the encrypted version of the password, set the encryption type to 5, to specify the algorithm used to encrypt the password.
|
password
|
A regular or encrypted password set for the access level. If you specify encryption-type, you must supply an encrypted password.
|
Defaults
password = cisco
Command Modes
Global Configuration
Usage Guidelines
After the command is entered, any user executing the enable command must supply the specified password.
•
Passwords must be at least 4 and no more than 100 characters long.
•
Passwords can contain any printable characters.
•
Passwords must begin with a letter.
•
Passwords cannot contain spaces.
•
Passwords are case-sensitive.
Authorization: admin
Examples
The following example sets a level 10 password as a123*man.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#enable password level 10 a123*man
SCE(config)#
Related Commands
Command
|
Description
|
enable
|
|
service password-encryption
|
|
erase startup-config-all
Removes all current configuration by removing all configuration files.
erase startup-config-all
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
The following data is deleted by this command:
•
General configuration files
•
Application configuration files
•
Static party DB files
•
Management agent installed MBeans
After using this command, the SCE platform should be reloaded immediately to ensure that it returns to the 'factory default' state.
You can use the copy startup-config destination-file command to create a backup of the current configuration before it is deleted.
Authorization: admin
Examples
The following example shows how to erase the startup configuration.
SCE>enable 10
Password:<cisco>
SCE#erase startup-config-all
Related Commands
Command
|
Description
|
reload
|
|
copy startup-config destination-file
|
|
exit
Exits from the current mode to the next "lower" mode.
exit
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
All
Usage Guidelines
Use this command each time you want to exit a mode, as illustrated in the following figure. The system prompt changes to reflect the lower-level mode.
Figure 2-3 Exit Command
Authorization: admin
Examples
The following example exits from the Linecard Interface Configuration Mode to Global Configuration Mode and then to Privileged Exec and Viewer Modes.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#exit
SCE(config)#exit
SCE#
Related Commands
Command
|
Description
|
configure
|
|
interface gigabitethernet
|
|
interface linecard
|
|
interface tengigabitethernet
|
|
line vty
|
|
external-bypass
Manually activates the external bypass modules.
Use the no form of the command to deactivate the external bypass modules.
Use the default form of the command to return the external bypass module to the default state (deactivated).
external-bypass
no external-bypass
default external-bypass
Syntax Description
This command has no arguments or keywords.
Defaults
By default the external bypass module is deactivated.
Command Modes
Interface Linecard Configuration
Usage Guidelines
Authorization: admin
Examples
The following example illustrates how to use this command.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#external-bypass
SSCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard external-bypass
|
|
failure-recovery operation-mode
Specifies the operation mode to be applied after boot resulting from failure. When using the default switch, you do not have to specify the mode.
failure-recovery operation-mode mode
default failure-recovery operation-mode
Syntax Description
mode
|
operational or non-operational. Indicates whether or not the system will boot as operational following a failure.
|
Defaults
mode = operational
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example sets the system to boot as operational after a failure
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#failure-recovery operation-mode operational
SCE(config)#
Related Commands
Command
|
Description
|
show failure-recovery operation-mode
|
|
flow-capture
Executes flow capture operations.
flow-capture (start format cap file-destination | stop)
Syntax Description
file-destination
|
Destination (FTP site path) where the cap file should be created in the format: ftp://<username>:<password>@<ip_address>/<path>/<filename>
|
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
The flow capture is a useful debugging capability that captures packets from the traffic stream in real time and stores them for later analysis using a standard cap format. The classification of the traffic portion to be captured is based on L4 attributes. The captured information is sent to a specified FTP destination. The FTP transaction is done online on SCE2000 platform, or immediately after the capture process concluded on SCE8000 platform.
The following operations are available:
•
start - start recording
•
stop - stop recording
Note that traffic can be captured only when an application is loaded.
To perform a flow capture, complete the following steps:
1.
(Optional) Configure limits to the flow capture operation using the flow-capture controllers command, to prevent a negative impact on traffic processing.
You may skip this step and use the default controller values.
2.
Configure an appropriate recording rule using the traffic-rule command. Assign the flow-capture action to the rule (see traffic-rule).
You must use the traffic-rule command to define the recording rule. You cannot use the flow-filter command.
3.
Start the actual capture. The capture will not start unless a valid recording rule has been defined.
Use the flow-capture start command.
4.
(Optional) Stop the capture.
Use the flow-capture stop command.
If not stopped by the operator, the flow capture will stop when the maximum duration or capacity has been reached
At any point, you can use the show interface linecard flow-capture command to display the flow capture status, including whether flow capture is currently recording or is stopped, the capacity already used and the number of packets recorded.
Authorization: admin
Examples
The following examples show how to use this command.
Example 1
The following example shows how to perform all the steps in a flow capture:
1.
Define the limits. (flow-capture controllers max-l4-payload-length and flow-capture controllers time)
2.
Define the recording traffic rule. (traffic-rule with action flow-capture option)
3.
Start the capture. (flow-capture start)
(show command shows that recording is in progress.)
4.
Stop the capture. (flow-capture stop)
SCE>enable 10
Password:<cisco>
SCE#>configure
SCE(config)#interface linecard 0
SCE(config if)#flow-capture controllers max-l4-payload-length 200
SCE(config if)#flow-capture controllers time 45
SCE(config if)#traffic-rule name FlowCaptureRule IP-addresses subscriber-side all
network-side all protocol 250 direction both traffic-counter counter2 action flow-capture
SCE(config if)# flow-capture start format cap
ftp://myUser:myPassword@10.10.10.80/./myCap.cap
SCE(config if)#do show interface linecard 0 flow-capture
Flow Capture Status:
Flow capture status: RECORDING
Target file size (bytes): 219616
Max L4 payload length (bytes): 200
Number of recorded packets: 830
Number of lost packets: 0
SCE(config if)#do flow-capture stop
SCE(config if)#do show interface linecard 0 flow-capture
Flow capture status: NOT RECORDING
Last stop cause: User Request
Target file size (bytes): 197256
Max L4 payload length (bytes): 200
Number of recorded packets: 713
Number of lost packets: 0
Example 2
The following example is identical to the previous one, except that instead of using the stop command, the capturing process continues until the defined time limit is reached.
1.
Define the limits. (flow-capture controllers max-l4-payload-length and flow-capture controllers time)
2.
Define the recording traffic rule. (traffic-rule with action flow-capture option)
3.
Start the capture. (flow-capture start)
(show command shows that recording is in progress.)
4.
Capture concludes automatically after 45 seconds.
SCE>enable 10
Password:<cisco>
SCE#>configure
SCE(config)#interface linecard 0
SCE(config if)#flow-capture controllers max-l4-payload-length 200
SCE(config if)#flow-capture controllers time 45
SCE(config if)#traffic-rule name FlowCaptureRule IP-addresses subscriber-side all
network-side all protocol 250 direction both traffic-counter counter2 action flow-capture
SCE(config if)# flow-capture start format cap
ftp://myUser:myPassword@10.10.10.80/./myCap.cap
SCE(config if)#do show interface linecard 0 flow-capture
Flow Capture Status:
Flow capture status: RECORDING
Target file size (bytes): 219616
Max L4 payload length (bytes): 200
Number of recorded packets: 830
Number of lost packets: 0
SCE(config if)#do show interface linecard 0 flow-capture
Flow Capture Status:
Flow capture status: NOT RECORDING
Last stop cause: Time Limit
Target file size (bytes): 758172
Max L4 payload length (bytes): 200
Number of recorded packets: 2863
Number of lost packets: 0
Example 3
In this example instead of using the stop command, the capturing process continues until the defined file-size limit (128MB in SCE8000) is reached.
1.
Set the limits back to default (default flow-capture controllers max-l4-payload-length and default flow-capture controllers time)
2.
Define the recording traffic rule. (traffic-rule with action flow-capture option)
3.
Start the capture. (flow-capture start)
(show command shows that recording is in progress.)
4.
Capture concludes automatically when file size reaches the limit.
SCE>enable 10
Password:<cisco>
SCE#>configure
SCE(config)#interface linecard 0
SCE(config if)#default flow-capture controllers max-l4-payload-length
SCE(config if)#default flow-capture controllers time
SCE(config if)#traffic-rule name FlowCaptureRule IP-addresses subscriber-side all
network-side all protocol 250 direction both traffic-counter counter2 action flow-capture
SCE(config if)# flow-capture start format cap
ftp://myUser:myPassword@10.10.10.80/./myCap.cap
SCE(config if)#do show interface linecard 0 flow-capture
Flow Capture Status:
Flow capture status: RECORDING
Target file size (bytes): 219616
Max L4 payload length (bytes): 200
Number of recorded packets: 830
Number of lost packets: 0
SCE(config if)#do show interface linecard 0 flow-capture
Flow capture status: NOT RECORDING
Last stop cause: Cannot Write To File or Max Allowed File Size Exceeded
Target file size (bytes): 13417700
Max L4 payload length (bytes): Unlimited
Number of recorded packets: 2216548
Number of lost packets: 0
Related Commands
Command
|
Description
|
flow-capture controllers
|
|
traffic-rule
|
|
show interface linecard flow-capture
|
|
flow-capture controllers
Configures limitations on the flow capture feature. Use the default form of the command to reset all options to the default values.
flow-capture controllers time (duration | unlimited)
flow-capture controllers max-l4-payload-length (length | unlimited)
default flow-capture controllers (time | max-l4-payload-length)
Syntax Description
duration
|
Maximum duration for the flow capture recording time in seconds.
To specify unlimited duration, use the unlimited keyword.
|
length
|
To specify unlimited payload bytes per packet, use the unlimited keyword.
|
Defaults
duration = 3600 seconds
length = unlimited
Command Modes
Interface Linecard Configuration
Usage Guidelines
The flow capture is a useful debugging capability that captures packets from the traffic stream in real time and stores them for later analysis. The classification of the traffic portion to be captured is based on L4 attributes.
The portion of traffic that is captured does not receive service (is not processed by the application). Therefore it is important to control the capturing scenario so that service is not negatively affected. This is done by limiting certain aspects of the flow capture.
The following options are available:
•
time (flow capture recording time) — The duration of the flow capture may be limited to the specified time limit, or it may be unlimited, so that the flow capture is stopped only by executing the explicit stop command, or when maximum file size is reached (128MB in SCE8000 platform).
•
max-l4-payload-length (payload size)— The maximum number of L4 bytes captured from each packet may be specified. This parameter relates to each packet in the traffic stream rather than overall flow capture capacity. Using this parameter, the flow-capture throughput (in terms of captured packets) can be increased.
Authorization: admin
Examples
The following example shows how to configure the limitations to the flow capture.
SCE>enable 10
Password:<cisco>
SCE#>configure
SCE(config)#interface linecard 0
SCE(config if)#flow-capture controllers time 120
SCE(config if)#flow-capture controllers max-l4-payload-length 200
SCE(config if)#
Related Commands
Command
|
Description
|
traffic-rule
|
|
flow-capture
|
|
show interface linecard flow-capture
|
|
force failure-condition
Forces a virtual failure condition, and exits from the failure condition, when performing an application upgrade.
force failure-condition
no force failure-condition
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
When upgrading the application in a cascaded system, use this command to force failure in the active SCE8000 platform (see 'System Upgrades' in the Chapter "Redundancy and Fail-Over" in the Cisco SCE8000 Software Configuration Guide ).
Authorization: admin
Examples
The following example forces a virtual failure condition.
At the displayed 'n', type 'Y' and press Enter to confirm the forced failure.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#force failure-condition
Forcing failure will cause a failover - do you want to continue? n
SCE(config if)#
Related Commands
Command
|
Description
|
pqi upgrade file
|
|
help
Displays information relating to all available CLI commands.
help bindings|tree
Syntax Description
This command has no arguments.
Defaults
This command has no default settings.
Command Modes
Exec
Usage Guidelines
Use the bindings keyword to print a list of keyboard bindings (shortcut commands).
Use the tree keyword to display the entire tree of all available CLI commands.
Authorization: User
Examples
The following example shows the partial output of the help bindings command.
SCE>help bindings
Line Cursor Movements
---------------------
Ctrl-F /->Moves cursor one character to the right.
Ctrl-B /<-Moves cursor one character to the left.
Esc-FMoves cursor one word to the right.
Esc-BMoves cursor one word to the left.
Ctrl-AMoves cursor to the start of the line.
Ctrl-EMoves cursor to the end of the line.
Esc F Moves cursor forward one word.
Esc BMoves cursor backward one word.
Editing
-------
Ctrl-DDeletes the character where the cursor is located.
Esc-DDeletes from the cursor position to the end of the word.
BackspaceDeletes the character before the current location of the cursor.
Ctrl-H Deletes the character before the current location of the cursor.
Ctrl-KDeletes from the cursor position to the end of the line.
Ctrl-UDeletes all characters from the cursor to the beginning of the line.
Ctrl-XDeletes all characters from the cursor to the beginning of the line.
Ctrl-WDeletes the word to the left of the cursor.
Ctrl-YRecall the last item deleted.
Help and Operation Features
----------------------------
? Argument help.
<Tab>Toggles between possible endings for the typed prefix.
<Esc><Tab>Displays all the possible arguments backwards.
Ctrl-I <TAB>
SCE>
Related Commands
history
Enables the history feature, that is, a record of the last command lines that executed. Use the no form of this command to disable history.
history
no history
Syntax Description
This command has no arguments or keywords.
Defaults
History is enabled.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following examples illustrate how to use this command.
EXAMPLE 1
The following example enables the history feature.
SCE>enable 10
Password:<cisco>
SCE#history
SCE#
EXAMPLE 2
The following example disables the history feature.
SCE>enable 10
Password:<cisco>
SCE#no history
SCE#
Related Commands
Command
|
Description
|
history size
|
|
history size
Sets the number of command lines that the system records in the history.
history size size
no history size
Syntax Description
size
|
The number of command lines stored in the history of commands for quick recall.
|
Defaults
size = 10 lines
Command Modes
Privileged EXEC
Usage Guidelines
The size of the history buffer can be any number from 0-50. Use the no form of this command to restore the default size.
Authorization: admin
Examples
The following example sets the history buffer size to 50 command lines.
SCE>enable 10
Password:<cisco>
SCE#history size 50
SCE#
Related Commands
Command
|
Description
|
history
|
|
hostname
Modifies the name of the SCE platform. The host name is part of the displayed prompt.
hostname host-name
Syntax Description
host-name
|
The new host name. Maximum length is 20 characters.
|
Defaults
host-name = SCE
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example changes the host name to MyHost.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#>hostname MyHost
MyHost(config)#>
Related Commands
Command
|
Description
|
show hostname
|
|
interface gigabitethernet
Enters GigabitEthernet Interface Configuration mode to configure the Gigabit Ethernet management interface in slot #1.
interface gigabitethernet slot-number/interface-number
Syntax Description
slot-number
|
Enter a value of 1.
|
interface-number
|
Enter a value of 1.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Use this command to configure the management port.
To return to the Global Configuration Mode, use the exit command.
The system prompt changes to reflect the GigabitEthernet Interface Configuration mode.
Authorization: admin
Examples
The following example enters into GigabitEthernet Configure Interface Mode to configure the managment port.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface gigabitethernet 1/1
SCE(config if)#
Related Commands
Command
|
Description
|
exit
|
|
show interface gigabitethernet
|
|
interface linecard
Enters Linecard Interface Configuration Mode.
interface linecard slot-number
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
The system prompt is changed to reflect the Line Card Configuration mode. To return to the Global Configuration Mode, use the exit command.
Authorization: admin
Examples
The following example enters LineCard Interface Configuration Mode.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#
Related Commands
ip access-class
Specifies which access control list (ACL) controls global access to the SCE platform. Use the no form of the command to permit global access to the SCE platform from any IP address.
ip access-classnumber
no ip access-class
Syntax Description
number
|
The number of the access list (1-99) to use to allow global access to the SCE platform.
|
Defaults
none (all IP addresses can access the system)
Command Modes
Global Configuration
Usage Guidelines
The ACL specified in this command contains the definitions for all IP addresses with permission to access the SCE platform. IP addresses not permitted in this access list cannot access or detect the SCE platform; even a ping command will receive no response if it is not from a permitted IP address.
Authorization: admin
Examples
The following example sets access list 1 as the global ACL.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip access-class 1
SCE(config)#
Related Commands
Command
|
Description
|
access-list
|
|
show access-lists
|
|
ip address
Sets the IP address and subnet mask of the Management Interface.
ip address new-address subnet-mask
Syntax Description
new-address
|
The new IP address.
|
subnet-mask
|
The network mask for the associated IP network.
|
Defaults
This command has no default settings.
Command Modes
GigabitEthernet Interface Configuration
Usage Guidelines
Note
Changing the IP address of the management interface via telnet will result in loss of the telnet connection and inability to reconnect with the interface.
Note
After changing the IP address, you must reload the SCE platform (see reload ) so that the change will take effect properly in all internal and external components of the SCE platform.
If there is a routing table entry mapped to the old address, but not to the new address, the command may fail.
Authorization: admin
Examples
The following example sets the IP address of the SCE platform to 10.1.1.1 and the subnet mask to 255.255.0.0.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#gigabitethernet interface 1/1
SCE(config if)#ip address 10.1.1.1 255.255.0.0
SCE(config if)#
Related Commands
Command
|
Description
|
gigabitethernet interface
|
|
ip advertising
Enables IP advertising. If either the destination or interval is not configured, the default values are assumed.
Use the no version of the command to disable IP advertising.
Use the default version of the command to restore IP advertising destination or interval to the default values.
ip advertising [(destination destination ) | (interval interval )]
no ip advertising
default ip advertising [destination | interval]
Syntax Description
destination
|
The IP address of the destination for the ping requests
|
interval
|
The frequency of the ping requests in seconds
|
Defaults
By default, IP advertising is disabled
destination = 127.0.0.1
interval = 300 seconds
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following examples illustrate the use of this command.
EXAMPLE 1:
The following example enables IP advertising, specifying 10.1.1.1 as the destination and an interval of 240 seconds.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip advertising destination 10.1.1.1
SCE(config)#ip advertising interval 240
SCE(config)#
EXAMPLE 2:
The following example restores the IP advertising destination to the default value.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#default ip advertising destination
SCE(config)#
Related Commands
Command
|
Description
|
show ip advertising
|
|
ip default-gateway
Configures the default gateway for the SCE platform. Use theno form of this command to remove the SCE platform default gateway configuration
ip default-gateway x.x.x.x
no ip default-gateway
Syntax Description
x.x.x.x
|
The IP address of the default gateway for the SCE platform.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example sets the default gateway IP of the SCE platform to 10.1.1.1.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip default-gateway 10.1.1.1
SCE(config)#
Related Commands
Command
|
Description
|
show ip default-gateway
|
|
ip domain-lookup
Enables or disables the domain name lookups. Use theno form of the command to disable the domain name lookup.
ip domain-lookup
no ip domain-lookup
Syntax Description
This command has no arguments or keywords.
Defaults
By default, domain name lookup is enabled.
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following examples illustrate how to use this command.
EXAMPLE 1:
The following example enables the domain lookup.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip domain-lookup SCE(config)#
EXAMPLE 2:
The following example disables the domain lookup
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no ip domain-lookup
SCE(config)#
Related Commands
Command
|
Description
|
ip domain-name
|
|
ip name-server
|
|
show hosts
|
|
ip domain-name
Defines a default domain name. Use the no parameter of this command to remove the current default domain name. When using the no parameter, you do not have to specify the domain name.
ip domain-name domain-name
no ip domain-name
Syntax Description
domain-name
|
The default domain name used to complete host names that do not specify a domain. Do not include the initial period that separates an unqualified name from the domain name.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following examples illustrate the use of this command.
EXAMPLE 1:
The following example configures a domain name
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip domain-name cisco.com
SCE(config)#
EXAMPLE 2:
The following example removes the configured domain name.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no ip domain-name
SCE(config)#
Related Commands
Command
|
Description
|
ip domain-lookup
|
|
ip name-server
|
|
show hosts
|
|
ip ftp password
Specifies the password to be used for FTP connections for the current session. The system will use this password if no password is given in the copy FTP command.
ip ftp password password
Syntax Description
password
|
The password for FTP connections.
|
Defaults
Default password is admin
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example sets the password to be used in the FTP connection to mypw.
SCE>enable 10
Password:<cisco>
SCE#ip ftp password mypw
SCE#
Related Commands
Command
|
Description
|
copy ftp://
|
|
copy-passive
|
|
ip ftp username
|
|
ip ftp username
Configures the username for FTP connections for the current session. This username will be used if no username is given in the copy FTP command.
ip ftp username user-name
Syntax Description
user-name
|
The username for FTP connections.
|
Defaults
Default username is anonymous
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example sets myname as the username for FTP connections.
SCE>enable 10
Password:<cisco>
SCE#ip ftp username myname
SCE#
Related Commands
Command
|
Description
|
copy ftp://
|
|
copy-passive
|
|
ip ftp password
|
|
ip host
Adds a host name and address to the host table. Use the no form of the command to remove a host name and address from the host table.
ip host hostname ip-address
no ip host hostname [ip-address]
Syntax Description
hostname
|
The host name to be added or removed.
|
ip-address
|
The host IP address in x.x.x.x format.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example adds a host to the host table.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip host PC85 10.1.1.1
SCE(config)#
Related Commands
Command
|
Description
|
show hosts
|
|
ip name-server
Specifies the address of 1-3 servers to use for name and address resolution. The system maintains a list of up to 3 name servers. If the current list is not empty, this command adds the specified servers to the list. The no option of this command removes specified servers from the current list.
ip name-server server-address1 [server-address2] [server-address3]
no ip name-server
Syntax Description
server-address1
|
The IP address of the name server.
|
server-address2
|
The IP address of an additional name server.
|
server-address3
|
The IP address of an additional name server.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example adds the DNS 10.1.1.1 and 10.1.1.2 to the configured servers list.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip name-server 10.1.1.1 10.1.1.2
SCE(config)#
Related Commands
Command
|
Description
|
ip domain-lookup
|
|
show hosts
|
|
ip radius-client retry limit
Configures the parameters for retransmitting unacknowledged RADIUS client messages.
ip radius-client retry limit times [timeout timeout ]
Syntax Description
times
|
The maximum number of times the RADIUS client can try unsuccessfully to send a message.
|
timeout
|
Timeout interval for retransmitting a message, in seconds
|
Defaults
times = 3
timeout = 5 second
Command Modes
Global Configuration
Usage Guidelines
Due to the unreliable nature of UDP, the RADIUS client retransmits requests to the SCMP peer device if they were not acknowledged within the configured number of seconds. Messages that were not acknowledged can be retransmitted up to the configured maximum number of retries.
The optional timeout parameter limits the time interval for retransmitting a message.
Authorization: admin
Examples
The following example illustrates how to configure the retransmission parameters.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)# ip radius-client retry limit 5 timeout 5
SCE(config)#
Related Commands
Command
|
Description
|
scmp name
|
|
show ip radius-client
|
|
ip route
Adds an IP routing entry to the routing table. Use theno option to remove an IP routing entry from the routing table.
ip route ip-address mask [next-hop]
no ip route prefix mask [next-hop]
no ip route all
Syntax Description
ip-address
|
The IP address of the new entry.
|
mask
|
The relevant subnet mask.
|
next-hop
|
The next hop in the route.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
All addresses must be in dotted notation.
The next-hop must be within the Management Interface subnet.
Use the all keyword with the no form of the command to remove all IP routing entries from the routing table.
Authorization: admin
Examples
The following examples illustrate the use of this command:
EXAMPLE 1:
The following example sets the next-hop to 20.2.2.2 for IP addresses in the range 10.10.10.0 to 10.10.10.255.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip route 10.10.10.0 255.255.255.0 20.2.2.2
SCE(config)#
EXAMPLE 2:
The following example removes the entry added in the previous example.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no ip route 10.10.10.0 255.255.255.0 S
CE(config)#
Related Commands
Command
|
Description
|
show ip route
|
|
ip rpc-adapter
Enables the RPC adapter. Use the no option of this command to disable the RPC adapter.
ip rpc-adapter
no ip rpc-adapter
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following examples illustrate the use of this command.
EXAMPLE 1:
The following example enables the RPC adapter.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip rpc-adapter
SCE(config)#
EXAMPLE 2:
The following example disables the RPC adapter.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no ip rpc-adapter
SCE(config)#
Related Commands
Command
|
Description
|
ip rpc-adapter port
|
|
show ip rpc-adapter
|
|
ip rpc-adaptor security-level
|
|
ip rpc-adapter port
Defines the RPC adapter port. Use the default option to reset the RPC adapter port assignment to the default port of 14374.
ip rpc-adapter portport-number
default ip rpc-adapter port
Syntax Description
port-number
|
The number of the port assigned to the RPC adapter.
|
Defaults
port number = 14374
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following examples illustrate the use of this command:
EXAMPLE 1:
The following example shows how to configure the RPC interface, specifying 1444 as the RPC adapter port.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip rpc-adapter
SCE(config)#ip rpc-adapter port 1444
EXAMPLE 2:
The following example shows how reset the RPC adapter port.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#default ip rpc-adapter port
Related Commands
Command
|
Description
|
ip rpc-adapter
|
|
show ip rpc-adapter
|
|
ip rpc-adaptor security-level
Sets the PRPC server security level.
ip rpc-adaptor security-level {full|semi|none}
Syntax Description
Defaults
default = semi
Command Modes
Global Configuration
Usage Guidelines
Specify the desired PRPC server security level:
•
full : all PRPC connections require authentication
•
semi : PRPC connections that supply a user-name and password during connection establishment are authenticated. Connections that do not supply a user-name and password are accepted with no authentication
•
none : no authentication is performed
Authorization: admin
Examples
The following example illustrates how to set the PRPC server security level.
SCE>enable 10
Password:<cisco>
SCE#configure
SCE(config)#ip rpc-adaptor security-level full
SCE>
Related Commands
Command
|
Description
|
ip rpc-adapter
|
|
show ip rpc-adapter
|
|
ip ssh
Enables the SSH server. Use the no option to disable the SSH server.
ip ssh [SSHv1]
no ip ssh [SSHv1]
Syntax Description
This command has no arguments.
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
If the SSHv1 keyword is not specified, both SSHV1 and SSHv2 are enabled. If you wish to enable only SSHv2, use the no form of the command to disable SSHv1, as explained in Example 3. Use the ip ssh SSHv1 command to re-enable SSHv1.
When using an SSH server, you should also do the following:
•
Generate an SSH key set ( ip ssh key command). A set of keys must be generated at least once before enabling the SSH server
Authorization: admin
Examples
The following examples illustrate the use of this command:
EXAMPLE 1:
The following example enables the SSH server. Both SSHV1 and SSHv2 are enabled.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip ssh
SCE(config)#
EXAMPLE 2:
The following example disables the SSH server.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no ip ssh
SCE(config)#
EXAMPLE 3:
The following example shows how to disable SSHv1 so that only SSHv2 is enabled.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip ssh
SCE(config)#no ip ssh SSHv1
Related Commands
Command
|
Description
|
ip ssh access-class
|
|
ip ssh key
|
|
show ip ssh
|
|
ip ssh key
Generates or removes the SSH key set. A set of keys must be generated at least once before enabling the SSH server.
ip ssh key [generate|remove]
Syntax Description
generate
|
generates a new SSH key set and saves it to non-volatile memory. Key size is always 2048 bits.
|
remove
|
removes the existing key set.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Each SSH server should define a set of keys (DSA2, RSA2 and RSA1) to be used when communicating with various clients. The key sets are pairs of public and private keys. The server publishes the public key while keeping the private key in non-volatile memory, never transmitting it to SSH clients.
Note that the keys are kept on the /system/ file, which means that a person with knowledge of the `enable' password can access both the private and public keys. The SSH server implementation provides protection against eavesdroppers who can monitor the management communication channels of the SCE platform, but it does not provide protection against a user with knowledge of the `enable' password.
When using an SSH server, you should also do the following:
•
Enable the SSH server ( ip ssh command).
Authorization: admin
Examples
The following examples illustrate how to use this command.
EXAMPLE 1:
The following example generates a new SSH key set.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip ssh key generate
SCE(config)#
EXAMPLE 2:
The following example removes the SSH key set,
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#ip ssh key remove
SCE(config)#
Related Commands
Command
|
Description
|
ip ssh
|
|
ip ssh access-class
|
|
show ip ssh
|
|
ip-tunnel IPinIP skip
Enables the recognition of IPinIP tunnels and skipping into the internal IP packet. Use the no form of this command to disable IPinIP skip.
ip-tunnel IPinIP skip
no ip-tunnel IPinIP skip
Syntax Description
This command has no arguments or keywords.
Defaults
By default, IPinIP skip is disabled.
Command Modes
Interface Linecard Configuration
Usage Guidelines
•
IPinIP and other tunnels: IPinIP is supported simultaneously with plain IP traffic and any other tunneling protocol supported by the SCE platform.
•
Overlapping IP addresses: There is no support for overlapping IP addresses within different IPinIP tunnels.
•
IPinIP can only be enabled or disabled when there is no application loaded or the linecard is shut down.
•
DSCP marking: For IPinIP traffic, DSCP marking can be done on either the external or the internal IP header exclusively.
See the ip-tunnel IPinIP DSCP-marking-skip command.
Authorization: admin
Examples
The following example shows how to use this command.
Note that you must access the root level to shutdown the linecard, even though the IPinIP command is at the admin level.
SCE>enable 15
Password:<cisco>
SCE#> configure
SCE(config)#>interface linecard 0
SCE(config if)#>shutdown
SCE(config if)#>ip-tunnel IPinIP skip
SCE(config if)#>no shutdown
Related Commands
Command
|
Description
|
ip-tunnel IPinIP DSCP-marking-skip
|
|
show interface linecard ip-tunnel IPinIP
|
|
ip-tunnel IPinIP DSCP-marking-skip
Configures the SCE platform to perform DSCP marking on the internal IP header of IPinIP traffic.
Use the no form of the command to perform DSCP marking on the external IP header.
ip-tunnel IPinIP DSCP-marking-skip
no ip-tunnel IPinIP DSCP-marking-skip
Syntax Description
This command has no arguments or keywords.
Defaults
By default, DSCP marking of IPinIP traffic is done on the external IP header (no form of the command).
Command Modes
Interface Linecard Configuration
Usage Guidelines
DSCP marking modifies the DSCP bits of the IPv4 header. In IPinIP tunnels there are at least two IP headers. By default, DSCP marking is performed only on the external IP header. Use this command to mark the DSCP bits of the internal IP header.
This command takes effect only when IPinIP skip is enabled (see the ip-tunnel IPinIP skip command, above).
Note
DSCP marking should be enabled and configured through SCA BB console. Refer to the section "How to Manage DSCP ToS Marker Values" in the chapter "Using the Service Configuration Editor: Traffic Control" in the Cisco Service Control Application for Broadband User Guide for further information.
IPinIP DSCP marking can only be configured when there is no application loaded or the linecard is shut down.
Authorization: admin
Examples
The following example shows how to configure the SCE platform to perform DSCP marking on the internal IP header of an IPinIP flows.
Note that you must access the root level to shutdown the linecard, even though the DSCP marking command is at the admin level.
SCE>enable 15
Password:<cisco>
SCE#> configure
SCE(config)#>interface linecard 0
SCE(config if)#>shutdown
SCE(config if)#>ip-tunnel IPinIP DSCP-marking-skip
SCE(config if)#>no shutdown
ip-tunnel l2tp skip
Configures the recognition of L2TP tunnels and skipping into the internal IP packet. Use the no form of this command to disable tunnel recognition and classify traffic by the external IP address.
ip-tunnel L2TP skip
no ip-tunnel
Syntax Description
This command has no arguments or keywords.
Defaults
By default, IP tunnel recognition is disabled.
Command Modes
Linecard Interface Configuration
Usage Guidelines
L2TP is an IP-based tunneling protocol. Therefore, the system must be specifically configured to recognize the L2TP flows, given the UDP port used for L2TP. The SCE platform can then skip the external IP, UDP, and L2TP headers, reaching the internal IP, which is the actual subscriber traffic. If L2TP is not configured, the system treats the external IP header as the subscriber traffic, thus all the flows in the tunnel are seen as a single flow.
The IP tunnel mode is mutually exclusive with other VLAN-based classification.
Use the L2TP identify-by command to configure the port number that the LNS and LAC use for L2TP tunnels.
Authorization: admin
Examples
The following example enables recognition of L2TP tunnels.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#ip-tunnel L2TP skip
SCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard ip-tunnel
|
|
L2TP identify-by
|
|
VLAN
|
|
l2tp identify-by
Configures the port number that the LNS and LAC use for L2TP tunnels.
l2tp identify-by port-number port-number
l2tp identify-by default port
Syntax Description
port-number
|
The port number to be configured for L2TP tunnels.
|
Defaults
port-number = 1701
Command Modes
Linecard Interface Configuration
Usage Guidelines
Use the default port keyword to replace the user-configured port number with the default port.
Note that if external fragmentation exists in the L2TP environment, it is required to configure a quick-forwarding-ignore Traffic Rule (see the section "Configuring Traffic Rules and Counters" in the Cisco SCE Software Configuration Guide ) that bypasses all IP traffic targeted to either the LNS or LAC IP address. This will make sure that any packets not having the L2TP port indication (i.e. non-first fragments) will not require handling by the traffic processors.
In addition, in order to prevent reordering of L2TP tunneled fragments, it is advised to define a quick-forwarding traffic-rule for all the L2TP traffic. This can be done based on the IP ranges in use by the internal IPs in the tunnel (as allocated by the LNS), or simply for all of the traffic passing through the SCE platform.
Note that flow redirection and flow blocking cannot be performed on the quick-forwarded traffic.
Authorization: admin
Examples
The following example configures port# 1000 as the L2TP port.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#l2tp identify-by port-number 1000
SCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard l2tp
|
|
ip-tunnel
|
|
line vty
Enters Line Configuration Mode for Telnet lines, configuring all Telnet lines.
line vty start-number [end-number]
Syntax Description
start-number
|
A number in the range 0-4. The actual number supplied does not matter. All telnet lines will be configured by this command.
|
end-number
|
A number in the range 0-4. The actual number supplied does not matter. All telnet lines will be configured by this command.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
The system prompt changes to reflect the Line Configuration mode. To return to Global Configuration Mode, use the exit command.
Authorization: admin
Examples
The following example enters the Line Configuration Mode for all lines.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#line vty 0
SCE(config-line)#
Related Commands
Command
|
Description
|
show line vty
|
|
exit
|
|
link failure-reflection
Enables/disables the link failure reflection.
link failure-reflection [on-all-ports] [linecard-aware]
no link failure-reflection [linecard-aware]
Syntax Description
on-all-ports
|
Enables reflection of a link failure to all ports
|
linecard-aware
|
Prevents link failure reflection if the indications are that the failure is in the line card
|
Defaults
By default, link failure reflection is disabled
Command Modes
Linecard Interface Configuration
Usage Guidelines
Use the on-all-ports keyword to enable reflection of a link failure to all ports
Use the linecard-aware keyword when each link of the SCE8000 platform (Subscriber-side interface and the corresponding Network-side interface) is connected to a different linecard.
This mode reflects a failure of one port to the other three ports of the SCE8000, differently, depending on whether the failure appears to be in the SCE platform itself or not, as follows:
•
One interface of the SCE8000 is down, indicating a problem with the SCE platform: Link failure is reflected to the other three SCE platform ports.
•
Two reciprocal ports of the SCE8000 are down, indicating a problem in the linecard to which the SCE platform is connected and not the interface: No action is taken. This allows the second link in the SCE platform to continue functioning without interruption
Use the no form of this command to disable failure reflection. The on-all-ports keyword is not used in the no form of the command.
Use the no form of this command with the linecard-aware keyword to disable the linecard aware mode, without disabling link failure reflection itself.
Authorization: admin
Examples
The following example enables the reflection of a link failure to all ports:
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#link failure-reflection on-all-ports S
CE(config if)#
link mode
Configures the link mode. The link mode allows the user to force the specified behavior on the link. This may be useful during installation and for debugging the network.
link mode all-links mode
Syntax Description
mode
|
• Forwarding
• Bypass
• Cutoff
|
Defaults
Command Modes
Linecard Interface Configuration
Usage Guidelines
Always use the all-links keyword; the link mode cannot be set separately for the individual links.
Authorization: admin
Examples
The following example illustrates the use of this command:
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#link mode all-links bypass
Related Commands
Command
|
Description
|
show interface linecard link mode
|
|
logger add-user-message
Adds a message string to the user log files.
logger add-user-message message-text
Syntax Description
message-text
|
The message string you wish to add.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example adds "testing 123" as the message to the user log files:
SCE>enable 10
Password:<cisco>
SCE#logger add-user-message testing 123
SCE#
logger device
Disables or enables the specified logger device.
logger device {line-attack-file-log | statistics-file-log | user-file-log} status
Syntax Description
status
|
enabled or disabled, indicating whether to turn on or off logging.
|
Defaults
By default, the log devices are enabled.
Command Modes
Global Configuration
Usage Guidelines
Available logger devices are:
•
Line-Attack-File-Log
•
SCE-agent-Statistics-Log
•
User-File-Log
Authorization: admin
Examples
The following example disables the User-File-Log device.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#logger device user-file-log disabled
SCE(config)#
Related Commands
Command
|
Description
|
logger device user-file-log max-file-size
|
|
logger get user-log file-name
|
|
clear logger
|
|
logger device user-file-log max-file-size
Sets the maximum log file size.
logger device User-File-Log max-file-size size
Syntax Description
size
|
The maximum size for the user log (in bytes).
|
Defaults
size = 1,000,000 bytes
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example configures the maximum size of the User-File-Log device to 65000 bytes.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#logger device user-file-log max-file-size 65000
SCE(config)#
Related Commands
Command
|
Description
|
logger device
|
|
show logger device
|
|
logger get support-file
Generates a log file for technical support via FTP. Note that this operation may take some time.
logger get support-file filename
Syntax Description
filename
|
Name of the generated log file. The specified file must be located on an FTP site, not on the local file system.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example generates a technical support log file (via FTP) named support.zip.
SCE>enable 10
Password:<cisco>
SCE#logger get support-file ftp://user:1234@10.10.10.10/c:/support.zip
SCE#
Related Commands
logger get user-log file-name
Outputs the current user log to a target file. The output file name can be a local path, full path, or full FTP path file name.
logger get user-log file-name target-file
Syntax Description
target-file
|
The name of the output file to which the system will write the log file information.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example retrieves the current user log files.
SCE>enable 10
Password:<cisco>
SCE#logger get user-log file-name ftp://myname:mypw@10.1.1.205/d:/log.txt
SCE#
Related Commands
Command
|
Description
|
logger get support-file
|
|
logout
Logs out of the Command-Line Interface of the SCE platform.
logout
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Exec
Usage Guidelines
The system prompts for confirmation of the logout command with 'N'. Type 'Y' to confirm the logout.
Examples
The following example shows how the user logs out (and confirms the logout).
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#exit
SCE>logout
Are you sure? Y
Related Commands
mac-resolver arp
Adds a static IP entry to the MAC resolver database. Use theno form of the command to remove the static IP entry from the data base.
mac-resolver arpip_address [vlan vlan_tag] mac_address
no mac-resolver arp ip_address [vlan vlan_tag] mac_address
Syntax Description
ip address
|
IP address entry to be added to the database.
|
vlan tag
|
VLAN tag that identifies the VLAN that carries this IP address (if applicable).
|
mac address
|
MAC address assigned to the IP address, in xxxx.xxxx.xxxx format.
|
Defaults
This command has no default settings.
Command Modes
Interface Linecard Configuration
Usage Guidelines
When adding an entry, if a client has previously registered a dynamic entry with the same IP address and VLAN tag, the entry receives the MAC address specified in the CLI command, and the entry is changed to static.
When removing an entry, if an entry has been added both as a dynamic entry and a static entry, it exists in the database as a static entry only (as explained in the preceding paragraph). Removing the static configuration changes the entry from a static entry to a dynamic entry and deletes the corresponding user-configured MAC address.
Authorization: admin
Examples
The following example assigns the MAC address 1111.2222.3333 to the IP address 10.20.30.40.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#mac-resolver arp 10.20.30.40 1111.2222.3333
SCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard mac-resolver arp
|
|
management-agent sce-api ignore-cascade-violation
Configures the agent to ignore the errors issued when logon operations are performed on a standby SCE platform. Use the no form of this command to configure the agent to issue an error when a logon operation is performed on a standby SCE platform. Use thedefault form of this command to set the value to the default (the default behavior is to issue an error when a logon operation is performed on a standby SCE platform).
management-agent sce-api ignore-cascade-violation
no management-agent sce-api ignore-cascade-violation
default management-agent sce-api ignore-cascade-violation
Syntax Description
This command has no arguments or keywords.
Defaults
By default, an error is issued when a logon operation is performed on a standby SCE platform ( no form of the command).
Command Modes
Global Configuration
Usage Guidelines
Starting in release 3.1.0, the SCE platform issues an error message when a logon operation is performed on the standby SCE platform in a cascaded system. This behavior is not backward compatible for previous versions of the SCE Subscriber API.
Use this command with SCOS release 3.1.0 to provide backward-compatible behavior to previous releases in which such errors were not issued.
Authorization: admin
Examples
The following example illustrates how to use this command.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)# management-agent sce-api ignore-cascade-violation
SCE(config)#
Related Commands
management-agent sce-api logging
Enables the SCE subscriber API trouble-shooting logging, which is written to the user-log. Use the no form of this command to disable SCE subscriber API trouble-shooting logging.
management-agent sce-api logging
no management-agent sce-api logging
Syntax Description
This command has no arguments or keywords.
Defaults
By default, the SCE subscriber API trouble-shooting logging is disabled.
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example enables SCE subscriber API trouble-shooting logging.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)# management-agent sce-api logging
SCE(config)#
Related Commands
management-agent sce-api timeout
Defines the timeout interval for disconnection of an SCE subscriber API client, after which the resources allocated for this client would be released.
management-agent sce-api timeout timeout-interval
Syntax Description
timeout-interval
|
Default time in seconds that the client waits before timing out.
|
Defaults
Default = 300 seconds
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
This example shows how to configure a timeout interval of 10 seconds.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)# management-agent sce-api timeout 10
Related Commands
management-agent system
Specifies a new package file to install for the management agent. The SCE platform extracts the actual image file(s) from the specified package file only during the copy running-config startup-config command. When using the no version of this command, you do not have to specify the package-file-name.
management-agent system package-file-name
no management-agent system
Syntax Description
package-file-name
|
The name of a package file that contains the new management agent software. The filename should end with the.pkg extension.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Use this command to upgrade the SCE platform management agent. The package file is verified for the system and checked that it is not corrupted. The actual upgrade takes place only after executing the copy running-config startup-config command and rebooting the SCE platform.
Authorization: admin
Examples
The following example upgrades the system with the mng45.pkg package.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#management-agent system mng45.pkg
Verifying package file...
Package file verified OK.
SCE(config)#do copy running-config startup-config
Backing -up configuration file...
Writing configuration file...
Extracting new management agent...
Extracted OK.
Related Commands
Command
|
Description
|
copy running-config startup-config
|
|
mkdir
Creates a new directory.
mkdir directory-name
Syntax Description
directory-name
|
The name of the directory to be created.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example creates a new directory named mydir.
SCE>enable 10
Password:<cisco>
SCE#mkdir mydir
CE#
Related Commands
more
Displays the contents of a file.
more {file-name | running-config [all-data] | startup-config}
Syntax Description
file-name
|
The name of the file to be displayed.
|
all data
|
Displays defaults as well as non-default settings (running-config option only)
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
The running-config option displays the running configuration file. You can use the all data switch with this option to see sample usage for many CLI configuration commands.
The startup-config option displays the startup configuration file.
Authorization: admin
Examples
The following sample output displays the contents of the running configuration file.
SCE>enable 10
Password:<cisco>
SCE#more running-config
#This is a general configuration file (running-config).
#Created on 16:48:11 UTC WED June 13 2001
cli-type 1
#version 1
service logger
no service password-encryption
enable password level 10 0 "cisco"
enable password level 15 0 "cisco"
service RDR-formatter
no RDR-formatter destination all
RDR-formatter history-size 0
clock timezone UTC 0
ip domain-lookup
no ip domain-name
no ip name-server
service telnetd
FastEthernet 0/0
ip address 10.1.5.120 255.255.0.0
speed auto
duplex auto
exit
ip default-gateway 10.1.1.1
no ip route all
line vty 0 4
no access-class in
timeout 30
exit
SCE#
Related Commands
Command
|
Description
|
show running-config
|
|
show startup-config
|
|
more user-log
Displays the user log on the CLI console screen.
more user-log
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example displays the user log on the CLI console screen.
SCE>enable 10
Password:<cisco>
SCE#more user-log
<INFO>| 01/28/97 22:29:22 | CPU #000 | Logger: Task Initialized successfully
Related Commands
Command
|
Description
|
logger get user-log file-name
|
|
show log
|
|
mpls
Configures the MPLS environment. MPLS labels are supported up to a maximum of 15 labels per packet.
mpls traffic-engineering skip
mpls vpn skip
default mpls
Syntax Description
See "Usage Guidelines"
Defaults
By default, traffic-engineering skip is enabled.
Command Modes
Interface Linecard Configuration
Usage Guidelines
Use the traffic-engineering skip form of the command when all IP addresses are unique and MPLS labels are not mandatory (a non-MPLS/VPN environment). Any packets that are injected by the SCE into the MPLS labeled traffic (block or redirect) are sent with no MPLS labels. Use this mode when the MPLS labels in the traffic are only used for traffic engineering, such as QOS, and not for routing.
This is the default mode, and it should be changed only if MPLS is used for routing in the network and block or redirect is being employed. However, first verify that there are no private IP conflicts in the network.
Use the VPN skip form of the command when all IP addresses are unique, but MPLS labels are used, and the labels used for injection are the correct ones, as seen on the flow. This mode can be used when the MPLS labels are used for routing, or even VPNs (assuming there are no private IP addresses).
The VPN skip mode is an asymmetric layer 2 mode, and as with all asymmetric layer 2 modes, you should expect reduced performance and capacity, since the system must follow the flow and keep the layer 2 information.
Use the default keyword to set the MPLS configuration to the default value.
Authorization: admin
Examples
The following example illustrates the use of this command in a non-MPLS/VPN environment..
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#mpls traffic-engineering skip
SCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard mpls
|
|
no subscriber
Removes a specified subscriber from the system. Use theall option to remove all introduced subscribers.
no subscriber name subscriber-name
no subscriber scmp name scmp-name all
no subscriber sm all
no subscriber all
Syntax Description
subscriber-name
|
The specific subscriber name to be removed from the system.
|
scmp-name
|
Name of an SCMP peer device.
|
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
Use the scmp name all option to remove all subscribers managed by the specified SCMP peer device.
Use the sm all option to remove all subscribers managed by the SM.
Authorization: admin
Examples
The following example removes all subscribers.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)# no subscriber all SCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard subscriber
|
|
no subscriber mappings included-in
Use this command to remove all existing subscriber mappings from a specified IP range.
no subscriber mappings included-in ip-range IP-range
Syntax Description
IP-range
|
IP address and mask length defining the IP range
|
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
Use the IP-range parameter to remove all existing subscriber mappings from a specified IP range.
Authorization: admin
Examples
The following example removes any existing subscriber mappings from the specified IP range.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)# no subscriber mappings included-in IP-range 10.10.10.10/0
Related Commands
ping
Pings the given host to test for connectivity. The ping program sends a test message (packet) to an address and then awaits a reply. Ping output can help you evaluate path-to-host reliability, delays over the path, and whether the host can be reached or is functioning.
ping host
Syntax Description
host
|
The host name or IP address of a remote station to ping.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example pings the host 10.1.1.201.
SCE>enable 10
Password:<cisco>
SCE#ping 10.1.1.201
pinging 10.1.1.201...
PING 10.1.1.201: 56 data bytes
64 bytes from host (10.1.1.201): icmp_seq=0. time=0. ms
64 bytes from host (10.1.1.201): icmp_seq=1. time=0. ms
64 bytes from host (10.1.1.201): icmp_seq=2. time=0. ms
64 bytes from host (10.1.1.201): icmp_seq=3. time=0. ms
----10.1.1.201 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
SCE#
Related Commands
pqi install file
Installs the specified pqi file using the installation options specified (if any). This may take up to 5 minutes.
pqi install file filename [options options ]
Syntax Description
filename
|
The filename of the pqi application file to be installed.
|
options
|
The desired installation options. Use the show pqi file command to display the available installation options.
|
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
Always run the pqi uninstall file command before installing a new pqi file to prevent accumulation of old files on the disk.
Authorization: admin
Examples
The following example installs the Subscriber Manager anr10015.pqi file. No options are specified.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#pqi install file anr10015.pqi
SCE(config if)#
Related Commands
Command
|
Description
|
show pqi file
|
|
pqi uninstall file
|
|
pqi rollback file
Reverses an upgrade of the specified pqi file. This may take up to 5 minutes.
pqi rollback file filename
Syntax Description
filename
|
The filename of the pqi application file to be rolled-back. It must be the pqi file that was last upgraded.
|
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
Always specify the last pqi file that was upgraded. Use the show pqi last-installed command.
Authorization: admin
Examples
The following example reverses the upgrade for the Subscriber Manager using the anr100155.pqi file.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#pqi rollback file anr100155.pqi
SCE(config if)#
Related Commands
Command
|
Description
|
show pqi last-installed
|
|
pqi uninstall file
Uninstalls the specified pqi file. This may take up to 5 minutes.
pqi uninstall file filename
Syntax Description
filename
|
The filename of the pqi application file to be uninstalled. It must be the pqi file that was installed last.
|
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
Always specify the last pqi file that was installed. Use the show pqi last-installed command.
Always run the pqi uninstall command before installing a new pqi file to prevent accumulation of old files on the disk.
Authorization: admin
Examples
The following example uninstalls the Subscriber Manager anr10015.pqi file.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#pqi uninstall file anr10015.pqi
SCE(config if)#
Related Commands
Command
|
Description
|
show pqi last-installed
|
|
pqi install file
|
|
pqi upgrade file
Upgrades the application using the specifiedpqi file and the upgrade options specified (if any). This may take up to 5 minutes.
pqi upgrade file filename [options options ]
Syntax Description
filename
|
The filename of the pqi application file to be used for the upgrade.
|
options
|
The desired upgrade options. Use the show pqi file command to display the available options.
|
Defaults
This command has no default settings.
Command Modes
Linecard Interface Configuration
Usage Guidelines
A given pqi upgrade file is suitable for upgrading only from specific previously installed pqi files. The upgrade procedure checks that an upgrade is possible from the currently installed pqi file. The upgrade procedure will be stopped with an error message if the upgrade is not possible.
When upgrading the application in a cascaded system, use the force failure-condition command to force failure in the active SCE 2000 platform (see 'System Upgrades' in the Chapter "Redundancy and Fail-Over" in the Cisco Service Control Engine Software Configuration Guide ).
Authorization: admin
Examples
The following example upgrades the Subscriber Manager using the anr100155.pqi file. No options are specified.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#pqi upgrade file anr100155.pqi
SCE(config if)#
Related Commands
Command
|
Description
|
show pqi file
|
|
force failure-condition (SCE 2000 only)
|
|
pwd
Displays the current working directory.
pwd
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example shows the current working directory as system.
SCE>enable 10
Password:<cisco>
SCE#pwd
system:
SCE#
Related Commands
queue
Sets the queue shaping.
queue queue-number bandwidth bandwidth burst-size burstsize
Syntax Description
queue-number
|
Queue-number from 1-4, where 4 is the highest priority (fastest).
• 1=BE. BE is the best effort queue, that is the lowest priority.
• 2, 3=AF. The AF (Assured Forwarding) queues are middle-priority, with 3 being a higher priority queue, that is, packets from queue 3 are transferred faster than those in queue 2.
• 4=EF. EF is the Expedited Forwarding queue, that is the highest priority forwarding
|
bandwidth
|
Bandwidth measured in kbps. The maximum bandwidth is determined by the line rate.
0 disables packet transmission from the queue.
Bandwidth is set in resolutions of ~140Kbps, that is rounded to the nearest multiple of approximately 140 Kbps.
|
burstsize
|
Burst size in bytes, from 0-16000000.
|
Defaults
Bandwidth = 100000K (100 Mbps)
Burst size = 8000 (8K bytes)
Command Modes
TenGigabitEthernet Interface Configuration
Usage Guidelines
This command is valid for a specified TenGigabitEthernet line interface only. It must be executed explicitly for each interface.
Use the interface tengigabitethernet command to access the configuration mode for the desired interface.
Authorization: admin
Examples
The following example configures queue shaping for queue 1 for 10GBE interface in bay #3.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface TenGigabitEthernet 3/3/0
SCE(config if)#queue 1 bandwidth 20000 burstsize 1000
Related CommandsE
Command
|
Description
|
bandwidth
|
|
interface tengigabitethernet
|
|
rdr-formatter category number
Assigns a meaningful name to a category. This category name can then be used in any rdr-formatter command instead of the category number. Use the no option of this command to disassociate the name from the category. The name will then not be recognized by any CLI commands.
rdr-formatter category number [1-4] name category name
no rdr-formatter category number [1-4] name category name
Syntax Description
category name
|
The user-defined name to be assigned to the category.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example assigns the name "prepaid" to Category 1.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#rdr-formatter category number 1 name prepaid
SCE(config)#
Related Commands
Command
|
Description
|
show rdr-formatter
|
|
service rdr-formatter
|
|
rdr-formatter buffer-size
|
|
rdr-formatter destination
Configures an RDRV1 or Netflow destination. This is where the RDR formatter sends the records (RDRs or export packets) it produces. Use theno form of the command to remove the mappings of a destination to categories. When all categories for a destination are removed, the entire destination is removed.
rdr-formatter destinationip-address port port-number [category {name category-name }|
{number [1-4] }] [priority priority-value ] [category ...] protocol {RrdrV1 | NetflowV9}
[transport {udp | tcp}]
no rdr-formatter destination ip-address port port-number [category {name category-name }|
{number [1-4 ]}]
no rdr-formatter destination all
Syntax Description
ip-address
|
The destination IP address.
|
port-number
|
The destination port number.
|
category
|
(Optional) Use this parameter to assign a priority to a particular category for this destination.
|
category-name
|
(Optional) User-defined name that identifies the category
|
number
|
(Optional) Use this parameter to identify the category by number (1 to 4).
|
priority-value
|
(Optional) The priority of the destination. The priority value may be any number between 1 (lowest) to 100 (highest).
|
protocol
|
The protocol configured for this destination. Specify either of the following:
• RDRv1
• NetflowV9
|
transport
|
(Optional) The transport type configured for this destination. Specify either of the following:
• UDP when protocol = Netflow
• TCP when protocol = RDRv1.
|
Defaults
Default protocol = RDRv1
Command Modes
Global Configuration
Usage Guidelines
Up to eight destinations can be configured. Multiple destinations over the same category must have distinct priorities. In redundancy mode, the entry with the highest priority is used by the RDR formatter; in multicast mode or load-balancing mode priorities have no meaning.
In its simplest form, this command specifies only the IP address and port number of the destination and the protocol being used. In addition, a global priority may be assigned to the destination. Or a specific priority may be assigned to any or all of the four categories for the specified destination. If a global priority is not explicitly configured, the highest priority is assigned automatically.
Categories may be identified by either name or number.
A certain destination may be configured to one or more categories on the same time. A maximum of three destinations may be assigned to a specific category.
Note
RDRv1 may only be configured with transport type of TCP and NetflowV9 may only be configured with transport type of UDP.
PRIORITIES
Following are some guidelines for configuring priorities for the report destinations:
•
In redundancy mode, the entry with the highest priority is used by the RDR formatter, provided that a connection with this destination can be established
•
Priority configuration is not relevant in multicast mode, since all reports are sent to all destinations.
•
Priority configuration is not relevant in load-balancing mode, since all destinations are used for load balancing
•
For the first destination defined, if no priority is set, the highest priority is automatically assigned.
•
For all subsequently defined destinations, the priority must be explicitly defined, otherwise it will collide with the first destination priority.
•
It is also possible to assign a different priority to each category for each destination. If no category is specified, the same priority is assigned to all categories for that destination.
•
The same priority cannot be assigned to the same category for two different destinations.
Authorization: admin
Examples
The following examples illustrate the use of this command:
EXAMPLE 1:
The following example configures a Netflow destination with the default priority (highest) to be used by all categories.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#rdr-formatter destination 10.1.1.205 port 33000 protocol NetflowV9 transport
udp
SCE(config)#
EXAMPLE 2:
The following example configures an RDR formatter destination for two categories with a different priority for each category. This configuration will send RDRs from category 2 to this destination, but generally not RDRs from category 1.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#rdr-formatter destination 10.1.1.206 port 34000 category number 1 priority 10
category number 2 priority 90 protocol RrdrV1
SCE(config)#
Related Commands
Command
|
Description
|
show rdr-formatter destination
|
|
service rdr-formatter
|
|
rdr-formatter protocol NetflowV9 dscp
|
|
rdr-formatter destination protocol netflowv9 template data timeout
|
|
rdr-formatter destination protocol NetflowV9 template data timeout
Configures the interval after which all Netflow templates must be exported to the specified destination (refreshed). Use theno or the default form of the command to disable the template refresh mechanism.
rdr-formatter destination ip-address port port-number protocol NetflowV9 template data
timeout timeout-value
no rdr-formatter destination ip-address port port-number protocol NetflowV9 template data
default rdr-formatter destination ip-address port port-number protocol NetflowV9 template
data
Syntax Description
ip-address
|
The destination IP address.
|
port-number
|
The destination port number.
|
timeout-value
|
The time interval, in seconds,.between exporting the Netflow templates to the specified destination. Valid range is 1 - 86400 seconds.
|
Defaults
By default, the refresh mechanism is disabled.
Command Modes
Global Configuration
Usage Guidelines
A template record defines the structure of each Netflow data record. The RDR formatter transmits the templates only along with their matching data records. The RDR formatter refreshes the templates on the collector by resending them at configured intervals.
The no form of the command disables the refresh mechanism.
The default form of the command also disables the refresh mechanism, since the default state is disabled.
Authorization: admin
Examples
The following example illustrates the use of this command:
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#rdr-formatter destination 10.1.1.205 port 33000 protocol NetflowV9 template
data timeout 240
SCE(config)#
Related Commands
Command
|
Description
|
show rdr-formatter destination
|
|
rdr-formatter destination
|
|
rdr-formatter forwarding-mode
Defines the mode in which the RDR formatter will send the RDRs to the destinations.
rdr-formatter forwarding-mode mode
Syntax Description
mode
|
Settings: redundancy, multicast, simple-load-balancing as described in the Valid Mode Settings table in the Usage Guidelines.
|
Defaults
Default mode = redundancy
Command Modes
Global Configuration
Usage Guidelines
Table 2-2 Valid Mode Settings
redundancy
|
All RDRs are sent only to the primary (active) connection.
|
multicast
|
All RDRs are sent to all destinations.
|
simple-load-balancing
|
Each successive record is sent to a different destination, one destination after the other, in a round robin manner.
|
Authorization: admin
Examples
The following example sets the RDR formatter mode to "redundancy".
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#rdr-formatter forwarding-mode redundancy
SCE(config)#
Related Commands
Command
|
Description
|
show rdr-formatter forwarding-mode
|
|
rdr-formatter history-size
Configures the size of the history buffer. This command is currently not supported.
rdr-formatter history-size size
Syntax Description
size
|
Size of the history buffer in bytes. Must be = 0 only (default)
|
Defaults
Default size = 0
Command Modes
Global Configuration
Usage Guidelines
Do not change the size of the history buffer from the default value.
Since currently only RDRv1 is supported, the size of the history buffer must be zero bytes, even though the system will accept a command specifying a larger size.
Authorization: admin
Examples
Related Commands
Command
|
Description
|
show rdr-formatter history-size
|
|
rdr-formatter protocol NetflowV9 dscp
Defines the DSCP value to be assigned to the Netflow packets.
rdr-formatter protocol NetflowV9 dscp dscp-value
Syntax Description
dscp-value
|
DSCP value to be assigned to the Netflow packets, in HEX format. Accepted range is 0-63.
|
Defaults
Default dscp-value = 0
Command Modes
Global Configuration
Usage Guidelines
You can assign a DSCP value to specify the diffserv value of the Netflow traffic exported from your SCE platform.
Authorization: admin
Examples
The following example illustrates the use of this command.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#rdr-formatter protocol NetflowV9 dscp 0x20
SCE(config)#
Related Commands
Command
|
Description
|
show rdr-formatter protocol NetflowV9 dscp
|
|
rdr-formatter rdr-mapping
Adds a dynamic RDR mapping to a category or removes one from a category. Use the no form of this command to remove an existing mapping.
rdr-formatter rdr-mapping (tag-id tag number category-number category number )
no rdr-formatter rdr-mapping (tag-id tag number category-number category number )
Syntax Description
tag number
|
The complete 32 bit value given as an hexadecimal number. The RDR tag must be already configured in the Formatter by the application.
|
category number
|
Number of the category (1-4) to which to map the RDR tag
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
The configuration of categories to RDR tags is done by adding and removing mappings. You can add a mapping of RDR tag to a category and remove a mapping, including the default mapping. If the table already contains a mapping with the same tag and category number, an error is issued and nothing is done.
If all categories are removed from a tag, this tag will be ignored and will not be formatted and sent - this is `ignore mapping'.
Authorization: admin
Examples
The following examples illustrate how to use this command.
EXAMPLE 1
This example shows how to add a mapping to a category.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#rdr-formatter rdr-mapping tag-id 0xf0f0f000 category-number 1
SCE(config)#
EXAMPLE 2
This example shows how to restore the default mapping for a specified RDR tag.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#default rdr-formatter rdr-mapping tag-id 0xf0f0f000
SCE(config)#
Related Commands
Command
|
Description
|
show rdr-formatter rdr-mapping
|
|
reload
Note
In order not to lose the current configuration, use the copy running-config-all startup-config-all command before using the reload command.
Reboots the SCE platform.
reload
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example shows backing up of the configuration and performing a system reboot.
SCE>enable 10
Password:<cisco>
SCE#copy running-config-all startup-config-all
SCE#reload
Are you sure? Y
The system is about to reboot, this will end your CLI session
Related Commands
Command
|
Description
|
copy running-config startup-config
|
|
reload shutdown
|
|
reload shutdown
Shuts down the SCE platform, preparing it for being turned off.
reload shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Use this command to shut down the SCE platform in an orderly manner, before turning it off. After issuing this command, the only way to revive the SCE platform from its power-down state is to turn it off, then back on.
This command can only be issued from the serial CLI console port. When issued during a telnet CLI session, an error message is returned and the command is ignored. This is done to prevent the possibility of shutting it down from a remote location, from which it is not possible to power back up.
Authorization: admin
Examples
The following example shows the shutdown process.
SCE>enable 10
Password:<cisco>
SCE#reload shutdown
You are about to shut down the system.
The only way to resume system operation after this
is to cycle the power off, and then back on.
Continue?Y
IT IS NOW SAFE TO TURN THE POWER OFF.
Related Commands
Command
|
Description
|
reload
|
|
rename
Changes the file name to the specified name.
renameexisting-file-name new-file-name
Syntax Description
existing-file-name
|
The original name of the file.
|
new-file-name
|
The new name of the file.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example changes the name of file test1.pkg to test3.pkg.
SCE>enable 10
Password:<cisco>
SCE#rename test1.pkg test3.pkg
SCE#
Related Commands
rmdir
Removes an empty directory. To remove a directory that is not empty, use the delete command with the recursive switch.
rmdir directory-name
Syntax Description
directory-name
|
The name of the directory to be removed.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
You can only remove an empty directory. Use the dir command to verify that no files are listed in this directory.
Authorization: admin
Examples
The following example deletes the code directory.
SCE>enable 10
Password:<cisco>
SCE#rmdir code
SCE#
Related Commands
Command
|
Description
|
dir
|
|
delete
|
|
salt
Configures the value of the salt to be applied to the Personally Identifying Field of Extended Transaction Usage RDRs prior to hashing it.
Use the default form of the command to reset the salt to the default value.
salt salt-value1 salt-value2 salt-value3 salt-value4
default salt
Syntax Description
salt-value1 - salt-value4
|
Four 4-byte salt values in HEX
|
Defaults
0x12345678 0x12345678 0x12345678 0x12345678
Command Modes
Interface Linecard Configuration
Usage Guidelines
When generating Extended Transaction Usage RDRs for analyzing subscriber browsing patterns, it is necessary to hash the Personally Identifying Field to protect the identity of the subscriber. This command configures the salt to be applied to the field before hashing.
Always make sure to save the running configuration using the copy running-config startup-config
command.
Authorization: admin
Examples
The following example shows how to use this command.
SCE>enable 10
Password:<cisco>
SCE#configure
SCE(config)#interface linecard 0
SCE(config if)#salt 0xfafafafa 0xfafafafa 0xfafafafa 0xfafafafa
SCE(config if)#
sce-url-database add-entry
Adds a single entry to the protected URL database
sce-url-database add-entry url-wildcard URL-wildcard-format flavor-id flavor-id
Syntax Description
URL-wildcard-format
|
*' | URL-Prefix ['*'] | [URL-Prefix] '*' URL-Suffix
|
flavor-id
|
The ID of the flavor to be applied to the entry. The specified flavor must be the one that was designated for the black list in the pqb file that was applied, other wise the operation will fail.
|
Defaults
This command has no default settings.
Command Modes
Interface Linecard Configuration
Usage Guidelines
Use this command to add only a few new entries to the database. Add a large number of new URLs by importing an updated protected URL database file.
The user executing the command must have write permission for the protected URL database.
.Authorization: admin
Examples
The following example shows how to add an entry to the database. Since the flavor-ID is included in the command, this indicates that it is not present in the import file.
SCE>enable 10
Password:<cisco>
SCE#>configure
SCE(config)#interface linecard 0
SCE(config if)#sce-url-database add-entry url-wildcard xxx* flavor-id 50
Related Commands
Command
|
Description
|
sce-url-database protection
|
|
sce-url-database import
|
|
show interface linecard sce-url-database
|
|
sce-url-database import
Imports entries from an encrypted or cleartext file into the protected URL database.
sce-url-database import (cleartext-file | encrypted-file file-name) [flavor-id flavor-id]
Syntax Description
file-name
|
Path and filename of the protected URL database import file.
|
flavor-id
|
The ID of the flavor to be applied to all entries in the file. The specified flavor must be the one that was designated for the black list in the pqb file that was applied, otherwise the operation will fail.
• If the import file does not contain the flavor per entry, you must specify the flavor in this command.
• If the import file does contain the flavor per entry, you may not specify the flavor in this command.
|
Defaults
This command has no default settings.
Command Modes
Interface Linecard Configuration
Usage Guidelines
Specify the type of file:
•
Clear text file
•
Encrypted file: An encrypted file can be imported only if a matching encryption key has been configured. (See sce-url-database protection.)
Guidelines for Managing the Protected URL Database
•
The user executing the command must have write permission for the protected URL database.
•
When a new file is imported, the existing database is cleared before the import. Incremental update is not supported via the import command. Therefore the import file must contain all the relevant URLs, not only new ones to be added to the database.
•
Add a large number of new URLs by importing an updated protected URL database file. Typically, if the database is protected this option is used with an encrypted file.
•
Add a few new URLs by adding the new URLs using the sce-url-database add-entry command.
Protected URL Database Import File
The database import file may either contain cleartext or be encrypted. If the file is encrypted, the matching encryption key must be configured by the database owner.
If the file is encrypted, it must be prefixed with a cleartext header. The encrypted file header format must be exactly as follows:
Encrypted file version: 0x01
Block cipher index: 0x01
Mode of operation index: 0x02
Padder index: 0x02
IV length: 0x10
IV: <16 unformatted bytes which form the 128 bits IV of the encrypted data >
Following the header, the following data should appear in AES 128, CFB mode, encrypted format:
A random number (in the range [16...31]) of random bytes, followed by the word "Signed", and then again 32 random bytes.
Each following line represents a single URL.
Protected URL Database Import File Format
[Flavor <tab>] URL
Where:
•
Flavor: Flavor-id. The flavor ID must either be included for every line in the file or none of the lines. The flavor must be separated from the URL by a <tab>.
•
URL: ('*' | URL-Prefix ['*'] | [URL-Prefix] '*' URL-Suffix)
Results
•
The sce-url-database is first cleared.
•
The entries from the file are written to the database.
•
Duplicate keys in the file are overwritten with no warning.
•
In case of a failure, writing continues to the next entry.
The total number of failures and a listing of the failed file line numbers are reported when the import is finished.
Authorization: admin
Examples
The following example shows how to import the protected URL database from an encrypted file. Since the flavor-ID is included in the command, this indicates that it is not present in the import file.
SCE>enable 10
Password:<cisco>
SCE#>configure
SCE(config)#interface linecard 0
SCE(config if)#sce-url-database import encrypted-file blacklist-file flavor-id 50
Related Commands
Command
|
Description
|
sce-url-database protection
|
|
sce-url-database add-entry
|
|
show interface linecard sce-url-database
|
|
sce-url-database protection
Configures user authorization for the protected URL database.
Use the no form of the command to either remove all protection settings, or to remove only the encryption key.
sce-url-database protection owner (myself | (name user-name))
sce-url-database protection allow-write (all-users | owner-only)
sce-url-database protection allow-lookup (owner-only | no-user)
sce-ur l-database protection encryption-key encryption-key
no sce-url-database protection
no sce-url-database protection encryption-key
Syntax Description
user-name
|
Username that is defined as the owner of the protected URL database.
Cannot be the default username.
|
encryption-key
|
The AES encryption key - either 128-, 192-, or 256-bits long. The key is supplied in hexadecimal format and is 32, 48, or 64 hexadecimal digits respectively.
|
all-users
|
All users can perform the specified action.
|
owner-only
|
Only the owner of the protected URL database can perform the specified action.
|
no-user
|
No user can perform the specified action.
|
Defaults
•
By default there is no designated owner.
•
Read permission—no-user. This setting is not configurable
•
Write permission
–
If no owner has been assigned, the default is all-users.
–
If an owner has been assigned, the default is owner-only.
•
Lookup permission
–
If no owner has been assigned, the default is all-users.
–
If an owner has been assigned, the default is no-user.
•
Encryption key—no key.
Command Modes
Interface Linecard Configuration
Usage Guidelines
When the protected URL database is protected, one user is designated as the owner of the database and only that user can execute the protection CLI commands on the database; the database manipulation commands then being restricted according to the owner configuration. This requires defining the AAA authorization method (either based on local users or based on a TACACS+ server, etc.) and defining at least one user who should be assigned to be the owner of the database.
If the database is defined to be protected, none of the database information (including the owner, the database entries, and the authorization information itself) is accessible to any users, including the relevant saved configuration in the log files and in the relevant SCA BB reports. The database-owner user may change the authorizations using the CLI; however, when any of the protections are relaxed (or all of the protections are relaxed by removing the protections entirely) the database is reset.
In order to ensure the secrecy of the database information, the database entries may be imported to the SCE (using the CLI) in an encrypted form using 128-, 192-, or 256-bit key length AES. The key may be set or updated using the appropriate CLI command; typically, this command should be run over a secure Telnet session.
User Authorization Guidelines:
•
The default user cannot be the owner.
•
When there is no designated owner, the sce-url-database is unprotected and the contents can be read and modified by any user.
•
Only the owner can configure the protection settings. If there is no owner, the database is unprotected and any user has read and write permissions. A user may be configured to be the owner of the database only while no owner user is designated for the database.
•
When any protection setting is relaxed, the database is reset. Protection is relaxed in the following cases:
–
Protection is removed completely using the no sce-url-database protection command.
–
Write permission is changed from owner-only to all-users.
–
Lookup permission is changed from no-user to owner-only.
•
The sce-url-database configuration information is not accessible as part of the running config and startup config files.
–
Protected information is not displayed when a show or more command is executed on the config files.
–
Protected information is included when a copy command is executed on the config files.
Authorization: admin
Examples
The following example shows how to configure protected URL database protection.
SCE>enable 10
Password:<cisco>
SCE#>configure
SCE(config)#interface linecard 0
SCE(config if)#sce-url-database protection owner myself
SCE(config if)#sce-url-database protection allow-write all-users
SCE(config if)#sce-url-database protection allow-lookup no-user
SCE(config if)#sce-url-database protection encryption-key AABBCCDDEEFF11223344556677889900
Related Commands
Command
|
Description
|
sce-url-database import
|
|
show interface linecard sce-url-database protection
|
|
sce-url-database remove-all
|
|
sce-url-database add-entry
|
|
sce-url-database remove-all
Clears the protected URL database
sce-url-database remove-all
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Interface Linecard Configuration
Usage Guidelines
The user executing the command must have write permission for the protected URL database.
.Authorization: admin
Examples
The following example shows how to use this command.
SCE>enable 10
Password:<cisco>
SCE#>configure
SCE(config)#interface linecard 0
SCE(config if)#sce-url-database remove-all
Related Commands
Command
|
Description
|
sce-url-database protection
|
|
sce-url-database import
|
|
show interface linecard sce-url-database
|
|
scmp
Enables the Service Control Management Protocol functionality. Use the no form of the command to disable the SCMP.
scmp
no scmp
Syntax Description
This command has no arguments or keywords.
Defaults
By default, SCMP is disabled.
Command Modes
Global Configuration
Usage Guidelines
SCMP is a protocol by which an SCE platform communicates with peers such as Cisco routers running ISG to manage subscriber sessions.
SCMP performs the following functions:
•
Manages the connection status to all SCMP peer devices
•
Encodes and decodes the SCMP messages
•
Orders northbound messages per subscriber
When the SCMP is disabled, all subscribers provisioned via this interface are removed.
Authorization: admin
Examples
The following example illustrates how to disable the SCMP.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no scmp
SCE(config)#
Related Commands
Command
|
Description
|
scmp keepalive-interval
|
|
scmp loss-of-sync-timeout
|
|
scmp name
|
|
scmp reconnect-interval
|
|
scmp subscriber force-single-sce
|
|
scmp subscriber id append-to-guid
|
|
scmp subscriber send-session-start
|
|
no subscriber
|
|
show scmp
|
|
scmp keepalive-interval
Defines interval between keep-alive messages to the SCMP peer device.
scmp keepalive-interval interval
Syntax Description
interval
|
Interval between keep-alive messages from the SCE platform to the SCMP peer device.
|
Defaults
interval = 5 seconds
Command Modes
Global Configuration
Usage Guidelines
The SCE platform sends keep-alive messages to all connected SCMP peer device at the defined interval.
•
If a response is received within the defined interval, the keep-alive time-stamp is updated.
•
If a response is not received within the defined interval, the connection is assumed to be down; the connection state is changed to not-connected, and the SCMP begins attempts to reconnect.
Authorization: admin
Examples
The following example illustrates how to define the SCMP keepalive message interval.
SCE>enable 10
Password:<cisco>
SCE#configure
SCE(config)#scmp keepalive-interval 10
SCE(config)#
Related Commands
Command
|
Description
|
show scmp
|
|
scmp loss-of-sync-timeout
Defines the loss of sync timeout interval; that is the amount of time between loss of connection between the SCE platform and an SCMP peer device and the loss-of-sync event.
scmp loss-of-sync-timeout interval
Syntax Description
interval
|
Loss of sync timeout interval in seconds
|
Defaults
interval = 90 seconds
Command Modes
Global Configuration
Usage Guidelines
If the connection between an SCE platform and an SCMP peer device fails, a timer starts. If the configured loss of sync timeout interval is exceeded, the connection is assumed to be not-in-sync, a loss-of-sync event occurs, and the following actions are performed:
•
connection status is set to not-in-sync
•
all messages are removed from the SCMP buffers
•
all subscribers associated with the SCMP peer device are removed
Authorization: admin
Examples
The following example illustrates how to define loss of sync timeout interval.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)# scmp loss-of-sync-timeout 120
SCE(config)#
Related Commands
Command
|
Description
|
show scmp
|
|
scmp reconnect-interval
|
|
scmp name
Adds an SCMP peer device. Use the no form of the command to delete the specified SCMP peer device.
scmp name name radius host-name secret secret [auth-port auth-port# acct-port acct-port# ]
no scmp name name
Syntax Description
name
|
Name of the SCMP peer device
|
host-name
|
IP address or name of the RADIUS host
|
secret
|
RADIUS shared secret
|
auth-port#
|
authentication port number
|
acct-port#
|
accounting port number
|
Defaults
Default: Ports configuration as specified in RFC #2865 and RFC #2866
Authentication port = 1812
Accounting port = 1813
Command Modes
Global Configuration
Usage Guidelines
After defining an SCMP peer device, you must associate it with one or more unmapped anonymous groups (see subscriber anonymous-group name scmp name ). This provides the ability to query the SCMP peer regarding unmapped IP addresses in cases where the SCE platform is not updated when the subscriber session has started (see scmp subscriber send-session-start ) or in recovery scenarios.
You cannot delete an SCMP device that has anonymous groups assigned to it. Use the no form of the subscriber anonymous-group name scmp name command to remove all associated anonymous groups before deleting the device.
Authorization: admin
Examples
The following example illustrates how to define an SCMP peer device.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)# scmp name peer_device1 radius radius1 secret abcdef
SCE(config)#
Related Commands
Command
|
Description
|
subscriber anonymous-group name scmp name
|
|
no subscriber
|
Use the 'scmp name scmp-name all' option to remove subscribers managed by a specified SCMP peer device
|
ip radius-client retry limit
|
|
show scmp
|
|
scmp reconnect-interval
Defines the SCMP reconnect interval; that is the amount of time between attempts by the SCE platform to reconnect with an SCMP peer.
scmp reconnect-interval interval
Syntax Description
interval
|
Interval between attempts by the SCE platform to reconnect with an SCMP peer, in seconds
|
Defaults
interval = 30 seconds
Command Modes
Global Configuration
Usage Guidelines
The SCE platform attempts to reconnect to the SCMP peer device at the defined intervals by sending an establish peering request message. If a valid reply is received, the SCMP connection state for the SCMP peer is changed, and the SCMP performs the required reconnection operations, such as the following:
•
Re-querying the peer regarding all subscribers provisioned by this device
•
Querying the peer regarding all anonymous subscribers created using the anonymous group assigned to this peer
Authorization: admin
Examples
The following example illustrates how to define the SCMP reconnect interval.
SCE>enable 10
Password:<cisco>
SCE#configure
SCE(config)#scmp reconnect-interval 60
SCE(config)#>
Related Commands
Command
|
Description
|
show scmp
|
|
scmp loss-of-sync-timeout
|
|
scmp subscriber force-single-sce
Configures the SCMP to make the SCMP peer device verify that each subscriber is only provisioned for one SCE platform. This configuration must be enabled in MGSCP deployments. Use the no form of the command to disable verifying each subscriber is only provisioned for one SCE platform.
scmp subscriber force-single-sce
no scmp subscriber force-single-sce
Syntax Description
This command has no arguments or keywords.
Defaults
Default is disabled.
Command Modes
Global Configuration
Usage Guidelines
This command takes effect only if it is set before the connection with the SCMP peers is established. Use the no scmp and scmp commands to stop and then restart the SCMP if active connections exist.
Authorization: admin
Examples
The following example illustrates how to use this command.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#scmp subscriber force-single-sce
SCE(config)#
Related Commands
Command
|
Description
|
show scmp
|
|
scmp
|
|
scmp subscriber id append-to-guid
Defines the subscriber ID structure for subscribers provisioned via the SCMP interface. Use the no form of the command to clear the subscriber ID structure setting.
scmp subscriber id append-to-guid radius-attributes Calling-Station-Id | NAS-Port-Id |
User-Name [Calling-Station-Id | NAS-Port-Id | User-Name] [Calling-Station-Id |
NAS-Port-Id | User-Name]
no scmp subscriber id append-to-guid
Syntax Description
This command has no arguments.
Defaults
By default, all settings are cleared.
Command Modes
Global Configuration
Usage Guidelines
The GUID is a global unique ID assigned to each subscriber session by the SCMP peer device.
The user can define the structure of the subscriber ID via this command by specifying which of the following RADIUS attributes to include and in which order:
•
Calling-Station-Id
•
NAS-port
•
User-Name
The GUID is always appended at the end of the subscriber ID as defined by this command.
The no form of the command clears the subscriber ID structure setting,resulting in no other elements being used with the GUID to form the subscriber ID.
You must disable the SCMP interface before executing this command. (Use the command no scmp.)
Authorization: admin
Examples
The following example illustrates how to use this command.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no scmp
SCE(config)#scmp subscriber id append-to-guid radius-attributes User-Name
Calling-Station-Id NAS-Port-Id
SCE(config)#scmp
SCE(config)#
Related Commands
Command
|
Description
|
scmp
|
|
show scmp
|
|
scmp subscriber send-session-start
Configures the SCMP to make the SCMP peer device push sessions to the SCE platform immediately when the session is created on the peer device. Use the no form of the command to disable pushing of sessions from the SCMP peer device to the SCE platform.
scmp subscriber send-session-start
no scmp subscriber send-session-start
Syntax Description
This command has no arguments or keywords.
Defaults
Default is disabled.
Command Modes
Global Configuration
Usage Guidelines
This command takes effect only if it is set before the connection with the SCMP peers is established. Use the no scmp and scmp commands to stop and then restart the SCMP if active connections exist.
This feature must be disabled in MGSCP deployments.
Authorization: admin
Examples
The following example illustrates how to use this command.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#scmp subscriber send-session-start
SCE(config)#
Related Commands
Command
|
Description
|
show scmp
|
|
script capture
Begins the recording of a script. It tracks all commands typed until the script stop command is used.
script capture script-file-name
Syntax Description
script-file-name
|
The name of the output file where the script is stored.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Use this command to capture a sequence of repeated commands into a file for the purpose of executing the commands again.
Use the script stop command to stop capturing the script.
Authorization: admin
Examples
The following example shows the script capture for the script1.txt.
SCE>enable 10
Password:<cisco>
SCE#script capture script1.txt
SCE#cd log
SCE#cd..
SCE#pwd
SCE#script stop
Related Commands
Command
|
Description
|
script stop
|
|
script print
Displays a script file.
script print script-file-name
Syntax Description
script-file-name
|
The name of the file containing the script.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example prints the commands captured in script1.txt.
SCE>enable 10
Password:<cisco>
SCE#script print script1.txt cd log
cd..
pwd
script stop
SCE#
Related Commands
Command
|
Description
|
script capture
|
|
script run
|
|
script run
Runs a script. The script may be created using the script capture command, or it may be created as a text file containing the appropriate commands.
script run script-file-name [halt]
Syntax Description
script-file-name
|
The name of the file containing the script.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Use this command to run a script that you have previously created using the script capture command.
Use the halt keyword to break script on errors.
Authorization: admin
Examples
The following example runs the script named monitor.txt, which contains commands to enable the generation of the real-time subscriber usage RDRs for the specified subscribers.
Following is the contents of the file:
configure
interface linecard 0
subscriber name Jerry property name monitor value 1
subscriber name George property name monitor value 1
subscriber name Elaine property name monitor value 1
subscriber name Kramer property name monitor value 1
The following show how to run the script:
SCE>enable 10
Password:<cisco>
SCE#script run monitor.txt
SCE#configure
SCE(config)#interface linecard 0
SCE(config if)#subscriber name Jerry property name monitor value 1
SCE(config if)#subscriber name George property name monitor value 1
SCE(config if)#subscriber name Elaine property name monitor value 1
SCE(config if)#subscriber name Kramer property name monitor value 1
SCE(config if)#
Related Commands
Command
|
Description
|
script capture
|
|
script print
|
|
script stop
Stops script capture. Used in conjunction with the script capture command, it marks the end of a script being recorded.
script stop
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example stops the capturing of a script.
SCE>enable 10
Password:<cisco>
SCE#script capture script1.txt
SCE#cd log
SCE#cd..
SCE#pwd
SCE#script stop
SCE#
Related Commands
Command
|
Description
|
script capture
|
|
service-bandwidth-prioritization-mode
Defines the service bandwidth prioritization mode.
service-bandwidth-prioritization-mode {global | subscriber-internal}
Syntax Description
This command has no arguments.
Defaults
default = subscriber-internal
Command Modes
Interface Linecard Configuration
Usage Guidelines
This parameter configures how bandwidth controllers compete for bandwidth by specifying which assurance level (AL) value is used when allocating bandwidth between bandwidth controllers. The AL can either be taken from either of the following:
•
global prioritization mode — the global controller AL is taken from current bandwidth controller Assurance Level.
•
subscriber-internal prioritization mode — the global controller AL of each bandwidth controller is taken from the Primary BWC Relative Priority (the party or "total" bandwidth-controller Relative-Priority value)
Authorization: admin
Examples
The following example shows how to use this command.
SCE>enable 10
Password:<cisco>
SCE#configure
SCE(config)#interface linecard 0
SCE(config if)#service-bandwidth-prioritization-mode global
SCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard service-bandwidth-prioritization-mode
|
|
service password-encryption
Enables password encryption, so that the password remains secret when the configuration file is displayed. Use the no form of this command to disable password encryption.
service password-encryption
no service password-encryption
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled (no encryption)
Command Modes
Global Configuration
Usage Guidelines
Passwords that were configured in an encrypted format are not deciphered when password encryption is disabled.
Authorization: admin
Examples
The following example shows the effect of enabling password encryption.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#enable password abcd
SCE(config)#do more running-config
#This is a general configuration file (running-config).
#Created on 10:20:57 ISR TUE July 3 2001
...
enable password level 10 0 "abcd"
...
SCE(config)#service password-encryption
SCE(config)#do more running-config
#This is a general configuration file (running-config).
#Created on 10:21:12 ISR TUE July 3 2001
...
service password-encryption
enable password level 10 0 "e2fc714c4727ee9395f324cd2e7f331f"
...
SCE(config)#
Related Commands
Command
|
Description
|
| |
enable password
|
service rdr-formatter
Enables/disables the RDR-formatter. The RDR-formatter is the element that formats the reports of events produced by the linecard and sends them to an external data collector. Use the no keyword of this command to disable the RDR-formatter.
service rdr-formatter
no service rdr-formatter
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following examples illustrate the use of the service rdr-formatter command:
EXAMPLE 1:
The following example enables the RDR-formatter.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#service rdr-formatter
SCE(config)#
EXAMPLE 2:
The following example disables the RDR-formatter.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no service rdr-formatter
SCE(config)#
Related Commands
Command
|
Description
|
show rdr-formatter enabled
|
|
rdr-formatter category-number
|
|
rdr-formatter destination
|
|
service telnetd
Enables the Telnet daemon. Use the no form of this command to disable the daemon preventing new users from accessing the SCE platform via Telnet.
service telnetd
no service telnetd
Syntax Description
This command has no arguments or keywords.
Defaults
Telnet daemon enabled
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following examples illustrate the use of the service telnetd command:
EXAMPLE 1:
The following example enables the Telnet daemon.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#service telnetd
SCE(config)#
EXAMPLE 2:
The following example disables the Telnet daemon.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no service telnetd
SCE(config)#
Related Commands
Command
|
Description
|
show telnet status
|
|
telnet
|
|
show access-lists
Shows all access-lists or a specific access list.
show access-lists [number ]
Syntax Description
number
|
Number of the access list to show
|
Defaults
Default access list number = 1.
Command Modes
Privileged EXEC
Usage Guidelines
Authorization: admin
Examples
The following example displays the configuration of access-list 5.
SCE>enable 5
Password:<cisco>
SCE#show access-lists 5
Standard IP access list 5
Permit 10.1.1.0, wildcard bits 0.0.0.255
deny any
SCE#
Related Commands
Command
|
Description
|
access-list
|
|
show blink
Displays the blinking status of a slot. A slot blinks after it receives a blink command.
show blink slot slot-number
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the blink status of slot 0.
SCE>enable 5
Password:<cisco>
SCE>show blink slot 0
Slot 0 blink status: off
SCE>
Related Commands
Command
|
Description
|
blink
|
|
show calendar
Displays the time maintained by the real-time system calendar clock.
show calendar
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the current system calendar.
SCE>enable 5
Password:<cisco>
SCE>show calendar
12:50:03 GMT MON November 13 2005
SCE>
Related Commands
Command
|
Description
|
calendar set
|
|
show clock
Displays the time maintained by the system clock.
show clock
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the current system clock.
SCE>enable 5
Password:<cisco>
SCE>show clock
12:50:03 GMT MON November 13 2005
SCE>
Related Commands
Command
|
Description
|
clock set
|
|
show environment all
Displays information about the SCE platform environment, including the following:
•
cooling
•
power supply units
•
temperature
•
voltage
show environment all
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to use this command.
SCE>enable 5
Password:<cisco>
SCE>show environment all
scm[0].smc[0].max1668[0] - temperature device
==========================================================================================
=======================================================
PCB_Upper local1 29C 29 29.0 29 0.0 -18 -8 60 75
OK 0000:00:00:54 ----------- ----:--:--:-- 0
CurrStatus : OK fan tray is in non-manual mode (0000:00:00:50)
PrevStatus : <none> (----:--:--:--)
Sts# : 0 (access=2, fail=0)
CurrStatus : OK (0000:00:00:50)
PrevStatus : <none> (----:--:--:--)
Sts# : 0 (access=1, fail=0)
VOLTAGE status is: {OK, <DISABLED>}
TEMPERATURE status is: {OK}
show environment cooling
Displays information about the SCE platform cooling.
show environment cooling
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to use this command.
SCE>enable 5
Password:<cisco>
SCE>show environment cooling
Environment Cooling information:
fan-tray[0] - cooling device
CurrStatus : OK (0000:00:01:43)
PrevStatus : <none> (----:--:--:--)
Sts# : 0 (access=7, fail=0)
CurrStatus : OK fan tray is in non-manual mode (0000:00:01:43)
PrevStatus : <none> (----:--:--:--)
Sts# : 0 (access=4, fail=0)
Control Mode : HP (High Power)
Test Enable State : Disabled
Thermistor Value : 24 Celsius
VOLTAGE status is: {OK, <DISABLED>}
TEMPERATURE status is: {OK}
show environment power
Displays information about the SCE platform PSUs (power supply unit).
show environment power
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to use this command.
SCE>enable 5
Password:<cisco>
SCE>show environment power
Environment Power information:
psu[0] - power supply device
CurrStatus : OK (0000:00:01:59)
PrevStatus : <none> (----:--:--:--)
Sts# : 0 (access=4, fail=0)
CurrStatus : OK (0000:00:01:59)
PrevStatus : <none> (----:--:--:--)
Sts# : 0 (access=4, fail=0)
VOLTAGE status is: {OK, <DISABLED>}
TEMPERATURE status is: {OK}
show environment temperature
Displays information about the temperature of the SCE platform.
show environment temperature
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to use this command.
SCE>enable 5
Password:<cisco>
SCE>show environment temperature
Environment Temperature information:
scm[0].smc[0].max1668[0] - temperature device
CurrStatus : OK (0000:00:02:15)
PrevStatus : <none> (----:--:--:--)
Sts# : 0 (access=35, fail=0)
Name General CurrVal MinVal AvgVal MaxVal DevVal ErrL WrnL WrnH ErrH
CurrStatus dddd:hh:mm:ss PrevStatus dddd:hh:mm:ss Sts#
==========================================================================================
=======================================================
PCB_Upper local1 29C 29 29.0 29 0.0 -18 -8 60 75
OK 0000:00:02:15 ----------- ----:--:--:-- 0
DPT sd_1 39C 38 38.7 39 0.5 -8 2 74 89
OK 0000:00:02:15 ----------- ----:--:--:-- 0
CLS sd_2 33C 32 32.8 33 0.4 -8 2 63 78
OK 0000:00:02:15 ----------- ----:--:--:-- 0
show environment voltage
Displays information about the SCE platform voltage.
show environment voltage
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to use this command.
SCE>enable 5
Password:<cisco>
SCE>show environment voltage
Environment Voltage information:
scm[0].smc[0].summit766[0] - voltage device
CurrStatus : OK (0000:00:01:28)
PrevStatus : <none> (----:--:--:--)
Sts# : 0 (access=23, fail=0)
Name General CurrVal MinVal AvgVal MaxVal DevVal ErrL WrnL WrnH ErrH
CurrStatus dddd:hh:mm:ss PrevStatus dddd:hh:mm:ss Sts#
==========================================================================================
=======================================================
Main_3_3 CH_A 3286mV 3286 3286.0 3286 0.0 3168 3234 3366 3432
OK 0000:00:01:28 ----------- ----:--:--:-- 0
Main_2_5 CH_B 2490mV 2490 2490.0 2490 0.0 2400 2450 2550 2600
OK 0000:00:01:28 ----------- ----:--:--:-- 0
show failure-recovery operation-mode
Displays the operation mode to apply after boot resulted from failure.
show failure-recovery operation-mode
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example displays the failure recovery operation mode:
SCE>enable 5
Password:<cisco>
SCE>show failure-recovery operation-mode
System Operation mode on failure recovery is: operational
SCE>
Related Commands
Command
|
Description
|
failure-recovery operation-mode
|
|
show hostname
Displays the currently configured hostname.
show hostname
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows that SCE8000 is the current hostname.
SCE>enable 5
Password:<cisco>
SCE>show hostname
SCE8000
SCE>
Related Commands
Command
|
Description
|
hostname
|
|
show hosts
Displays the default domain name, the address of the name server, and the content of the host table.
show hosts
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the domain and hosts configured.
SCE>enable 5
Password:<cisco>
SCE>show hosts
Default domain is cisco.com
Name/address lookup uses domain service
Name servers are 10.1.1.60, 10.1.1.61
Host Address
---- -------
PC85 10.1.1.61
SCE>
Related Commands
Command
|
Description
|
hostname
|
|
ip domain-name
|
|
ip name-server
|
|
show interface gigabitethernet
Displays the details of the GigabitEthernet management interface.
show interface gigabitethernet slot-number/interface-number [counters [direction ]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 1.
|
interface-number
|
GigabitEthernet management interface number. Enter a value of 1.
|
direction
|
Optional direction specification, to show only counters of a specific direction. Use in or out.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
The counters keyword displays the values of counters of the GigabitEthernet management interface.
Authorization: viewer
Examples
The following example shows the GigabitEthernet details.
SCE>enable 5
Password:<cisco>
SCE>show interface gigabitethernet 1/1
SCE>
Related Commands
Command
|
Description
|
interface gigabitethernet
|
|
show interface linecard
Displays information for a specific linecard Interface.
show interface linecard slot-number
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to use this command.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0
The application assigned to slot 0 is /system/app/eng30102.sli
Silent is off
Configured shutdown is off
Shutdown due to sm-connection-failure is off
Resulting current shutdown state is off
WAP handling is disabled
SCE>
Related Commands
Command
|
Description
|
interface linecard
|
|
show interface linecard accelerate-packet-drops
Displays the currently configured hardware packet drop mode.
show interface linecard slot-number accelerate-packet-drops
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
Authorization: viewer
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 accelerate-packet-drops
Accelerated packet drops mode is enabled
SCE>
Related Commands
Command
|
Description
|
accelerate-packet-drops
|
|
show interface linecard application
Displays the name of the application loaded on the Linecard Interface.
show interface linecard slot-number application
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the currently loaded application.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 application
/system/app/eng30102.sli
SCE>
Related Commands
show interface linecard asymmetric-L2-support
Displays the current asymmetric layer 2 support configuration.
show interface linecard slot-number asymmetric-L2-support
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates how to use this command:
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 asymmetric-L2-support
Asymmetric layer 2 support is disabled
SCE>
Related Commands
Command
|
Description
|
asymmetric-L2-support
|
|
show interface linecard asymmetric-routing-topology
Displays information relating to asymmetric routing topology.
show interface linecard slot-number asymmetric-routing-topology
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Displays the following:
•
Current asymmetric routing topology status
•
The ratio of TCP unidirectional flows to total TCP flows per traffic processor ( TCP unidirectional flows ratio ).
The unidirectional flows ratio is displayed only for TCP flows, and reflects the way the flows were opened. It is calculated over the period of time since the SCE platform was last reloaded, or since the counters were last reset.
To reset the asymmetric routing mode counters, see clear interface linecard asymmetric-routing-topology counters.
Note
The SCE platform identifies unidirectional flows by default and regardless of the asymmetric routing mode.
Authorization: viewer
Examples
The following example illustrates how to use this command:
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 asymmetric-routing-topology
Asymmetric Routing Topology mode is disabled
TCP Unidirectional flows ratio statistics:
==========================================
Traffic Processor 1 : 0%
Traffic Processor 2 : 0%
Traffic Processor 3 : 0%
Traffic Processor 4 : 0%
Traffic Processor 5 : 0%
Traffic Processor 6 : 0%
Traffic Processor 7 : 0%
Traffic Processor 8 : 0%
Traffic Processor 9 : 0%
Traffic Processor 10 : 0%
Traffic Processor 11 : 0%
Traffic Processor 12 : 0%
Note that the statistics are updated only if the system is configured to work in Enhanced
Open Flow (i.e. following settings are disabled:
Classical Open Flow mode, VAS, TCP no bypass est, etc.).
The statistics are updated once every two minutes
SCE>
Related Commands
Command
|
Description
|
asymmetric-routing-topology enabled
|
|
clear interface linecard asymmetric-routing-topology counters
|
|
show interface linecard attack-detector
Displays the configuration of the specified attack detector.
show interface linecard slot-number attack-detector [default|all]
show interface linecard slot-number attack-detector attack-detector
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
attack-detector
|
The number of the specific attack detector to be displayed.
|
all
|
Displays the configuration of all existing attack detectors
|
default
|
Displays the default attack detector configuration.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use the all keyword to display the configuration of all existing attack detectors.
Use the default keyword to display default attack detector configuration.
The following information is displayed:
•
Protocol Side — Whether the attack detector applies to attacks originating at the subscriber or network side.
•
Direction — Whether the attack detector applies to single sided or dual sided attacks.
•
Action to take if an attack is detected.
•
Thresholds:
–
open-flows-rate — Default threshold for rate of open flows (new open flows per second).
–
suspected-flows-rate — Default threshold for rate of suspected DDoS flows (new suspected flows per second).
–
suspected-flows-ratio — Default threshold for ratio of suspected flow rate to open flow rate.
•
Subscriber notification — enabled or disabled.
•
Alarm — sending an SNMP trap enabled or disabled.
Authorization: viewer
Examples
The following examples illustrate the show interface linecard attack-detector command:
EXAMPLE 1:
The following example displays the configuration of attack detector number 3.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 attack-detector 3
Detector #3:
Comment: 'Sample'
Access-list: 1
Effective only for TCP port(s) 21,23,80
Effective for all UDP ports
Protocol|Side|Direction ||Action| Thresholds |Sub- |Alarm
| | || |Open flows|Ddos-Suspected flows|notif|
| | || |rate |rate |ratio | |
--------|----|-----------||------|----------|------------|-------|-----|-----
TCP |net.|source-only|| | | | | |
TCP |net.|dest-only || | | | | |
TCP |sub.|source-only|| | | | | |
TCP |sub.|dest-only || | | | | |
TCP |net.|source+dest|| | | | | |
TCP |sub.|source+dest|| | | | | |
TCP+port|net.|source-only||Block | | | | |Yes
TCP+port|net.|dest-only || | | | | |
TCP+port|sub.|source-only||Block | | | | |Yes
TCP+port|sub.|dest-only || | | | | |
TCP+port|net.|source+dest|| | | | | |
TCP+port|sub.|source+dest|| | | | | |
UDP |net.|source-only|| | | | | |
UDP |net.|dest-only || | | | | |
UDP |sub.|source-only|| | | | | |
UDP |sub.|dest-only || | | | | |
UDP |net.|source+dest|| | | | | |
UDP |sub.|source+dest|| | | | | |
UDP+port|net.|source-only|| | | | | |
UDP+port|net.|dest-only || | | | | |
UDP+port|sub.|source-only|| | | | | |
UDP+port|sub.|dest-only || | | | | |
UDP+port|net.|source+dest|| | | | | |
UDP+port|sub.|source+dest|| | | | | |
ICMP |net.|source-only|| | | | | |
ICMP |net.|dest-only || | | | | |
ICMP |sub.|source-only|| | | | |Yes |
ICMP |sub.|dest-only || | | | | |
other |net.|source-only|| | | | | |
other |net.|dest-only || | | | | |
other |sub.|source-only|| | | | | |
other |sub.|dest-only || | | | | |
Empty fields indicate that no value is set and configuration from
the default attack detector is used.
SCE>
EXAMPLE 2:
The following example displays the configuration of the default attack detector.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 attack-detector default
Protocol|Side|Direction ||Action| Thresholds |Sub- |Alarm
| | || |Open flows|Ddos-Suspected Flows|notif|
| | || |rate |rate |ratio | |
--------|----|-----------||------|----------|------------|-------|-----|-----
TCP |net.|source-only||Report| 1000| 500|50 |No |No
TCP |net.|dest.-only ||Report| 1000| 500|50 |No |No
TCP |sub.|source-only||Report| 1000| 500|50 |No |No
TCP |sub.|dest.-only ||Report| 1000| 500|50 |No |No
TCP |net.|source+dest||Report| 100| 50|50 |No |No
TCP |sub.|source+dest||Report| 100| 50|50 |No |No
TCP+port|net.|source-only||Report| 1000| 500|50 |No |No
TCP+port|net.|dest.-only ||Report| 1000| 500|50 |No |No
TCP+port|sub.|source-only||Report| 1000| 500|50 |No |No
TCP+port|sub.|dest.-only ||Report| 1000| 500|50 |No |No
TCP+port|net.|source+dest||Report| 100| 50|50 |No |No
TCP+port|sub.|source+dest||Report| 100| 50|50 |No |No
UDP |net.|source-only||Report| 1000| 500|50 |No |No
UDP |net.|dest.-only ||Report| 1000| 500|50 |No |No
UDP |sub.|source-only||Report| 1000| 500|50 |No |No
UDP |sub.|dest.-only ||Report| 1000| 500|50 |No |No
UDP |net.|source+dest||Report| 100| 50|50 |No |No
UDP |sub.|source+dest||Report| 100| 50|50 |No |No
UDP+port|net.|source-only||Report| 1000| 500|50 |No |No
UDP+port|net.|dest.-only ||Report| 1000| 500|50 |No |No
UDP+port|sub.|source-only||Report| 1000| 500|50 |No |No
UDP+port|sub.|dest.-only ||Report| 1000| 500|50 |No |No
UDP+port|net.|source+dest||Report| 100| 50|50 |No |No
UDP+port|sub.|source+dest||Report| 100| 50|50 |No |No
ICMP |net.|source-only||Report| 500| 250|50 |No |No
ICMP |net.|dest.-only ||Report| 500| 250|50 |No |No
ICMP |sub.|source-only||Report| 500| 250|50 |No |No
ICMP |sub.|dest.-only ||Report| 500| 250|50 |No |No
other |net.|source-only||Report| 500| 250|50 |No |No
other |net.|dest.-only ||Report| 500| 250|50 |No |No
other |sub.|source-only||Report| 500| 250|50 |No |No
other |sub.|dest.-only ||Report| 500| 250|50 |No |No
SCE>
Related Commands
Command
|
Description
|
attack-detector
|
|
attack-detector default
|
|
attack-detector <number>
|
|
show interface linecard attack-filter
Displays the attack filtering configuration.
show interface linecard slot-number attack-filter [option ]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
option
|
See Usage Guidelines for the list of options.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Following is a list of options that may be displayed:
•
query IP configured : displays the configured threshold values and action as follows:
–
query single-sided IP ip-address configured : displays the configured threshold values and action for attack detection for a specified IP address (single-sided detection)
–
query dual-sided source-IP ip-address1 dest ip-address2 configured : displays the configured threshold values and action for attack detection between two specified IP addresses (dual-sided detection)
–
dest-port port#: displays the configured threshold values and action for the specified port. You can include this argument with both single-sided and dual-sided queries.
•
query IP current : displays the current counters for a specified attack detector for all protocols and attack directions as follows:
–
query single-sided IP ip-address current : displays the current counters for attack detection for a specified IP address (single-sided detection)
–
query dual-sided source-IP ip-address1 dest ip-address2 current : displays the current counters for attack detection between two specified IP addresses (dual-sided detection)
–
dest-port port #: displays the configured threshold values and action for the specified port. You can include this argument with both single-sided and dual-sided queries.
•
current-attacks : displays all currently handled attacks
•
counters : displays all attack detection counterd
•
dont-filter : displays all existing stopped attack filters
•
force-filter : displays all existing forced attack filters
•
subscriber-notification ports : displays the list of subscriber-notification ports
•
subscriber-notification redirect: displays the configuration of subscriber-notification redirection, such as the configured destination and dismissal URLs, and allowed hosts.
Authorization: viewer
Examples
The following examples illustrate the use of this command.
EXAMPLE 1:
The following example displays the configuration of attack detection between two specified IP addresses (dual-sided) for destination port 101.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 attack-filter
query dual-sided source-IP 10.10.10.10 dest 10.10.10.145 dest-port 101 configured
SCE>
EXAMPLE 2:
The following example displays all existing forced attack filters.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 attack-filter
force-filter No force-filter commands are set for slot 0
SCE>
EXAMPLE 3:
The following example displays the subscriber notification ports.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 attack-filter
subscriber-notification ports
Configured Subscriber notification ports: 100
SCE>
Related Commands
Command
|
Description
|
attack-filter
|
|
attack-filter force-filter | dont-filter
|
|
show interface linecard connection-mode
Shows the current configuration of the SCE platform link connection.
show interface linecard slot-number connection-mode
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to use this command.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 connection-mode
slot 0 connection mode
Connection mode is inline
slot failure mode is bypass
Redundancy status is standalone
SCE>
Related Commands
Command
|
Description
|
connection-mode
|
|
show interface linecard counters
Displays the Linecard Interface hardware counters.
show interface linecard slot-number counters [bandwidth] [cpu-utilization]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Specify any of the optional keywords to display only the desired counters.
Authorization: viewer
Examples
The following example shows the hardware counters for the Linecard Interface.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 counters
DP IP packets checksum err: 0
DP IP packets length err: 0
DP IP broadcast packets: 0
DP IP fragmented packets: 0
DP IP packets with TTL=0 err: 0
DP Non TCP/UDP packets: 0
DP TCP/UDP packets checksum err: 0
DP PPP compressed packets: 0
DP L7 Filter congested packets: 0
DP IPinIP skipped packets: 0
DP no payload packets: 53
DP L2TP control packets: 0
DP L2TP packets with offset: 0
traffic-counters information:
-----------------------------
Counter 'myCounter' value: 0 L3 bytes. Rules using it: None.
1 counters listed out of 36 available
...
SCE>
Related Commands
Command
|
Description
|
clear interface linecard
|
|
show interface linecard duplicate-packets-mode
Displays the currently configured duplicate packets mode.
show interface linecard slot-number duplicate-packets-mode
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates the use of this command:
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 duplicate-packets-mode
Packet duplication of flows due to Delay Sensitive <bundles>is enabled
Packet duplication of flows due to No-Online-Control <set-flow>is enabled
Packet duplication of flows due to No-Online-Control <set-flow>ratio percent is 70
Packet duplication in case of shortage is enabled
SCE>
Related Commands
show interface linecard external-bypass
Displays the state of the external bypass module.
show interface linecard slot-number exteranl-bypass
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following examples illustrate the use of this command.
EXAMPLE 1
The following example shows the output of this command when both external bypass modules are functioning properly.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 external-bypass
External bypass current state is `not activated'.
External bypass failure state is `activated'.
Amount of expected external bypass devices: 2
(automatically configured)
SCE>
EXAMPLE 2
The following example shows the output of this command when one external bypass module is not detected.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 external-bypass
External bypass current state is `not activated'.
External bypass failure state is `activated'.
Amount of expected external bypass devices: 2
(automatically configured)
Warning: External bypass device expected but not detected on link #1
SCE>
Related Commands
Command
|
Description
|
external-bypass
|
|
show interface linecard flow-open-mode
Displays the currently configured flow open mode.
show interface linecard slot-number flow-open-mode
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates the use of this command.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 flow-open-mode
Enhanced flow open mode is disabled
Asymmetric layer 2 support is disabled
Note that other settings may override all/part of the Enhanced Flow Open mode, e.g. VAS,
TCP no bypass est, etc.(in which cases will behave as in the classical mode)
Related Commands
Command
|
Description
|
flow-open-mode
|
|
show interface linecard ip-tunnel
Displays the current IP tunnel configuration.
show interface linecard slot-number ip-tunnel
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates the use of this command:
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 ip-tunnel
no IP tunnel
SCE>
Related Commands
Command
|
Description
|
ip tunnel
|
|
show interface linecard ip-tunnel IPinIP
Displays the current IPinIP configuration.
show interface linecard slot-number IP-tunnel IPinIP
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to use this command.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 ip-tunnel IPinIP
IPinIP skip mode is enabled
IPinIP DSCP skip mode is disabled
SCE>
Related Commands
Command
|
Description
|
ip-tunnel IPinIP skip
|
|
ip-tunnel IPinIP DSCP-marking-skip
|
|
show interface linecard l2tp
Displays the currently configured L2TP support parameters.
show interface linecard slot-number l2tp
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates the use of the show interface linecard L2TP command:
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 l2tp
L2TP identify-by port-number 1701
SCE>
Related Commands
Command
|
Description
|
l2tp identify-by
|
|
show interface linecard link mode
Displays the configured Linecard Interface link mode.
show interface linecard slot-number link mode
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the configured link mode for the Linecard Interface.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 link mode
Link mode on port1-port2
Current link mode is :forwarding
Actual link mode on active is :forwarding
Actual link mode on failure is :monopath-bypass
SCE>
Related Commands
Command
|
Description
|
link mode
|
|
show interface linecard link-to-port-mappings
Displays the link ID to port ID mappings.
show interface linecard slot-number link-to-port-mappings
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the link ID to port ID mapping for the Linecard Interface.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 link-to-port-mappings
Link Id | Upstream Port <Out>| Downstream Port <Out>
-----------------------------------------------------------
0 | 0/2 | 0/1
SCE>
Related Commands
show interface linecard mac-mapping
Displays the linecard MAC mapping information.
show interface linecard slot-number mac-mapping
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the MAC mapping information.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 mac-mapping
MAC mapping status is: disabled
MAC mapping default mapping is: none set
MAC mapping dynamic insertion to table is enabled
SCE>
Related Commands
Command
|
Description
|
show interface linecard mac-resolver arp
|
|
mac-resolver
|
|
show interface linecard mac-resolver arp
Displays a listing of all IP addresses and corresponding MAC addresses currently registered in the MAC resolver database.
show interface linecard 0 mac-resolver arp
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to display the entries in the MAC-resolver ARP database.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 mac-resolver arp
There are no entries in the mac-resolver arp database
SCE>
Related Commands
Command
|
Description
|
mac-resolver arp
|
|
show interface linecard mpls
Displays the current MPLS tunnelling configuration.
show interface linecard slot-number mpls
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates the use of this command:
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 mpls
MPLS Traffic-Engineering skip
SCE>
Related Commands
show interface linecard physically-connected-links
Displays the link mapping for the Linecard Interface.
show interface linecard slot-number physically-connected-links
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the link mapping for the Linecard Interface.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 physically-connected-links
slot 0 is connected to link-0 and link-1
SCE>
Related Commands
Command
|
Description
|
connection-mode
|
|
show interface linecard sce-url-database
Displays the contents of the protected URL database.
Can also be used to look for a specific URL and display the related flavor ID.
show interface linecard slot-number sce-url-database
show interface linecard slot-number sce-url-database url url
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
url
|
The specific URL to lookup in the sce-url-database.
|
Defaults
This command has no default settings.
Command Modes
Privileged Exec
Usage Guidelines
•
In order to display the contents of the protected URL database, it must have all protection removed and no assigned owner. If there is an assigned owner, the database is protected and cannot be displayed.
•
In order to display the flavor ID of a specific URL, the user executing the command must have lookup permission for the protected URL database.
Authorization: admin
Examples
The following example shows how to use this command
SCE>enable 10
Password:<cisco>
SCE#show interface linecard 0 sce-url-database
SCE#
Related Commands
Command
|
Description
|
sce-url-database protection
|
|
show interface linecard sce-url-database
|
|
show interface linecard sce-url-database protection
Displays the following current protected URL database protection settings:
•
owner username
•
current protection settings
•
whether a key is configured
show interface linecard slot-number sce-url-database protection
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to use this command
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 sce-url-database protection
Protection Domain BLACK_LIST_DOMAIN Status:
Domain owner:black
Read is allowed to no user
Write is allowed to user black only
Lookup is allowed to no user
Encryption key is not set
Related Commands
Command
|
Description
|
sce-url-database protection
|
|
show interface linecard sce-url-database
|
|
show interface linecard service-bandwidth-prioritization-mode
Displays the currently configured service bandwidth prioritization mode.
show interface linecard slot-number service-bandwidth-prioritization-mode
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates the use of this command:
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 service-bandwidth-prioritization-mode
Service bandwidth prioritization mode is: Subscriber Internal
SCE>
Related Commands
Command
|
Description
|
service-bandwidth-prioritization-mode
|
|
show interface linecard shutdown
Displays the current shutdown state.
show interface linecard slot-number shutdown
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the linecard Interface shutdown mode.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 shutdown
off
SCE>
Related Commands
Command
|
Description
|
shutdown
|
|
show interface linecard silent
Displays the current Linecard Interface silent state. When the silent state is Off, the linecard events reporting function is enabled.
show interface linecard slot-number silent
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the Linecard Interface silent mode.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 silent
off
SCE>
Related Commands
Command
|
Description
|
silent
|
|
show interface linecard subscriber
Displays subscribers meeting specified criteria.
show interface linecard slot-number subscriber [amount] [prefix prefix] [suffix suffix ]
[property propertyname equals|bigger-than|less-than property-val ] [all-names]
show interface linecard slot-number subscriber name subscriber-name
show interface linecard slot-number subscriber all-names
show interface linecard slot-number subscriber [amount] (prefix prefix | suffix suffix)
show interface linecard slot-number subscriber [amount] property propertyname
equals|bigger-than|less-than property-val
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
prefix
|
The desired subscriber name prefix to match.
|
suffix
|
The desired subscriber name suffix to match.
|
propertyname
|
The name of the subscriber property to match.
|
property-val
|
The value of the specified subscriber property. Specify whether to search for values equal to, greater than, or less than this value.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use this command to display names of subscribers or the number of subscribers meeting one of the following specified criteria:
•
Having a value of a subscriber property that is equal to, larger than, or smaller than a specified value
•
Having a subscriber name that matches a specific prefix
•
Having a subscriber name that matches a specific suffix
Use the amount keyword to display the number of subscribers meeting the criteria rather than listing actual subscriber names.
Use the all-names keyword to display the names of all subscribers currently in the SCE platform subscriber database.
Authorization: viewer
Examples
The following examples illustrate the use of this command.
EXAMPLE 1
Following is an example that lists the number of subscribers with the prefix `gold' in the subscriber name
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber amount prefix gold
There are 40 subscribers with name prefix 'gold'.
SCE>
EXAMPLE 2
Following is an example that lists all subscribers currently in the SCE platform subscribers database.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber all-names
There are 8 subscribers in the database.
john_doe
mary_smith
david_jones
betty_peters
bill_jackson
jane_doe
bob_white
andy_black
SCE>
Related Commands
Command
|
Description
|
subscriber name property
|
|
show interface linecard subscriber aging
Displays the subscriber aging configuration for the specified type of subscriber (anonymous or introduced).
show interface linecard slot-number subscriber aging [anonymous|introduced]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use the anonymous keyword to display the subscriber aging configuration for anonymous subscribers.
Use the introduced keyword to display the subscriber aging configuration for introduced subscribers.
Authorization: viewer
Examples
The following is an example of how to display the aging of introduced subscribers.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber aging introduced
Introduced subscriber aging is enabled.
Introduced subscriber aging time is 30 minutes.
SCE>
Related Commands
Command
|
Description
|
subscriber aging
|
|
show interface linecard subscriber anonymous
Displays the subscribers in a specified anonymous subscriber group. Use the amount form to display the number of subscribers in the group rather than a complete listing of members.
show interface linecard slot-number subscriber anonymous [amount] [name group-name ]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
group-name
|
The anonymous subscriber group.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
If no group-name is specified, all anonymous subscribers in all groups are displayed.
Authorization: viewer
Examples
The following is an example of how to display the number of subscribers in the anonymous subscriber group anon1.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber anonymous amount name anon1
SCE>
Related Commands
Command
|
Description
|
clear interface linecard subscriber
|
|
show interface linecard subscriber anonymous-group
Displays the configuration of the specified anonymous subscriber group. Use the all form with no group name to display all existing anonymous subscriber groups.
show interface linecard slot-number subscriber anonymous-group [name group-name ] [all]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
group-name
|
The anonymous subscriber group.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following is an example of how to display the anonymous subscriber groups.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber anonymous-group all
name IP range Template #
---- -------- ----------
Group1 10.10.10.10/99 0
1 anonymous groups are configured
SCE>
Related Commands
show interface linecard subscriber db counters
Displays the subscriber database counters.
show interface linecard slot-number subscriber db counters
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Counter Definitions
The following sections present definitions of the counters displayed in the output of this command.
Current values:
Subscribers: Number of currently existing subscribers (excluding subscribers waiting to be removed).
Introduced subscribers: Number of introduced subscribers.
Anonymous subscribers: Number of anonymous subscribers.
Subscribers with mappings: Number of subscribers with mappings.
Single non-VPN IP mappings: Number of mappings to single IP addresses.
Non-VPN IP Range mappings: Number of mappings to ranges of IP addresses.
VLAN based subscribers (appears only if VLAN-based subscribers are enabled): Number of VLAN based VPNs with subscribers.
Subscribers with open sessions: Number of subscribers with open flows (sessions).
SSessions mapped to the default subscriber: Number of open flows (sessions) related to the default party.
Peak values:
Peak number of subscribers with mappings:
Peak number occurred at:
Peak number cleared at:
Event counters:
Subscriber introduced: Number of login calls resulting in adding a subscriber.
Subscriber pulled: Number of pullResponse calls.
Subscriber aged: Number of aged subscribers.
Pull-request notifications sent: Number of pull request notifications sent.
State notifications sent: Number of state change notifications sent to peers.
Logout notifications sent: Number of logout events.
Examples
The following example illustrates the output for this command.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber db counters
Current values:
===============
Subscribers: 3 used out of 9999 max.
Introduced/Pulled subscribers: 3.
Anonymous subscribers: 0.
Subscribers with mappings: 3 used out of 9999 max.
Single non-VPN IP mappings: 1.
non-VPN IP Range mappings: 1.
Subscribers with open sessions: 0.
Sessions mapped to the default subscriber: 0.
Related Commands
Command
|
Description
|
clear interface linecard subscriber db counters
|
|
show interface linecard subscriber mapping
Displays subscribers whose mapping meets the specified criteria.
show interface linecard slot-number subscriber mapping [IP ipaddress/range ] [[amount]
included-in IP iprange [none]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
ip-range
|
Specified range of IP addresses.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use this command to display subscribers whose mapping meets one of the following specified criteria:
•
Matches a specified IP address or range of IP addresses (exact match of the specified range)
•
Intersects a specified IP range (not necessarily an exact match of the specified range, but with IP addresses that are within the specified range).
Use the amount keyword to display the number of subscribers meeting the criteria rather than listing actual subscriber names.
•
Has no mapping
Authorization: viewer
Examples
The following example lists the number of subscribers with no mapping.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber mapping amount none
Subscribers with no mappings:
N/A
Total 1 subscribers listed.
SCE>
Related Commands
show interface linecard subscriber max-subscribers
Displays the maximum number of subscribers. Also indicates whether the capacity options have been disabled.
show interface linecard slot-number subscriber max-subscribers
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following is an example of how to display the maximum number of subscribers when the capacity options have not been disabled. (In which case the capacity options determine the maximum number of subscribers.)
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber max-subscribers
Configured actual maximum number of subscribers: 80000.
Note, however, that Subscriber Capacity Options are enabled, and they determine the actual
maximum number of subscribers.
SCE>
Related Commands
Command
|
Description
|
subscriber max-subscribers
|
|
subscriber capacity-options
|
|
show interface linecard subscriber name
Displays information about a specified subscriber.
show interface linecard slot-number subscriber name name [mappings] [counters] [properties]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
name
|
The subscriber name.
|
mappings
|
Display subscriber mappings.
|
counters
|
Display OS counters.
|
properties
|
Display values of all subscriber properties
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
The following information can be displayed:
•
Mappings
•
OS counters (bandwidth and current number of flows)
•
All values of subscriber properties
•
All of the above
If no category is specified, a complete listing of property values, mappings and counters is displayed.
Authorization: viewer
Examples
The following is an example of how to list the mappings for the specified subscriber.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber name gold123 mappings
Subscriber 'gold123' mappings:
IP 10.0.0.0 - Expiration (sec): Unlimited
SCE>
Related Commands
Command
|
Description
|
subscriber name property
|
|
show interface linecard subscriber properties
Displays all existing subscriber properties.
show interface linecard slot-number subscriber properties
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following is an example of how to display the subscriber properties.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber properties
Subscriber properties:
"monitor" : int16, minValue=0, maxValue=1.
"new_classification_policy" : Uint16.
"packageId : Uint16, minValue=0, maxValue=4999.
"QpLimit" : int32[18].
"QpSet" : Uint8[18].
Subscriber read-only properties:
"concurrentAttacksNumber" : Uint8.
"PU_QP_QuotaSetCounter" : Uint8[18].
"PU_QP_QuotaUsageCounter" : int32[18].
"PU_REP_nonReportedSessionsInTUR" : int32.
"P_aggPeriodType" :Uint8.
"P_blockReportCounter : int32
"P_endOfAggPeriodTimestamp : Uint32.
"P_firstTimeParty" : bool.
"P_localEndOfAggPeriodTimestamp : Uint32.
"P_mibSubCounters16" : Uint16[36][2].
"P_mibSubCounters32" : Uint32[36][2].
"P_newParty" : bool.
"P_numOfRedirections : Uint8.
"P_partyCurrentPackage : Uint16
"P_partyGoOnlineTime : Uint32
"P_partyMonth : Uint16
SCE>
Related Commands
show interface linecard subscriber sm-connection-failure
Displays the current state of the SM-SCE platform connection, as well as the configured action to take in case of failure of that connection.
show interface linecard slot-number subscriber sm-connection-failure [timeout]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use the timeout keyword to display the configured SM-SCE platform link failure timeout value.
Authorization: viewer
Examples
The following examples illustrate the use of this command.
EXAMPLE 1
The following is an example of how to display the state of the SM-SCE platform connection.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber subscriber sm-connection-failure
Current SM link state: down.
Please note that this refers to the logical connection,
which means the synchronization with the SM i.e.
There might be cases where the connection at the SM will be up
and down at the SE since synchronization hasn't been completed yet.
Configured action to take when SM link is down: No action
SCE>
EXAMPLE 2
The following is an example of how to display the configured timeout value for the SM-SCE platform connection.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 subscriber subscriber sm-connection-failure timeout
SM SCE link failure timeout is: 90
SCE>
Related Commands
Command
|
Description
|
subscriber sm-connection-failure
|
|
show interface linecard subscriber templates
Displays a specified subscriber template.
show interface linecard slot-number subscriber templates [all|index template-number ]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
template-number
|
The index number of the template to be displayed.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use the all keyword to display all existing subscriber templates.
Authorization: viewer
Examples
The following is an example of how to display a specified subscriber template.
SCE>enable 5
SCE>show interface linecard 0 subscriber templates index 3
Subscriber template 3 properties
monitor=0
new_classification_policy=0
packageId=0
QpLimit[0..17]=0*17,8
QpSet[0..17]=0*17,1
SCE>
Password:<cisco>
Related Commands
show interface linecard tos-marking
Displays the current TOS marking state.
show interface linecard slot-number tos-marking
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use this command to display the current TOS marking state, including:
•
translation table
•
marking mode per interface (enable/disable)
Authorization: viewer
Examples
The following example shows a sample of the output from this command.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 tos-marking
ToS Translation Table
=====================
| tos-id | tos-value (DSCP) |
|--------|------------------|
| 1 | 00 (0x00) |
| 2 | 00 (0x00) |
| 3 | 00 (0x00) |
| 4 | 00 (0x00) |
| 5 | 00 (0x00) |
| 6 | 00 (0x00) |
| 7 | 00 (0x00) |
ToS Marking state by egress interface
=====================================
| Interface | State |
|------------|----------|
| 1 | Disabled |
| 2 | Disabled |
| 3 | Disabled |
| 4 | Disabled |
SCE>
Related Commands
Command
|
Description
|
tos-marking enabled
|
|
tos-marking clear-table
|
|
tos-marking set-table-entry
|
|
show interface linecard traffic-counter
Displays the specified traffic counter.
show interface linecard slot-number traffic-counter name [all]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
name
|
Name of the traffic counter to be displayed.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use the all keyword to display all traffic counters.
Authorization: viewer
Examples
The following example displays information for all existing traffic counters.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 traffic-counter all
Counter 'cnt' value: 0 packets. Rules using it: None.
Counter 'cnt2' value: 1284 packets. Rules using it: Rule2.
2 counters listed out of 32 available.
SCE>
Related Commands
Command
|
Description
|
traffic-counter
|
|
clear interface linecard traffic-counter
|
|
show interface linecard traffic-rule
Displays the specified traffic rule configuration.
show interface linecard slot-number traffic-rule name name |tunnel-id-mode|all
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
name
|
Name of the traffic rule to be displayed.
|
Defaults
This command has no default settings.s
Command Modes
User Exec
Usage Guidelines
Use the all keyword to display all traffic counter rules.
Use the tunnel-id-mode keyword to display all rules defined in tunnel-id-mode.
Authorization: viewer
Examples
The following example displays traffic rule information.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 traffic-rule name Rule1
0 rules listed out of 127 available.
SCE>
Related Commands
Command
|
Description
|
traffic-rule
|
|
show interface linecard virtual-links
Displays the currently configured virtual links
You can also use this command to see which virtual links have GCs whose values have been changed from the original SCA BB configuration.
show interface linecard slot-number virtual-links all
show interface linecard slot-number virtual-links changed
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0
|
Defaults
This command has no default settings.
Command Modes
User Exec.
Usage Guidelines
Use the all keyword to see all the currently configured virtual links, with their ID number and direction.
Use the changed keyword to see which virtual links have GCs for which the PIR is now different from the values configured for the template GCs via the console.
Examples
The following examples illustrate the use of this command.
Example 1
This example shows how to display all existing virtual links.
SCE>show interface LineCard 0 virtual-links all
Virtual Link enabled
Virtual link index 1 direction upstream
Virtual link index 2 direction upstream
Virtual link index 3 direction upstream
Virtual link index 4 direction upstream
Virtual link index 12 direction upstream
Virtual link index 13 direction upstream
Virtual link index 14 direction upstream
Virtual link index 15 direction upstream
Example 2
This example displays the virtual links that have GCs with values that are different from the original configuration.
SCE>show interface LineCard 0 virtual-links changed
Virtual Link enabled
Virtual link index 3 direction upstream
Global Controller index 0 timebased values = 300,300,300,300
Global Controller index 1 timebased values = 500,500,500,500
Virtual link index 12 direction upstream
Global Controller index 0 timebased values = 700,700,700,700
Virtual link index 14 direction upstream
Global Controller index 0 timebased values = 5500,5500,5500,5500
Global Controller index 1 timebased values = 1500,1500,1500,1500
Related Commands
Command
|
Description
|
virtual-links index direction
|
|
show interface linecard vlan
Displays the VLAN tunnel configuration.
show interface linecard slot-number vlan
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the VLAN configuration.
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 vlan
VLAN symmetric skip
SCE>
Related Commands
sshow interface linecard wap
Displays the current WAP handling state.
show interface linecard slot-number wap
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 0.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates how to use this command:
SCE>enable 5
Password:<cisco>
SCE>show interface linecard 0 wap
WAP handling is disabled
SCE>
Related Commands
show interface tengigabitethernet
Displays the details of a TenGigabitEthernet Interface.
show interface tengigabitethernet slot-number/bay-number/interface-number [counters
[direction ]|queue queue-number ]
Syntax Description
slot-number
|
The number of the identified slot. Enter a value of 3.
|
bay-number
|
The number of the SPA bay or sub-slot in the SCE8000-SIP module 0-3
|
interface-number
|
The TenGigabitEthernet interface number. Enter a value of 0.
|
direction
|
Optional direction specification, to show only counters of a specific direction. Use in or out.
|
queue-number
|
Number of queue, in the range 0-3
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
The counters keyword displays the values of counters of a TenGigabitEthernet line interface.
The queue keyword displays the bandwidth and burst size of a queue in a TenGigabitEthernet line interface.
Authorization: viewer
Examples
The following examples shows output of this command
EXAMPLE 1
.The following example shows how to display the inventory (UDIs) for the FRUs only.
SCE>enable 5
Password:<cisco>
SCE>show inventory
NAME: "SCE8000 Chassis", DESCR: "CISCO7604"
PID: CISCO7604 , VID: V0 , SN: FOX105108X5
NAME: "SCE8000 Service Control Module (SCM) in slot 1", DESCR: "SCE8000-SCM-E"
PID: SCE8000-SCM-E , VID: V0 , SN: CAT1122584N
NAME: "SCE8000 SPA Interface Processor (SIP) in slot 3", DESCR: "SCE8000-SIP"
PID: SCE8000-SIP , VID: V0 , SN: CAT1150G07F
NAME: "SPA-1X10GE-L-V2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE11517RMR
NAME: "SPA-1X10GE-L-V2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE11496E1P
NAME: "SPA-1X10GE-L-V2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE11517RIO
NAME: "SPA-1X10GE-L-V2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE115295HH
NAME: "SCE8000 FAN 1", DESCR: "FAN-MOD-4HS"
PID: FAN-MOD-4HS , VID: V0 , SN: DCH11013744
NAME: "SCE8000 AC or DC power supply 0", DESCR: "PWR-2700-AC/4"
PID: PWR-2700-AC/4 , VID: V0 , SN: APQ105000MV
NAME: "SCE8000 AC or DC power supply 1", DESCR: "PWR-2700-DC/4"
PID: PWR-2700-AC/4 , VID: V0 , SN: APQ105000MV
NAME: "XFP-10GLR-OC192SR ", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: AGA1142N4B7
NAME: "XFP-10GLR-OC192SR ", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: AGA1142N4AL
NAME: "XFP-10GLR-OC192SR ", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: AGA1141N43R
NAME: "XFP-10GLR-OC192SR ", DESCR: "XFP-10GLR-OC192SR "
PID: XFP-10GLR-OC192SR , VID: V02, SN: AGA1143N4JN
EXAMPLE 2
The following example shows how to display the complete inventory (UDIs) of the SCE platform.
SCE>enable 5
Password:<cisco>
SCE>show inventory raw
PID: CISCO7604 , VID: V0 , SN: FOX105108XB
NAME: "SCE8000 Physical Slot 1", DESCR: "Container SCE8000 Service Control Module (SCM)
slot"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Physical Slot 2", DESCR: "Container SCE8000 Service Control Module (SCM)
slot"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Physical Slot 3", DESCR: "Container SCE8000 SPA Interface Processor (SIP)
slot"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Physical Slot 4", DESCR: "Container SCE8000 Optical Bypass slot"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Fan Module", DESCR: "Container SCE8000 Fan Module"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 AC or DC power supply", DESCR: "Container SCE8000 AC or DC power supply"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link", DESCR: "Container SCE8000 Link"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Backplane", DESCR: "Container SCE8000 Backplane "
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Service Control Module (SCM) in slot 1", DESCR: "SCE8000-SCM-E"
PID: SCE8000-SCM-E , VID: V0 , SN: CAT1151G00Z
NAME: "SCE8000 SPA Interface Processor (SIP) in slot 3", DESCR: "SCE8000-SIP"
PID: SCE8000-SIP , VID: V0 , SN: CAT1204G020
NAME: "SCE8000 Link 0", DESCR: "SCE8000 Link"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 Link 1", DESCR: "SCE8000 Link"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 SIP bay 3/0", DESCR: "SCE8000 SIP bay"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 SIP bay 3/1", DESCR: "SCE8000 SIP bay"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 SIP bay 3/2", DESCR: "SCE8000 SIP bay"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 SIP bay 3/3", DESCR: "SCE8000 SIP bay"
PID: "" , VID: "" , SN: ""
NAME: "SPA-1X10GE-L-V2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE11485LPJ
NAME: "SPA-1X10GE-L-V2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE11485L4C
NAME: "SPA-1X10GE-L-V2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE11485L9V
NAME: "SPA-1X10GE-L-V2", DESCR: "SPA-1X10GE-L-V2"
PID: SPA-1X10GE-L-V2 , VID: V02, SN: JAE11485LAP
NAME: "TenGigabitEthernet3/0/0", DESCR: "SCE8000 SPA port"
PID: "" , VID: "" , SN: ""
NAME: "TenGigabitEthernet3/1/0", DESCR: "SCE8000 SPA port"
PID: "" , VID: "" , SN: ""
NAME: "TenGigabitEthernet3/2/0", DESCR: "SCE8000 SPA port"
PID: "" , VID: "" , SN: ""
NAME: "TenGigabitEthernet3/3/0", DESCR: "SCE8000 SPA port"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 FAN 1", DESCR: "FAN-MOD-4HS"
PID: FAN-MOD-4HS , VID: V0 , SN: DCH10511402
NAME: "SCE8000 AC or DC power supply 0", DESCR: "PWR-2700-AC/4"
PID: PWR-2700-AC/4 , VID: V0 , SN: APQ105100F8
NAME: "SCE8000 AC or DC power supply 1", DESCR: "PWR-2700-AC/4"
PID: PWR-2700-AC/4 , VID: V0 , SN: APQ105100F8
NAME: "XFP-10GZR-OC192LR ", DESCR: "XFP-10GZR-OC192LR "
PID: XFP-10GZR-OC192LR , VID: V01, SN: FNS11061SBB
NAME: "XFP-10GZR-OC192LR ", DESCR: "XFP-10GZR-OC192LR "
PID: XFP-10GZR-OC192LR , VID: V01, SN: FNS11021359
NAME: "XFP-10G-MM-SR ", DESCR: "XFP-10G-MM-SR "
PID: XFP-10G-MM-SR , VID: V01, SN: FNS12130MLQ
NAME: "XFP-10G-MM-SR ", DESCR: "XFP-10G-MM-SR "
PID: XFP-10G-MM-SR , VID: V01, SN: FNS12130MHF
NAME: "SCE8000 traffic processor 1", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 2", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 3", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 4", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 5", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 6", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 7", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 8", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 9", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 10", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 11", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
NAME: "SCE8000 traffic processor 12", DESCR: "SCE8000 traffic processor"
PID: "" , VID: "" , SN: ""
Related Commands
show inventory
Displays UDI information for the SCE platform.
show inventory [raw]
Syntax Description
This command has no arguments..
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use this command to display the following UDI information for the SCE platform:
•
Device name
•
Description
•
Product identifier
•
Version identifier
•
Serial number
Use the raw keyword to display the complete inventory of the SCE platform.
When the raw keyword is not used, only field replaceable units (FRUs) are displayed.
Authorization: viewer
Examples
The following example displays the UDI information for the SCE platform.
SCE>enable 5
Password:<cisco>
SCE>show inventory
NAME: "Chassis", DESCR: "Cisco SCE 2020 Service Control Engine, Multi Mode, 4-port GE"
PID: SCE2020-4XGBE-MM , VID: V01, SN: CAT093604K3
SCE>
Related Commands
show ip access-class
Shows the access list defined for global IP access to the SCE platform. Only IP addresses permitted access according to this access list are allowed access to the system.
show ip access-class
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the IP access class mapping.
SCE>enable 5
Password:<cisco>
SCE>show ip access-class
IP layer is using access-list # 1.
SCE>
Related Commands
Command
|
Description
|
ip access-class
|
|
show ip advertising
Shows the status of IP advertising, the configured destination and the configured interval.
show ip advertising [destination|interval]
Syntax Description
destination
|
Displays IP advertising destination.
|
interval
|
Displays the interval between ping commands
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use the form show ip advertising destination to display the IP advertising destination.
Use the form show ip advertising interval to display the interval between ping commands.
Authorization: viewer
Examples
The following example shows the IP advertising status and configuration.
SCE>enable 5
Password:<cisco>
SCE>show ip advertising
IP advertising is disabled
IP advertising destination is 10.10.10.10
IP advertising interval is 853 seconds
SCE>
Related Commands
Command
|
Description
|
ip advertising
|
|
show ip default-gateway
Shows configured default gateway.
show ip default-gateway
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example displays the default gateway.
SCE>enable 5
Password:<cisco>
SCE>show ip default-gateway
Default gateway: 10.1.1.1
SCE>
Related Commands
Command
|
Description
|
ip default-gateway
|
|
show ip filter
Displays information regarding the management interface IP filtering.
show ip filter
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use this command to display the following information for management interface IP filtering.
•
IP fragment filter enabled or disabled
•
configured attack threshold (permitted and not-permitted IP addresses)
•
configured end of attack threshold (permitted and not-permitted IP addresses)
•
burst size in seconds (permitted and not-permitted IP addresses)
Authorization: viewer
Examples
The following command shows how to display information for management interface IP filtering
SCE>enable 5
Password:<cisco>
SCE>show ip filter
is fragment filtered : 0
Input Bandwidth : 0 Kb/sec
Input packets rate : 2 Pkt/sec
Input bandwidth policer : CIR: 20000.00 Kb/sec BTime: 200 msec LP: 100 %
Input packet rate policer : CIR: 5000.00 Pkt/sec BTime: 200 msec LP: 100 %
Permit monitor :state : no_attack BW: 0
High : CIR: 20000.00 Kb/sec BTime: 10000 msec LP: 100 %
Low : CIR: 20000.00 Kb/sec BTime: 10000 msec LP: 100 %
Denied monitor :state : no_attack BW: 0
High : CIR: 20000.00 Kb/sec BTime: 10000 msec LP: 100 %
Low : CIR: 20000.00 Kb/sec BTime: 10000 msec LP: 100 %
in_bytes : 85115466
in_pkt : 371598
in_pkt_accept : 371598
in_pkt_denied : 0
drop_fragment_cnt : 0
action_delay_due_bw : 0
action_delay_due_pkt : 0
PERMIT events
meStartAttack : 0
meStopAttack : 0
DENIED events
meStartAttack : 0
SCE>
Related Commands
Command
|
Description
|
ip filter fragment
|
|
ip filter moniter
|
|
show ip radius-client
Displays the RADIUS client general configuration.
show ip radius-client
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged Exec
Usage Guidelines
Authorization: admin
Examples
The following example illustrates how to use this command.
SCE>enable 10
Password:<cisco>
SCE#show ip radius-client
SCE>
Related Commands
Command
|
Description
|
ip radius-client retry limit
|
|
show ip route
Shows the entire routing table and the destination of last resort (default-gateway). When using the prefix and mask parameters, it shows the routing entries from the subnet specified by the prefix and mask pair.
show ip route [prefix mask ]
Syntax Description
prefix
|
The prefix of the routing entries to be included.
|
mask
|
Used to limit the search of routing entries.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following examples illustrate the use of this command.
EXAMPLE 1:
The following example shows the default gateway.
SCE>enable 5
Password:<cisco>
SCE>show ip route gateway of last resort is 10.1.1.1
SCE>
EXAMPLE 2:
The following example shows retrieval of the ip route.
SCE>enable 5
Password:<cisco>
SCE>show ip route 10.1.60.0 255.255.255.0
| prefix | mask | next hop |
|--------------|--------------|--------------|
| 10.1.60.0 | 255.255.255.0 | 10.1.1.5 |
SCE>
Related Commands
Command
|
Description
|
ip route
|
|
show ip rpc-adapter
Displays the status of the RPC adapter (enabled or disabled) and the configured port.
show ip rpc-adapter [sessions]
Syntax Description
sessions
|
Display information regarding RPC adapter sessions.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the configuration of the RPC adapter.
SCE>enable 5
Password:<cisco>
SCE>show ip rpc-adapter
RPC Server is OFFLINE
RPC Server port is 14374
SCE>
Related Commands
Command
|
Description
|
ip rpc-adapter
|
|
ip rpc-adapter port
|
|
show ip ssh
Shows the status of the SSH sever, including current SSH sessions.
show ip ssh
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to retrieve the current SSH status.
SCE>enable 5
Password:<cisco>
SCE>show ip ssh
SSH server is enabled.
SSHv1 support is enabled
SSH server does not use any access-list.
There are no active SSH sessions.
SCE>
Related Commands
Command
|
Description
|
ip ssh
|
|
show line vty
Displays the Telnet configuration.
show line vty timeout|access-class in
Syntax Description
timeout
|
Shows the timeout configured to the Telnet sessions.
|
access-class in
|
Shows the access list configured to the Telnet server that contains the list of addresses that have access to the system.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the access list configured for telnet lines.
SCE>enable 5
Password:<cisco>
SCE>show line vty access-class in
Telnet server is using access-list # 1.
SCE>
Related Commands
Command
|
Description
|
line vty
|
|
show log
Displays the contents of the user log file.
show log
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates the use of this command.
SCE>enable 5
Password:<cisco>
SCE>show log
2006-01-25 00:14:46 | INFO | CPU #000 | User message files were successfully cleared, new
files were opened
2006-01-25 00:23:07 | INFO | CPU #000 | A new password was set for level 10
2006-01-25 00:49:41 | INFO | CPU #000 | System hostname changed to :ecco"
2006-01-25 01:02:41 | INFO | CPU #000 | Time zone set to GMT
2006-01-25 01:06:33 | INFO | CPU #000 | A new password was set for level 15
2006-01-25 01:08:07 | INFO | CPU #000 | A new password was set for level 5
2006-01-25 01:23:07 | INFO | CPU #000 | IP address of slot 0, port 0 set to 10.10.10
2006-01-25 01:56:44 | INFO | CPU #000 | Configuration file '/system/config.txt' was saved
- file size 1200
2006-01-25 05:34:45 | INFO | CPU #000 | A telnet session from 20.20.20.20 was established
SCE>
Related Commands
Command
|
Description
|
clear logger
|
|
logger get user-log file-name
|
|
more user-log
|
|
show logger device
Displays the configuration of the specified SCE platform logger file. Also displays the current user log counters.
show logger device {line-attack-file-log |
user-file-log[counters|max-file-size|status|nv-counters]}
Syntax Description
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Specify the desired logger device:
•
Line-Attack-File-Log : displays the following information:
–
Status
–
Maximum file size
•
User-File-Log: displays the following information:
–
Status
–
Maximum file size
If you specify User-File-Log, you can specify one of the following options:
•
counters: Displays the User-File-Log counters
•
max-file-size: Displays the currently configures maximum file size for the User-File-Log
•
nv-counters: Displays the User-File-Log non-volatile counters
•
status: Displays the current status of the User-File-Log
Authorization: viewer
Examples
The following examples illustrate the use of this command.
EXAMPLE 1
The following example shows the SCE platform Line-Attack-File-Log status and configuration.
SCE>enable 5
Password:<cisco>
SCE>show logger device Line-Attack-File-Log
Line-Attack-File-Log status: Enabled
Line-Attack-File-Log file size: 1000000
SCE>
EXAMPLE 2
The following example shows the SCE platform User-File-Log counters.
SCE>enable 5
Password:<cisco>
SCE>show logger device line-attack-file-log counters
device User-File-Log counters
Total info messages: 62
Total warning messages: 4
Total error messages: 0
Total fatal messages: 0
Last time these counters were cleared: 02:23:27 GMT TUES January 17 2006
SCE>
Related Commands
Command
|
Description
|
logger device
|
|
clear logger
|
|
show management-agent
Displays information regarding the management agent.
show management-agent
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use this command to display the following information for the management agent:
•
status (enabled or disabled)
•
access control list number assigned
Authorization: viewer
Examples
The following example shows how to display the information for the management-agent.
SCE>enable 5
Password:<cisco>
SCE>show management-agent
management agent is enabled.
management agent is active, version: SCE Agent 3.0.3 Build 15
management agent does not use any access-list.
SCE>
Related Commands
Command
|
Description
|
management-agent access-class
|
|
service management-agent
|
|
show management-agent sce-api quota
Displays information relating to the quota message buffer.
show management-agent sce-api quota
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use this command to display the following information:
•
Quota rate control
•
Maximum size of the quota message buffer
•
Number of messages currently in the quota message buffer, waiting to be sent to the QM
Authorization: viewer
Examples
The following example shows how to display the information for the management-agent.
SCE>enable 5
Password:<cisco>
SCE>show management-agent sce-api quota
Quota rate control : 125
Quota max buffer size : 1000
Related Commands
Command
|
Description
|
management-agent sce-api quota-buffer-size
|
|
show pqi file
Displays information, such as installation options, about the specified application file.
show pqi file filename info
Syntax Description
filename
|
The filename of the desired application file.
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to display application file information.
SCE>enable 5
Password:<cisco>
SCE>show pqi file myfile.pqi info
application: sm
description: SCE 1000 sm
target SCE : SCE 1000
module names: sm20001.pm0
SCE>
Related Commands
Command
|
Description
|
pqi install file
|
|
show pqi last-installed
Displays the name of the last pqi file that was installed.
show pqi last-installed
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows how to find out what pqi file is installed.
SCE>enable 5
Password:<cisco>
SCE>show pqi last-installed
package name: SACS BB
package version 3.0.1. build 02
package date: Tue Jun 10 17:27:55 GMT+00:00 2006
operation: Upgrade
SCE>
Related Commands
Command
|
Description
|
pqi rollback file
|
|
pqi uninstall file
|
|
show rdr-formatter
Displays the RDR formatter configuration.
show rdr-formatter
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the configuration of the RDR formatter.
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter
Status: enabled
Connection is: down
Forwarding mode: redundancy
Connection table:
----------------------------------------------------------
Collector | Port | Status | Priority per Category: |
IP Address / | | |--------------------------|
Host-Name | | | Category1 | Category2 |
----------------------------------------------------------
10.1.1.205 |33000 | Down | 100 | 100 |
10.1.1.206 |33000 | Down | 60 | 60 |
10.12.12.12 |33000 | Down | 40 | 40 |
----------------------------------------------------------
RDR: queued: 0, sent:4460807, thrown: 0, format-mismatch:0
UM: queued: 0, sent: 0, thrown: 0
Logger: queued: 0, sent: 39, thrown: 0
Errors: thrown: 0
Last time these counters were cleared: 20:23:05 IST WED March 14 2007
SCE>
Related Commands
Command
|
Description
|
rdr-formatter destination
|
|
service rdr-formatter
|
|
show rdr-formatter connection-status
Displays information regarding the RDR formatter connections.
show rdr-formatter connection-status
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Displays the following information regarding the RDR formatter connections:
•
main connection
•
status: status and forwarding mode connection table with the following information for each destination:
–
port
–
status
–
priority
Authorization: viewer
Examples
The following example shows the RDR formatter connection status.
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter connection-status
Connection is: up
Forwarding mode: redundancy
Connection table:
----------------------------------------------------------
Collector | Port | Status | Priority per Category: |
IP Address / | | |--------------------------|
Host-Name | | | Category1 | Category2 |
----------------------------------------------------------
10.1.1.205 |33000 | Up | 100 primary | 100 primary|
10.1.1.206 |33000 | Down | 60 | 60 |
10.12.12.12 |33000 | Up | 40 | 40 |
----------------------------------------------------------
SCE>
Related Commands
Command
|
Description
|
show rdr-formatter
|
|
show rdr-formatter counters
|
|
show rdr-formatter destination
|
|
show rdr-formatter enabled
|
|
show rdr-formatter forwarding-mode
|
|
show rdr-formatter history-size
|
|
show rdr-formatter protocol NetflowV9 dscp
|
|
show rdr-formatter rdr-mapping
|
|
show rdr-formatter statistics
|
|
show rdr-formatter counters
Displays the RDR formatter counters.
show rdr-formatter counters
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the RDR-formatter counters.
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter counters
RDR: queued: 0, sent:4460807, thrown: 0, format-mismatch:0
UM: queued: 0, sent: 0, thrown: 0
Logger: queued: 0, sent: 39, thrown: 0
Last time these counters were cleared: 20:23:05 IST WED March 14 2007
SCE>
Related Commands
Command
|
Description
|
show rdr-formatter
|
|
show rdr-formatter connection-status
|
|
show rdr-formatter destination
|
|
show rdr-formatter enabled
|
|
show rdr-formatter forwarding-mode
|
|
show rdr-formatter history-size
|
|
show rdr-formatter protocol NetflowV9 dscp
|
|
show rdr-formatter rdr-mapping
|
|
show rdr-formatter statistics
|
|
show rdr-formatter destination
Displays the RDR formatter destinations, including protocol and transport type.
show rdr-formatter destination
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the configured RDRv1 formatter destinations.
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter destination
Destination: 10.56.201.50
Port: 33000
Protocol: RDRv1
Destination: 10.56.204.7
Port: 33000
Protocol: NetflowV9
Destination: 10.56.204.10
Port: 33000
Protocol: RDRv1
SCE>
Related Commands
Command
|
Description
|
rdr-formatter destination
|
|
show rdr-formatter
|
|
show rdr-formatter connection-status
|
|
show rdr-formatter counters
|
|
show rdr-formatter enabled
|
|
show rdr-formatter forwarding-mode
|
|
show rdr-formatter history-size
|
|
show rdr-formatter protocol NetflowV9 dscp
|
|
show rdr-formatter rdr-mapping
|
|
show rdr-formatter statistics
|
|
show rdr-formatter enabled
Shows the RDR-formatter status (enabled/disabled).
show rdr-formatter enabled
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows that the RDR formatter is enabled.
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter enabled
Status: enabled
SCE>
Related Commands
Command
|
Description
|
service rdr-formatter
|
|
show rdr-formatter
|
|
show rdr-formatter connection-status
|
|
show rdr-formatter counters
|
|
show rdr-formatter destination
|
|
show rdr-formatter forwarding-mode
|
|
show rdr-formatter history-size
|
|
show rdr-formatter rdr-mapping
|
|
show rdr-formatter statistics
|
|
show rdr-formatter forwarding-mode
Shows the configured RDR-formatter forwarding-mode (redundancy/multicast/simple load balancing).
show rdr-formatter forwarding-mode
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the RDR formatter forwarding-mode.
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter forwarding-mode
Forwarding mode: redundancy
SCE>
Related Commands
Command
|
Description
|
rdr-formatter forwarding-mode
|
|
show rdr-formatter
|
|
show rdr-formatter connection-status
|
|
show rdr-formatter counters
|
|
show rdr-formatter destination
|
|
show rdr-formatter enabled
|
|
show rdr-formatter history-size
|
|
show rdr-formatter rdr-mapping
|
|
show rdr-formatter statistics
|
|
show rdr-formatter history-size
Shows the configured size of the RDR formatter history buffer.
show rdr-formatter history-size
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the size of the RDR formatter history buffer.
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter history-size
History buffer size: 16000 bytes
SCE>
Related Commands
Command
|
Description
|
rdr-formatter history-size
|
|
show rdr-formatter
|
|
show rdr-formatter connection-status
|
|
show rdr-formatter counters
|
|
show rdr-formatter destination
|
|
show rdr-formatter enabled
|
|
show rdr-formatter forwarding-mode
|
|
show rdr-formatter rdr-mapping
|
|
show rdr-formatter statistics
|
|
show rdr-formatter protocol NetflowV9 dscp
Displays the NetflowV9 assigned DSCP value.
show rdr-formatter protocol NetflowV9 dscp
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example illustrates the use of this command.
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter protocol NetflowV9 dscp
Configured DSCP for Netflow traffic: 0
SCE>
Related Commands
Command
|
Description
|
rdr-formatter protocol NetflowV9 dscp
|
|
show rdr-formatter
|
|
show rdr-formatter connection-status
|
|
show rdr-formatter counters
|
|
show rdr-formatter destination
|
|
show rdr-formatter statistics
|
|
show rdr-formatter rdr-mapping
Shows to which RDR formatter category a specified RDR tag is mapped.
show rdr-formatter rdr-mapping all|tag-ID
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use the all keyword to display all current RDR-category mappings.
Authorization: viewer
Examples
The following example illustrates the use of this command, showing partial output:
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter rdr-mapping all
Tag Categories
--- ----------
0xb2d05e01 1
0xb2d05e02 1
0xb2d05e04 1
0xb2d05e05 1
0xf0f0f000 1
0xf0f0f002 1
0xf0f0f004 1
0xf0f0f005 1
0xf0f0f010 1
0xf0f0f016 1
0xf0f0f017 1
0xf0f0f018 1
---More---
SCE>
Related Commands
Command
|
Description
|
rdr-formatter rdr-mapping
|
|
show rdr-formatter
|
|
show rdr-formatter counters
|
|
show rdr-formatter destination
|
|
show rdr-formatter enabled
|
|
show rdr-formatter forwarding-mode
|
|
show rdr-formatter history-size
|
|
show rdr-formatter statistics
|
|
show rdr-formatter statistics
Displays RDR formatter statistics.
show rdr-formatter statistics
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Use this command to display the following RDR formatter statistics:
•
Rates and counters per connection
•
Protocol and transport attributes for each connection
•
For Netflow destinations only:
–
Number of templates sent
–
Number of records sent
Authorization: viewer
Examples
The following example shows the current RDR statistics.
SCE>enable 5
Password:<cisco>
SCE>show rdr-formatter statistics
RDR-formatter statistics:
=========================
Category 1:
sent: 1794517
in-queue: 0
thrown: 0
format-mismatch: 0
unsupported-tags: 1701243
rate: 2 RDRs per second
max-rate: 64 RDRs per second
Category 2:
sent: 12040436
in-queue: 0
thrown: 0
format-mismatch: 0
unsupported-tags: 0
rate: 12 RDRs per second
max-rate: 453 RDRs per second
Category 3:
sent: 0
in-queue: 0
thrown: 0
format-mismatch: 0
unsupported-tags: 0
rate: 0 RDRs per second
max-rate: 0 RDRs per second
Category 4:
sent: 0
in-queue: 0
thrown: 0
format-mismatch: 0
unsupported-tags: 0
rate: 0 RDRs per second
max-rate: 0 RDRs per second
Destination: 10.56.201.50 Port: 33000 Status: up
Sent: 13835366
Rate: 211 Max: 679
Last connection establishment: 17 hours, 5 minutes, 14 seconds
Destination: 10.56.204.7 Port: 33000 Status: up
Sent: 12134054
Rate: 183 Max: 595
Sent Templates: 13732
Sent Data Records: 12134054
Refresh Timeout (Sec): 5
Last connection establishment: 17 hours, 5 minutes, 15 seconds
SCE>
Related Commands
Command
|
Description
|
show rdr-formatter
|
|
show rdr-formatter connection-status
|
|
show rdr-formatter counters
|
|
show rdr-formatter destination
|
|
show rdr-formatter enabled
|
|
show rdr-formatter forwarding-mode
|
|
show rdr-formatter history-size
|
|
show rdr-formatter protocol NetflowV9 dscp
|
|
show rdr-formatter rdr-mapping
|
|
show running-config
Shows the current configuration.
show running-config [all-data]
Syntax Description
all data
|
Displays defaults as well as non-default settings.
|
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Use the all data keyword to see sample usage for many CLI configuration commands.
Authorization: admin
Examples
The following example shows the output of the show running-config command.
SCE>enable 10
Password:<cisco>
SCE#>show running-config all-data
#This is a general configuration file (running-config).
#Created on 12:06:13 UTC SUN May 11 2008
#cli-type 1
#version 1
no management-agent notifications notification-list
1417,1418,804,815,1404,1405,1406,1407,1408,400
no management-agent notifications notification-list
402,421,440,441,444,445,446,450,437,457
no management-agent notifications notification-list 3593,3594,3595,10040
snmp-server community "public" ro
RDR-formatter forwarding-mode multicast
RDR-formatter destination 10.56.96.26 port 33000 category number 1 priority 100
RDR-formatter destination 10.56.96.26 port 33000 category number 2 priority 100
RDR-formatter destination 10.56.96.26 port 33000 category number 3 priority 100
RDR-formatter destination 10.56.96.26 port 33000 category number 4 priority 100
interface LineCard 0
connection-mode inline on-failure external-bypass
no silent
no shutdown
attack-filter subscriber-notification ports 80
replace spare-memory code bytes 3145728
interface GigabitEthernet 1/1
ip address 10.56.96.46 255.255.252.0
interface TenGigabitEthernet 3/0/0
bandwidth 10000000 burst-size 50000
global-controller 0 name "Default Global Controller"
interface TenGigabitEthernet 3/1/0
bandwidth 10000000 burst-size 50000
global-controller 0 name "Default Global Controller"
interface TenGigabitEthernet 3/2/0
bandwidth 10000000 burst-size 50000
global-controller 0 name "Default Global Controller"
interface TenGigabitEthernet 3/3/0
bandwidth 10000000 burst-size 50000
global-controller 0 name "Default Global Controller"
exit
ip default-gateway 10.56.96.1
line vty 0 4
exit
management-agent property "com.pcube.management.framework.install.activation.operation"
"Install"
management-agent property "com.pcube.management.framework.install.activated.package" "SCA
BB"
management-agent property "com.pcube.management.framework.install.activated.version"
"3.1.6 build 79"
management-agent property "com.pcube.management.framework.install.activation.date" "Sun
May 11 08:44:04 GMT+00:00 2008"
flow-filter partition name "ignore_filter" first-rule 4 num-rules 32
flow-filter partition name "udpPortsToOpenBySw" first-rule 40 num-rules 21
SCE#
Related Commands
show scmp
Displays the SCMP (ISG) general configuration and status.
show scmp [all | name name ] [counters]
Syntax Description
name
|
Display configuration or counters for the specified destination (SCMP peer device).
|
Defaults
This command has no default settings.
Command Modes
Privileged Exec
Usage Guidelines
You can display configuration for a specified destination by using the name argument. Use the all keyword to display configuration for all destinations.
Use the counters keyword to display the statistics per destination. For this option, you must either specify the desired destination, using the name argument, or use the all keyword to display statistics for all destinations.
Authorization: admin
Examples
The following example illustrates how to display the SCMP counters for a specified destination.
SCE>enable 10
Password:<cisco>
SCE#show scmp name scmp_peer1 counters
SCMP Connection 'scmp_peer1' counters:
Total messages sent: 72
Total messages received: 72
Establish requests sent: 1
Establish replies received: 1
Accounting requests sent: 20
Accounting replies received: 20
Subscriber queries sent: 0
Subscriber query response recv: 0
Request retry exceeded: 0
Requests replied with errors: 0
Subscriber requests received: 50
Subscriber responses sent: 50
Failed Requests: 0
Keep-alive sent: 1
Keep-alive received: 1
SCE>
Related Commands
Command
|
Description
|
clear scmp name counters
|
|
scmp
|
|
show snmp
Displays the SNMP configuration and counters.
show snmp
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the SNMP server configuration and statistics.
SCE>enable 5
Password:<cisco>
SCE>show snmp
SNMP server status: Enabled
Location: London_Office
Contact: Brenda
Authentication Trap Status: Enabled
Communities:
------------
Community: public, Access Authorization: RO, Access List Index: 1
Trap managers:
------------
Trap host: 10.1.1.205, community: public, version: SNMPv2c
SNMP stats:
29 SNMP packets input
0 Bad SNMP version errors
29 Unknown community name
0 Illegal operation for community name supplied
0 Encoding errors
0 Number of requested variables
0 Number of altered variables
0 Get-request PDUs
0 Get-next PDUs
0 Set-request PDUs
29 SNMP packets output
0 Too big errors
0 No such name errors
0 Bad values errors
0 General errors
0 Response PDUs
29 Trap PDUs
SCE>
Related Commands
Command
|
Description
|
show snmp community
|
|
show snmp contact
|
|
show snmp enabled
|
|
show snmp host
|
|
show snmp location
|
|
show snmp community
Displays configured communities.
show snmp community
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the SNMP manager communities.
SCE>enable 5
Password:<cisco>
SCE>show snmp community
Community: public, Access Authorization: RO,
Access List Index: 1
SCE>
Related Commands
Command
|
Description
|
snmp-server community
|
|
show snmp
|
|
show snmp contact
Displays the configured MIB-2 variable sysContact.
show snmp contact
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the system contact.
SCE>enable 5
Password:<cisco>
SCE>show snmp contact
Contact: Brenda@mycompany.com
SCE>
Related Commands
Command
|
Description
|
snmp-server contact
|
|
show snmp
|
|
show snmp enabled
Displays the SNMP agent status (enabled/disabled).
show snmp enabled
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the SNMP server enabled status.
SCE>enable 5
Password:<cisco>
SCE>show snmp enabled
SNMP server status: Enabled
SCE>
Related Commands
Command
|
Description
|
snmp-server
|
|
show snmp
|
|
show snmp host
Displays the destination hosts for SNMP traps.
show snmp host
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the destination hosts for SNMP traps.
SCE>enable 5
Password:<cisco>
SCE>show snmp host
Trap host: 10.1.1.205, community: public, version: SNMPv2c
SCE>
Related Commands
Command
|
Description
|
snmp-server host
|
|
show snmp
|
|
show snmp location
Displays the configured MIB-2 variable sysLocation.
show snmp location
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the system location.
SCE>enable 5
Password:<cisco>
SCE>show snmp location
Location: London_Office
SCE>
Related Commands
Command
|
Description
|
snmp-server location
|
|
show snmp
|
|
show snmp mib
Displays MIB variables.
show snmp mib mib variables
Syntax Description
mib
|
Name of MIB to display.
MIB-II
pcube-SE-MIB
|
variables
|
Name of group to display.
MIB-II : Use one of the following values: AT, ICMP, interfaces, IP, SNMP, system, TCP or UDP.
pcube-SE-MIB: Use one of the following values: application, chassis, disk, global-controller, link, logger, module, port, rdr-formatter, subscriber, system, traffic-counters, tx-queue
|
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the MIB-2 system group.
SCE>enable 5
Password:<cisco>
SCE>show snmp mib MIB-II system
sysDescr.0 = CiSco Service Engineering,
SW version: Control Card Version 1.30 build 29,
HW version: SCE GE "RevE"
sysObjectID.0 = 1.3.6.1.4.1.5655.1.2
sysUpTime.0 = 14 hours, 25 minutes, 59 seconds
sysContact.0 = Brenda@mycompany.com
sysName.0 = SCE sysLocation.0 = London_Office
sysServices.0 = 2
SCE>
Related Commands
show snmp traps
Displays the SNMP traps generation status (enabled/disabled).
show snmp traps
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the SNMP server traps status.
SCE>enable 5
Password:<cisco>
SCE>show snmp traps
Authentication-failure trap status: Disabled
operational-status traps status: Enabled
system-reset trap status: Enabled
chassis traps status: Enabled
RDR-formatter traps status: Enabled
Telnet traps status: Enabled
logger traps status: Enabled
SNTP traps status: Enabled
link-bypass traps status: Enabled
subscriber traps status: Enabled
pull-request-failure traps status: Disabled
attack traps status: Enabled
port-operational-status traps status: Enable
SCE>
Related Commands
Command
|
Description
|
snmp-server enable traps
|
|
show startup-config
Shows the startup configuration file. Use this command to review the configuration used by the SCE platform at boot time in comparison with the current configuration to make sure that you approve of all the differences before saving the configuration by using copy running-config startup-config command.
show startup-config
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Usage Guidelines
Use this command to review the configuration used by the SCE platform at boot time in comparison with the current configuration, to make sure that you approve of all the differences before saving the configuration (use the copy running-config startup-config command to save the configuration).
Authorization: admin
Examples
The following example shows a sample output.
SCE>enable 10
Password:<cisco>
SCE#show startup-config
#Created on 12:06:13 UTC SUN May 11 2008
#cli-type 1
#version 1
no management-agent notifications notification-list
1417,1418,804,815,1404,1405,1406,1407,1408,400
no management-agent notifications notification-list
402,421,440,441,444,445,446,450,437,457
no management-agent notifications notification-list 3593,3594,3595,10040
snmp-server community "public" ro
RDR-formatter forwarding-mode multicast
RDR-formatter destination 10.56.96.26 port 33000 category number 1 priority 100
RDR-formatter destination 10.56.96.26 port 33000 category number 2 priority 100
RDR-formatter destination 10.56.96.26 port 33000 category number 3 priority 100
RDR-formatter destination 10.56.96.26 port 33000 category number 4 priority 100
interface LineCard 0
connection-mode inline on-failure external-bypass
no silent
no shutdown
attack-filter subscriber-notification ports 80
replace spare-memory code bytes 3145728
interface GigabitEthernet 1/1
ip address 10.56.96.46 255.255.252.0
interface TenGigabitEthernet 3/0/0
bandwidth 10000000 burst-size 50000
global-controller 0 name "Default Global Controller"
interface TenGigabitEthernet 3/1/0
bandwidth 10000000 burst-size 50000
global-controller 0 name "Default Global Controller"
interface TenGigabitEthernet 3/2/0
bandwidth 10000000 burst-size 50000
global-controller 0 name "Default Global Controller"
interface TenGigabitEthernet 3/3/0
bandwidth 10000000 burst-size 50000
global-controller 0 name "Default Global Controller"
exit
ip default-gateway 10.56.96.1
line vty 0 4
exit
management-agent property "com.pcube.management.framework.install.activation.operation"
"Install"
management-agent property "com.pcube.management.framework.install.activated.package" "SCA
BB"
management-agent property "com.pcube.management.framework.install.activated.version"
"3.1.6 build 79"
management-agent property "com.pcube.management.framework.install.activation.date" "Sun
May 11 08:44:04 GMT+00:00 2008"
flow-filter partition name "ignore_filter" first-rule 4 num-rules 32
flow-filter partition name "udpPortsToOpenBySw" first-rule 40 num-rules 21
SCE#
Related Commands
show system operation-status
Displays the operation status of the system.
show system operation-status
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the system operation status:
SCE>enable 5
Password:<cisco>
SCE>show system operation-status
System Operation status is Operational
SCE>
Related Commands
show system-uptime
Displays the length of time the system has been running since the last reboot..
show system-uptime
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the system uptime for the SCE platform.
SCE>enable 5
Password:<cisco>
SCE>show system-uptime
SCE uptime is 4 days, 13 hours, 21 minutes, 37 seconds
SCE>
Related Commands
show tacacs
Displays statistics for the TACACS+ servers.
show tacacs [all]
Syntax Description
This command has no arguments.
Defaults
This command has no default settings.
Command Modes
User Exec
The 'all' option is available only at the Privileged Exec level.
Use the 'all' keyword to display keys and timeouts as well as other statistics.
Usage Guidelines
Note that, although most show commands are accessible to viewer level users, the 'all' option is available only at the admin level. Use the command ' enable 10 ' to access the admin level.
Authorization: viewer
The ' all ' option is at the admin authorization level.
Examples
The following examples illustrate how to use this command.
EXAMPLE 1
This example shows how to display statistics for all TACACS+ servers.
SCE>enable 5
Password:<cisco>
SCE>show tacacs
Server: 100.10.10.10./49: opens=0 closes=0 error=0
messages in=0 messages out=0
SCE>
EXAMPLE 2
This example shows how to display statistics, including keys and timeouts, for all TACACS+ servers.
SCE>enable 10
Password:<cisco>
SCE# show tacacs all
Server: 100.10.10.10./49: opens=0 closes=0 error=0
messages in=0 messages out=0
timeout=20
uses default timeout= yes
key= a
uses default key= no
SCE#
Related Commands
Command
|
Description
|
tacacs-server host
|
|
tacacs-server key
|
|
tacacs-server timeout
|
|
show telnet sessions
Displays any active Telnet sessions.
show telnet sessions
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows that there is one active Telnet session.
SCE>enable 5
Password:<cisco>
SCE>show telnet sessions
There is 1 active telnet session:
Index | Source
================
0 | 10.1.1.201
SCE>
Related Commands
Command
|
Description
|
telnet
|
|
show telnet status
|
|
show telnet status
Displays the status of the telnet server daemon.
show telnet status
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows that the telnet daemon is currently enabled.
SCE>enable 5
Password:<cisco>
SCE>show telnet status
Telnet daemon is enabled.
SCE>
Related Commands
Command
|
Description
|
service telnetd
|
|
show telnet sessions
|
|
show timezone
Displays the current time zone and daylight saving time configuration as configured by the user.
show timezone
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the time zone configured by the user.
SCE>enable 5
Password:<cisco>
SCE>show timezone
Time zone: ISR minutes offset from UTC: 120
SCE>
Related Commands
Command
|
Description
|
clock timezone
|
|
show users
Displays the users in the local database, including passwords.
show users
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privilege Exec
Usage Guidelines
Note that, although most show commands are accessible to viewer level users, this command is available only at the admin level. Use the command ' enable 10 ' to access the admin level.
Authorization: admin
Examples
This example shows how to display the users in the local database.
SCE>enable 10
Password:<cisco>
SCE# show users
User: name = Joe
privilege level = 10
password = joespwd
is password encrypted = no
SCE#
Related Commands
Command
|
Description
|
username
|
|
username privilege
|
|
show version
Displays the configuration information for the system including the hardware version, the software version, the application used, and other configuration information.
show version
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the current version information of the SCE platform.
SCE>enable 5
Password:<cisco>
SCE>show version
SCE>show version
System version: Version 3.1.6S Build 279
Build time: Jun 10 2008, 19:27:47 (Change-list 335658)
Software version is: Version 3.1.6S Build 279
Hardware information is:
----------------
Firmware
----------------
kernel : [kernel] 1.0.0/5 (inactive: [kernel] 1.0.0/5)
u-boot : [uboot] 1.0.0/6 (field: [uboot] 0.8.1/13)
select : [ubs-cf1] 1.0.0/5 (secondary: [ubs-cf1] 1.0.0/5)
----------------
Slot 1: SCM-8000
----------------
serial-num : CAT1202G07D
part-num : 73-10598-01 38
cpld : 0x8162
vtpld : 0xc001
summit-0 : 0x10008
summit-1 : 0x10008
dpt/tx : 0x4837
cls/ff : 0x2047
cls flow cap: 33554432
----------------
TVR
----------------
#cpus : 1
cpu SVR : 0x80900120
cpu PVR : 0x80040202
cpu freq : 1000MHz
cpu (eeprom): 2.1, 1000MHz
cpld : 0xa1b7
cpld-ufm : 0xa803
summit : 0x10007
cf : Model=SMART CF, FwRev=0x20060811, Size=4062240KB
----------------
CFC-0
----------------
board type : P2
#cpus : 3
cpu-0 SVR : 0x80900121
cpu-0 PVR : 0x80040202
cpu-0 freq : 1500MHz
cpu-1 SVR : 0x80900121
cpu-1 PVR : 0x80040202
cpu-1 freq : 1500MHz
cpu-2 SVR : 0x80900121
cpu-2 PVR : 0x80040202
cpu-2 freq : 1500MHz
cpu (eeprom): 2.1, 1500MHz
cpld-0 : 0xb20e
cpld-1 : 0xb20e
cpld-2 : 0xb20e
cpld-0-ufm : 0xb803
cpld-1-ufm : 0xb803
cpld-2-ufm : 0xb803
summit-0 : 0x1000a
summit-1 : 0x1000a
fc : 0x1044
----------------
CFC-1
----------------
board type : P2
#cpus : 3
cpu-0 SVR : 0x80900121
cpu-0 PVR : 0x80040202
cpu-0 freq : 1500MHz
cpu-1 SVR : 0x80900121
cpu-1 PVR : 0x80040202
cpu-1 freq : 1500MHz
cpu-2 SVR : 0x80900121
cpu-2 PVR : 0x80040202
cpu-2 freq : 1500MHz
cpu (eeprom): 2.1, 1500MHz
cpld-0 : 0xb20e
cpld-1 : 0xb20e
cpld-2 : 0xb20e
cpld-0-ufm : 0xb803
cpld-1-ufm : 0xb803
cpld-2-ufm : 0xb803
summit-0 : 0x1000a
summit-1 : 0x1000a
fc : 0x1044
----------------
Slot 3: SIP-8000
----------------
serial-num : CAT1204G01H
part-num : 73-10947-01
cpld : 0x9162
summit-0 : 0x10006
summit-1 : 0x10006
dpt-0 : 0x3033
dpt-1 : 0x3033
spa[0] : SPA-1X10GE-L-V2
spa[1] : SPA-1XTENGE-XFP
spa[2] : SPA-1X10GE-L-V2
spa[3] : SPA-1XTENGE-XFP
----------------
SCE8000 Chassis
----------------
product-num : CISCO7604
serial-num : FOX10420BKZ
part-num : 73-9789-02
part-rev : A0
vid : V01
Part number: 73-10598-01 38
Revision:
Software revision:
LineCard S/N : CAT1202G07D
Power Supply type: AC
SML Application information is:
No application is configured.
Logger status: Enabled
Platform: SCE8000 - 4x10GBE
Management agent interface version: SCE Agent 3.1.6 Build 134
Software package file: ftp://ftpserver/simba.pkg
SCE8000 uptime is 9 minutes, 54 seconds
Related Commands
Command
|
Description
|
show version all
|
|
show version software
|
|
show version all
Displays the complete version information as well as the running configuration for all components.
show version all
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows version and configuration information for all the system components.
SCE>enable 5
Password:<cisco>
SCE>show version all
SSystem version: Version 3.1.6S Build 279
Build time: Jun 10 2008, 19:27:47 (Change-list 335658)
Software version is: Version 3.1.6S Build 279
Hardware information is:
----------------
Firmware
----------------
kernel : [kernel] 1.0.0/5 (inactive: [kernel] 1.0.0/5)
u-boot : [uboot] 1.0.0/6 (field: [uboot] 0.8.1/13)
select : [ubs-cf1] 1.0.0/5 (secondary: [ubs-cf1] 1.0.0/5)
----------------
Slot 1: SCM-8000
----------------
serial-num : CAT1202G07D
part-num : 73-10598-01 38
cpld : 0x8162
vtpld : 0xc001
summit-0 : 0x10008
summit-1 : 0x10008
dpt/tx : 0x4837
cls/ff : 0x2047
cls flow cap: 33554432
----------------
TVR
----------------
#cpus : 1
cpu SVR : 0x80900120
cpu PVR : 0x80040202
cpu freq : 1000MHz
cpu (eeprom): 2.1, 1000MHz
cpld : 0xa1b7
cpld-ufm : 0xa803
summit : 0x10007
cf : Model=SMART CF, FwRev=0x20060811, Size=4062240KB
----------------
CFC-0
----------------
board type : P2
#cpus : 3
cpu-0 SVR : 0x80900121
cpu-0 PVR : 0x80040202
cpu-0 freq : 1500MHz
cpu-1 SVR : 0x80900121
cpu-1 PVR : 0x80040202
cpu-1 freq : 1500MHz
cpu-2 SVR : 0x80900121
cpu-2 PVR : 0x80040202
cpu-2 freq : 1500MHz
cpu (eeprom): 2.1, 1500MHz
cpld-0 : 0xb20e
cpld-1 : 0xb20e
cpld-2 : 0xb20e
cpld-0-ufm : 0xb803
cpld-1-ufm : 0xb803
cpld-2-ufm : 0xb803
summit-0 : 0x1000a
summit-1 : 0x1000a
fc : 0x1044
----------------
CFC-1
----------------
board type : P2
#cpus : 3
cpu-0 SVR : 0x80900121
cpu-0 PVR : 0x80040202
cpu-0 freq : 1500MHz
cpu-1 SVR : 0x80900121
cpu-1 PVR : 0x80040202
cpu-1 freq : 1500MHz
cpu-2 SVR : 0x80900121
cpu-2 PVR : 0x80040202
cpu-2 freq : 1500MHz
cpu (eeprom): 2.1, 1500MHz
cpld-0 : 0xb20e
cpld-1 : 0xb20e
cpld-2 : 0xb20e
cpld-0-ufm : 0xb803
cpld-1-ufm : 0xb803
cpld-2-ufm : 0xb803
summit-0 : 0x1000a
summit-1 : 0x1000a
fc : 0x1044
----------------
Slot 3: SIP-8000
----------------
serial-num : CAT1204G01H
part-num : 73-10947-01
cpld : 0x9162
summit-0 : 0x10006
summit-1 : 0x10006
dpt-0 : 0x3033
dpt-1 : 0x3033
spa[0] : SPA-1X10GE-L-V2
spa[1] : SPA-1XTENGE-XFP
spa[2] : SPA-1X10GE-L-V2
spa[3] : SPA-1XTENGE-XFP
----------------
SCE8000 Chassis
----------------
product-num : CISCO7604
serial-num : FOX10420BKZ
part-num : 73-9789-02
part-rev : A0
vid : V01
Part number: 73-10598-01 38
Revision:
Software revision:
LineCard S/N : CAT1202G07D
Power Supply type: AC
SML Application information is:
No application is configured.
Logger status: Enabled
Platform: SCE8000 - 4x10GBE
Management agent interface version: SCE Agent 3.1.6 Build 134
Software package file: ftp://ftpserver/simba.pkg
SCE8000 uptime is 9 minutes, 54 seconds
======================
#This is a general configuration file (running-config).
#Created on 10:14:59 UTC TUE November 12 2006
.
interface LineCard 0
connection-mode active
no silent
.
.
Software package file: Not available
Unified management package file: /system/images/um13012.pkg
SCE>
Related Commands
Command
|
Description
|
show version
|
|
show version software
|
|
show version software
Displays version information for the current software.
show version software
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
User Exec
Usage Guidelines
Authorization: viewer
Examples
The following example shows the current software version.
SCE>enable 5
Password:<cisco>
SCE>show version software
Software version is: Version 3.0.5 Build 240
SCE>
Related Commands
Command
|
Description
|
show version
|
|
show version all
|
|
silent
Disables the linecard from reporting events. Use the no form of this command if you want the linecard to send reports.
silent
no silent
Syntax Description
This command has no arguments or keywords.
Defaults
No silent
Command Modes
Linecard Interface Configuration
Usage Guidelines
Authorization: admin
Examples
The following example changes the linecard state to silent.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#interface linecard 0
SCE(config if)#silent
SCE(config if)#
Related Commands
Command
|
Description
|
show interface linecard silent
|
|
snmp-server
Enables the SNMP agent. You can use any of the other SNMP-server commands to enable the SNMP agent. Use the no form to disable the SNMP agent from responding to SNMP managers. All SNMP settings are saved and are restored when the SNMP agent is re-enabled.
snmp-server enable
no snmp-server
Syntax Description
This command has no arguments or keywords.
Defaults
disabled
Command Modes
Global Configuration
Usage Guidelines
You must define at least one community string in order to allow SNMP access. For complete information on community strings.
Authorization: admin
Examples
The following example disables the SNMP server.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#no snmp-server
SCE(config)#
Related Commands
Command
|
Description
|
snmp-server community
|
|
show snmp
|
|
snmp-server community
Sets a community string. Use the no form of the command to remove a community string.
snmp-server community community-string [read-option]
no snmp-server community community-string [read-option]
no snmp-server community all
Syntax Description
community-string
|
The SNMPv1 and SNMPv2c security string that identifies a community of managers that can access the SNMP server.
|
read-option
|
Legal values are ro and rw. The default ro (read-only) option allows managers to view MIB variables. rw sets the variable to read-write.
|
Defaults
no SNMP access
Command Modes
Global Configuration
Usage Guidelines
Use the all keyword with the no form of the command to remove all configured communities.
Authorization: admin
Examples
The following example configures an SNMP managers community that has read-only permissions for the SCE platform MIB. Only SNMP managers in access list 1 can access the SCE platform.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#snmp-server community public ro 1
SCE(config)#
Related Commands
Command
|
Description
|
access-list
|
|
show access-lists
|
|
snmp-server contact
Sets the MIB-2 variable system contact. Use theno form of this command to remove the contact setting.
snmp-server contact contact
no snmp-server contact
Syntax Description
contact
|
A string that identifies the system contact.
|
Defaults
This command has no default settings.
Command Modes
Global Configuration
Usage Guidelines
Authorization: admin
Examples
The following example configures the system contact.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#snmp-server contact Brenda@MyCompany.com
SCE(config)#
Related Commands
Command
|
Description
|
show snmp contact
|
|
snmp-server enable traps
Enables/disables SNMP traps (only authentication-failure traps and enterprise traps can be controlled using this command). Use thedefault form of this command to reset SNMP traps to the default status.
snmp-server enable traps [snmp [snmp trap name ]] [enterprise [enterprise trap name ]]
no snmp-server enable traps [snmp [snmp trap name ]] [enterprise [enterprise trap name ]]
default snmp-server enable traps [snmp [snmp trap name ]] [enterprise [enterprise trap name ]]
Syntax Description
snmp trap name
|
Optional parameter used with the snmp parameter to control a specific snmp trap.
Setting = Authentication
|
enterprise trap name
|
Optional parameter used with the enterprise parameter to control a specific enterprise trap.
Settings = attack, chassis, link-bypass, logger, operational-status, port-operational-status, pull-request-failure, RDR-formatter, session, SNTP, subscriber, system-reset, telnet
|
Defaults
snmp traps: disabled
enterprise traps: enabled
Command Modes
Global Configuration
Usage Guidelines
There are two classes of SNMP traps that are controlled by this command
•
snmp traps
•
enterprise traps
The options snmp and enterprise are parameters specifying the class of traps that are to be enabled/disabled by this command. Each class, or type, is composed of specific traps. Use these parameters as follows:
•
To enable/disable all traps of one type: Specify only snmp or enterprise.
•
To enable/disable only one specific trap: Specify snmp or enterprise with the additional trap name parameter naming the desired trap.
•
To enable/disable all traps: Do not specify either snmp or enterprise.
Since, at this time, the only snmp type trap is the authentication trap, the snmp and authentication parameters arecurrently redundant.
Authorization: admin
Examples
The following example configures the SNMP server to send traps.
SCE>enable 10
Password:<cisco>
SCE#config
SCE(config)#snmp-server enable traps
SCE(config)#
Related Commands
Command
|
Description
|
show snmp traps
|
|
snmp-server host
Sets destination hosts for SNMP traps.
snmp-server host address [traps] [version version] community-string
no snmp-server host address [traps] [version version] community-string
no snmp-server host all
Syntax Description
address
|
The IP address of the SNMP server host.
|
traps
|
Optional switch, does not influence command functionality.
|
version
|
SNMP version running in the system. Can be set to 1 or 2c.
|
community-string
|
The SNMPv1 and SNMPv2c security string that identifies a community of managers that are able to access the SNMP server.
|
Defaults
No hosts
Command Modes
Global Configuration
Usage Guidelines
If no