Re: RBE on ipv6 - Page 2

paolo-prandini · ‎10-29-2010

Hi,

my network works in RBE in ipv4.

I have a 7204 router connected with ATM network to CPEs.

CPEs are configured in IRB brdige mode and receives IP addresses from an external DHCP server.

Now I want to introduce the ipv6.

I woul like to use the dual-stack (ipv4 and v6) transition.

How can I configure CPE and 7204?

I have tried, whitout success, to follow these documents:

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6553/whitepaper
_c11-602131.html

http://www.iphelp.ru/doc/3/Cisco.Press,.Deploying.IPv6.Networks.%282006%29.BBL/1587052105/ch03lev1sec3.html


http://www.cisco.com/en/US/docs/ios/12_4t/12_4t2/htrbeqos.html


I have also found that there is a bug in the IRB mode so ipv4 and v6 can't coexist:
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCej50923

Any tips are welcome.

Thanks.

Regards.

Phillip Remaker · ‎11-08-2010

If you look at "show ipv6 neighbbors" on both sides, are they two devices seeing each other across the ATM?

paolo-prandini · ‎11-10-2010

Hi Phill,

here the result of show ipv6 neighbors:

7204:
IPv6 Address Age Link-layer Addr State Interface

2A00:19A8::6                              102           000c.29dc.0014 STALE Gi0/1
2A00:19A8::7                              102            000c.2971.71fd STALE Gi0/1
FE80::20C:29FF:FEDC:14            102           000c.29dc.0014 STALE Gi0/1
FE80::20C:29FF:FE71:71FD         102           000c.2971.71fd STALE Gi0/1

Client:

IPv6 Address                                 Age         Link-layer Addr State Interface
FE80::A8BE:DB56:DF50:A8A0       3             0023.54ed.401a STALE FastEthernet 0/0
2A00:19A8:100::2                          3             0023.54ed.401a STALE FastEthernet 0/0

In the 2a00:19a8:/64 network there is the cisco7204 (2a00:19a8::14) and two machines (2a00:19a8::6, 2a00:19a8::7).

In the 2a00:19a8:0100::/64 network there is the cisco2600 (2a00:19a8::1) and a PC (2a00:19a8::2).

As you can see there is no presence of the 2a00:19a8:1::/64 network (the network used by the bridge)!!

Bye

Phillip Remaker · ‎11-10-2010

So remind me why you are using bridge encapsulation here and not straight routing? This is a pure routing configuration, really.

The RBE case is really for the CPE to be a pure bridge, but the central device to act as a router.

I suspect the use of the BVI interface is exposing the bug CSCej50923 mentioned earlier in the thread.

Do you need to keep bridge encapsulation in place to support dual v4/v6 stack? Why not do straight routing?

If you eliminate the BVI interface and move the BVI address configuration direct to interface ATM0/1, will that work? You probably have to also configure atm route-bridged ipv6 so that both sides use the same bridge encapsulation for IPv6.

Warning: I am making educated guesses here. I would be curious to know if that works, though.

(PS: Can you upgrade the edge router to the latest 15.1T?)

paolo-prandini · ‎11-10-2010

Hi Phill,

maybe you have forgiven the initial point.

In IPv4 I'm using the RBE with RFC1483 bridged client because I don't want to use PPPOA and the radius server.

The network works in this way:

The 7204 acts as a DHCP relay and it is connected to an external DHCP server.

For each client there is a subinterface atm unnumbered with loopback 0.

The clients have a BVI interface that takes an IP address from the DHCP server.

When the host boots up, it sends out DHCP requests.

These requests are then relayed by 7204 to the DHCP server, which assigns to the host a public IP address matching one of the remote-id stored int the DHCP server configuration.

In order to forward the initial DHCP requests from the host to the appropriate DHCP server, it use the ip helper-address command to the sub-interface which is receiving the broadcasts.

After the broadcasts are received, the Cisco IOS looks at the configuration of the ip helper-address for that interface and forwards those requests in a unicast packet to the DHCP server whose IP address is specified in ip helper-address.

After the DHCP server replies with the IP address, it sends the response to the interface on the router that originally forwarded the request.

This is used as the outbound interface to send the DHCP server response to the host that originally requested the service.

The 7204 also automatically installs a host route for this address and that's the point.

In the DHCP request forwarded by the relay there is the option 82 with the remote-id information.

So the remote-id stored in the request has to match one of the entries of the DHCP server configuration.

If the remote-id matches with one of the entries I have inserted, the DHCP assign the corresponding IPv4 address to the client and sets up a route to this host!

So if you try to assign a different IP (e.g other client IP) to a BVI client interface the 7204 doesn't create a route to this host!

This is one of the main advantages of the RBE tecnology for my network.

I want to make the same thing in IPV6.

I have ridden that in IPv6 & DHCPv6 the addition of the remote-ID option to the RELAY-FORWARD packet occurs automatically, no user configuration is necessary

At the moment I'm testing the network with a static IPv6 addresses but it isn't what I want to do in the end.

It is only for a preliminary test purpose.

If I try to not use the BVI interface and use straight routing the system works.. but not in the way I want!

Maybe you haven't considered that I have a lot of CPE clients and the straight routing creates a lot of problems.

For example there is no "route-on-demand" (sorry for the silly term, but it clarify the concept) offered by the RBE implementation.

Moreover with a a straight routing a client can use the other clients IP addresses.. and it is not good.

I hope to have explained my reasons for using the RBE.

The core router is actually in production, so the upgrading process can cause loss of service for the clients, but I can use my core network backup.

Thanks

Phillip Remaker · ‎11-12-2010

OK, thanks for the extra detail.

Is the long term strategy to hand out /64 or /48 subnets to end users? Do you have any plans to use DHCP-PD? Or are you planning specifically that DHCPv6 provides everything that the CPE needs to know?

Are you working for a service provider? Are you already working with the TAC or anyone else in Cisco?

I think we may be able to use your situation to develop a best practice use case. I beg your patience while I involve the correct people.

paolo-prandini · ‎11-12-2010

Yes I'm a Service Provider and I'm already working with cisco TAC about this problem.

I'm working with Ravish Malhotra, Pradeep Negi and Steven Loos.

We haven't found a solution yet.

At the moment they are waiting my result in using IOS 15.1(2)-T based client.

I have already informed these people about this topic.

Next week I'll receive a cisco 2800 and I should be able to test this scenario.

In IPv6 you have to give at least a /48 subnet to each client.

The /64 subnet is our work network. In this network you can find DHCP and DNS servers and also the edge routers connected to the Internet.

I have two DHCPDv6 server working in my network.

Is there some good reasons for preferring DHCP-PD rather than DCHPDv6?

I noticed that you have experience in IPv6.

Can I open a TAC with you in order to better explain and develop this problem?

Thanks

Bye

Phillip Remaker · ‎11-12-2010

I have less IPv6 experience than I would like, but work very closely with the teams that do. While I don't take cases directly, I frequently work with people in the TAC. I will be very happy to work with them or to talk directly with you if you think that will help.

As for DHCPv6 and DHCP-PD, I have not worked with them in an SP environment, though my colleagues have. My focus has mainly been on transition technologies, but I am eager to help forward thinking ISPs who provide native IPv6 to end users. Two of the key folks who may help are based in Europe and on holiday. I hope to get their attention soon.

paolo-prandini · ‎11-15-2010

Hi Phill,

the 2800 with IOS 15.1(2)-T2 is arrived... and it works in the way I want!!!

Now the next step.

The clients have to receive their IPv6 addresses from an external DHCPv6 server.

I think I can use the remote-id option integrated in the DHCPv6 protocol.

So I have to configure clients BVI interface in order to get IPv6 address from the SERVER.

7204 should acts as a relay.

And the DHCPv6 server has to match the remote-id of the request.

Do you have any tips?

Some news about the team you spoken about?

Is there any chance to contact you or this "ipv6" team?

Thanks

paolo-prandini · ‎11-18-2010

Hi Phill,

I'm having trouble with DHCPv6.

There is a DHCPDv6 server (unix machine) connected to the gigabitethernet 0/1 interface. It's ipv6 address is 2a00:19a8::6/64.

The BVI interface client should receive the ipv6 2a00:19a8:1::1/64. The subinterface atm2/0.1 has the ipv6: 2a00:19a8:1::11/64.

At the moment the Client receive from the DHCP the address: 2a00:19a8:1::1/128 and there is no chanche to route the traffic through the bridge.

In the DHCPD config there is no way to set the length of the subnet.

So the 7204 has to inform the client about the length of the subnet.

I have set in the sub interface atm2/0.1 the command: ipv6 dhcp nd prefix 2a00:19a8:1::/64 but the client doesn' t use this information.

Also I have founf that in the DHCP message there is a option 18 (interface-ID). In which way can I modify this value?

Thanks

I will paste the dhcp debug of the two devices:

2800

000625: *Nov 18 11:22:58.971 MEZ: IPv6 DHCP: DHCPv6 address changes state from I
DLE to SOLICIT (ADDR_START) on BVI1
000626: *Nov 18 11:23:00.051 MEZ: IPv6 DHCP: Sending SOLICIT to FF02::1:2 on BVI
1
000627: *Nov 18 11:23:00.051 MEZ: IPv6 DHCP: detailed packet contents
000628: *Nov 18 11:23:00.051 MEZ:   src FE80::200:CFF:FE05:8E74
000629: *Nov 18 11:23:00.051 MEZ:   dst FF02::1:2 (BVI1)
000630: *Nov 18 11:23:00.051 MEZ:   type SOLICIT(1), xid 700355
000631: *Nov 18 11:23:00.051 MEZ:   option ELAPSED-TIME(8), len 2
000632: *Nov 18 11:23:00.051 MEZ:     elapsed-time 0
000633: *Nov 18 11:23:00.051 MEZ:   option CLIENTID(1), len 10
000634: *Nov 18 11:23:00.051 MEZ:     00030001001EBEBC5DC2
000635: *Nov 18 11:23:00.051 MEZ:   option ORO(6), len 4
000636: *Nov 18 11:23:00.051 MEZ:     DNS-SERVERS,DOMAIN-LIST
000637: *Nov 18 11:23:00.051 MEZ:   option IA-NA(3), len 12
000638: *Nov 18 11:23:00.051 MEZ:     IAID 0x000A0001, T1 0, T2 0
000639: *Nov 18 11:23:00.063 MEZ: IPv6 DHCP: Received ADVERTISE from FE80::202:7
EFF:FEEB:601B on BVI1
000640: *Nov 18 11:23:00.067 MEZ: IPv6 DHCP: detailed packet contents
000641: *Nov 18 11:23:00.067 MEZ:   src FE80::202:7EFF:FEEB:601B (BVI1)
000642: *Nov 18 11:23:00.067 MEZ:   dst FE80::200:CFF:FE05:8E74 (BVI1)
000643: *Nov 18 11:23:00.067 MEZ:   type ADVERTISE(2), xid 700355
000644: *Nov 18 11:23:00.067 MEZ:   option IA-NA(3), len 40
000645: *Nov 18 11:23:00.067 MEZ:     IAID 0x000A0001, T1 0, T2 0
000646: *Nov 18 11:23:00.067 MEZ:     option IAADDR(5), len 24
000647: *Nov 18 11:23:00.067 MEZ:       IPv6 address 2A00:19A8:1::1
000648: *Nov 18 11:23:00.067 MEZ:       preferred 1125, valid 1800
000649: *Nov 18 11:23:00.067 MEZ:   option CLIENTID(1), len 10
000650: *Nov 18 11:23:00.067 MEZ:     00030001001EBEBC5DC2
000651: *Nov 18 11:23:00.067 MEZ:   option SERVERID(2), len 14
000652: *Nov 18 11:23:00.067 MEZ:     00010001147522B3000C29DC0014
000653: *Nov 18 11:23:00.067 MEZ:   option DNS-SERVERS(23), len 32
000654: *Nov 18 11:23:00.067 MEZ:     2A00:19A8::6
000655: *Nov 18 11:23:00.067 MEZ:     2A00:19A8::7
000656: *Nov 18 11:23:00.067 MEZ:   option DOMAIN-LIST(24), len 12
000657: *Nov 18 11:23:00.067 MEZ:     eleusi.com
000658: *Nov 18 11:23:01.131 MEZ: IPv6 DHCP: Sending REQUEST to FF02::1:2 on BVI
1
000659: *Nov 18 11:23:01.131 MEZ: IPv6 DHCP: detailed packet contents
000660: *Nov 18 11:23:01.131 MEZ:   src FE80::200:CFF:FE05:8E74
000661: *Nov 18 11:23:01.131 MEZ:   dst FF02::1:2 (BVI1)
000662: *Nov 18 11:23:01.131 MEZ:   type REQUEST(3), xid 702516
000663: *Nov 18 11:23:01.131 MEZ:   option ELAPSED-TIME(8), len 2
000664: *Nov 18 11:23:01.131 MEZ:     elapsed-time 0
000665: *Nov 18 11:23:01.131 MEZ:   option CLIENTID(1), len 10
000666: *Nov 18 11:23:01.131 MEZ:     00030001001EBEBC5DC2
000667: *Nov 18 11:23:01.131 MEZ:   option ORO(6), len 4
000668: *Nov 18 11:23:01.131 MEZ:     DNS-SERVERS,DOMAIN-LIST
000669: *Nov 18 11:23:01.131 MEZ:   option SERVERID(2), len 14
000670: *Nov 18 11:23:01.131 MEZ:     00010001147522B3000C29DC0014
000671: *Nov 18 11:23:01.131 MEZ:   option IA-NA(3), len 40
000672: *Nov 18 11:23:01.131 MEZ:     IAID 0x000A0001, T1 0, T2 0
000673: *Nov 18 11:23:01.131 MEZ:     option IAADDR(5), len 24
000674: *Nov 18 11:23:01.131 MEZ:       IPv6 address 2A00:19A8:1::1
000675: *Nov 18 11:23:01.131 MEZ:       preferred 1125, valid 1800
000676: *Nov 18 11:23:01.131 MEZ: IPv6 DHCP: DHCPv6 address changes state from S
OLICIT to REQUEST (ADDR_ADVERTISE_RECEIVED) on BVI1
000677: *Nov 18 11:23:01.147 MEZ: IPv6 DHCP: Received REPLY from FE80::202:7EFF:
FEEB:601B on BVI1
000678: *Nov 18 11:23:01.147 MEZ: IPv6 DHCP: detailed packet contents
000679: *Nov 18 11:23:01.147 MEZ:   src FE80::202:7EFF:FEEB:601B (BVI1)
000680: *Nov 18 11:23:01.147 MEZ:   dst FE80::200:CFF:FE05:8E74 (BVI1)
000681: *Nov 18 11:23:01.147 MEZ:   type REPLY(7), xid 702516
000682: *Nov 18 11:23:01.147 MEZ:   option IA-NA(3), len 40
000683: *Nov 18 11:23:01.147 MEZ:     IAID 0x000A0001, T1 0, T2 0
000684: *Nov 18 11:23:01.147 MEZ:     option IAADDR(5), len 24
000685: *Nov 18 11:23:01.147 MEZ:       IPv6 address 2A00:19A8:1::1
000686: *Nov 18 11:23:01.151 MEZ:       preferred 1125, valid 1800
000687: *Nov 18 11:23:01.151 MEZ:   option CLIENTID(1), len 10
000688: *Nov 18 11:23:01.151 MEZ:     00030001001EBEBC5DC2
000689: *Nov 18 11:23:01.151 MEZ:   option SERVERID(2), len 14
000690: *Nov 18 11:23:01.151 MEZ:     00010001147522B3000C29DC0014
000691: *Nov 18 11:23:01.151 MEZ:   option DNS-SERVERS(23), len 32
000692: *Nov 18 11:23:01.151 MEZ:     2A00:19A8::6
000693: *Nov 18 11:23:01.151 MEZ:     2A00:19A8::7
000694: *Nov 18 11:23:01.151 MEZ:   option DOMAIN-LIST(24), len 12
000695: *Nov 18 11:23:01.151 MEZ:     eleusi.com
000696: *Nov 18 11:23:01.151 MEZ: IPv6 DHCP: Processing options
000697: *Nov 18 11:23:01.151 MEZ: IPv6 DHCP: Adding address 2A00:19A8:1::1/128 t
o BVI1
000698: *Nov 18 11:23:01.151 MEZ: IPv6-Addrmgr-ND: DAD request for 2A00:19A8:1::
1 on BVI1
000699: *Nov 18 11:23:01.151 MEZ: ICMPv6: Sent type 254, Src=FE80::200:CFF:FE05:
8E74, Dst=FF02::16
000700: *Nov 18 11:23:01.151 MEZ: ICMPv6-ND: Sending NS for 2A00:19A8:1::1 on BV
I1
000701: *Nov 18 11:23:01.151 MEZ: IPv6 DHCP: T1 set to expire in 562 seconds
000702: *Nov 18 11:23:01.155 MEZ: IPv6 DHCP: T2 set to expire in 900 seconds
000703: *Nov 18 11:23:01.155 MEZ: IPv6 DHCP: Configuring DNS server 2A00:19A8::6

000704: *Nov 18 11:23:01.155 MEZ: IPv6 DHCP: Configuring DNS server 2A00:19A8::7

000705: *Nov 18 11:23:01.155 MEZ: IPv6 DHCP: Configuring domain name eleusi.com
000706: *Nov 18 11:23:01.155 MEZ: IPv6 DHCP: DHCPv6 address changes state from R
EQUEST to OPEN (ADDR_REPLY_RECEIVED) on BVI1
000707: *Nov 18 11:23:01.155 MEZ: ICMPv6: Sent N-Solicit, Src=::, Dst=FF02::1:FF
00:1
000708: *Nov 18 11:23:01.155 MEZ: ICMPv6-ND: DELETE -> INCMP: 2A00:19A8:1::1
000709: *Nov 18 11:23:01.155 MEZ: ICMPv6-ND: Sending NS for 2A00:19A8:1::1 on BV
I1
000710: *Nov 18 11:23:01.163 MEZ: ICMPv6: Sent N-Solicit, Src=FE80::200:CFF:FE05
:8E74, Dst=FF02::1:FF00:1
000711: *Nov 18 11:23:01.575 MEZ: ICMPv6: Sent type 254, Src=FE80::200:CFF:FE05:
8E74, Dst=FF02::16
000712: *Nov 18 11:23:02.151 MEZ: IPv6-Addrmgr-ND: DAD: 2A00:19A8:1::1 is unique
.
000713: *Nov 18 11:23:02.151 MEZ: ICMPv6-ND: Sending NA for 2A00:19A8:1::1 on BV
I1
000714: *Nov 18 11:23:02.155 MEZ: ICMPv6: Sent N-Advert, Src=2A00:19A8:1::1, Dst
=FF02::1
000715: *Nov 18 11:23:02.219 MEZ: ICMPv6-ND: Sending NS for 2A00:19A8:1::1 on BV
I1
000716: *Nov 18 11:23:02.223 MEZ: ICMPv6: Sent N-Solicit, Src=FE80::200:CFF:FE05
:8E74, Dst=FF02::1:FF00:1
000717: *Nov 18 11:23:03.311 MEZ: ICMPv6-ND: Sending NS for 2A00:19A8:1::1 on BV
I1
000718: *Nov 18 11:23:03.315 MEZ: ICMPv6: Sent N-Solicit, Src=FE80::200:CFF:FE05
:8E74, Dst=FF02::1:FF00:1
000719: *Nov 18 11:23:04.403 MEZ: ICMPv6-ND: INCMP deleted: 2A00:19A8:1::1
000720: *Nov 18 11:23:04.403 MEZ: ICMPv6-ND: INCMP -> DELETE: 2A00:19A8:1::1
000721: *Nov 18 11:23:05.063 MEZ: ICMPv6: Received N-Solicit, Src=FE80::202:7EFF
:FEEB:601B, Dst=FE80::200:CFF:FE05:8E74
000722: *Nov 18 11:23:05.063 MEZ: ICMPv6-ND: Received NS for FE80::200:CFF:FE05:
8E74 on BVI1 from FE80::202:7EFF:FEEB:601B
000723: *Nov 18 11:23:05.063 MEZ: ICMPv6-ND: Sending NA for FE80::200:CFF:FE05:8
E74 on BVI1
000724: *Nov 18 11:23:05.067 MEZ: ICMPv6-ND: STALE -> DELAY: FE80::202:7EFF:FEEB
:601B
000725: *Nov 18 11:23:05.067 MEZ: ICMPv6: Sent N-Advert, Src=FE80::200:CFF:FE05:
8E74, Dst=FE80::202:7EFF:FEEB:601B
000726: *Nov 18 11:23:10.123 MEZ: ICMPv6-ND: DELAY -> PROBE: FE80::202:7EFF:FEEB
:601B
000727: *Nov 18 11:23:10.123 MEZ: ICMPv6-ND: Sending NS for FE80::202:7EFF:FEEB:
601B on BVI1
000728: *Nov 18 11:23:10.127 MEZ: ICMPv6: Sent N-Solicit, Src=FE80::200:CFF:FE05
:8E74, Dst=FE80::202:7EFF:FEEB:601B
000729: *Nov 18 11:23:10.135 MEZ: ICMPv6: Received N-Advert, Src=FE80::202:7EFF:
FEEB:601B, Dst=FE80::200:CFF:FE05:8E74
000730: *Nov 18 11:23:10.135 MEZ: ICMPv6-ND: Received NA for FE80::202:7EFF:FEEB
:601B on BVI1 from FE80::202:7EFF:FEEB:601B
000731: *Nov 18 11:23:10.135 MEZ: ICMPv6-ND: PROBE -> REACH: FE80::202:7EFF:FEEB
:601B
000732: *Nov 18 11:23:40.227 MEZ: ICMPv6-ND: REACH -> STALE: FE80::202:7EFF:FEEB
:601B
000733: *Nov 18 11:23:48.611 MEZ: ICMPv6-ND: Request to send RA for FE80::21E:BE
FF:FEBC:5DC2
000734: *Nov 18 11:23:48.611 MEZ: ICMPv6-ND: Sending RA from FE80::21E:BEFF:FEBC
:5DC2 to FF02::1 on FastEthernet0/0
000735: *Nov 18 11:23:48.611 MEZ: ICMPv6-ND:     MTU = 1500
000736: *Nov 18 11:23:48.611 MEZ: ICMPv6-ND:     prefix = 2A00:19A8:100:1::/64 o
nlink autoconfig
000737: *Nov 18 11:23:48.611 MEZ: ICMPv6-ND:         1800/1125 (valid/preferred)

000738: *Nov 18 11:23:48.615 MEZ: ICMPv6: Sent R-Advert, Src=FE80::21E:BEFF:FEBC
:5DC2, Dst=FF02::1

7204

FE05:8E74 on ATM2/0.1
407591: Nov 18 11:13:59.822 MEZ: IPv6 DHCP: detailed packet contents
407592: Nov 18 11:13:59.822 MEZ:   src FE80::200:CFF:FE05:8E74 (ATM2/0.1)
407593: Nov 18 11:13:59.822 MEZ:   dst FF02::1:2
407594: Nov 18 11:13:59.822 MEZ:   type SOLICIT(1), xid 700355
407595: Nov 18 11:13:59.822 MEZ:   option ELAPSED-TIME(8), len 2
407596: Nov 18 11:13:59.822 MEZ:     elapsed-time 0
407597: Nov 18 11:13:59.822 MEZ:   option CLIENTID(1), len 10
407598: Nov 18 11:13:59.822 MEZ:     00030001001EBEBC5DC2
407599: Nov 18 11:13:59.822 MEZ:   option ORO(6), len 4
407600: Nov 18 11:13:59.822 MEZ:     DNS-SERVERS,DOMAIN-LIST
407601: Nov 18 11:13:59.822 MEZ:   option IA-NA(3), len 12
407602: Nov 18 11:13:59.822 MEZ:     IAID 0x000A0001, T1 0, T2 0
407603: Nov 18 11:13:59.822 MEZ: IPv6 DHCP_RELAY: Relaying SOLICIT from FE80::20
0:CFF:FE05:8E74 on ATM2/0.1
407604: Nov 18 11:13:59.822 MEZ: IPv6 DHCP_RELAY: to 2A00:19A8::6 via GigabitEth
ernet0/1
407605: Nov 18 11:13:59.822 MEZ: IPv6 DHCP: Sending RELAY-FORWARD to 2A00:19A8::
6 on GigabitEthernet0/1
407606: Nov 18 11:13:59.822 MEZ: IPv6 DHCP: detailed packet contents
407607: Nov 18 11:13:59.822 MEZ:   src 2A00:19A8::1
407608: Nov 18 11:13:59.822 MEZ:   dst 2A00:19A8::6 (GigabitEthernet0/1)
407609: Nov 18 11:13:59.822 MEZ:   type RELAY-FORWARD(12), hop 0
407610: Nov 18 11:13:59.822 MEZ:   link 2A00:19A8:1::11
407611: Nov 18 11:13:59.822 MEZ:   peer FE80::200:CFF:FE05:8E74
407612: Nov 18 11:13:59.822 MEZ:   option RELAY-MSG(9), len 48
407613: Nov 18 11:13:59.822 MEZ:     type SOLICIT(1), xid 700355
407614: Nov 18 11:13:59.822 MEZ:     option ELAPSED-TIME(8), len 2
407615: Nov 18 11:13:59.822 MEZ:       elapsed-time 0
407616: Nov 18 11:13:59.822 MEZ:     option CLIENTID(1), len 10
407617: Nov 18 11:13:59.822 MEZ:       00030001001EBEBC5DC2
407618: Nov 18 11:13:59.822 MEZ:     option ORO(6), len 4
407619: Nov 18 11:13:59.822 MEZ:       DNS-SERVERS,DOMAIN-LIST
407620: Nov 18 11:13:59.822 MEZ:     option IA-NA(3), len 12
407621: Nov 18 11:13:59.822 MEZ:       IAID 0x000A0001, T1 0, T2 0
407622: Nov 18 11:13:59.822 MEZ:   option INTERFACE-ID(18), len 4
407623: Nov 18 11:13:59.822 MEZ:     0x00000009
407624: Nov 18 11:13:59.822 MEZ: ICMPv6-ND: STALE -> DELAY: 2A00:19A8::6
407625: Nov 18 11:13:59.822 MEZ: IPv6 DHCP: Received RELAY-REPLY from 2A00:19A8:
:6 on GigabitEthernet0/1
407626: Nov 18 11:13:59.822 MEZ: IPv6 DHCP: detailed packet contents
407627: Nov 18 11:13:59.822 MEZ:   src 2A00:19A8::6 (GigabitEthernet0/1)
407628: Nov 18 11:13:59.822 MEZ:   dst 2A00:19A8::1
407629: Nov 18 11:13:59.822 MEZ:   type RELAY-REPLY(13), hop 0
407630: Nov 18 11:13:59.822 MEZ:   link 2A00:19A8:1::11
407631: Nov 18 11:13:59.822 MEZ:   peer FE80::200:CFF:FE05:8E74
407632: Nov 18 11:13:59.822 MEZ:   option INTERFACE-ID(18), len 4
407633: Nov 18 11:13:59.822 MEZ:     0x00000009
407634: Nov 18 11:13:59.822 MEZ:   option RELAY-MSG(9), len 132
407635: Nov 18 11:13:59.822 MEZ:     type ADVERTISE(2), xid 700355
407636: Nov 18 11:13:59.822 MEZ:     option IA-NA(3), len 40
407637: Nov 18 11:13:59.822 MEZ:       IAID 0x000A0001, T1 0, T2 0
407638: Nov 18 11:13:59.822 MEZ:       option IAADDR(5), len 24
407639: Nov 18 11:13:59.822 MEZ:         IPv6 address 2A00:19A8:1::1
407640: Nov 18 11:13:59.822 MEZ:         preferred 1125, valid 1800
407641: Nov 18 11:13:59.822 MEZ:     option CLIENTID(1), len 10
407642: Nov 18 11:13:59.822 MEZ:       00030001001EBEBC5DC2
407643: Nov 18 11:13:59.822 MEZ:     option SERVERID(2), len 14
407644: Nov 18 11:13:59.822 MEZ:       00010001147522B3000C29DC0014
407645: Nov 18 11:13:59.822 MEZ:     option DNS-SERVERS(23), len 32
407646: Nov 18 11:13:59.822 MEZ:       2A00:19A8::6
407647: Nov 18 11:13:59.822 MEZ:       2A00:19A8::7
407648: Nov 18 11:13:59.822 MEZ:     option DOMAIN-LIST(24), len 12
407649: Nov 18 11:13:59.822 MEZ:       eleusi.com
407650: Nov 18 11:13:59.822 MEZ: IPv6 DHCP_RELAY: Relaying RELAY-REPLY from 2A00
:19A8::6 on GigabitEthernet0/1
407651: Nov 18 11:13:59.822 MEZ: IPv6 DHCP_RELAY: to FE80::200:CFF:FE05:8E74 via
ATM2/0.1
407652: Nov 18 11:13:59.822 MEZ: IPv6 DHCP: Sending ADVERTISE to FE80::200:CFF:F
E05:8E74 on ATM2/0.1
407653: Nov 18 11:13:59.822 MEZ: IPv6 DHCP: detailed packet contents
407654: Nov 18 11:13:59.822 MEZ:   src FE80::202:7EFF:FEEB:601B
407655: Nov 18 11:13:59.822 MEZ:   dst FE80::200:CFF:FE05:8E74 (ATM2/0.1)
407656: Nov 18 11:13:59.822 MEZ:   type ADVERTISE(2), xid 700355
407657: Nov 18 11:13:59.822 MEZ:   option IA-NA(3), len 40
407658: Nov 18 11:13:59.822 MEZ:     IAID 0x000A0001, T1 0, T2 0
407659: Nov 18 11:13:59.822 MEZ:     option IAADDR(5), len 24
407660: Nov 18 11:13:59.822 MEZ:       IPv6 address 2A00:19A8:1::1
407661: Nov 18 11:13:59.822 MEZ:       preferred 1125, valid 1800
407662: Nov 18 11:13:59.822 MEZ:   option CLIENTID(1), len 10
407663: Nov 18 11:13:59.822 MEZ:     00030001001EBEBC5DC2
407664: Nov 18 11:13:59.822 MEZ:   option SERVERID(2), len 14
407665: Nov 18 11:13:59.822 MEZ:     00010001147522B3000C29DC0014
407666: Nov 18 11:13:59.822 MEZ:   option DNS-SERVERS(23), len 32
407667: Nov 18 11:13:59.822 MEZ:     2A00:19A8::6
407668: Nov 18 11:13:59.822 MEZ:     2A00:19A8::7
407669: Nov 18 11:13:59.822 MEZ:   option DOMAIN-LIST(24), len 12
407670: Nov 18 11:13:59.822 MEZ:     eleusi.com
407671: Nov 18 11:13:59.822 MEZ: ICMPv6-ND: STALE -> DELAY: FE80::200:CFF:FE05:8
E74
407672: Nov 18 11:14:00.902 MEZ: IPv6 DHCP: Received REQUEST from FE80::200:CFF:
FE05:8E74 on ATM2/0.1
407673: Nov 18 11:14:00.902 MEZ: IPv6 DHCP: detailed packet contents
407674: Nov 18 11:14:00.902 MEZ:   src FE80::200:CFF:FE05:8E74 (ATM2/0.1)
407675: Nov 18 11:14:00.902 MEZ:   dst FF02::1:2
407676: Nov 18 11:14:00.902 MEZ:   type REQUEST(3), xid 702516
407677: Nov 18 11:14:00.902 MEZ:   option ELAPSED-TIME(8), len 2
407678: Nov 18 11:14:00.902 MEZ:     elapsed-time 0
407679: Nov 18 11:14:00.902 MEZ:   option CLIENTID(1), len 10
407680: Nov 18 11:14:00.902 MEZ:     00030001001EBEBC5DC2
407681: Nov 18 11:14:00.902 MEZ:   option ORO(6), len 4
407682: Nov 18 11:14:00.902 MEZ:     DNS-SERVERS,DOMAIN-LIST
407683: Nov 18 11:14:00.902 MEZ:   option SERVERID(2), len 14
407684: Nov 18 11:14:00.902 MEZ:     00010001147522B3000C29DC0014
407685: Nov 18 11:14:00.902 MEZ:   option IA-NA(3), len 40
407686: Nov 18 11:14:00.902 MEZ:     IAID 0x000A0001, T1 0, T2 0
407687: Nov 18 11:14:00.902 MEZ:     option IAADDR(5), len 24
407688: Nov 18 11:14:00.902 MEZ:       IPv6 address 2A00:19A8:1::1
407689: Nov 18 11:14:00.902 MEZ:       preferred 1125, valid 1800
407690: Nov 18 11:14:00.902 MEZ: IPv6 DHCP_RELAY: Relaying REQUEST from FE80::20
0:CFF:FE05:8E74 on ATM2/0.1
407691: Nov 18 11:14:00.902 MEZ: IPv6 DHCP_RELAY: to 2A00:19A8::6 via GigabitEth
ernet0/1
407692: Nov 18 11:14:00.902 MEZ: IPv6 DHCP: Sending RELAY-FORWARD to 2A00:19A8::
6 on GigabitEthernet0/1
407693: Nov 18 11:14:00.902 MEZ: IPv6 DHCP: detailed packet contents
407694: Nov 18 11:14:00.902 MEZ:   src 2A00:19A8::1
407695: Nov 18 11:14:00.902 MEZ:   dst 2A00:19A8::6 (GigabitEthernet0/1)
407696: Nov 18 11:14:00.902 MEZ:   type RELAY-FORWARD(12), hop 0
407697: Nov 18 11:14:00.902 MEZ:   link 2A00:19A8:1::11
407698: Nov 18 11:14:00.902 MEZ:   peer FE80::200:CFF:FE05:8E74
407699: Nov 18 11:14:00.902 MEZ:   option RELAY-MSG(9), len 94
407700: Nov 18 11:14:00.902 MEZ:     type REQUEST(3), xid 702516
407701: Nov 18 11:14:00.902 MEZ:     option ELAPSED-TIME(8), len 2
407702: Nov 18 11:14:00.902 MEZ:       elapsed-time 0
407703: Nov 18 11:14:00.906 MEZ:     option CLIENTID(1), len 10
407704: Nov 18 11:14:00.906 MEZ:       00030001001EBEBC5DC2
407705: Nov 18 11:14:00.906 MEZ:     option ORO(6), len 4
407706: Nov 18 11:14:00.906 MEZ:       DNS-SERVERS,DOMAIN-LIST
407707: Nov 18 11:14:00.906 MEZ:     option SERVERID(2), len 14
407708: Nov 18 11:14:00.906 MEZ:       00010001147522B3000C29DC0014
407709: Nov 18 11:14:00.906 MEZ:     option IA-NA(3), len 40
407710: Nov 18 11:14:00.906 MEZ:       IAID 0x000A0001, T1 0, T2 0
407711: Nov 18 11:14:00.906 MEZ:       option IAADDR(5), len 24
407712: Nov 18 11:14:00.906 MEZ:         IPv6 address 2A00:19A8:1::1
407713: Nov 18 11:14:00.906 MEZ:         preferred 1125, valid 1800
407714: Nov 18 11:14:00.906 MEZ:   option INTERFACE-ID(18), len 4
407715: Nov 18 11:14:00.906 MEZ:     0x00000009
407716: Nov 18 11:14:00.906 MEZ: IPv6 DHCP: Received RELAY-REPLY from 2A00:19A8:
:6 on GigabitEthernet0/1
407717: Nov 18 11:14:00.906 MEZ: IPv6 DHCP: detailed packet contents
407718: Nov 18 11:14:00.906 MEZ:   src 2A00:19A8::6 (GigabitEthernet0/1)
407719: Nov 18 11:14:00.906 MEZ:   dst 2A00:19A8::1
407720: Nov 18 11:14:00.906 MEZ:   type RELAY-REPLY(13), hop 0
407721: Nov 18 11:14:00.906 MEZ:   link 2A00:19A8:1::11
407722: Nov 18 11:14:00.906 MEZ:   peer FE80::200:CFF:FE05:8E74
407723: Nov 18 11:14:00.906 MEZ:   option INTERFACE-ID(18), len 4
407724: Nov 18 11:14:00.906 MEZ:     0x00000009
407725: Nov 18 11:14:00.906 MEZ:   option RELAY-MSG(9), len 132
407726: Nov 18 11:14:00.906 MEZ:     type REPLY(7), xid 702516
407727: Nov 18 11:14:00.906 MEZ:     option IA-NA(3), len 40
407728: Nov 18 11:14:00.906 MEZ:       IAID 0x000A0001, T1 0, T2 0
407729: Nov 18 11:14:00.906 MEZ:       option IAADDR(5), len 24
407730: Nov 18 11:14:00.906 MEZ:         IPv6 address 2A00:19A8:1::1
407731: Nov 18 11:14:00.906 MEZ:         preferred 1125, valid 1800
407732: Nov 18 11:14:00.906 MEZ:     option CLIENTID(1), len 10
407733: Nov 18 11:14:00.906 MEZ:       00030001001EBEBC5DC2
407734: Nov 18 11:14:00.906 MEZ:     option SERVERID(2), len 14
407735: Nov 18 11:14:00.906 MEZ:       00010001147522B3000C29DC0014
407736: Nov 18 11:14:00.906 MEZ:     option DNS-SERVERS(23), len 32
407737: Nov 18 11:14:00.906 MEZ:       2A00:19A8::6
407738: Nov 18 11:14:00.906 MEZ:       2A00:19A8::7
407739: Nov 18 11:14:00.906 MEZ:     option DOMAIN-LIST(24), len 12
407740: Nov 18 11:14:00.906 MEZ:       eleusi.com
407741: Nov 18 11:14:00.906 MEZ: IPv6 DHCP_RELAY: Relaying RELAY-REPLY from 2A00
:19A8::6 on GigabitEthernet0/1
407742: Nov 18 11:14:00.906 MEZ: IPv6 DHCP_RELAY: to FE80::200:CFF:FE05:8E74 via
ATM2/0.1
407743: Nov 18 11:14:00.906 MEZ: IPv6 DHCP: Sending REPLY to FE80::200:CFF:FE05:
8E74 on ATM2/0.1
407744: Nov 18 11:14:00.906 MEZ: IPv6 DHCP: detailed packet contents
407745: Nov 18 11:14:00.906 MEZ:   src FE80::202:7EFF:FEEB:601B
407746: Nov 18 11:14:00.906 MEZ:   dst FE80::200:CFF:FE05:8E74 (ATM2/0.1)
407747: Nov 18 11:14:00.906 MEZ:   type REPLY(7), xid 702516
407748: Nov 18 11:14:00.906 MEZ:   option IA-NA(3), len 40
407749: Nov 18 11:14:00.906 MEZ:     IAID 0x000A0001, T1 0, T2 0
407750: Nov 18 11:14:00.906 MEZ:     option IAADDR(5), len 24
407751: Nov 18 11:14:00.906 MEZ:       IPv6 address 2A00:19A8:1::1
407752: Nov 18 11:14:00.906 MEZ:       preferred 1125, valid 1800
407753: Nov 18 11:14:00.906 MEZ:   option CLIENTID(1), len 10
407754: Nov 18 11:14:00.906 MEZ:     00030001001EBEBC5DC2
407755: Nov 18 11:14:00.906 MEZ:   option SERVERID(2), len 14
407756: Nov 18 11:14:00.906 MEZ:     00010001147522B3000C29DC0014
407757: Nov 18 11:14:00.906 MEZ:   option DNS-SERVERS(23), len 32
407758: Nov 18 11:14:00.906 MEZ:     2A00:19A8::6
407759: Nov 18 11:14:00.906 MEZ:     2A00:19A8::7
407760: Nov 18 11:14:00.906 MEZ:   option DOMAIN-LIST(24), len 12
407761: Nov 18 11:14:00.906 MEZ:     eleusi.com
407762: Nov 18 11:14:00.926 MEZ: ICMPv6: Received ICMPv6 packet from FE80::200:C
FF:FE05:8E74, type 143
407763: Nov 18 11:14:01.342 MEZ: ICMPv6: Received ICMPv6 packet from FE80::200:C
FF:FE05:8E74, type 143
407764: Nov 18 11:14:01.922 MEZ: ICMPv6: Received ICMPv6 packet from 2A00:19A8:1
::1, type 136
407765: Nov 18 11:14:01.922 MEZ: ICMPv6-ND: Received NA for 2A00:19A8:1::1 on AT
M2/0.1 from 2A00:19A8:1::1
407766: Nov 18 11:14:04.822 MEZ: ICMPv6-ND: DELAY -> PROBE: 2A00:19A8::6
407767: Nov 18 11:14:04.822 MEZ: ICMPv6-ND: Sending NS for 2A00:19A8::6 on Gigab
itEthernet0/1
407768: Nov 18 11:14:04.822 MEZ: ICMPv6-ND: DELAY -> PROBE: FE80::200:CFF:FE05:8
E74
407769: Nov 18 11:14:04.822 MEZ: ICMPv6-ND: Sending NS for FE80::200:CFF:FE05:8E
74 on ATM2/0.1
407770: Nov 18 11:14:04.822 MEZ: ICMPv6: Received ICMPv6 packet from 2A00:19A8::
6, type 136
407771: Nov 18 11:14:04.822 MEZ: ICMPv6-ND: Received NA for 2A00:19A8::6 on Giga
bitEthernet0/1 from 2A00:19A8::6
407772: Nov 18 11:14:04.822 MEZ: ICMPv6-ND: PROBE -> REACH: 2A00:19A8::6
407773: Nov 18 11:14:04.822 MEZ: ICMPv6: Received ICMPv6 packet from FE80::20C:2
9FF:FEDC:14, type 135
407774: Nov 18 11:14:04.822 MEZ: ICMPv6-ND: Received NS for 2A00:19A8::1 on Giga
bitEthernet0/1 from FE80::20C:29FF:FEDC:14
407775: Nov 18 11:14:04.822 MEZ: ICMPv6-ND: Sending NA for 2A00:19A8::1 on Gigab
itEthernet0/1
407776: Nov 18 11:14:04.822 MEZ: ICMPv6-ND: STALE -> DELAY: FE80::20C:29FF:FEDC:
14
407777: Nov 18 11:14:04.834 MEZ: ICMPv6: Received ICMPv6 packet from FE80::200:C
FF:FE05:8E74, type 136
407778: Nov 18 11:14:04.834 MEZ: ICMPv6-ND: Received NA for FE80::200:CFF:FE05:8
E74 on ATM2/0.1 from FE80::200:CFF:FE05:8E74
407779: Nov 18 11:14:04.834 MEZ: ICMPv6-ND: PROBE -> REACH: FE80::200:CFF:FE05:8
E74
407780: Nov 18 11:14:09.822 MEZ: ICMPv6-ND: DELAY -> PROBE: FE80::20C:29FF:FEDC:
407779: Nov 18 11:14:04.834 MEZ: ICMPv6-ND: PROBE -> REACH: FE80::200:CFF:FE05:8
E74
407780: Nov 18 11:14:09.822 MEZ: ICMPv6-ND: DELAY -> PROBE: FE80::20C:29FF:FEDC:
14
407781: Nov 18 11:14:09.822 MEZ: ICMPv6-ND: Sending NS for FE80::20C:29FF:FEDC:1
4 on GigabitEthernet0/1
407782: Nov 18 11:14:09.822 MEZ: ICMPv6: Received ICMPv6 packet from FE80::20C:2
9FF:FEDC:14, type 135
407783: Nov 18 11:14:09.822 MEZ: ICMPv6-ND: Received NS for FE80::202:7EFF:FEEB:
601B on GigabitEthernet0/1 from FE80::20C:29FF:FEDC:14
407784: Nov 18 11:14:09.822 MEZ: ICMPv6-ND: Sending NA for FE80::202:7EFF:FEEB:6
01B on GigabitEthernet0/1
407785: Nov 18 11:14:09.822 MEZ: ICMPv6: Received ICMPv6 packet from FE80::20C:2
9FF:FEDC:14, type 136
407786: Nov 18 11:14:09.822 MEZ: ICMPv6-ND: Received NA for FE80::20C:29FF:FEDC:
14 on GigabitEthernet0/1 from FE80::20C:29FF:FEDC:14
407787: Nov 18 11:14:09.822 MEZ: ICMPv6-ND: PROBE -> REACH: FE80::20C:29FF:FEDC:
14
407788: Nov 18 11:14:09.894 MEZ: ICMPv6: Received ICMPv6 packet from FE80::200:C
FF:FE05:8E74, type 135
407789: Nov 18 11:14:09.894 MEZ: ICMPv6-ND: Received NS for FE80::202:7EFF:FEEB:
601B on ATM2/0.1 from FE80::200:CFF:FE05:8E74
407790: Nov 18 11:14:09.894 MEZ: ICMPv6-ND: Sending NA for FE80::202:7EFF:FEEB:6
01B on ATM2/0.1

sloos · ‎11-19-2010

Hi Paolo,

Lets continue this work via the TAC case you have opened on this.

As a reference for the thread, I proposed to use ipv6 RA on the ATM interface of the 7200 by configuring:

no ipv6 nd suppress-ra

Steven

paolo-prandini · ‎11-19-2010

I have tried but the client still not receive the subnet.

I have insert the command no ipv6 nd suppress-ra in the main ATM interface.

If I insert this line in the sub-interface it doesn't appear in the configuration.

Bye

sloos · ‎11-26-2010

To followup on this thread (and hopefully close it by providing the final solution :-))

Topology:
-----------
RFC 1483 bridging implemenation over DSL with IPV6 addressing.
-CPE (887) is doing IRB (integrated routing and bridging). Its the DHCPv6 client.
-DSL Aggregation (7200) is doing RBE and is acting as DHCPv6 relay.

PC1---|    /---\       /-----\        /----\   /-----------\
      |-----CPE---dsl---DSLAM---atm--- 7200 ---DHCPv6 server
PC2---|    \---/       \-----/        \----/   \-----------/

How DHCPv6 works:
-----------------
CPE will request a prefix via DHCPv6 PD (DHCPv6 option 25: IA-PD )
DHCP server will provid the prefix.
DCHP relay (7200) will install a route for the ipv6 prefix.
CPE will install an IPV6 default route via IPV6 nd (RA advertisements)

Configuration:
-------------

1) On CPE running 15.1(2)T2:
===============================
bridge 1 protocol ieee
bridge 1 route ip
!
bridge irb
!
interface ATM0
bandwidth 1024
no ip address
no atm ilmi-keepalive
bridge-group 1
pvc 0/99
oam-pvc manage
encapsulation aal5snap
!
interface BVI1
ipv6 address PD_prefix ::5:0:0:1/64
ipv6 enable
ipv6 dhcp client pd PD_prefix

3) On DHCP relay agent running 12.2(33)SRE2 (required for static route insertion):
PS: Static route will only be inserted for Prefix delegated subnet.
=================================================================================
ipv6 unicast-routing
ipv6 cef
!
interface Loopback99
no ip address
ipv6 address 2A00:19A8:1::11/64
ipv6 enable
!
interface FastEthernet2/1
ip address 10.48.88.115 255.255.255.0
duplex half
ipv6 address 2A00:19A8::1/64
ipv6 enable
!
interface ATM1/0.1 point-to-point
atm route-bridged ipv6
ipv6 unnumbered Loopback99
ipv6 enable
ipv6 dhcp relay destination 2A00:19A8::6 FastEthernet2/1
pvc 0/100
oam-pvc manage
encapsulation aal5snap

4) On DHCP server:
==================
interface FastEthernet0/0
ipv6 address 2A00:19A8::6/64
ipv6 enable
ipv6 dhcp server dhcp-pool
!
ipv6 dhcp pool dhcp-pool
prefix-delegation pool client-prefix-pool1 <-- for PD
address prefix 2A00:19A8:1::/64 <-- for /128 add assignment.
dns-server 2001:DB8:3000:3000::42
domain-name example.com
!
ipv6 local pool client-prefix-pool1 2A00:19A8:2::/64 64

This results in (on client running 15.1(2)T2):
=============================================
founy#sh ipv6 int bvi1
BVI1 is up, line protocol is up
   IPv6 is enabled, link-local address is FE80::200:CFF:FE8A:B41A
   No Virtual link-local address(es):
   Global unicast address(es):
     2A00:19A8:2::5:0:0:1, subnet is 2A00:19A8:2::/64
   ...
   Default router is FE80::2D0:63FF:FE86:E800 on BVI1

founy#sh ipv6 dhcp int bvi1
BVI1 is in client mode
Prefix State is OPEN
Renew will be sent in 3d11h
Address State is OPEN
Renew for address will be sent in 11:59:48
List of known servers:
    Reachable via address: FE80::2D0:63FF:FE86:E800
    DUID: 0003000100062AA1BC08
    Preference: 0
    Configuration parameters:
      IA PD: IA ID 0x000E0001, T1 302400, T2 483840
        Prefix: 2A00:19A8:2::/64
                preferred lifetime 604800, valid lifetime 2592000
                expires at Nov 29 2010 10:04 AM (2591898 seconds)
      DNS server: 2001:DB8:3000:3000::42
      Domain name: example.com
      Information refresh time: 0
Prefix name: PD_prefix
Prefix Rapid-Commit: disabled
Address Rapid-Commit: disabled

On DHCP relay agent:
====================
Pagent#sh ipv6 route
S 2A00:19A8:2::/64 [1/0]
via FE80::200:CFF:FE05:B402, ATM1/0.1

paolo-prandini · ‎11-30-2010

Two wrong things in your configuration:

1) The unnumbered atm-subinterface in ipv6 doesn't work. I have tried, but the ping fails every time.

2) I don't want to assign the Ipv6 address to the client bvi interface with prefix delgation (for the reason i have stated in the previuos messages)

At this point i have this configuration:
- 7204 with IOS 12.2(33)SRE2
- numbered atm subinterface
- non-cisco client device (AVM fritz!box 7270)

Everything works good!!

The client bridge interface receives the correct address and it is correctly routed by
7204 atm2/0.1 subinterface.
The interface-id is correctly added by the relay in the DHCP request forwarded to the DHCP SERVER.
The DHCP server matches the inteface-id(option 18) and send the corresponding static ipv6 address.

Also the route to the host network (/48) is correctly added.

In the end I have to state that the Cisco client devices cannot work in IPv6 with RBE!

I'm a bit disappoited about that..
It seems that Cisco isn't ready to work with RBE in IPv6!

I'll write a short brief of the situations:The CPE has an ATM interface to which we want to assign an address, and
it belongs to the subnet you see above. Then the CPE has one or more local
ethernet interfaces, that need each a subnet, so we assign a /48 to each
customer ; that is done through a prefix assignment in DHCP.
You then have to remember that an ATM interface is a p-to-p one.
What happens with IPv4 and what we want to happen with IPv6 as well is:
a) there must NOT be a global route 2A00:19A8:1::/64 to all ATM/1.0.x interfaces
but only a 2a00:19a8:1::11 to the 7200 ; otherwise you can connect with
any address to any ATM interface.
b) the 7200 ATM/1.0.x interfaces have a p-to-p address of 2a00:19a8:1::11
(all of them! the same!)
c) when a CPE sends a DHCP request to the 7200 via a given ATM/1.0.y
interfaces, the 7200 relays it to the DHCP server. The DHCP server gets
the number of the interface ( the ATM/1.0.y ) and checks which address and
prefix it has to send to the CPE. It must act accordingly to the interface NOT
to the MAC otherwise we have to change DHCP tables each time we change
router ( this is the reason for option 18).
d) the DHCP server sends back the address (e.g. 2a00:19a8:1::1 ) to the
CPE, and the prefix (e.g. 2a00:19a8:100::/48) as well, to the 7200 relay
e) the 7200 relay when relaying the answer to the CPE reads which address
and prefix were assigned and adds the routes, so we must have 2 new routes
for 2a00:19a8:1::1 to ATM/0.1.1 and 2a00:19a8:100::/48 to ATM/0.1.1
f) the newly installed routes are also inserted in OSPF6 in the 7200 that sends
them to the other OSPF6 peers that are now aware of the new connection and
are able to correctly route the prefix and address to and from the 7200
g) let's suppose that another CPE connects to the 7200 ATM/0.1.2 port ;
all the above procedure is repeated, now we have 2 new routes e.g. to
2a00:19a8:1::2 and 2a00:19a8:101::/48 and so on

All this procedure, that is the normal RBE one apart from the /48 prefix that
is new, is described on Cisco documents BUT it is NOT working.
It is not working in point a) because a global route is set.
But this problem can be bypassed if we assign to each client a /64 subnet for each bridge interfaces.
For the point c) you have found that the values in options 18 are correctly assigned only with the 12.2(33)SRE2 IOS release.
It is not working in point e) because no new routes are added and therefore in f)
no routes are added to OSPF6.
I would like to point out that RBE in IPv4 works correctly in the above described way.

Thanks