|
|
The commands shown in this chapter apply to the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010. Where an entire command or certain attributes of a command have values specific to a particular switch, an exception is indicated by the following callouts:
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
interrupt-time | Integer (in microseconds) that limits the maximum number of microseconds to spend on fast switching within any one network interrupt context. The range is 500 to 6000 microseconds. The default is 4000 microseconds. |
process-time | Integer (in microseconds) that guarantees the minimum number of microseconds to spend at the process level when network interrupts are disabled. The range is 500 to 60000 microseconds. The default is 200 microseconds. |
Approximately five percent of the CPU is available for process tasks.
Global configuration
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.
The following example makes 20 percent of the CPU available for process tasks.
Switch(config)# scheduler allocate 2000 500
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}
all | Filter call failures that occur within the switch or on other external switches. |
external | Filter call failures that occur on other external switches. |
internal | Filter call failures that occur within the switch. |
all
ATM signalling diagnostics configuration
In the following example, call failures are filtered by failures that occur within the switch.
Switch(cfg-atmsig-diag)# scope internal
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
low-org-scope | Specifies the low end of the range of organizational scope values. The valid range of organizational scope values is from local (1) to global (15). |
high-org-scope | Specifies the high end of the range of organizational scope values. The valid range of organizational scope values is from local (1) to global (15). If no value is specified, then the range includes only one entry (for example, high-org-scope equals low-org-scope). |
level-indicator | Specifies the PNNI scope value to which the range of organizational scope values is mapped. The range is from 0 to 104. |
The default values specified in the ATM Forum PNNI 1.0 Specifications are shown in Table 18-1.
| org-scope Range | ATM Forum Default Level |
|---|---|
1-3 | 96 |
4-5 | 80 |
6-7 | 72 |
8-10 | 64 |
11-12 | 48 |
13-14 | 32 |
15 global | 0 |
PNNI node configuration
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 are considered acceptable.
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).
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.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# node 1 Switch(config-pnni-node)# scope mode manual Switch(config-pnni-node)# scope map 1 5 level 96
To specify the configuration mode of the mapping from organizational scope values (used at UNI interfaces) to PNNI scope (such as in terms of PNNI routing-level indicators), use the scope mode node-level subcommand.
scope mode {automatic | manual}
automatic | Generates a default scope mapping table automatically which is tied to the PNNI level of the node. In this mode, no modifications of the scope mapping table entries are allowed. |
manual | Allows for manual configuration of the scope mapping table using the scope map command. |
The default scope mappings for automatic are shown in Table 18-2.
| Organizational Scope Range | ATM Forum Default Level | Automatic Mode Level |
|---|---|---|
1-3 | 96 | min(l,96) |
4-5 | 80 | min(l,80) |
6-7 | 72 | min(l,72) |
8-10 | 64 | min(l,64) |
11-12 | 48 | min(l,48) |
13-14 | 32 | min(l,32) |
15(global) | 0 | 0 |
PNNI node configuration
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).
The following example shows setting the scope mode to manual using the scope mode PNNI node-level subcommand.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# node 1 Switch(config-pnni-node)# scope mode manual
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
scramblingmode | Specify either sts-stream or cell-payload. |
In SONET interfaces, both modes are enabled. In DS3 interfaces, the mode is disabled.
Interface configuration
The sts-stream scrambling is applicable only to SONET interfaces.
The following example shows how to disable sts-stream and cell-payload scrambling on the physical device associated with ATM 3/0/0.
Switch# configure terminal Switch(config)# interface atm 3/0/0 Switch(config-if)# no scrambling cell-payload Switch(config-if)# no scrambling sts-stream
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
name-string | Name of the PNNI node. |
node-id | Full 22-byte node ID for a PNNI node. |
node-id-prefix | The first 15 or more bytes of a node ID for a PNNI node. |
port hex-port-id | Optionally specifies an exit port to exclude for a PNNI node. Should be specified as a hexadecimal port ID rather than as a port name. The default is to allow any valid exit port. |
agg-token hex-agg-token-id | Optionally specifies the exit aggregation token, which is used in place of the port ID for higher-level PNNI LGNs. The default is to allow any valid exit port. |
See "Syntax Description."
PNNI explicit-path configuration
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
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.
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.
The following example shows how to perform the following PNNI explicit-path configuration tasks:
Switch# configure terminal Switch(config)# atm pnni explicit-path name boston_2.path1 Switch(cfg-pnni-expl-path)# next-node dallas_2 Switch(cfg-pnni-expl-path)# segment-target dallas_4 Switch(cfg-pnni-expl-path)# segment-target 40:72:47.009181000000106000000000
atm pnni explicit-path
exclude-node
next-node
show atm pnni explicit-paths
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}
abr | Sets the service category to ABR. |
all | Sets the service category to ABR, CBR, NRT-VBR, RT-VBR, and UBR. |
cbr | Sets the service category to CBR. |
nrt-vbr | Sets the service category to NRT-VBR. |
rt-vbr | Sets the service category to RT-VBR. |
ubr | Sets the service category to UBR. |
all
ATM signalling diagnostics configuration
In the following example, call failures for the ABR and UBR service categories are filtered.
Switch# configure terminal Switch(config)# interface atm 0/0/0 Switch(config-if)# atm signalling diagnostics 1 Switch(cfg-atmsig-diag)# service-category abr ubr
To enable the operation of the SGCP to interconnect ATM CES interface circuits on a switch, use the sgcp global configuration command. To disable the operation of SGCP on a switch, use the no form of this command.
sgcpThis command has no arguments or keywords.
Disabled
Global configuration
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. There is no attempt to gracefully release resources.
When SGCP receives a CreateConnection packet for the ATM switch endpoint, the endpoint name is in the following format:
CBR.x.y.z/c
where x, y, and z are standard ATM switch interface specifiers (card/subcard/interface), and c is a CES circuit ID.
For a CreateConnection packet to succeed:
The following example enables SGCP.
Switch# configure terminal Switch(config)# sgcp
sgcp call-agent
sgcp graceful-shutdown
sgcp request retries
sgcp request timeout
show sgcp
show sgcp connection
show sgcp endpoint
show sgcp statistics
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.
host | String representing a DNS name or IP address for the SGCP call agent. |
udp_port | Decimal UDP port number. |
Disabled
Global configuration
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.
The following example specifies a call-agent address to use. The default UDP port is used.
Switch# configure terminal Switch(config)# sgcp call-agent 172.69.1.129
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.
This command has no arguments or keywords.
Disabled
Global configuration
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 the show 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.
Switch# configure terminal Switch(config)# sgcp grace-shutdown
To specify the number of times the ATM switch 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
retryval | Decimal number of retries. |
Three
Global configuration
Currently, the ATM switch 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.
The following example sets the number of request retries to six.
Switch# configure terminal Switch(config)# sgcp request retries 6
sgcp
sgcp request timeout
show sgcp
To specify the time the ATM switch 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
timeval | Time value, in milliseconds. |
500 milliseconds
Global configuration
Currently, the ATM switch only sends DeleteConnection requests to the call agent.
The following example sets the request timeout to one second.
Switch# configure terminal Switch(config)# sgcp request timeout 1000
sgcp
sgcp request timeout
show sgcp
To disable a controller, use the shutdown controller configuration command. To restart a disabled controller, use the no form of this command.
shutdownThis command has no arguments or keywords.
Enabled
Controller configuration
The shutdown command disables transmission of data on the specified channelized DS3 (CDS3) Frame Relay or channelized E1 (CE1) controller. When the controller is shut down, an AIS is transmitted to the far end. All channel groups on this controller are put into a "down" state.
This command also marks the controller as unavailable. To check whether a controller is disabled, use the show controller EXEC command. A controller that has been shut down is shown as administratively down in the screen display.
The following example turns off E1 controller 11/0/0.
Switch# configure terminal Switch(config)# controller e1 11/0/0 Switch(config-controller)# shutdown
The following example turns the controller on.
Switch# configure terminal Switch(config)# controller e1 11/0/0 Switch(config-controller)# no shutdown
To disable an interface, use the shutdown interface configuration command. To restart a disabled interface, use the no form of this command.
shutdownThis command has no arguments or keywords.
Enabled
Interface configuration
The shutdown command disables all functions on the specified interface. When the ATM interfaces shut down, a loss of signal is transmitted to the far end.
This command also marks the interface as unavailable. To check whether an interface is disabled, use the EXEC command show interface. An interface that has been shut down is shown as administratively down in the display from this command.
The following example turns off Ethernet interface 0.
Switch# configure terminal Switch(config)# interface ethernet 0 Switch(config-if)# shutdown
The following example turns on the interface.
Switch# configure terminal Switch(config)# interface ethernet 0 Switch(config-if)# no shutdown
Use the slip EXEC command to attach or detach a SLIP interface.
slipThis command has no keywords or arguments.
EXEC
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]
trap-type | Type of trap to enable. If no type is specified, all traps are sent (including envmon and repeater). trap-type can have one of the following values: · atm-accounting---Enable SNMP ATM accounting traps. · chassis-change---Enable SNMP chassis change traps. · chassis-fail---Enable SNMP chassis fail traps. · config---Enable SNMP configuration traps. · entity---Enable SNMP entity traps. · snmp---Enable SNMP traps. · syslog---Enable SNMP syslog traps. |
trap-option | Enables authentication. When the snmp keyword is used for trap-type, you can specify the authentication option to enable SNMP Authentication Failure traps. (The snmp-sever enable traps snmp authentication command replaces the snmp-server trap-authentication command.) |
No traps are enabled.
If you enter this command with no keywords, the default is to enable all trap types.
Global configuration
Use the snmp-server enable command to specify which SNMP traps the switch 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.
To set the mode of operation and thus control the type of ATM cell used for cell-rate decoupling on the SONET, use the sonet interface configuration command. To restore the default sts3c operation to OC-3 and OC-12 interfaces, use the no form of this command.
sonet [stm-1 | sts-3c]
stm-1 | SDH/STM-1 operation (ITU-T specification).1 |
stm-4 | SDH/STM-4 operation (ITU-T specification). |
| 1The ITU-T carries out the functions of the former Consultative Committee for International Telegraph and Telephone (CCITT). |
The default for OC-3 is sts3c.
The default for OC-12 is sts12c.
Interface configuration
This command applies to all ports except the CPU. Use stm-1 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 default (sts3c) in applications where the ATM switch router requires unassigned cells for rate adaptation. An unassigned cell contains 32 zeros.
The following example specifies ATM SONET STM-1.
Switch# configure terminal Switch(config)# interface atm 3/0/0 Switch(config-if)# atm sonet stm-1
show controllers
show running-config
write terminal
Use the sonet tx-ais on-rx-defect command to enable a SONET interface to send an alarm indication signal (AIS) if it detects the receive port has failed. To disable AIS, use the no form of this command.
sonet tx-ais on-rx-defect
None |
|
Disabled
Interface Configuration
The sonet tx-ais on-rx-defect command should not be enabled on both ATM switch router interfaces connected to the same physical line. Even if no alarm exist, both interfaces will see the alarms signals and never come up.
The following example enables AIS on an ATM interface.
Switch# configure terminal Switch(config)# interface atm 3/0/0 Switch(config-if)# sonet tx-ais on-rx-defect
To turn on the PNNI statistics feature, use the statistics ATM router PNNI configuration command. To disable this feature, use the no form of this command.
statistics [call]
call | Specifies statistics related to route computation for call and party setups. |
Disabled
ATM router PNNI configuration
For more information, refer to the ATM Switch Router Software Configuration Guide.
The following script shows how to access the statistics ATM router PNNI configuration command.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# statistics call
To configure the status of this filter table entry, use the status ATM signalling diagnostics configuration command. To disable this feature, use the no form of this command.
status [active | inactive | delete]
active | Sets status to active to begin filtering failed connections. |
inactive | Sets status to inactive to stop filtering failed connections. |
delete | Sets status to delete if the signalling diagnostics filter table entry needs to be deleted. |
Inactive
ATM signalling diagnostics configuration
The following script shows how to access the status command.
Switch# configure terminal Switch(config)# status active
To configure summary address prefixes on a PNNI node, use the summary-address node-level subcommand. To remove configured summary address prefixes, use the no form of this command.
summary-address address-prefix [internal | exterior] [suppress]
address-prefix | Specifies the summary address prefix. The maximum length of the address prefix is 19 bytes. Each character in the prefix is 4-bits long. The length of the prefix must fall on a nibble boundary. In other words, the length of the prefix must be a multiple of 4 bits. |
internal | Specifies local knowledge of reachability, including end-system addresses registered via ILMI address registration. |
exterior | Specifies knowledge of reachability through remote networks or derived from other protocol exchanges outside the PNNI routing domain. |
suppress | Indicates that neither the summary address nor any addresses for which the summary address is the longest matching prefix are advertised. |
Default summary addresses are controlled by the auto-summary command.
The default summary address type is internal.
PNNI node configuration
Summary addresses can be used to decrease the amount of information advertised by this PNNI node. Summary addresses should only be configured when all end-system addresses matching the summary address are reachable from this switch (for example, not reachable through PNNI interfaces to other switches).
Summary addresses of type internal only summarize internal addresses reachable from this switch (such as ILMI-registered addresses and internal static routes). Summary addresses of type exterior only summarize exterior addresses reachable from this switch (for example, exterior static routes on IISP or public UNI interfaces).
Suppressed summary addresses can be used to prevent other PNNI nodes from learning of this switch's connectivity to certain addresses (for example, for back doors).
For more information, refer to the ATM Switch Router Software Configuration Guide.
The following script shows how to access the summary-address node-level subcommand.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# node 1 Switch(config-pnni-node)# summary-address 48.91...
atm route
auto-summary
show atm route
To synchronize the configuration between the primary and secondary route processors based on the primary configuration, use the sync-config main-cpu redundancy command. To disable the synchronization, use the no form of this command.
sync config {startup | running | both}
startup | Synchronizes the startup configuration. |
running | Synchronizes the running configuration. |
both | Synchronizes the startup and running configurations. |
Both
Main-cpu redundancy
The following example synchronizes the startup configuration of the primary and secondary route processors.
Switch# configure terminal Switch(config)# redundancy Switch(config-r)# main-cpu Switch(config-r-mc)# sync config startup
Posted: Mon Aug 16 14:36:30 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.