Transition Networks
S4224 Web User Guide
33558 Rev. C
Page 552 of 669
ERPS Troubleshooting
Failure of protocol defect
: due to errors in provisioning, the ERP control process may detect a
combination of conditions which should not occur during "normal" conditions. To warn the operator of
such an event, a failure of protocol – provisioning mismatch (FOP-PM) is defined. The FOP-PM defect,
detected if the RPL owner node receives one or more No Request R-APS message(s) with the RPL
Blocked status flag set (NR, RB), and a node ID that differs from its own. The ERP control process must
notify the equipment fault management process when it detects such a defect condition, and continue its
operation as well as possible. This is only an overview of the defect condition. The associated defect and
its details are defined in
as amended by its Amendments 1 and 2.
IPv6 Troubleshooting
Start by using these third party resources when performing general IPv6 problem solving:
The standard Windows 7 command-line tools with full IPv6 functionality (Ping, Ipconfig, Pathping,
Tracert, Netstat, and Route all support IPv6).
The IPv6-specific tools in the Netsh command.
Address Resolution in Windows 7
In unicast global IPv6 (equal to IPv4 Public) addresses, the 64-bit host portion of the address is derived
from the MAC address of the network adapter. The Neighbor Discovery (ND) protocol resolves IPv6
addresses to MAC addresses. The resolution of host names to IPv6 addresses is done by DNS with the
exception of link-local (equivalent to IPv4 APIPA) addresses, which resolve automatically. DNS handles
records for IPv6 host names similar to IPv4 and also uses pointer (PTR) records to perform reverse
lookups. Where DNS is not implemented (e.g., peer-to-peer environments) the Peer Name Resolution
Protocol (PNRP) provides dynamic name registration and name resolution.
Verify IPv6 Configuration in Windows 7
The main tool is Ipconfig. The command
ipconfig /all
displays both IPv4 and IPv6 configuration. To
display the configuration of only the IPv6 interfaces use netsh. The
netsh interface ipv6 show addres
s
command displays each interface IPv6 address including the interface ID after the % character (the
configuration can be accessed via the GUI).
Verify IPv6 Connectivity
ping
the local address. Note that if pinging link-local addresses from one host to another, you must
include the destination adapter interface ID (e.g., ping fe80::38e7:3df1:f5ff:fdf0%13). When pinging site-
local (equal to IPv4 Private) addresses you can add the interface ID to ensure that the address is
configured on the desired interface. You must add an ‘allow’ rule for ICMPv6 traffic to pass through each
computer’s firewall.
Command examples
- third party CLI commands for IPv6:
ipconfig /all
netsh interface ipv6 show address
ping fe80::38e7:3df1:f5ff:fdf0%13
)
netsh interface ipv6 delete neighbors
netsh interface ipv6 show neighbors
netsh interface ipv6 delete destinationcache
netsh interface ipv6 show destinationcache
netsh interface ipv6 show route
route print
tracert -d <destination IPv6 address>
pathping -d <destination IPv6 address>
