EasyManua.ls Logo

HPE MSR3000 - Page 40

HPE MSR3000
371 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
36
Condition: This symptom occurs if ARP snooping is enabled on interfaces on the HMIM-8GSW
or HMIM-24GSW interface card.
201512180334
Symptom: The MSR2004-24 or MSR2004-48 router reboots unexpectedly.
Condition: This symptom occurs if the parameter of an SDK function on the switching chip of the
router is null.
201511120124
Symptom: Packets are sent out of order.
Condition: This symptom occurs if packets are sent in per-flow mode.
201511270774
Symptom: A silent call is established after the called party goes off-hook.
Condition: This symptom occurs if the router uses the SIC-1VE1 or SIC-1VT1 voice card to
initiate calls.
201512140104
Symptom: The mac-address max-mac-count command does not take effect, and no error
message that the router does not support this command is displayed.
Condition: This symptom occurs if the mac-address max-mac-count command is executed
on a Layer 2 aggregate interface.
201511300156
Symptom: The static IPv6 address binding feature does not take effect on an interface of the
HMIM-8GSW interface card.
Condition: This symptom occurs if the static IPv6 address binding feature is configured on the
interface of the HMIM-8GSW card.
201512100157
Symptom: Transceiver modules on the HMIM-8GSW interface card might fail the equipment
test.
Condition: This symptom occurs if the equipment test is performed on the HMIM-8GSW
interface card.
201511170229
Symptom: When a POS terminal hangs up, the FCM interface stays in up state and the FCM
card becomes unavailable.
Condition: This symptom occurs if the router uses the FCM card for POS dial-up access and a
large number of POS terminals repeatedly dial up.
201511250418
Symptom: The 3G chip MC8705 fails to update the firmware.
Condition: This symptom occurs if an MSR2004/4000 router is used to update the firmware of
the 3G chip MC8705.
201510190389
Symptom: An L2TP tunnel cannot be established because the router performs strict check on
packets with hidden AVPs.
Condition: This symptom occurs if the router acts as the L2TP LNS and receives packets with
hidden AVPs sent by the LAC.

Table of Contents

Related product manuals