Table of Contents
Advertisement
Resolved Problems in CMW520-R2105P35
RTD53977
Symptom: There were some lost packets at the high PRI queue even if the high priority
packets didn't exceed the bandwidth assigned.
Condition: The FR traffic shaping function was enabled at the FR interface, and the CIR
of the DLCI was equal to the bandwidth of the interface, the QOS queues were set at
the DLCI.
Resolved Problems in CMW520-R2105P31
RTD54152
Symptom: If the ARP entries updated, the sequence of static ARP entries saved
changed.
Condition: Configure some static ARP entries at the router.
Resolved Problems in CMW520-R2105P26
RTD54042
Symptom: After doing the two operations simultaneity period of time, the router's
configuration file lost.
Condition: Execute the command "save" to save the configuration file at the router,
at the same time put the configuration file to the router using TFTP.
RTD53983
Symptom: The packets transmitted by the interface can't be translated correctly.
Condition: Certain interface of the router was bound to the VPN-instance, and was
enabled the NAT function.
RTD53976
Symptom: If defining several PU facilities using the same MAC address, the router only
could establish virtual circuit for one PU facility.
Condition: The two routers established the DLSw peer, and transmitted the packets
between the IBM mainframe and SNA host.
RTD53848
Symptom: Even though the L2TP client was asynchronous PPP, the router still sent the
SLI control packets with ACCM option, and sometime this should bring on that the L2TP
connection negotiated unsuccessfully.
Condition: The router acts as LNS established the L2TP connection with other
equipment.
38
Advertisement
Table of Contents
