3 confirming ospfv3 interface information, 4 confirming the peering information of bgp4, 3 confirming ospfv3 interface information -38 – Hitachi GR2000 Series User Manual
Page 138: 4 confirming the peering information of bgp4+ -38, Figure 5-71. result of s

Hitachi Gigabit Router GR2000 Series Enhanced Version Operations - Device Management Overview
5-38
GR2K-GA-0015
Ver. 07-02
5.6.3
Confirming OSPFv3 interface information
When a OSPFv3 function is set using the IPv6 unicast routing information of the
router, execute a show ipv6 ospf interface and confirm the following.
Confirm that adjacent routers exist in the Neighbor List that are to advertise the
relevant route. If they do not exist, Hello packets are not received from adjacent
routers. Examine the adjacent routers or interfaces connecting adjacent routers.
Confirm that the State is not Two Ways. If it is Two Ways, the priority of the local
device and adjacent router may not have been set. Set the priority of the local
device and adjacent routers.
Confirm that the State is Full. If it is other than Full, an adjacent relationship
has not been established with the adjacent routers. Examine adjacent routers.
If the State is Full, the adjacent routers may not be advertising the relevant
route. Examine the adjacent routers (it is possible to confirm whether or not the
adjacent routers are advertising the relevant route by using the
show ipv6 ospf
area
command).
Figure 5-71 Result of show ipv6 ospf interface Command
5.6.4
Confirming the peering information of BGP4+
When a BGP4+ function is set using the IPv4 unicast routing information of the
router, execute a show ipv6 bgp neighbors and confirm the following.
Make sure that the BGP4+ status is Established. If it is not, pairing with the
remote BGP4+ speaker has not been established. Using a command such as ping
ipv6 make sure that communication with the remote BGP4+ speaker is enabled.
If communication is disabled, there might be an error in this router or on the
interface between this router and the remote BGP4+ speaker. Enter the
traceroute
command to locate the fault. If communication is enabled, troubleshoot the
remote BGP4+ speaker.
Even though the BGP4+ Status is Established, the remote BGP4+ speaker might
not have reported the relevant route. For confirmation, enter the
show ipv6 bgp
command to see if the route is open to the remote BGP4+ speaker.
> show ipv6 ospf interface Ether00
Domain: 1
Area: 0.0.0.0
Interface ID: 2, Link Local Address: fe80::1000:00ff:fe00:0001%Ether00
IPv6 Address: 3ffe:501:ffff::1/64
MTU: 1460, DDinPacket: 70, LSRinPacket: 117, ACKinPacket:70
Router ID: 172.16.1.1, Network Type: Broadcast, State: Backup DR
DR: 172.17.1.1, Backup DR: 172.16.1.1
Priority: 1, Cost: 1, Instance: 0
Intervals:
Hello: 10s, Dead Router: 40s, Retransmission: 5s, Delay: 1s
Neighbor List (1):
Address State Router ID Priority
fe80::1000:00ff:fe00:2002 Full 172.16.10.11 1
Priority
fe80::1000:00ff:fe00:2002 Full 172.16.10.11 1
>