|
|
To enter map-class configuration mode to define parameters that are to be used in specifying a request for an ATM SVC (the SETUP message), use the map-class global configuration command. The no form of this command deletes this class.
map-class encapsulation class-name
encapsulation | Encapsulation type is ATM. |
class-name | User-assigned name of the traffic parameters table. |
No traffic parameters are defined.
Global configuration
If the map class identified by class-name does not already exist, the switch creates a new one. In either case, this command specifies the map class to which subsequent encapsulation-specific commands apply. Configuration of a map class is allowed only if the subsystem corresponding to the encapsulation is linked.
It is up to the media-specific routing that uses a static map to ensure that the referenced class exists if parameters are required.
Most parameters specified through a map-class are used to dictate the contents of the ATM Traffic Descriptor Information Element (ATD IE) present in a SETUP message used to initiate an SVC (note that this IE was called the User Cell Rate IE in UNI 3.0). These parameters are as follows:
forward-peak-cell-rate-clp0
forward-peak-cell-rate-clp1
backward-peak-cell-rate-clp0
backward-peak-cell-rate-clp1
forward-sustainable-cell-rate-clp0
forward-sustainable-cell-rate-clp1
backward-sustainable-cell-rate-clp0
backward-sustainable-cell-rate-clp1
forward-max-burst-size-clp0
forward-max-burst-size-clp1
backward-max-burst-size-clp0
backward-max-burst-size-clp1
When possible, Best Effort is signalled. In UNI 3, a Best Effort Indication is included in the ATD IE only if the contents of the IE consist of forward and backward Peak Cell Rate for CLP 0+1 (and the Best Effort Indication). Therefore, if any of the above parameters other than forward-peak-cell-rate-clp1 and backward-peak-cell-rate-clp1 are specified in the map-class, Best Effort cannot be signalled.
It is important that Best Effort is signalled, because this causes a switch to interpret the SETUP as a request for an Unspecified Bit Rate (UBR) connection. UBR requests do not cause bandwidth to be reserved per-connection.
If Best Effort cannot be signalled (one of the other parameters is specified in map-class), then this causes a switch to interpret the SETUP as a request for Non-Real Time Variable Bit Rate (VBR-NRT) service.
All combinations of parameters are allowed in the definition of map-class. The following recommendations can help to specify a correct set of parameters:
If default traffic parameters are used in the initiation of an SVC, a Best Effort ATD IE is used. The forward and backward peak-cell-rate0+1 values are 24-bits set to "1" (0xffffff). This is a unique value used to indicate that default shaping parameters can be applied.
The following example establishes traffic parameters for map-class atmclass1.
Switch# map-class atmlist
ip 172.21.180.121 atm-nsap 12.3456.7890.abcd.0000.00 broadcast class atmclass1 map-class atm atmclass1 atm forward-peak-cell-rate-clp0 8000 atm backward-peak-cell-rate-clp0 8000 interface atm 2/0/0 map-group atmlist
To associate an ATM map list to an interface or subinterface for either a PVC or SVC, use the map-group interface configuration command. The no form of this command removes the reference to the map list.
map-group name
name | Name of the map list identified by the map-list command. |
No ATM map lists are associated.
Interface configuration
More than one map-group can be configured for an interface. This command only applies to interfaces on the ASP card (2/0/0 in the LightStream 1010 ATM switch environment or 13/0/0 in the Catalyst 5500 environment) and to terminating connections.
In the following example, the map list named ATM is associated with the ATM interface.
Switch(config)# interface atm 2/0/0
Switch(config-if)# map-group atm
To define an ATM map statement for either a PVC or SVC, use the map-list global configuration command. The no form of this command deletes this list and all associated map statements.
map-list name
name | Name of the map list. |
No map statements are defined.
Global configuration
This command only applies to interfaces on the ASP card (2/0/0 in the LightStream 1010 ATM switch environment or 13/0/0 in the Catalyst 5500 environment) and to terminating connections. To allow the switch to propagate routing updates and ARP requests, a static map that maps the protocol address and the ATM address of the next-hop ATM station must be configured. The switch supports a mapping scheme that identifies the ATM address of remote hosts or switches. This address can be specified either as a virtual channel identifier descriptor (vci) for a PVC or an NSAP address for an SVC.
The map-list command specifies the map list to which the subsequent map-list configuration commands apply. These map-list configuration commands identify destination addresses. One map list can contain multiple map entries. A map list can be referenced by more than one interface or subinterface.
In the following example, to configure ATM static maps for a PVC, a map list named ATM is followed by one map statement for protocol addresses being mapped.
Switch# map-list atm
ip 172.21.168.112 atm-vc 1 broadcast
In the following example for an SVC, a map list named ATM includes two map statements for protocol addresses being mapped.
Switch# map-list atm
ip 172.21.97.165 atm-nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.13 ip 172.21.97.166 atm-nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.12
map-class
map-group
show atm map
To configure the maximum administrative weight percentage used to determine if an alternate route is acceptable, use the max-admin-weight-percentage ATM router PNNI configuration command. To remove the constraint on administrative weight for alternate routes, use the no form of this command.
max-admin-weight-percentage percentage
percentage | Specifies the maximum acceptable administrative weight for alternate routes as a percentage of the least administrative weight of any route to the destination. |
Infinity (no constraint on administrative weight for alternate routes).
ATM router PNNI configuration
This command increases network efficiency by preventing alternate routes that use too many network resources from being specified. The command provides a generalized form of a hop count limit.
This command only takes effect when background route computation is enabled.
The maximum acceptable administrative weight is equal to the specified percentage of the least administrative weight of any route to the destination (from the background routing tables). For example, if the least administrative weight to the destination is 5040 and the percentage is 300, the maximum acceptable administrative weight for the call is 5040x300/100 or 15120.
For more information, refer to the LightStream 1010 ATM Switch Software Configuration Guide.
The following script shows how to configure the max-admin-weight-percentage to 300 percent using the max-admin-weight-percentage ATM router PNNI configuration command.
Switch# configure terminal
Switch(config)# atm router pnni
Switch(config-atm-router)# max-admin-weight-percentage 300
administrative-weight
atm pnni admin-weight
show atm pnni background routes
show atm pnni node
To configure the maximum number of records to be collected for a particular signaling diagnostics filter table entry, use the max-records command. To return the max records to the default, use the no form of this command.
max-records max_num_records
max_num_records | Specifies the number of records to be collected. |
20
Diagnostics configuration
This value denotes the number of call failure records to be collected and stored. When the maximum value is reached, the older records are deleted, making way for the newly created records.
The collected records are overwritten when the max-records value is reached. If this field is set to -1, the records are not overwritten. Setting this field to -1 requires increased memory consumption for call failure records storage, and can lead to shortages of available system memory.
The following example shows setting the maximum number of records to 18.
Switch(config)# max-records 20
To set the amount of time that the switch waits for CTS after raising DTR in response to RING, use the modem answer-timeout line configuration command. Use the no form of this command to revert the switch to the default value.
modem answer-timeout seconds
seconds | Specifies the timeout interval in seconds. |
15 seconds
Line configuration
This command applies to the auxiliary port only. It is useful for modems that take a long time to synchronize to the appropriate line speed.
The following example sets the timeout interval to 20 seconds.
Switch(config)# line aux 0
Switch(config-line)# modem answer-timeout 20
To support dial-in modems that use DTR to control the off-hook status of the modem, use the modem callin line configuration command. In response to RING, the modem raises the DTR signal, which answers the modem. At the end of the session, the switch lowers DTR, which disconnects the modem. The no form of this command disables this feature.
modem callinThis command has no arguments or keywords.
No modem control
Line configuration
This command applies to the auxiliary port only.
The following example causes the modem connected to the switch to raise DTR in response to RING.
Switch(config)# line aux 0
Switch(config-line)# modem callin
To configure a line for reverse connections, use the modem callout line configuration command. The no form of this command disables this feature.
modem calloutThis command has no arguments or keywords.
No modem control
Line configuration
This command applies to the auxiliary port only and supports ports connected to computers that are designed to be connected to modems.
The following example configures the line for reverse connections.
Switch(config)# line aux 0
Switch(config-line)# modem callout
To configure a line to require a CTS signal, use the modem cts-required line configuration command. Use the no form of this command to disable this feature.
modem cts-requiredThis command has no arguments or keywords.
No modem control
Line configuration
This command applies to the auxiliary port only. It supports lines that either the user or the network can activate. It is useful for closing connections from a user's terminal when the terminal is turned off and for preventing disabled printers and other devices in a rotary group from being considered.
The following example configures a line to require a CTS signal.
Switch(config)# line aux 0
Switch(config-line)# modem cts-required
To configure a line to leave DTR low unless the line has an active incoming connection or an EXEC process, use the modem dtr-active line configuration command. The no form of this command disables this feature.
modem dtr-activeThis command has no arguments or keywords.
No modem control
Line configuration
This command applies to the auxiliary port only. It can be useful if the line is connected to an external device (for example, a timesharing system) that needs to know whether a line is in active use. The modem dtr-active command is similar to the no modem line configuration command.
The following example shows configuring the auxiliary port for low DTR.
Switch(config)# line aux 0
Switch(config-line)# modem dtr-active
To configure a line for both incoming and outgoing calls, use the modem inout line configuration command. The no form of this command disables this feature.
modem inoutThis command has no arguments or keywords.
No modem control
Line configuration
This command applies to the auxiliary port only.
The following example illustrates how to configure the auxiliary port for both incoming and outgoing calls.
Switch(config)# line aux 0
Switch(config-line)# modem in-out
To copy debug output to the current terminal line, use the monitor line configuration command.
monitorThis command has no keywords or arguments.
This command has no default setting.
Line configuration mode
To adjust the maximum packet size or maximum transmission unit (MTU) size, use the mtu interface configuration command. Use the no form of this command to restore the MTU value to its original default value.
mtu bytes
bytes | Desired size in bytes. |
Table 12-1 lists default MTU values according to media type.
| Media Type | Default MTU |
|---|---|
Ethernet | 1500 |
ATM | 4470 |
Interface configuration
This command only applies to the ASP interface card: Ethernet 2/0/0 or ATM 2/0/0 (or 13/0/0 in the Catalyst 5500). Each interface has a default maximum packet size or maximum transmission unit (MTU) size. This number generally defaults to the largest size possible for that type interface.
The following example specifies an MTU of 4470 bytes.
Switch(config)# interface atm 2/0/0
Switch(config-if)# mtu 4470
To configure a PPP multilink, use the multilink global configuration command.
multilink [virtual-template number]
virtual-template | Specifies the virtual-template interface. |
number | Specifies the virtual-template number. |
This command has no default setting.
Global configuration
|
|