Filter
Top Products
3. Troubleshooting Functional Failures in Operation
76
detail command, it is necessary to match the displayed DUIDs and client systems. To do that, compare the value
of distributed prefixes displayed in the binding information and the information of prefixes distributed to client
system.
(e) Checking client setting
Check the client setting referring manuals provided with client.
(f) Procedure for restoring from duplicate distribution
If it is determined that duplicated prefixes were distributed to the same client by the IPv6DHCP server in this system,
examine currently unused prefixes from the matching of displayed DUIDs and clients. Delete binding information for
currently unused prefixes using the clear ipv6 dhcp binding <unused prefixes> command.
[Execution results]
> show ipv6 dhcp binding detail
Total: 2 prefixes
<Prefix> <Lease expiration> <Type>
<DUID>
3ffe:1234:5678::/48 05/04/01 11:29:00 Automatic
00:01:00:01:55:55:55:55:00:11:22:33:44:55
3ffe:aaaa:1234::/48 05/04/01 11:29:00 Automatic
00:01:00:01:55:55:55:55:00:11:22:33:44:55
> clear ipv6 dhcp binding 3ffe:1234:5678::/48
> show ipv6 dhcp binding detail
<Prefix> <Lease expiration> <Type>
<DUID>
3ffe:aaaa:1234::/48 05/04/01 11:29:00 Automatic
00:01:00:01:55:55:55:55:00:11:22:33:44:55
>
(2) Communication with the target of the prefix distribution is disabled
The following two possible causes of route information are not set when using the automatic route information setting
feature for the route to prefix distribution target of the DHCP server in this system.
1. Information is configured but not distributed.
2. Operations or events have occurred that have an effect on functions relating to automatic route information setting.
It is possible to isolate the above reasons by comparing the results of the show ipv6 route -s command which
checks route information and distributed prefix information displayed by the show ipv6 dhcp server
binding command.
Table 3-33: Isolating Problems Relate Routing Information to Prefix Distribution Target
There are limits to the retention of route information to prefix distribution target, as indicated in the table below.
Condition Cause
Binding Information Route Information
Yes Route exists Not applicable. active state.
Yes No route Cause 2
None Route exists Cause 2
None No route Causes 1, 2