Possible causes for a failure to ping an IPv6 address

5

In V100R002 and later versions, the IPv6 address of a device fails to be pinged due to the following possible causes:
l. The physical state or protocol state of the interface is Down. You can run the display ipv6 interface interface-type interface-number command in any view to check the physical state and protocol state of an interface.
2. The switch fails to learn ND entries of the peer device. You can run the display ipv6 neighbors command in any view to check information about ND entries.
3. The link transmission delay is too long. The source device does not receive any Response packet from the destination device within the waiting time, and the ping operation fails. You can run the ping ipv6 -t timeout destination-ipv6-address command in any view to set “-t&rdquo to increase the timeout interval for waiting for Response packets.

Other related questions:
Possible causes for an IPv6 address conflict on an interface
In V100R002 and later versions, an IPv6 address conflict on an interface may be caused by the following - The peer interface directly connected to this interface has been configured with the same IPv6 address as that of the interface. - After the internal loopback detection function is enabled on an Ethernet interface, the IPv6 link-local address status of the interface is DUPLICATE, and the IPv6 global unicast address status of the interface is TENTATIVE (the address is a tentative address and have not passed the duplicate address detection). You can run the undo loopback command in the Ethernet interface view to disable the loopback detection mode on the interface. - There is a loop on the network. Note: By default, a switch performs duplicate address detection after an IPv6 address is configured for an interface on the switch. You can run the display ipv6 interface interface-type interface-number command in any view to check whether the IPv6 address of an interface conflicts with another IPv6 address.

What are possible causes for L2TP dial-up failures of the AR router
Possible causes for L2TP dialup failures are as follows: - The firewall is configured on the public network or the local PC has the firewall, so L2TP packets are discarded. - When corresponding L2TP port is disabled or occupied, UDP port 1701 is often used. For example, ACL and NAT are configured. - The user name and password of the LAC are incorrect, or no users are specified for the LNS. - The configured address is incorrect. For example, the statically configured address of the VT interface is incorrect. - Tunnel authentication modes are different. - LCP renegotiation is not configured. - The IP address allocation is improper. The IP address pool has a small address range or not configured. - Gateway addresses are not configured in the IP address pool, so gateway addresses are allocated to clients. - There are unreachable routes. - In the L2TP group view, the specified tunnel name at the remote end is incorrect. - The configured authentication domain is incorrect. - L2TP negotiation fails because control packets sent by clients of the local PC do not carry the SQ. - When IPSec encryption is used, the IPSec parameters on the two ends of the tunnel are inconsistent.

Possible causes for a failure to learn ND entries
In V100R002 and later versions, a switch fails to learn ND entries due to the following possible causes: - The physical state or protocol state of the interface is Down. You can run the display ipv6 interface interface-type interface-number command in any view to check the physical state and protocol state of an interface. - The STP state of the interface is Discarding. You can run the display stp brief command in any view to check the STP state of an interface. - The number of ND entries or IPv6 routes exceeds the limit. - You can run the display ipv6 neighbors command in any view to check information about ND entries. - You can run the display ipv6 routing-table statistics command in any view to check statistics on IPv6 routes.

Possible causes of S1700 login failure using the default management IP address
The possible causes of S1700 login failure using the default management IP address are as follows: �?The switch IP address is incorrect. �?The IP address of the PC and the switch IP address are on different network segments or are unreachable for each other. �?The user name and password are incorrect. �?The switch cannot be managed on the web platform. �?The browser is problematic or incompatible. Rectify the fault as follows: 1. The management IP address of a web-managed switch (the S1728GWR-4P) is 192.168.0.1 or assigned by the DHCP server. The management IP address of an SNMP-based switch (the S1700-28GFR-4P-AC, S1700-52GFR-4P-AC, S1700-28FR-2T2P-AC, S1700-52FR-2T2P-AC, S1720-20GFR-4TP, or S1720-28GFR-4TP switch) is 192.168.1.253. If the switch obtains an IP address through DHCP and you cannot check the IP address, connect a PC to the switch and log in to the switch using the IP address of 192.168.0.1. 2. Check whether the IP address of the PC and the switch IP address are on the same network segment. Check whether the cable between the PC and switch is properly connected and whether the interface indicator status is normal. If not, replace the cable or connect the cable to another interface. 3. The default user name and password for logging in to a switch are admin and Admin@123, respectively. The password for logging in to the S1720 is admin@huawei.com. If you have changed the login password and forget the changed password, holding down the Reset button to restore the factory setting and re-log in to the switch. 4. Only the S1700 series switches of which the name contains the letter w or F support web-based management. 5. Clear the browser's cache or use another browser.

What are the possible causes for SSH+TACACS authentication failure
There is no default authentication mode for SSH users. If no authentication mode is specified for SSH users, users cannot access the Internet. Solution: When configuring SSH authentication, run the ssh authentication-type default password command to configure password authentication for SSH users.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top