HPE MSR1000 - Page 58

54
201501290181
•
Symptom: When a L2VPN cross-connect is bound to a Layer 3 aggregate interface, receiving
LACPDUs times out, and the aggregation group member ports flap frequently.
•
Condition: This symptom occurs when the L2VPN cross-connect is bound to a Layer 3
aggregate interface.
•
Workaround: None.
201501080118
•
Symptom: The VAM process reboots repeatedly.
•
Condition: This symptom occurs when the hub device also acts as the VAM server.
•
Workaround: Use a separate device as the VAM server.
201411140486
•
Symptom: Ping packets are lost on an eight-wire G.SHDSL.BIS EFM interface of the MSR
router after the interface is shut down and then brought up.
•
Condition: This symptom might occur if the EFM interface is connected to a Cisco device.
201502150313
•
Symptom: Packet loss occurs on an interface that is configured with both policy nesting and
CBQ.
•
Condition: This symptom might occur if the interface has been forwarding traffic at near wire
rate for a long time.
201502030476
•
Symptom: The MSR router forwards some packets out of their incoming interface after an
active/standby link switchover.
•
Condition: This symptom might occur if the active/standby link switchover occurs when the
router is forwarding a large amount of traffic.
201502270045
•
Symptom: The serial communication protocol goes down and LCP packets are lost on a serial
interface when it is processing bidirectional traffic during the T1 delay test.
•
Condition: This symptom might occur if the qos qmtoken 1 command is executed on the
interface.
201503090250
•
Symptom: The MSR router does not update the media channel after it receives a re-INVITE
message with only the c field updated.
•
Condition: This symptom might occur if the MSR router receives a re-INVITE message with only
the c field updated.
201503160098
•
Symptom: CAR does not support the bandwidth percentage method.
•
Condition: This symptom might occur if CAR is configured by using the bandwidth percentage
method.
201407180184
•
Symptom: A local PBR policy does not take effect when no other services are configured.
•
Condition: This symptom might occur if only a local PBR policy is configured on the router.