|
|
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. 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 is 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 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 the 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# interface atm 3/0/0
Switch# no scrambling cell-payload
Switch# no scrambling sts-stream
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 | Set the service category to ABR. |
all | Set the service category to ABR, CBR, NRT-VBR, RT-VBR, and UBR. |
cbr | Set the service category to CBR. |
nrt-vbr | Set the service category to NRT-VBR. |
rt-vbr | Set the service category to RT-VBR. |
ubr | Set 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(cfg-atmsig-diag)# service-category abr ubr
Switch(cfg-atmsig-diag)#
To disable an interface, use the shutdown controller configuration command. To restart a disabled interface, 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 E1 interface. When the E1 interfaces are shut down, an Alarm Indication Signal (AIS) is transmitted to the far end.
This command also marks the controller as unavailable. To check whether a controller is disabled, use the EXEC command show controller. A controller that has been shut down is shown as administratively down in the screen display.
The following example turns off E1 interface 11/0/0.
Switch(config)# controller e1 11/0/0
Switch(config-controlle)# shutdown
The following example turns the interface on.
Switch# controller e1 11/0/0
Switch(config-controlle)# 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# interface ethernet 0
Switch(config-if)# shutdown
The following example turns on the interface.
Switch# 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 trap. · chassis-fail---Enable SNMP chassis fail trap. · 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.) If no option is specified, all SNMP traps are enabled. |
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 enable SNMP link trap generation, use the snmp trap link-status interface configuration command. To disable SNMP link traps, use the no form of this command.
snmp trap link-statusThis command has no arguments or keywords.
Disabled
Interface configuration
The following example enables snmp trap link status on serial interface 11/0/0:1.
Switch# config t
Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# interface serial 11/0/0:1
Switch(config-if)# snmp trap link-status
show snmp
snmp enable traps frame-relay
To set the mode of operation and thus control 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 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 requires unassigned cells for rate adaptation. An unassigned cell contains 32 zeros.
The following example specifies ATM SONET STM-1.
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, 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 interfaces connected to the same physical line. Even if no alarm exist, both interfaces will see the AISs and never come up.
The following example enables AIS on an ATM interface.
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 Catalyst 8510 and LightStream 1010 ATM Switch 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(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 | Local knowledge of reachability, including end-system addresses registered via ILMI address registration. |
exterior | 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 Catalyst 8510 and LightStream 1010 ATM Switch 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
|
|