Table of Contents

S Commands

The commands shown in this chapter apply to the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. Where an entire command or certain attributes of a command have values specific to a particular switch or switch router, an exception is indicated by the following callouts:

Refer to Appendix D of this command reference for a detailed list of commands that have been removed, changed or replaced.

scheduler allocate

To guarantee CPU time for processes, use the scheduler allocate global configuration command.
To restore the default guaranteed CPU time, use the no form of this command.

scheduler allocate interrupt-time process-time

no scheduler-allocate

Syntax Description

Defaults

Approximately five percent of the CPU is available for process tasks.

Command Modes

Global configuration

Command History

Usage Guidelines

The normal operation of the network server allows the switching operations to use as much of the central processor as required. If the network is running unusually heavy loads that do not allow the processor the time to handle the routing protocols, give priority to the system process scheduler.
Use the scheduler allocate command to guarantee processor time.

Examples

The following example makes 20 percent of the CPU available for process tasks.

scope

To filter ATM signalling call failures that occur within the switch and on other switches, use the scope ATM signalling diagnostics configuration command. To disable this feature, use the no form of this command.

scope {all | external | internal}

no scope

Syntax Description

Defaults

all

Command Modes

ATM signalling diagnostics configuration

Command History

Examples

In the following example, call failures are filtered by failures that occur within the switch.

scope map

To specify the mapping from a range of organizational scope values (used at UNI interfaces) to a PNNI scope value (such as in terms of PNNI routing-level indicators), use the scope map PNNI node-level subcommand. To set to default a range of organizational scope values, use the no form of this command.

scope map low-org-scope [high-org-scope] level level-indicator

no scope map low-org-scope [high-org-scope]

Syntax Description

Defaults

Table Table 17-1 shows the default values specified in the ATM Forum PNNI 1.0 Specifications.

Command Modes

PNNI node configuration

Command History

Usage Guidelines

The scope map command is used to change the values of specific entries. This command is only accepted when the scope mode is set to manual.

When the organizational scope of a registered address maps to a PNNI level that is lower in the PNNI hierarchy (larger PNNI routing level) than the level of this node, the registered address is not advertised. Similarly, when the connection scope of a setup attempt maps to a PNNI level that is lower in the PNNI hierarchy than the level of this node, then only destinations directly attached to this switch router are considered acceptable.

Note   Modifying the node level without altering the scope map table can result in some advertisements being suppressed.

The ATM switch router provides an option to automatically adjust the level changes. In automatic mode, the default scope map table is tied to the level of the node when it is generated.

Note that the default organizational scope of an individual address is global (15), and the default organizational scope of a group address is local (1).

Examples

The following example shows setting the scope mode to manual and setting the scope map entries for organizational scope values 1 through 5 to PNNI level 96, using the scope map PNNI node-level subcommand.

Related Commands

scope mode

To specify the configuration mode of the mapping from organizational scope values (used at UNI interfaces) to PNNI scope (such as PNNI routing-level indicators), use the scope mode node-level subcommand.

scope mode {automatic | manual}

Syntax Description

Defaults

The default scope mappings for automatic are shown in Table 17-2.

Command Modes

PNNI node configuration

Command History

Usage Guidelines

Use this command to modify the way in which the default scope mapping table is computed.

Using the automatic mode ensures that all organizational scope values cover an area at least as wide as this node's peer group, even when the node is at a level higher than 96. As a result, all addresses including those of local scope are advertised across this node's peer group.

For each organizational scope value, the corresponding PNNI level is the minimum of the ATM Forum PNNI 1.0 default value and level l of this node.

Note that the scope mapping table is overwritten whenever the scope mode is changed from manual to automatic (for example, all scope map commands for this node are removed).

Examples

The following example shows setting the scope mode to manual using the scope mode PNNI node-level subcommand.

Related Commands

scrambling

To allow scrambling to be enabled or disabled from the current port, use the scrambling interface configuration command. To disable scrambling, use the no form of this command.

scrambling scramblingmode

no scrambling scramblingmode

Syntax Description

Defaults

In SONET interfaces, both modes are enabled. In DS3 interfaces, the mode is disabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

The sts-stream scrambling is applicable only to SONET interfaces.

Examples

The following example shows how to disable sts-stream and cell-payload scrambling on the physical device associated with ATM 3/0/0.

segment-target

To specify a target entry in a partially specified PNNI explicit-path, use the segment-target PNNI explicit-path configuration command.

segment-target {name-string | node-id | node-id-prefix} [port hex-port-id | agg-token hex-agg-token-id]

Syntax Description

Defaults

See "Syntax Description."

Command Modes

PNNI explicit-path configuration

Command History

Usage Guidelines

Note   See the atm pnni explicit-path command for a description of how to edit or delete an existing segment-target path entry.

Node IDs can be entered with either the full 22-byte length address, or as a node ID prefix with a length of 15 bytes or more. To specify routes that include higher-level nodes (parent LGNs) for other peer groups, we recommend that you enter exactly 15 bytes so that the address remains valid in the event of a PGL update.

Node IDs appear in the following format:

dec: dec: 13-20 hex digits

Note   To display the node IDs that correspond to named nodes in a network, use either the show atm pnni identifier command or the show atm pnni topology command with the node keyword.

Node names can be entered instead of node IDs. If names are used to identify higher-level LGNs, the resulting explicit paths are not guaranteed to remain valid if the PGL changes in the neighboring peer group. To prevent invalid paths, configure all parent LGNs (for all potential PGL nodes) with the same node name.

An exit port can be specified for any entry. The port should be specified as a hexadecimal port ID rather than as a port name. For excluded entries, only this port is excluded from the path.

Note   To display the corresponding hexadecimal port IDs for a node, use either the show atm pnni identifier command with the port keyword, or the show atm pnni topology command with the node and hex-port-id keywords.

Since the port-id could change if the following neighbor peer group changes PGL leaders, the aggregation token is used in place of the port ID for nodes with higher-level LGNs. The LGN aggregation token can only identify the port uniquely if the following entry is the next-node entry. Aggregation tokens are not allowed for excluded tokens.

Examples

The following example shows how to perform the following PNNI explicit-path configuration tasks:

Related Commands

service-category

To filter ATM signalling call failures by service category, use the service-category ATM signalling diagnostics configuration command. To return the service category to the default, use the no form of this command.

service-category {abr | all | cbr | nrt-vbr | rt-vbr | ubr}

no service-category

Syntax Description

Defaults

all

Command Modes

ATM signalling diagnostics configuration

Command History

Examples

In the following example, call failures for the ABR and UBR service categories are filtered.

sgcp

To enable the operation of the SGCP to interconnect ATM CES interface circuits on a switch router, use the sgcp global configuration command. To disable the operation of SGCP on a switch router, use the no form of this command.

sgcp

no sgcp

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration

Command History

Usage Guidelines

When enabled, SGCP listens on all interfaces for UDP packets that contain SGCP requests or responses. For call setup, SGCP allocates connections to endpoints: CES ATM single time slot circuits. For call teardown, SGCP releases connections between endpoints. The no form of the command releases all network connections established for SGCP and all endpoints from connections. It also returns resources allocated to SGCP. The no form also stops SGCP from listening for UDP packets. No attempt is made to gracefully release resources.

When SGCP receives a CreateConnection packet for the ATM switch router endpoint, the endpoint name is in the following format:

where x, y, and z are standard ATM switch router interface specifiers (card/subcard/interface), and c is a CES circuit ID.

For a CreateConnection packet to succeed:

T1: 1<=c<=24

E1: 1<=c<=31

Examples

The following example enables SGCP.

Related Commands

sgcp call-agent

To send SGCP response packets to a predetermined IP address and UDP port, use the sgcp call-agent global configuration command. To restore the default behavior of responding to SGCP request packets using the source address in the request packet, use the no form of this command.

sgcp call-agent host [udp_port]

no sgcp call-agent

Syntax Description

Defaults

Disabled

Command Modes

Global configuration

Command History

Usage Guidelines

Use this command to determine the IP address and UDP port of the call agent for sending requests and responses if the call-agent address is not configured.

If the address is specified, but no port is specified, SGCP uses the well-known SGCP port 2427.

Examples

The following example specifies a call-agent address to use. The default UDP port is used.

Related Commands

sgcp graceful-shutdown

To shut down SGCP operation, use the sgcp graceful-shutdown global configuration command.
To allow SGCP to resume operation, use the no form of this command.

sgcp graceful-shutdown

no sgcp graceful-shutdown

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Global configuration

Command History

Usage Guidelines

The graceful shutdown configuration is used while SGCP is active. This command stops SGCP operation after attempting to notify the call agent about the release of any connections in progress.

The no sgcp command operates in a similar manner in that any active network connections established by SGCP are torn down.

The gateway also sends DeleteConnection requests to the call agent for all endpoints allocated to connections. After responses (or retransmission limits, or call agent-initiated DeleteConnection) have been received for all connections, the gateway stops listening to UDP. During this activity, SGCP rejects any requests for new connections.

After you enter the sgcp graceful-shutdown command with SGCP enabled, the operational state of SGCP that theshow sgcp command reflects can be Down or Going Down. The Going Down state is entered only if there are active connections. Once all connections are inactive (not allocated and network connection released), the global operational state is Down. While sgcp is outstanding, the no form of this command resumes SGCP operation.

The no form of this command has no effect when issued while SGCP is not operating.

Examples

Related Commands  

sgcp request retries

To specify the number of times the ATM switch router sends an SGCP request to the call agent without receiving a response and before ceasing to retry, use the sgcp request retries global configuration command. To restore the default value, use the no form of this command.

sgcp request retries retryval

no sgcp request retries

Syntax Description

Defaults

Three

Command Modes

Global configuration

Command History

Usage Guidelines

Currently, the ATM switch router sends only DeleteConnection requests to the call agent. When UDP is sending packets, there is no assurance that all packets are received. When the number of specified retries has been exceeded, the response to DeleteConnection appears to the ATM switch as positive.

Examples

The following example sets the number of request retries to six.

Related Commands

sgcp request timeout

To specify the time the ATM switch router waits after sending an SGCP request to the call agent before considering the request lost, use the sgcp request timeout global configuration command. To restore the default value, use the no form of this command.

sgcp request timeout timeval

no sgcp request timeout

Syntax Description

Defaults

500 milliseconds

Command Modes

Global configuration

Command History

Usage Guidelines

Currently, the ATM switch router only sends DeleteConnection requests to the call agent.

Examples

The following example sets the request timeout to one second.

Related Commands

slip

Use the slip EXEC command to attach or detach a SLIP interface.

slip

Syntax Description

This command has no keywords or arguments.

Command Modes

EXEC

Command History

snmp-server enable traps

To enable the router to send SNMP traps, use the snmp-server enable traps global configuration command. To disable SNMP and stop sending traps, use the no form of this command.

snmp-server enable traps [trap-type] [trap-option]

no snmp-server enable traps [trap-type] [trap-option]

Syntax Description

Defaults

No traps are enabled.

If you enter this command with no keywords, the default is to enable all trap types.

Command Modes

Global configuration

Command History

Usage Guidelines

Use the snmp-server enable command to specify which SNMP traps the switch router sends, and use the snmp-server host command to specify which host or hosts receive SNMP traps.

You must issue a separate snmp-server enable command for each trap type, including envmon
and repeater.

sonet

To set the mode of operation and control the type of ATM cell used for cell-rate decoupling on the SONET, use the sonet interface configuration command. To restore the default operation to OC-3, OC-12, and OC-48c interfaces, use the no form of this command.

Catalyst 8540 MSR

sonet {stm-1 | sts-3c} | {stm-4c | sts-12c} | {stm-16 | sts-48c}

no sonet {stm-1 | sts-3c} | {stm-4c | sts-12c} | {stm-16 | sts-48c}

Catalyst 8510 MSR and LightStream 1010

sonet {stm-1 | sts-3c} | {stm-4c | sts-12c}

no sonet {stm-1 | sts-3c} | {stm-4c | sts-12c}

Syntax Description

Defaults

For OC-3: sts-3c.

For OC-12: sts-12c.

For OC-48c: sts-48c.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command applies to all ports except the CPU. Use stm-1, stm-4c and stm-16 in applications where the ATM switch router requires idle cells for rate adaptation. An idle cell contains 31 zeros followed by a 1.

Use the appropriate default in applications where the ATM switch router requires unassigned cells for rate adaptation. An unassigned cell contains 32 zeros.

Examples

The following example specifies ATM SONET STM-1.

Related Commands

sonet overhead

To set SONET/SDH overhead bytes, use the sonet overhead interface configuration command.
To restore the default value, use the no form of this command.

sonet overhead {c2 bytes | j0 {bytes | msg line} | j1{16byte {exp-msg line | msg line} |
64byte {exp-msg line | msg line}} | s1s0 bits}

no sonet overhead {c2 bytes | j0 {bytes | msg line} | j1{16byte {exp-msg line | msg line} |
64byte {exp-msg line | msg line}} | s1s0 bits}

Syntax Description