These release notes describe the features and caveats for Cisco Internetwork Operating System (Cisco IOS(TM)) Release 11.1(9) for the LightStream 1010 Asynchronous Transfer Mode (ATM) switch software. The LightStream 1010 ATM switch software is based on Cisco IOS Release 11.1(9). This release includes enhancements in support of the LightStream 1010 ATM switch.
The following features have been added to the LightStream 1010 ATM switch software:
F4 operations, administration, and maintenance (OAM) traffic flows and the atm ping command are supported. For detailed information refer to the atm oam and the atm ping commands in the LightStream 1010 ATM Switch Command Reference publication.
A new management information base (MIB) variable, named ciscoAtmIfSvcUpcIntent, has been added to the CISCO-ATM-IF-MIB.my. This variable allows configuration using SNMP as the usage parameter control (UPC) mode for switched virtual circuits (SVCs) on an interface.
The following features have been added to the LightStream 1010 ATM switch software:
Private Network-to-Network Interface (PNNI) Protocol support for single level hierarchy configuration. For detailed information see the chapter "Configuring PNNI" in the LightStream 1010 ATM Switch Software Configuration Guide.
User Network Interface (UNI) Protocol Version 3.1 support. For detailed information see the atm uni and atm iisp commands in the LightStream 1010 ATM Switch Command Reference Guide.
ATM Address Resolution Protocol (ARP) Server support on the ATM switch processor (ASP) module. For detailed information see the chapter "Configuring the LANE and IP over ATM Clients" in the LightStream 1010 ATM Switch Software Configuration Guide.
Network clock selection priority support. For detailed information see the network-clock-select command in the LightStream 1010 ATM Switch Command Reference Guide.
Per-port configuration of the LECS address is supported. For detailed information refer to the atm-ilmi, atm lecs-address, and the atm lecs-address default commands in the LightStream 1010 ATM Switch Command Reference.
F5 OAM flows and atm ping commands are supported. For detailed information refer to the atm oam and the atm ping commands in the LightStream 1010 ATM Switch Command Reference.
Management information base (MIB) changes include:
AAL5 table for RFC1695 (AToM MIB)
VC/VP cross-connect table support for RFC1695 (AToM MIB)
support for management of logical interfaces (VP tunnels)
For documentation of Cisco IOS Release 11.1 LightStream 1010 ATM switch software features, refer to the following publications, available as printed manuals or electronic documents:
For electronic documentation of Release 11.1 ATM switch software features, available on the Cisco Connection Documentation, Enterprise Series CD-ROM, refer to the LightStream 1010 ATM Switch Software Configuration Guide and LightStream 1010 ATM Switch Command Reference publications, which are located in the LightStream 1010 database under ATM Adapters and Switches database.
You can also access Cisco technical documentation on the World Wide Web: http://www.cisco.com.
The LightStream1010 supports the routing of ATM signaling requests across a network of switches using the ATM routing protocols. Two standard routing protocols have been developed by the ATM Forum---Internet InterSwitch Signaling Protocol (IISP) and the Public Network-to-Network Interface (PNNI) Protocol, version 1.0. Both protocols are supported by the LightStream 1010. The default IISP software image supports the IISP only; the optional PNNI image also supports the PNNI version 1.0 Protocol. Table 1 lists the feature set for the Cisco IOS Release 11.1(9), Release 11.1(8), Release 11.1(6), Release 11.1(410), and Release 11.1(4) of the LightStream 1010 ATM switch software.
This section describes caveats that have been corrected by Release 11.1(9) for the LightStream 1010 ATM switch.
Repeatedly entering the same parameter in the command timer (or ptse) can result in a system crash. For example: timer ack-delay 10 ack-delay 10 ack-delay 10 and so forth. [CSCdi82523]
In the disabled state and under heavy traffic, PNNI has a memory leak due to some receive and transmit entries not being freed. [CSCdi83012]
The command no atm address-registration can be configured and is accepted, but ILMI address registration continues to operate. [CSCdi84200]
The trap ciscoLS1010ChassisChangeNotification is not being sent when modules are inserted in or removed from the chassis. [CSCdi84289]
PNNI gives incorrect route because the BACKGROUND-ROUTE table is not updated by significant events like interfaces being shut down. [CSCdi86779]
DCL interrupt errors on system boot up may appear when a PowerOne power supply is installed in slot 1 of the chassis and if the image to be booted resides on a flash card in either one of the PCMCIA slots. This defect can also be created if there is a faulty fan tray alarm or temprature alarm.
Workaround
Copy the image that needs to be booted into "bootflash" device and point the configuration command to load from the bootflash device or set the config-register to 0x2101 (which causes first image in the bootflash device to load). [CSCdi87896]
The clock-source command has been changed to be clock source to be compatible with Cisco IOS.
Both versions of the command will be accepted from LS1010 release 11.1(9) onward. However, the new form of the command will be written to NVRAM when the configuration is saved. [CSCdi87922]
The MIB object ciscoLS1010SubModuleHwVersion always returns the value 0. [CSCdi87927]
Traffic pacing interface configuration allows the transmit rate of a physical interface to be reduced artificially to a desired rate. This configuration should not be allowed for OC-12 ports. [CSCdi88412]
VP Tunnel interface requires number of maximum VPI bits equal to zero. During validation of the VP tunnel interface creation, the check for number of VPI bits should compare with zero and not with the maximum VPI bits value of the physical interface on which the VP tunnel is configured. [CSCdi88799]
OAM connection information block is allocated only when the connection is installed in the hardware. For the connections which are not installed in the hardware, the information block can be NULL.
The Null pointer error message is printed the console screen fro these connections [CSCdi89105]
If one of the LS1010 switches is powered off in a PNNI domain, other LS1010 switches show the prefix state of the powered-down LS1010 switch as up when it should be marked as down. [CSCdi89292]
The state of a logical interface (VP Tunnel), displayed by the show atm interface rm command may incorrectly display the Available Cell Rate (ACR) for CBR or VBR tunnels. A logical interface can only support connections of the same Service Category. The current display can erroneously indicate non-zero ACR for CBR on a VBR logical interface, or vice versa. It can also display a value of 0 ACR for VBR on a VBR logical interface, when the actual ACR is non-zero. [CSCdi90594]
Grammar in the atm-vc command line parsing is incorrect and does not allow mapping the protocol address to a PVC. [CSCdi90784]
Displaying the PNNI prefix table using the command show atm route may lead to a software crash in the PNNI module. [CSCdi92135]
When defining a PVC on interface ATM 2/0/0, you can configure INARP and time in minutes for refresh. The LS1010 parser will always convert the time to 0, and when rebooting the system, it will reject it as being 0 and not in the allowed range. [CSCdi92166]
When sourcing an SVC from the ASP interface, using a map-class that specifies PCR and SCR, the Service Category of the VC should be determined to be VBR-NRT. Instead it is UBR. This only occurs on the LS1010 sourceing the SVC. Transit and destination LS1010 sourcing correctly determine the Service Category. [CSCdi92852]
If an end system address (registered through ILMI) matching exactly with a configured summary address, is registered, deregistered, and registered again in quick succession, the PNNI software crashes. [CSCdi93099]
Under certain low memory conditions, the PNNI module may not be able to get a buffer to send out a Hello message and could lock itself in a one-way state. [CSCdj01365]
The STATUS message sent in response to STATUS-ENQUIRY does not have the end point state information element set properly. [CSCdj03898]
In establishing or releasing ATM SVC connections to client applications on the ATM ASP interface, referencing a pointer to a data structure with an invalid value could cause the software to restart. [CSCdj04204]
This section describes potential unexpected behavior by Release 11.1(9) for the LightStream 1010 ATM switch.
The no atm service-category-limit [cbr | vbr-rt | ...] command works only as the generic no (applying to all service categories), but not for individual service categories as the command syntax suggests. [CSCdj01176]
It is possible to create VBR, ABR, and UBR VCs across the switch with PCR values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
VBR: SCR + sustained-cell-rate-margin-factor x (PCR - SCR)
ABR, UBR: no bandwidth is allocated (guaranteed)
[CSCdj01016]
Configuration memory full error message appears.
Adding too many configuration commands will cause earlier commands to be lost and the following error massage to appear:
% Configuration buffer full, can't add command: user command
This error indicates that the configuration memory limit has been reached and earlier working commands may be lost if you proceed.
Do not use the write memory or copy running-config commands if this error message appears. This bug was introduced in release 11.1(1). [CSCdi54713]
The ARP cache entries might not appear complete in the following two situations:
When you forward a packet to an IP-address (for example using ping) that is mapped to a PVC map-list, the packet is sent across an atm network using map-list. During the operation, an IP ARP cache is not updated with the index value (VCD) of the map-list PVC. This means the IP ARP cache appears incomplete even though the ping was successful.
When you forward a packet to an IP-address (for example using ping) with a destination that is mapped to a SVC map-list, the packet is sent across an ATM network using map-list, and the SVC to IP destination is established, and IP ARP cache is updated. After the SVC is established, when the clear arp command is used, all entries are cleared and the ARP cache is not updated. This means the IP ARP cache appears incomplete even though the ping was successful. This behavior was present in release 11.1(1). [CSCdi55010]
The RDI cells sent by an end point in response to the AIS (Alarm Indication Signal) cells, which are generated during a fault condition at an intermediate switch, are not propagated beyond that intermediate switch. This is because the switch removes the connection leg entries for both interfaces participating in the connection once the fault on one interface is detected, even though the other interface may be running. As a result, the RDI cells are dropped at the switch. [CSCdi55937]
Static maps are used to associate IP addresses with NSAP addresses, so that an ATM SVC can be established to contact the associated host.
The static-map specifies a map-class to indicate traffic parameters to use when initiating an ATM SVC. Many static-maps should be able to use the same map-class. Currently, confusion occurs if several static-maps share the same map-class, so that only one of the maps sharing the map-class is used at one time. The correct behavior is to keep all static-map status information in the static-map only, rather than the map-class data structure. A workaround is to not share map-classes among static-maps.
If changes are made to a map-list, a static-map, or a map-group while the map is associated with an active SVC, connectivity to the IP address(es) associated with the static-map is interrupted. The IP address is not reachable until the associated Address Resolution Protocol (ARP) table entry is timed-out. The correct behavior is to allow map-list, a static-map, or a map-group to be modified at any time. This behavior was present in release 11.1(1). [CSCdi56066]
The SNMP ifPhysAddr of interface ATM 2/0/0 displays an empty string rather than (one of) the ATM address of the switch. [CSCdi59248]
The ATM ARP server does not check the IP subnet mask during registration. The ARP server registers an IP address that resides outside of its own subnet boundary. [CSCdi62225]
You can not disable signaling and SSCOP on an interface, except through the use of the atm nni command using the IISP image. This behavior was present in release 11.1(1). [CSCdi64829]
Under certain conditions, when one of the LightStream 1010 interfaces is shut/noshut repeatedly, some the SVCs may not be released properly. This can result in a LEC not being able to connect to the LECS if its SVC connection to LECS is not released properly from the LECS side.
A workaround is to use the clear atm-vc command to clear the SVC. [CSCdi65885]
The traffic which can go through an E3 board for one pvc is limited to 65535 c/secs independently of the framing type used. This means that there is no benefit from the G832 framing. [CSCdi72255]
When large number (more than 1000) of SVC' s are present on a specific interface and a shutdown command is executed then %SYS-3-CPUHOG: Message may appear. All the SVCs on that interface are released as expected. The message indicates that the process is running for a long time before it gives back the control to the kernel which then can schedule other tasks. [CSCdi74229]
Currently, global service-category-limits are set to 65535. This number should be reduced by the minimum number of cells allocated to ports, including the CPU port. [CSCdi77160]
Under heavy loads, the following message may appear on the console when debug atm sig-error command is enabled.
ATMSIG: incoming pak size 16 does not match embedded msg size
This caveat does not cause any side effects and does not affect the operation of the switch in any way. [CSCdi76330]
This section describes caveats that have been corrected by Release 11.1(8) for the LightStream 1010 ATM switch.
The LEC (LAN Emulation Client), when configured on a LightStream 1010 ATM switch, was not flushing the packets under the following conditions:
1. The LANE data packets with LECID.
2. The LANE data packets with destination MAC was unicast and not LS1010.
The above problem would lead to a broadcast storm, because the packets would be bounced back and forth between the LEC and the BUS depending on the configuration. [CSCdi84426]
There was out-of-range error being reported when the ILMI keepalive was set using SNMP. [CSCdi83329]
Specifying non-default (not CTT row 1) peak-cell-rate for a UBR PNNI VP-tunnel results in failure to route calls over the tunnel. This is because Max cell-rate is 0. [CSCdi81836]
When the VP tunnels are deleted and recreated, the amount of free memory drops each time the VP tunnel is recreated. The memory is not released until the next time the switch is rebooted. [CSCdi81831]
When the snmp-server host command is entered, an Illegal subtree OID error message is displayed, indicating a problem registering the chassis MIB traps with SNMP. [CSCdi81630]
Creating and deleting the same tunnels quickly (for example before the tunnel reaches the "2-way inside" state causes a memory leak. [CSCdi81419]
Deleting a VP tunnel from an interface that was in a down state can lead to a BUS error exception. [CSCdi81253]
The show atm pnni node command did not reflect the correct state of auto-summary. [CSCdi80599]
Configuring PNNI refresh interval to a low value (for example 5 seconds) and lifetime-factor too close to 100 (for example 101) can lead to the removal of node 1 from the topology. As a result, all call attempts fail. [CSCdi80207]
The software does not set the endpoint reference flag correctly if the ingress port was in UNI 3.0 and egress port was in UNI 3.1. This bug does not affect the endpoint reference value. [CSCdi79093]
Two linkDown traps are issues when a link goes down; one reasonDown and one goingDown. [CSCdi78735]
For VBR connections with SCR equal to zero, the switch can crash due to a "divide by zero" exception in the limit computation for UPC in converting MBS to burst tolerance. [CSCdi78656]
When a call is released, the source node attempts to reroute the call using crankback information obtained through the release message. When a rerouting attempt is made and there are no alternate routes currently available, the software classifies this call failure as a routing failure with a correct "no router destination" cause code. [CSCdi78412]
The show atm arp command might not display the full table, while the show atm map command does show all maps. [CSCdi78233]
When the SVC drops under a sustained rate of 54000 packets per second, the map sometimes showed the VC as being up even though there is no SVC. [CSCdi78125]
When you start the system, the VCs inside a VP tunnel on a DS3 interface may launch in DOWN state. To work around this problem, the user can issue a shut followed by a no shut on that VP tunnel. [CSCdi78094]
The default framing mode is changed for E3 is to G.832 adm. Scrambling default is changed to be on. [CSCdi77851]
An ADD-PARTY message may get rejected due to an outstanding SETUP on the first port in the port list returned by routing to signaling, even though the ADD-PARTY message could have been routed through an alternate port. [CSCdi77842]
Input error counters might wrap up on a link state transition since the counters were not being properly handled. [CSCdi77618]
Transmission on an Ethernet port can aborted due to excessive collisions caused by flood pinging, and %SONICT-3-OWNER may be seen. [CSCdi77541]
If auto-summary is on, summary prefixes that are shorter than the 13 byte auto summary and match the summary can not be configured. [CSCdi77174]
If the physical interface is shutdown and changed to atm iisp then, when no shutdown is issued, ILMI is disabled for the physical interface and for all subordinate subinterfaces. The physical interface is never reenabled even if it is changed back to NNI and auto-configuration is set. [CSCdi76919]
The VPI/VCI bits fails negotiatation with ILMI when a peer delays in responding to the ILMI queries for the maximum VPI/VCI bit values. [CSCdi76912]
When a VP tunnel is created on an interface and is followed by the deletion of the associated PVP, the configuration commands related to the VP tunnel subinterface are still allowed and are not rejected. [CSCdi76770]
The PNNI routing module was checking for the requested service class in one direction only. As a result, links that did not support the requested traffic class in both directions, were also being considered as potential candidates for routes. [CSCdi75806]
If there are VP-tunnels on an interface and they are in a shut state, issuing shut/no shut on the physical interface automatically changes the state of the VP-tunnels to no shut. [CSCdi75677]
When accessing a PAM, while the PAM is hots-wapped, the system crashes. Now, whenever such failure occurs, while accessing a PAM address, an error message will be indicated on the console and the system continues to run. [CSCdi75563]
Deleting the active address on a switch with configured soft VCs can lead to a crash. [CSCdi75550]
When the PAM modules are inserted (or re-inserted) after the system startup, the SNMP traps sent for interface status (UP, DOWN and so on) will have incorrect interface indexes assigned. The incorrect interface indexes usually overlap valid interface indexes value for other sublayers (such as the AAL-5 sublayer), subinterfaces (such as tunnels), or replaced PAMs. [CSCdi75534]
The interface level PNNI configuration commands for link selection and administrative weight do not survive switch reloads. [CSCdi75324]
The current RX cell counter algorithm causes a problem if a connection with a high VCI value is added on an existing port and VPI. [CSCdi75172]
With port pacing enabled, the VC TX counters do not reflect the correct values. [CSCdi74394]
When a change in the active ATM address of the switch occurs, the soft VC manager will not be notified and the soft VC calls for the new address fails. [CSCdi74231]
Connection cells at ingress may be policed at a higher rate than configured due to a wraparound in the expected arrival time counter. [CSCdi74198]
Some terminating SVCs setup by the configured soft-vc commands are aged out. This happens when the IP over ATM (1577) or SVC static map is configured on the CPU port of the switch. [CSCdi74125]
For constant bit rate (CBR) and variable bit rate real-time (VBR-RT) service categories, the maximum cell loss ratio (CLR) default value is set as don't care. [CSCdi73017]
When using the snmp-server host command an error might be displayed indicating a problem exists in permitting Chassis Failure and Chassis Change traps to be sent to an SNMP trap-host. [CSCdi72353]
Under heavy traffic conditions, the LightStream 1010 LAN emulation client (LEC) could degrade performance of an external BUS entity that has the root for the point-to-multipoint virtual circuit (VC) connection in the same switch.
Workaround:
If an LEC needs to be configured for Network Management, configure the LEC on a light-traffic emulated LAN (ELAN). [CSCdi69829]
This section describes potential unexpected behavior by Release 11.1(8) for the LightStream 1010 ATM switch.
If an end system address (registered through ILMI) matching exactly with a configured summary address, is registered, deregistered, and registered again in quick succession, the PNNI software crashes. [CSCdi93099]
When sourcing an SVC from the ASP interface, using a map-class that specifies PCR and SCR, the Service Category of the VC should be determined to be VBR-NRT. Instead it is UBR. This only occurs on the LS1010 sourceing the SVC. Transit and destination LS1010 sourcing correctly determine the Service Category. [CSCdi92852]
When defining a PVC on interface ATM 2/0/0, you can configure INARP and time in minutes for refresh. The LS1010 parser will always convert the time to 0, and when rebooting the system, it will reject it as being 0 and not in the allowed range. [CSCdi92166]
Displaying the PNNI prefix table using the command show atm route may lead to a software crash in the PNNI module. [CSCdi92135]
Grammar in the atm-vc command line parsing is incorrect and does not allow mapping the protocol address to a PVC. [CSCdi90784]
The state of a logical interface (VP Tunnel), displayed by the show atm interface rm command may incorrectly display the Available Cell Rate (ACR) for CBR or VBR tunnels. A logical interface can only support connections of the same Service Category. The current display can erroneously indicate non-zero ACR for CBR on a VBR logical interface, or vice versa. It can also display a value of 0 ACR for VBR on a VBR logical interface, when the actual ACR is non-zero. [CSCdi90594]
If one of the LS1010 switches is powered off in a PNNI domain, other LS1010 switches show the prefix state of the powered-down LS1010 switch as up when it should be marked as down. [CSCdi89292]
OAM connection information block is allocated only when the connection is installed in the hardware. For the connections which are not installed in the hardware, the information block can be NULL.
The Null pointer error message is printed the console screen fro these connections [CSCdi89105]
VP Tunnel interface requires number of maximum VPI bits equal to zero. During validation of the VP tunnel interface creation, the check for number of VPI bits should compare with zero and not with the maximum VPI bits value of the physical interface on which the VP tunnel is configured. [CSCdi88799]
Traffic pacing interface configuration allows the transmit rate of a physical interface to be reduced artificially to a desired rate. This configuration should not be allowed for OC-12 ports. [CSCdi88412]
The MIB object ciscoLS1010SubModuleHwVersion always returns the value 0. [CSCdi87927]
DCL interrupt errors on system boot up may appear when a PowerOne power supply is installed in slot 1 of the chassis and if the image to be booted resides on a flash card in either one of the PCMCIA slots. This defect can also be created if there is a faulty fan tray alarm or temprature alarm.
Workaround
Copy the image that needs to be booted into "bootflash" device and point the configuration command to load from the bootflash device or set the config-register to 0x2101 (which causes first image in the bootflash device to load). [CSCdi87896]
PNNI gives incorrect route because the BACKGROUND-ROUTE table is not updated by significant events like interfaces being shut down. [CSCdi86779]
The command no atm address-registration can be configured and is accepted, but ILMI address registration continues to operate. [CSCdi84200]
The trap ciscoLS1010ChassisChangeNotification is not being sent when modules are inserted in or removed from the chassis. [CSCdi84289]
In the disabled state and under heavy traffic, PNNI has a memory leak due to some receive and transmit entries not being freed. [CSCdi83012]
Repeatedly entering the same parameter in the command timer (or ptse) can result in a system crash. For example: timer ack-delay 10 ack-delay 10 ack-delay 10 and so forth. [CSCdi82523]
Currently, global service-category-limits are set to 65535. This number should be reduced by the minimum number of cells allocated to ports, including the CPU port. [CSCdi77160]
When large number (more than 1000) of SVC' s are present on a specific interface and a shutdown command is executed then %SYS-3-CPUHOG: Message may appear. All the SVCs on that interface are released as expected. The message indicates that the process is running for a long time before it gives back the control to the kernel which then can schedule other tasks. [CSCdi74229]
The traffic which can go through an E3 board for one pvc is limited to 65535 c/secs independently of the framing type used. This means that there is no benefit from the G832 framing. [CSCdi72255]
Under certain conditions, when one of the LightStream 1010 interfaces is shut/noshut repeatedly, some the SVCs may not be released properly. This can result in a LEC not being able to connect to the LECS if its SVC connection to LECS is not released properly from the LECS side.
A workaround is to use the clear atm-vc command to clear the SVC. [CSCdi65885]
You can not disable signaling and SSCOP on an interface, except through the use of the atm nni command using the IISP image. This behavior was present in release 11.1(1). [CSCdi64829]
The ATM ARP server does not check the IP subnet mask during registration. The ARP server registers an IP address that resides outside of its own subnet boundary. [CSCdi62225]
The SNMP ifPhysAddr of interface ATM 2/0/0 displays an empty string rather than (one of) the ATM address of the switch. [CSCdi59248]
Static maps are used to associate IP addresses with NSAP addresses, so that an ATM SVC can be established to contact the associated host.
The static-map specifies a map-class to indicate traffic parameters to use when initiating an ATM SVC. Many static-maps should be able to use the same map-class. Currently, confusion occurs if several static-maps share the same map-class, so that only one of the maps sharing the map-class is used at one time. The correct behavior is to keep all static-map status information in the static-map only, rather than the map-class data structure. A workaround is to not share map-classes among static-maps.
If changes are made to a map-list, a static-map, or a map-group while the map is associated with an active SVC, connectivity to the IP address(es) associated with the static-map is interrupted. The IP address is not reachable until the associated Address Resolution Protocol (ARP) table entry is timed-out. The correct behavior is to allow map-list, a static-map, or a map-group to be modified at any time. This behavior was present in release 11.1(1). [CSCdi56066]
The RDI cells sent by an end point in response to the AIS (Alarm Indication Signal) cells, which are generated during a fault condition at an intermediate switch, are not propagated beyond that intermediate switch. This is because the switch removes the connection leg entries for both interfaces participating in the connection once the fault on one interface is detected, even though the other interface may be running. As a result, the RDI cells are dropped at the switch. [CSCdi55937]
The ARP cache entries might not appear complete in the following two situations:
When you forward a packet to an IP-address (for example using ping) that is mapped to a PVC map-list, the packet is sent across an atm network using map-list. During the operation, an IP ARP cache is not updated with the index value (VCD) of the map-list PVC. This means the IP ARP cache appears incomplete even though the ping was successful.
When you forward a packet to an IP-address (for example using ping) with a destination that is mapped to a SVC map-list, the packet is sent across an ATM network using map-list, and the SVC to IP destination is established, and IP ARP cache is updated. After the SVC is established, when the clear arp command is used, all entries are cleared and the ARP cache is not updated. This means the IP ARP cache appears incomplete even though the ping was successful. This behavior was present in release 11.1(1). [CSCdi55010]
Configuration memory full error message appears.
Adding too many configuration commands will cause earlier commands to be lost and the following error massage to appear:
% Configuration buffer full, can't add command: user command
This error indicates that the configuration memory limit has been reached and earlier working commands may be lost if you proceed.
Do not use the write memory or copy running-config commands if this error message appears. This bug was introduced in release 11.1(1). [CSCdi54713]
Under certain low memory conditions, the PNNI module may not be able to get a buffer to send out a Hello message and could lock itself in a one-way state. [CSCdj01365]
The STATUS message sent in response to STATUS-ENQUIRY does not have the end point state information element set properly. [CSCdj03898]
In establishing or releasing ATM SVC connections to client applications on the ATM ASP interface, referencing a pointer to a data structure with an invalid value could cause the software to restart. [CSCdj04204]
This section describes caveats that have been corrected by Release 11.1(6) for the LightStream 1010 ATM switch.
The following caveats have been corrected for this release of the LightStream 1010 ATM switch software.
If PNNI receives a hello packet with a length exceeding pnni_hello_type---for example, a hello packet with multiple type_length_value (TLV) fields---it will enter into an infinite loop. [CSCdi65795]
If the switch did not detect the physical link going down, SSCOP may not tear down the active switched virtual circuits (SVCs) properly. This occurs when SSCOP receives a begin PDU and treats the PDU as a retransmission, and it is ignored. [CSCdi66728]
Systems with less than three ports---for example 2 OC-12 PAMs---cause a failure in the power-on diagnostic tests even though the system and the ports are functional. The test failure causes the LightStream 1010 status LED to be red after power-on and a failure is indicated at the console display. [CSCdi66729]
Removing the receive end of DS3/E3 PAM does not cause the transmit end of the connection to go down. [CSCdi68141]
AToM MIB does not report correct the neighbor name for the virtual path (VP) tunnel. [CSCdi69035]
When a VP switch is placed along the path of a VP tunnel between two LS1010 switches, calls through this VP tunnel will not be completed if the VPI numbers on incoming interfaces and outgoing interfaces have different VPI numbers assigned. [CSCdi69105]
The allocation of a soft permanent virtual circuit (PVC) destination half-leg VPI/VCI is not correct. This allowed a switched virtual circuit (SVC) to be established through an interface to also allocate this same VPI/VCI, and then release it. Then the Soft PVC destination half-leg would disappear. [CSCdi69254]
The Service Specific Connection Oriented Protocol (SSCOP) incorrectly parses the protocol data unit (PDU) state if list elements equal 4. This causes a sequence error. To verify this problem, enable debug SSCOP error and an MAA_ERROR_S error will appear on the console. [CSCdi70022]
PNNI routing software might crash when a link (that is followed by one or more links with NULL metrics) is removed from the internal topology database. [CSCdi71540]
The flag bit in the global call reference is not set correctly in the restart and restart-ack message. It is always set to 0. [CSCdi71545]
A Feature card FPGA download driver could fail causing occasional disabling of the multi-cast and available bit rate (ABR) functions on the Feature card. This would cause some of the multi-cast and traffic-management power-on tests to fail and the Status LED on the ASP card to show red. [CSCdi72070]
Strict restrictions on UPC based on interface type are enforced. For example, tagging or dropping is not allowed on non-UNI-Network-side interfaces. Destination half-leg UPC is always set to passing. Resolution of this DDTS modifies the operation of atm pvc, atm pvp, atm soft-vc, and atm soft-vp commands, to remove the restriction of UPC to UNI-Network-side. [CSCdi72411]
UNI 3.0 to UNI 3.1 conversion is incorrect on PNNI interfaces. This occurs if the ingress port is a UNI 3.0 and the egress port is a PNNI. [CSCdi72611]
The per-interface CLI configuration atm svc-upc-intent command is not allowed using a corresponding SNMP MIB object. This configuration determines the inbound UPC action to perform for SVCs and terminating legs of Soft PVCs at an interface. [CSCdi72604]
The DS-3 driver ignores loss of cell delineation (LCD) far end receive failure (FERF) when using Cbit physical layer convergence protocol (PLCP) framing. [CSCdi72667]
Currently OAM Manager handles fault management functions. If it receives a non-fault management type OAM cell---performance management, system management, or activation/deactivation cells---the software process drops the cell. [CSCdi73621]
Configuration of internal static routes is allowed even when the static route is a duplicate of an ILMI-registered address on another port of the same switch. This behavior was present in release 11.1(1). [CSCdi65799]
This section describes potential unexpected behavior by Release 11.1(6) for the LightStream 1010 ATM switch.
The following caveats have been identified for this release of the LightStream 1010 ATM switch software.
Configuration memory full error message appears.
Adding too many configuration commands will cause earlier commands to be lost and the following error massage to appear:
% Configuration buffer full, can't add command: user command
This error indicates that the configuration memory limit has been reached and earlier working commands may be lost if you proceed.
Do not use the write memory or copy running-config commands if this error message appears. This bug was introduced in release 11.1(1). [CSCdi54713]
The ARP cache entries might not appear complete in the following two situations:
When you forward a packet to an IP-address (for example using ping) that is mapped to a PVC map-list, the packet is sent across an atm network using map-list. During the operation, an IP ARP cache is not updated with the index value (VCD) of the map-list PVC. This means the IP ARP cache appears incomplete even though the ping was successful.
When you forward a packet to an IP-address (for example using ping) with a destination that is mapped to a SVC map-list, the packet is sent across an ATM network using map-list, and the SVC to IP destination is established, and IP ARP cache is updated. After the SVC is established, when the clear arp command is used, all entries are cleared and the ARP cache is not updated. This means the IP ARP cache appears incomplete even though the ping was successful. This behavior was present in release 11.1(1). [CSCdi55010]
The RDI cells sent by an end point in response to the AIS (Alarm Indication Signal) cells, which are generated during a fault condition at an intermediate switch, are not propagated beyond that intermediate switch. This is because the switch removes the connection leg entries for both interfaces participating in the connection once the fault on one interface is detected, even though the other interface may be running. As a result, the RDI cells are dropped at the switch. [CSCdi55937]
Static maps are used to associate IP addresses with NSAP addresses, so that an ATM SVC can be established to contact the associated host.
The static-map specifies a map-class to indicate traffic parameters to use when initiating an ATM SVC. Many static-maps should be able to use the same map-class. Currently, confusion occurs if several static-maps share the same map-class, so that only one of the maps sharing the map-class is used at one time. The correct behavior is to keep all static-map status information in the static-map only, rather than the map-class data structure. A workaround is to not share map-classes among static-maps.
If changes are made to a map-list, a static-map, or a map-group while the map is associated with an active SVC, connectivity to the IP address(es) associated with the static-map is interrupted. The IP address is not reachable until the associated Address Resolution Protocol (ARP) table entry is timed-out. The correct behavior is to allow map-list, a static-map, or a map-group to be modified at any time. This behavior was present in release 11.1(1). [CSCdi56066]
The SNMP ifPhysAddr of interface ATM 2/0/0 displays an empty string rather than (one of) the ATM address of the switch. [CSCdi59248]
The ATM ARP server does not check the IP subnet mask during registration. The ARP server registers an IP address that resides outside of its own subnet boundary. [CSCdi62225]
You can not disable signaling and SSCOP on an interface, except through the use of the atm nni command using the IISP image. This behavior was present in release 11.1(1). [CSCdi64829]
Note The primary function of the atm nni command is to configure an interface as an NNI interface (as opposed to a UNI or IISP interface). Signaling and SSCOP are disabled because the IISP image does not include any NNI signaling protocol. Any ambiguity in the meaning of the atm nni command is going to be removed when the new command to disable signaling and SSCOP is introduced.
Under certain conditions, when one of the LightStream 1010 interfaces is shut/noshut repeatedly, some the SVCs may not be released properly. This can result in a LEC not being able to connect to the LECS if its SVC connection to LECS is not released properly from the LECS side.
A workaround is to use the clear atm-vc command to clear the SVC. [CSCdi65885]
Under heavy traffic conditions, the LightStream 1010 LAN emulation client (LEC) could degrade performance of an external BUS entity that has the root for the point-to-multipoint virtual circuit (VC) connection in the same switch.
Work-around:
If an LEC needs to be configured for Network Management, configure the LEC on a light-traffic emulated LAN (ELAN). [CSCdi69829]
When using the snmp-server host configuration command an error may be displayed indicating a problem exists in permitting Chassis Failure and Chassis Change traps to be sent to an SNMP trap-host. [CSCdi72353]
For constant bit rate (CBR) and variable bit rate real-time (VBR-RT) service categories, the maximum cell loss ratio (CLR) default value is set as don't care. [CSCdi73017]
Some terminating SVCs setup by the configured soft-vc commands are aged out. This happens when the IP over ATM (1577) or SVC static map is configured on the CPU port of the switch. [CSCdi74125]
Connection cells at ingress may be policed at a higher rate than configured due to a wraparound in the expected arrival time counter. [CSCdi74198]
When a change in the active ATM address of the switch occurs, the soft VC manager will not be notified and the soft VC calls for the new address fails. [CSCdi74231]
With port pacing enabled, the VC TX counters do not reflect the correct values. [CSCdi74394]
The current RX cell counter algorithm causes a problem if a connection with a high VCI value is added on an existing port and VPI. [CSCdi75172]
The interface level PNNI configuration commands for link selection and administrative weight do not survive switch reloads. [CSCdi75324]
When the PAM modules are inserted (or re-inserted) after the system startup, the SNMP traps sent for interface status (UP, DOWN and so on) will have an incorrect interface indexes assigned. The incorrect interface indexes usually overlap valid interface indexes value for other sublayers (such as the AAL-5 sublayer), subinterfaces (such as tunnels), or replaced PAMs. [CSCdi75534]
Deleting the active address on a switch with configured soft VC's can lead to a crash. [CSCdi75550]
When accessing a PAM, while the PAM is hotswapped, the system crashes. With this fix, whenever such failure occurs, while accessing a PAM address, an error message will be indicated on the console and the system continues to run. [CSCdi75563]
If there are VP-tunnels on an interface and they are in a shut state, issuing shut/no shut on the physical interface automatically changes the state of the VP-tunnels to no shut. [CSCdi75677]
The PNNI routing module was checking for the requested service class in one direction only. As a result, links that did not support the requested traffic class in both directions, were also being considered as potential candidates for routes. [CSCdi75806]
When a VP tunnel is created on an interface and is followed by the deletion of the associated PVP, the configuration commands related to the VP tunnel subinterface are still allowed and are not rejected. [CSCdi76770]
The VPI/VCI bits fails negotiatation with ILMI when a peer delays in responding to the ILMI queries for the maximum VPI/VCI bit values. [CSCdi76912]
If the physical interface is shutdown and changed to atm iisp then, when no shutdown is issued, ILMI is disabled for the physical interface and for all subordinate subinterfaces. The physical interface is never reenabled even if it is changed back to NNI and auto-configuration is set. [CSCdi76919]
If auto-summary is on, summary prefixes that are shorter than the 13 byte auto summary and match the summary can not be configured. [CSCdi77174]
Transmission on an Ethernet port can aborted due to excessive collisions caused by flood pinging and %SONICT-3-OWNER may be seen. [CSCdi77541]
Input error counters might wrap up on a link state transition since the counters were not being properly handled. [CSCdi77618]
An ADD-PARTY message may get rejected due to an outstanding SETUP on the first port in the port list returned by routing to signaling), even though the ADD-PARTY message could have been routed through an alternate port. [CSCdi77842]
The default framing mode is changed for E3 is to G.832 adm. Scrambling default is changed to be on. [CSCdi77851]
When you start the system, the VCs inside a VP tunnel on a DS3 interface may launch in DOWN state. To workaround this problem, the user can issue a shut followed by a no shut on that VP tunnel. [CSCdi78094]
When the SVC drops under a sustained rate of 54000 packets per second, the map sometimes showed the VC as being up even though there is no SVC. [CSCdi78125]
The show atm arp command might not display the full table, while the show atm map command does show all maps. [CSCdi78233]
When a call is released, the source node attempts to reroute the call using crankback information obtained through the release message. When a rerouting attempt is made and there are no alternate routes currently available, the software classifies this call failure as a routing failure with a correct "no router destination" cause code. [CSCdi78412]
For VBR connections with SCR equal to zero, the switch can crash due to a "divide by zero" exception in the limit computation for UPC in converting MBS to burst tolerance. [CSCdi78656]
Two linkDown traps are issues when a link goes down; one reasonDown and one goingDown. [CSCdi78735]
The software does not set the endpoint reference flag correctly if the ingress port was in UNI 3.0 and egress port was in UNI 3.1. This bug does not affect the endpoint reference value. [CSCdi79093]
Configuring PNNI refresh interval to a low value (for example 5 seconds) and lifetime-factor too close to 100 (for example 101) can lead to the removal of node 1 from the topology. As a result, all call attempts fail. [CSCdi80207]
The show atm pnni node command did not reflect the correct state of auto-summary. [CSCdi80599]
Deleting a VP tunnel from an interface that was in a down state can lead to a BUS error exception. [CSCdi81253]
Creating and deleting the same tunnels quickly (for example before the tunnel reaches the "2-way inside" state causes a memory leak. [CSCdi81419]
When the snmp-server host command is entered, an Illegal subtree OID error message is displayed, indicating a problem registering the chassis MIB traps with SNMP. [CSCdi81630]
When the VP tunnels are deleted and recreated, the amount of free memory drops each time the VP tunnel is recreated. The memory is not released until the next time the switch is rebooted. [CSCdi81831]
Specifying non-default (not CTT row 1) peak-cell-rate for a UBR PNNI VP-tunnel results in failure to route calls over the tunnel. This is because Max cell-rate is 0. [CSCdi81836]
There is out-of-range error being reported when the ILMI keepalive was set using SNMP. [CSCdi83329]
The LEC (LAN Emulation Client), when configured on a LightStream 1010 ATM switch, was not flushing the packets under the following conditions:
1. The LANE data packets with LECID.
2. The LANE data packets with destination MAC is unicast and not LS1010.
The above problem would lead to a broadcast storm, because the packets would be bounced back and forth between the LEC and the BUS depending on the configuration. [CSCdi84426]
This section describes potential unexpected behavior by Release 11.1(410) for the LightStream 1010 ATM switch.
The following caveats have been identified for this release of the LightStream 1010 ATM switch software.
Systems with less than 3 ports, for example 2 OC-12 PAM's, causes a failure in the power-on diagnostic tests even though the system and the ports are functional. The test failure causes the LightStream 1010 status LED to be red after power-on and the following failure is indicated at the console display. A subsequent use of the show diag power-on command will not show any failures.
Booting on Sep 04 1996 13:46:56 with 2-PAM Configuration
LS1010 Diagnostics V2.29, Dated Aug 16 1996 19:06:23
Model CPU-Card, Serial# 3099381, H/W V3.2, SWC Rev-3
Model FC1-Card, Serial# 3098875, H/W V3.2
Copyright (c) Cisco Systems Inc. 1995-1996
.....................................F.........
Power-on Diagnostics Failed
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
[CSCdi66729]
Configuration memory full error message appears.
Adding too many configuration commands will cause earlier commands to be lost and the following error massage to appear:
% Configuration buffer full, can't add command: user command
This error indicates that the configuration memory limit has been reached and earlier working commands may be lost if you proceed.
Do not use the write memory or copy running-config commands if this error message appears. This bug was introduced in release 11.1(1). [CSCdi54713]
The ARP cache entries might not appear complete in the following two situations:
When you forward a packet to an IP-address (for example using ping) that is mapped to a PVC map-list, the packet is sent across an atm network using map-list. During the operation, an IP ARP cache is not updated with the index value (VCD) of the map-list PVC. This means the IP ARP cache appears incomplete even though the ping was successful.
When you forward a packet to an IP-address (for example using ping) with a destination that is mapped to a SVC map-list, the packet is sent across an ATM network using map-list, and the SVC to IP destination is established, and IP ARP cache is updated. After the SVC is established, when the clear arp command is used, all entries are cleared and the ARP cache is not updated. This means the IP ARP cache appears incomplete even though the ping was successful. This behavior was present in release 11.1(1). [CSCdi55010]
The RDI cells sent by an end point in response to the AIS (Alarm Indication Signal) cells, which are generated during a fault condition at an intermediate switch, are not propagated beyond that intermediate switch. This is because the switch removes the connection leg entries for both interfaces participating in the connection once the fault on one interface is detected, even though the other interface may be running. As a result, the RDI cells are dropped at the switch. [CSCdi55937]
Static maps are used to associate IP addresses with NSAP addresses, so that an ATM SVC can be established to contact the associated host.
The static-map specifies a map-class to indicate traffic parameters to use when initiating an ATM SVC. Many static-maps should be able to use the same map-class. Currently, confusion occurs if several static-maps share the same map-class, so that only one of the maps sharing the map-class is used at one time. The correct behavior is to keep all static-map status information in the static-map only, rather than the map-class data structure. A workaround is to not share map-classes among static-maps.
If changes are made to a map-list, a static-map, or a map-group while the map is associated with an active SVC, connectivity to the IP address(es) associated with the static-map is interrupted. The IP address is not reachable until the associated Address Resolution Protocol (ARP) table entry is timed-out. The correct behavior is to allow map-list, a static-map, or a map-group to be modified at any time. This behavior was present in release 11.1(1). [CSCdi56066]
The SNMP ifPhysAddr of interface ATM 2/0/0 displays an empty string rather than (one of) the ATM address of the switch. [CSCdi59248]
The ATM ARP server does not check the IP subnet mask during registration. The ARP server registers an IP address that resides outside of its own subnet boundary. [CSCdi62225]
You can not disable signaling and SSCOP on an interface, except through the use of the atm nni command using the IISP image. This behavior was present in release 11.1(1). [CSCdi64829]
Note The primary function of the atm nni command is to configure an interface as an NNI interface (as opposed to a UNI or IISP interface). Signaling and SSCOP are disabled because the IISP image does not include any NNI signaling protocol. Any ambiguity in the meaning of the atm nni command is going to be removed when the new command to disable signaling and SSCOP is introduced.
Configuration of internal static routes is allowed even when the static route is a duplicate of an ILMI-registered address on another port of the same switch. This behavior was present in release 11.1(1). [CSCdi65799]
Under certain conditions, when one of the LightStream 1010 interfaces is shut/noshut repeatedly, some the SVCs may not be released properly. This can result in a LEC not being able to connect to the LECS if its SVC connection to LECS is not released properly from the LECS side.
A workaround is to use the clear atm-vc command to clear the SVC. [CSCdi65885]
If PNNI receives a hello packet with a length exceeding pnni_hello_type---for example, a hello packet with multiple type_length_value (TLV) fields---it will enter into an infinite loop. [CSCdi65795]
If the switch did not detect the physical link going down, SSCOP may not tear down the active switched virtual circuits (SVCs) properly. This occurs when SSCOP receives a begin PDU and treats the PDU as a retransmission, and it is ignored. [CSCdi66728]
Systems with less than three ports---for example 2 OC-12 PAMs---cause a failure in the power-on diagnostic tests even though the system and the ports are functional. The test failure causes the LightStream 1010 status LED to be red after power-on and a failure is indicated at the console display. [CSCdi66729]
Removing the receive end of DS3/E3 PAM does not cause the transmit end of the connection to go down. [CSCdi68141]
AToM MIB does not report correct the neighbor name for the virtual path (VP) tunnel. [CSCdi69035]
When a VP switch is placed along the path of a VP tunnel between two LS1010 switches, calls through this VP tunnel will not be completed if the VPI numbers on incoming interfaces and outgoing interfaces have different VPI numbers assigned. [CSCdi69105]
The allocation of a soft permanent virtual circuit (PVC) destination half-leg VPI/VCI is not correct. This allowed a switched virtual circuit (SVC) to be established through an interface to also allocate this same VPI/VCI, and then release it. Then the Soft PVC destination half-leg would disappear. [CSCdi69254]
The Service Specific Connection Oriented Protocol (SSCOP) incorrectly parses the protocol data unit (PDU) state if list elements equal 4. This causes a sequence error. To verify this problem, enable debug SSCOP error and an MAA_ERROR_S error will appear on the console. [CSCdi70022]
PNNI routing software might crash when a link (that is followed by one or more links with NULL metrics) is removed from the internal topology database. [CSCdi71540]
The flag bit in the global call reference is not set correctly in the restart and restart-ack message. It is always set to 0. [CSCdi71545]
A Feature card FPGA download driver could fail causing occasional disabling of the multi-cast and available bit rate (ABR) functions on the Feature card. This would cause some of the multi-cast and traffic-management power-on tests to fail and the Status LED on the ASP card to show red. [CSCdi72070]
Strict restrictions on UPC based on interface type are enforced. For example, tagging or dropping is not allowed on non-UNI-Network-side interfaces. Destination half-leg UPC is always set to passing. Resolution of this DDTS modifies the operation of atm pvc, atm pvp, atm soft-vc, and atm soft-vp commands, to remove the restriction of UPC to UNI-Network-side. [CSCdi72411]
UNI 3.0 to UNI 3.1 conversion is incorrect on PNNI interfaces. This occurs if the ingress port is a UNI 3.0 and the egress port is a PNNI. [CSCdi72611]
The per-interface CLI configuration atm svc-upc-intent command is not allowed using a corresponding SNMP MIB object. This configuration determines the inbound UPC action to perform for SVCs and terminating legs of Soft PVCs at an interface. [CSCdi72604]
The DS-3 driver ignores loss of cell delineation (LCD) far end receive failure (FERF) when using Cbit physical layer convergence protocol (PLCP) framing. [CSCdi72667]
Currently OAM Manager handles fault management functions. If it receives a non-fault management type OAM cell---performance management, system management, or activation/deactivation cells---the software process drops the cell. [CSCdi73621]
This section describes potential unexpected behavior by Release 11.1(4) for the LightStream 1010 ATM switch.
Attempting to clear call statistics using the clear atm pnni statistics call command if call statistics collection is not enabled causes the switch to crash.
Confirm that call statistics collection is enabled using the show atm pnni statistics call command before clearing call statistics.
If you enter the show atm pnni statistics call command and call statistics collection is not enabled you will see "Statistics Not Enabled" as in the following example:
Switch#show atm pnni statistics call
Statistics Not Enabled
Switch#
Enable call statistics collection using the statistics call command in ATM router PNNI configuration mode as in the following example:
The minimum queue threshold setting does not function correctly and could cause potential performance degradation. [CSCdi67197]
Systems with less than 3 ports, for example 2 OC-12 PAM's, causes a failure in the power-on diagnostic tests even though the system and the ports are functional. The test failure causes the LightStream 1010 status LED to be red after power-on and the following failure is indicated at the console display. A subsequent use of the show diag power-on command will not show any failures.
Booting on Sep 04 1996 13:46:56 with 2-PAM Configuration
LS1010 Diagnostics V2.29, Dated Aug 16 1996 19:06:23
Model CPU-Card, Serial# 3099381, H/W V3.2, SWC Rev-3
Model FC1-Card, Serial# 3098875, H/W V3.2
Copyright (c) Cisco Systems Inc. 1995-1996
.....................................F.........
Power-on Diagnostics Failed
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
[CSCdi66729]
Configuration memory full error message appears.
Adding too many configuration commands will cause earlier commands to be lost and the following error massage to appear:
% Configuration buffer full, can't add command: user command
This error indicates that the configuration memory limit has been reached and earlier working commands may be lost if you proceed.
Do not use the write memory or copy running-config commands if this error message appears. This bug was introduced in release 11.1(1). [CSCdi54713]
The ARP cache entries might not appear complete in the following two situations:
When you forward a packet to an IP-address (for example using ping) that is mapped to a PVC map-list, the packet is sent across an atm network using map-list. During the operation, an IP ARP cache is not updated with the index value (VCD) of the map-list PVC. This means the IP ARP cache appears incomplete even though the ping was successful.
When you forward a packet to an IP-address (for example using ping) with a destination that is mapped to a SVC map-list, the packet is sent across an ATM network using map-list, and the SVC to IP destination is established, and IP ARP cache is updated. After the SVC is established, when the clear arp command is used, all entries are cleared and the ARP cache is not updated. This means the IP ARP cache appears incomplete even though the ping was successful. This behavior was present in release 11.1(1). [CSCdi55010]
The RDI cells sent by an end point in response to the AIS (Alarm Indication Signal) cells, which are generated during a fault condition at an intermediate switch, are not propagated beyond that intermediate switch. This is because the switch removes the connection leg entries for both interfaces participating in the connection once the fault on one interface is detected, even though the other interface may be running. As a result, the RDI cells are dropped at the switch. [CSCdi55937]
Static maps are used to associate IP addresses with NSAP addresses, so that an ATM SVC can be established to contact the associated host.
The static-map specifies a map-class to indicate traffic parameters to use when initiating an ATM SVC. Many static-maps should be able to use the same map-class. Currently, confusion occurs if several static-maps share the same map-class, so that only one of the maps sharing the map-class is used at one time. The correct behavior is to keep all static-map status information in the static-map only, rather than the map-class data structure. A workaround is to not share map-classes among static-maps.
If changes are made to a map-list, a static-map, or a map-group while the map is associated with an active SVC, connectivity to the IP address(es) associated with the static-map is interrupted. The IP address is not reachable until the associated Address Resolution Protocol (ARP) table entry is timed-out. The correct behavior is to allow map-list, a static-map, or a map-group to be modified at any time. This behavior was present in release 11.1(1). [CSCdi56066]
The SNMP ifPhysAddr of interface ATM 2/0/0 displays an empty string rather than (one of) the ATM address of the switch. [CSCdi59248]
The ATM ARP server does not check the IP subnet mask during registration. The ARP server registers an IP address that resides outside of its own subnet boundary. [CSCdi62225]
You can not disable signaling and SSCOP on an interface, except through the use of the atm nni command using the IISP image. This behavior was present in release 11.1(1). [CSCdi64829]
Note The primary function of the atm nni command is to configure an interface as an NNI interface (as opposed to a UNI or IISP interface). Signaling and SSCOP are disabled because the IISP image does not include any NNI signaling protocol. Any ambiguity in the meaning of the atm nni command is going to be removed when the new command to disable signaling and SSCOP is introduced.
Configuration of internal static routes is allowed even when the static route is a duplicate of an ILMI-registered address on another port of the same switch. This behavior was present in release 11.1(1). [CSCdi65799]
Under certain conditions, when one of the LightStream 1010 interfaces is shut/noshut repeatedly, some the SVCs may not be released properly. This can result in a LEC not being able to connect to the LECS if its SVC connection to LECS is not released properly from the LECS side.
A workaround is to use the clear atm-vc command to clear the SVC. [CSCdi65885]
If PNNI receives a hello packet with a length exceeding pnni_hello_type---for example, a hello packet with multiple type_length_value (TLV) fields---it will enter into an infinite loop. [CSCdi65795]
If the switch did not detect the physical link going down, SSCOP may not tear down the active switched virtual circuits (SVCs) properly. This occurs when SSCOP receives a begin PDU and treats the PDU as a retransmission, and it is ignored. [CSCdi66728]
Systems with less than three ports---for example 2 OC-12 PAMs---cause a failure in the power-on diagnostic tests even though the system and the ports are functional. The test failure causes the LightStream 1010 status LED to be red after power-on and a failure is indicated at the console display. [CSCdi66729]
Removing the receive end of DS3/E3 PAM does not cause the transmit end of the connection to go down. [CSCdi68141]
AToM MIB does not report correct the neighbor name for the virtual path (VP) tunnel. [CSCdi69035]
When a VP switch is placed along the path of a VP tunnel between two LS1010 switches, calls through this VP tunnel will not be completed if the VPI numbers on incoming interfaces and outgoing interfaces have different VPI numbers assigned. [CSCdi69105]
The allocation of a soft permanent virtual circuit (PVC) destination half-leg VPI/VCI is not correct. This allowed a switched virtual circuit (SVC) to be established through an interface to also allocate this same VPI/VCI, and then release it. Then the Soft PVC destination half-leg would disappear. [CSCdi69254]
The Service Specific Connection Oriented Protocol (SSCOP) incorrectly parses the protocol data unit (PDU) state if list elements equal 4. This causes a sequence error. To verify this problem, enable debug SSCOP error and an MAA_ERROR_S error will appear on the console. [CSCdi70022]
PNNI routing software might crash when a link (that is followed by one or more links with NULL metrics) is removed from the internal topology database. [CSCdi71540]
The flag bit in the global call reference is not set correctly in the restart and restart-ack message. It is always set to 0. [CSCdi71545]
A Feature card FPGA download driver could fail causing occasional disabling of the multi-cast and available bit rate (ABR) functions on the Feature card. This would cause some of the multi-cast and traffic-management power-on tests to fail and the Status LED on the ASP card to show red. [CSCdi72070]
Strict restrictions on UPC based on interface type are enforced. For example, tagging or dropping is not allowed on non-UNI-Network-side interfaces. Destination half-leg UPC is always set to passing. Resolution of this DDTS modifies the operation of atm pvc, atm pvp, atm soft-vc, and atm soft-vp commands, to remove the restriction of UPC to UNI-Network-side. [CSCdi72411]
UNI 3.0 to UNI 3.1 conversion is incorrect on PNNI interfaces. This occurs if the ingress port is a UNI 3.0 and the egress port is a PNNI. [CSCdi72611]
The per-interface CLI configuration atm svc-upc-intent command is not allowed using a corresponding SNMP MIB object. This configuration determines the inbound UPC action to perform for SVCs and terminating legs of Soft PVCs at an interface. [CSCdi72604]
The DS-3 driver ignores loss of cell delineation (LCD) far end receive failure (FERF) when using Cbit physical layer convergence protocol (PLCP) framing. [CSCdi72667]
Currently OAM Manager handles fault management functions. If it receives a non-fault management type OAM cell---performance management, system management, or activation/deactivation cells---the software process drops the cell. [CSCdi73621]
Error Message %ATMSIG-3-INVPNNIMSG : Invalid msg from routing/pnni : error return code No memory atmsys_get_buf for next_port_req No memory atmsys_get_buf for source_route_req No buffer for sending Setup message No buffer for sending Call Proceeding message No buffer for sending Connect message No buffer for sending Connect Ack messageNo buffer for sending Release message No buffer for sending Release Comp messageNo buffer for sending Status message No buffer for sending Status Enquiry message No buffer for sending Restart message No buffer for sending Restart Ack messageNo buffer for xfer Setup messageNo buffer for sending Connect message No buffer for sending Add Party messageNo buffer for sending Status message No buffer for sending AddPartyAck message No buffer for sending AddPartyRej messageNo buffer for sending DropParty message No buffer for sending DropPartyAck message No buffer for sending Begin Pdu No buffer for sending Begin Ack Pdu No buffer for sending Begin Rej Pdu No buffer for sending End Pdu No buffer for sending End Ack Pdu No buffer for sending Resync Pdu No buffer for sending Resync Ack Pdu No buffer for sending Ustat Pdu No buffer for sending Stat Pdu No buffer for sending Poll Pdu
Explanation <explanation>.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Explanation Unrecognized type of PNNI packet has been received.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message %PNNI-4-INTERNAL_ERROR: PNNI failed to get the argument to pnni_router process
Explanation An internal software error has occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message %PNNI-4-INTERNAL_ERROR: PNNI failed to set the argument to pnni_router process
Explanation An internal software error has occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message %PNNI-4-INTERNAL_ERROR: PNNI failed to set the argument to pnni_update process
Explanation An internal software error has occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message %PNNI-4-ADDRESS_EXIST: Address derived from the switch's prefix by soft PVC manager [chars] clashes with existing address in prefix table
Explanation Automatic soft PVC port address assignment fails. Address derived from the switch's prefix for soft PVC port clashes with an existing address in the prefix table.
Recommended Action If possible, assign a new MAC address to the end system that causes the clash.
Error Message %PNNI-4-ATM_SYS_ERROR: Error: Incorrect API version. Mismatched API message version received by PNNI.
Explanation An internal software error has occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message %PNNI-4-INTERNAL_ERROR: Cannot add NNI interface. An attempt to add an NNI interface failed.
Explanation An internal software error has occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message %PNNI-4-INTERNAL_ERROR: Received API message to create an interface for an existing port
Explanation An internal software error has occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message %PNNI-4-INTERNAL_ERROR:Received API message to delete an interface that PNNI does not know of
Explanation An internal software error has occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message %PNNI-4-ATM_SYS_ERROR: Error: Received Unrecognized API message
Explanation An internal software error has occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message %PNNI-4-INTERNAL_ERROR: Unrecognized req msg from signaling [hex]
Explanation Unrecognized request message from signaling error process.
Recommended Action If this message recurs, contact your technical support representative for assistance.
This section describes possibly unexpected behavior by Release 11.1(1) for the LightStream 1010 ATM switch.
The following caveats have been identified for this release of the LightStream 1010 ATM switch software.
If an existing End System Identifier (ESI) is removed from the ATM Switch Processor (ASP) interface or any of its sub-interfaces due to the following:
The command no esi-address
A new ESI is defined using the esi-address command. The 20 byte ATM address corresponding to the old ESI address which is registered with the Interim Link Management Interface (ILMI) is not removed. They exist together with the newly registered address corresponding to the new ESI. Similarly, when the prefix is changed the existing ILMI registered address (with the old prefix and the current ESI address) are not removed. [CSCdi47217]
The AAL5 table for the AToM MIB (RFC 1695) is not supported. [CSCdi48153]
The switch will reload if a large number of debug messages are configured to be processed.
If either the debug all or debug atm sig-all commands are enabled for all interfaces with a large number of calls, for example, thousands of calls, then the number of messages would be overwhelming for the system to handle.
To work around use specific debug flags for the appropriate modules. If possible, enable debug flags for the specific interfaces that are needed to be tracked.
Most debug flags allow interface specification as a variable. [CSCdi50862]
The atm idle-timeout command at the ASP interface 2/0/0 is not supported.
Idle timeout defines how long an SVC connection can remain idle before the connection is torn down. This command does exist in the configuration but will have no impact on idle SVCs. Even if the idle timeout interval is configured, the interface will not be torn down. [CSCdi51446]
The Virtual Channel (VC) and Virtual Path (VP) cross-connects tables in the AtoM MIB are not supported. Permanent Virtual Circuit (PVCs) can be currently configured using the proprietary Cisco ATM connection MIB. [CSCdi51809]
The interpretation of the tolerance traffic parameter for Usage Parameter Control (UPC, or policing) on ATM Variable Bit Rate (VBR) PVCs is incorrect. UPC monitors the cell-traffic received on a connection for correctness based on the Generic Cell Rate Algorithm (GCRA). Optionally, UPC can be configured, per connection, to pass, and tag (set) the Cell Loss Priority (CLP) bit, or drop cells, that GCRA considers to be in violation of the traffic contract.
When a VBR PVC on an interface is created with UPC set to allow tagging or dropping, the connection-traffic-table row specified for receive dictates the UPC parameters. If the tolerance parameter is specified in the connection-traffic-table row, this should be interpreted as maximum burst size, and a computation done to determine a burst tolerance to use in the GCRA UPC algorithm. This computation is not done, instead the tolerance parameter is interpreted directly as burst tolerance. This causes the tolerance parameter to be interpreted as a number of cell times at 2.72 microseconds. [CSCdi52517]
The per interface debugging for ILMI, if turned on using the command debug atm card/sub_card/port will be disabled if the interface is shutdown. If debugging is required on an interface it has to be explicitly turned on after the interface is brought up again. [CSCdi52596]
The show atm vc traffic command may display a false 0 value for a terminating connection. [CSCdi54094]
Configuration memory full error message appears.
Adding too many configuration commands will cause earlier commands to be lost and the following error massage to appear:
% Configuration buffer full, can't add command: user command
This error indicates that the configuration memory limit has been reached and earlier, working commands, may be lost if you proceed.
Do not use the write memory or copy running-config commands if this error message appears. [CSCdi54713]
Map class configuration for SVCs initiated on the switch CPU interface interprets cell rates in units of cells-per-second instead of the correct units of kilobits-per-second.
This includes the following configuration command variables: [CSCdi54716]
The LAN Emulation Configuration Server (LECS) address can be configured on a switch-wide basis. This is applicable to both the command line interface (CLI) as well as Simple Network Management Protocol (SNMP). A future release of the software will allow the LECS address to be configured on a per-interface basis. [CSCdi55506]
Multiple ESI addresses differing only in their selector byte can not be registered on the ASP interface ATM 2/0/0 and its sub-interfaces. [CSCdi55662]
ILMI keepalive changes to default after interface shutdown and restart.
If the interface configuration parameter, ILMI keep-alive, is enabled and configured using the keepalive command, and the interface is shutdown and restarted, the configuration is reset to the default value of 5 seconds. [CSCdi55676]
OAM cells are not handled correctly by the switch.
All OAM cells in the transit connections are being forwarded without processing. OAM related commands, for example, the atm ping command, are currently disabled. [CSCdi55921]
Currently all soft VP calls that specify service category as Constant Bit Rate (CBR) will be connected as Unspecified Bit Rate (UBR) calls. This problem does not affect the Soft VC calls. [CSCdi55962]
Static maps are used to associate IP addresses with NSAP addresses, so that an ATM SVC can be established to contact the associated host.
The static-map can specify a map-class to indicate traffic parameters to use when initiating an ATM SVC. Many static-maps should be able to use the same map-class. Currently, confusion can occur if several static-maps share the same map-class, such that only one of the maps sharing the map-class can be used at one time. The correct behavior would be to keep all static-map status information only in the static-map, rather than the map-class data structure. A workaround is to not share map-classes among static-maps.
If changes are made to a map-list, a static-map, or a map-group, while the map is associated with an active SVC, then connectivity to the IP address(es) associated with the static-map is interrupted. The IP address is not reachable until the associated Address Resolution Protocol (ARP) table entry is timed-out. The correct behavior would be to allow map-list, a static-map, or a map-group to be modified at any time. [CSCdi56066]
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information,productdocumentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
