|
|
To configure the mac-address associated with a LAN Emulation Client (LEC), use the mac-address lane configuration server database command. To remove the mac-address, use the no form of this command.
mac-address ieee-address
ieee-address | 48-bit IEEE MAC address written as a dotted triplet of four-digit hexadecimal numbers. |
No MAC layer address is set.
Lane configuration server database
The following example shows configuring the MAC address for the LEC where xx.xxxx is an appropriate second half of the MAC address to use.
Switch# config t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# lane database Switch(lane-config-database)# mac-address 5000.5axx.xxxx
To enter map-class configuration mode to define parameters that are to be used in specifying a request for an SVC (the SETUP message), use the map-class global configuration command. To delete this class, use the no form of this command.
map-class {atm | dialer | frame-relay} class-name
atm | Specifies the ATM map class for an SVC. |
dialer | Specifies a class of shared configuration parameters associated with the dialer map for an SVC. |
frame-relay | Specifies a class of quality of service (QOS) values for an SVC. |
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 ATD IE present in a SETUP message used to initiate an SVC. These parameters are as follows:
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 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 the map class), then this causes a switch to interpret the SETUP as a request for 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(config)# map-class atm atmclass1 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 main-atm 0 map-group atm atmlist1
To associate an ATM map list to an interface or subinterface for either a PVC or SVC, use the map-group interface configuration command. To remove the reference to the map list, use the no form of this command.
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 route processor card and to terminating connections.
In the following example, the map list named atm is associated with the ATM interface.
Switch(config)# main-atm 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. To delete this list and all associated map statements, use the no form of this command.
map-list name
name | Name of the map list. |
No map statements are defined.
Global configuration
This command only applies to interfaces on the route processor card 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 Switch(config-map-list)# 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 Switch(config-map-list)# ip 172.21.97.165 atm-nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.13 Switch(config-map-list)# 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 Catalyst 8540 MSR ATM Switch Software Configuration Guide.
The following script shows how to configure the maximum administrative 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 local-node
To configure the maximum number of records to be collected for a particular signalling diagnostics filter table entry, use the max-records ATM signalling diagnostics configuration command. To return the maximum 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
ATM signalling 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 configure the value of the minimum age of the VC for on-release or periodic collection of accounting records, use the min-age ATM accounting file subcommand. To return the min-age value to the default, use the no form of this command.
min-age seconds
seconds | Specifies the number of seconds. |
3600 seconds
ATM accounting file
atm accounting file
collection-modes
failed-attempts
To adjust the maximum packet size or MTU size, use the mtu interface configuration command. To restore the MTU value to its original default value, use the no form of this command.
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 route processor interface card: main Ethernet 0 or main ATM 0. Each interface has a default maximum packet size or 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)# main-atm 0
Switch(config-if)# mtu 4470
To enable collection and use of RIF information on a subinterface, use the multiring interface configuration command. To disable the use of RIF information, use the no form of this command.
multiring ip [all-routes | spanning]
ip | Protocol type for which to enable multiring. |
all-routes | Uses all-routes explorers. |
spanning | Uses spanning-tree explorers. |
Disabled
Interface configuration
In source-route bridged or Token Ring switched networks, only packets with RIF are forwarded by intermediate source-route bridges. To ensure that IP datagrams are transmitted across a Token Ring switch or source-route bridge to and from an ATM switch router, use the multiring command.
When multiring is enabled, the Token Ring LEC strips the RIF information and caches it in its RIF table for incoming IP/ARP packets. It adds a RIF for subsequent IP/ARP response packets to be sent back across the network. Use the show rif command to display the RIF table entries. To configure static RIF entries, use the rif command.
The following example shows how to configure a subinterface with an IP address and Token Ring LANE LEC, and then enable multiring.
Switch(config)# interface atm 0.1 Switch(config-subif)# ip address 1.1.1.2 255.255.255.0 Switch(config-subif)# lane client tokenring cisco Switch(config-subif)# multiring ip
rif
show rif
Posted: Thu Sep 2 10:30:33 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.