EasyManua.ls Logo

HPE MSR3000 - Page 42

HPE MSR3000
371 pages
Print Icon
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...
38
201509300412
•
Symptom: The peer drops the ARP packets sent by the router if the ARP packets carry 802.1Q
VLAN tags with the CFI bit set to 1.
•
Condition: This symptom might occur if the ARP packets carry 802.1Q VLAN tags with the CFI
bit set to 1.
201509240177
•
Symptom: The router reboots unexpectedly if an HMIM-CNDE module is removed by using the
remove command during the IPsec packet forwarding process.
•
Condition: This symptom might occur if an HMIM-CNDE module is removed by using the
remove command during the IPsec packet forwarding process.
201510260569
•
Symptom: If port isolation is configured on both a Layer 2 aggregate interface and its member
ports, the configuration fails on the aggregate interface or its member ports. Removal of the port
isolation configuration also fails.
•
Condition: This symptom might occur if port isolation is configured on a Layer 2 aggregate
interface and its member ports.
201509240346
•
Symptom: Channel configuration on radio interfaces is lost after a reboot.
•
Condition: None.
201509300064
•
Symptom: The traffic statistics for 3G/4G serial and Eth-channel interfaces are 0 in the MIB.
•
Condition: None.
201510300208
•
Symptom: The router cannot communicate with the peer if the router acts as the LNS to set up
an L2TP tunnel to the peer by using a SIC-4FSW module.
•
Condition: This symptom might occur if the router acts as the LNS to set up an L2TP tunnel to
the peer by using a SIC-4FSW module.
201511110304
•
Symptom: The router reboots unexpectedly if VLAN interfaces are created or deleted during the
traffic forwarding process.
•
Condition: This symptom might occur if VLAN interfaces are created or deleted during the traffic
forwarding process.
201508290046
•
Symptom: The CPU usage of the router rises if the router acts as a Telnet server and Telnet
login to the router is aborted abnormally.
•
Condition: This symptom might occur if the router acts as a Telnet server and Telnet login to the
router is aborted abnormally.
201509290092
•
Symptom: Telnet login with remote TACACS/RADIUS authentication fails.
•
Condition: This symptom might occur if Telnet login with remote TACACS/RADIUS
authentication is performed.
201505130349
•
Symptom: Static NAT444 traffic does not trigger NAT444 user logging.

Table of Contents