AW: AW: [j-nsp] DHCP Relay on an VRF interface

[Elmar Kirchner]

Hi Carsten,

see inline

At 02:01 PM 6/25/2004, Strahler, Carsten wrote:
>Hi,
>
>then you should add this to your manual (Release 6.3) :
>
>... 
>! You cannot configure the vrf-table-label statement on any of the following
>PE-router-to-P-router PICs:
>! 1-port Gigabit Ethernet QPP PIC <----these two are QPP
>! 2-port Gigabit Ethernet QPP PIC <----vrf-table-label does not work here
>! 4-port Gigabit Ethernet PIC <------ I would expect this to work, will check that
>! 10-port E1 PIC
>! 12-port Fast Ethernet PIC
>! 48-port Fast Ethernet PIC
>! All ATM PICs, except the ATM2 PIC
>! All Ethernet PICs configured with the VLAN encapsulation <--------- this is the hint for the 5.7 change
>...
>
>Thanks for your help
>
>Carsten
>
>
>
>
>-----Ursprungliche Nachricht-----
>Von: Josef Buchsteiner [mailto:josefb at juniper.net]
>Gesendet: Freitag, 25. Juni 2004 13:18
>An: Strahler, Carsten
>Cc: 'Elmar Kirchner'; juniper-nsp at puck.nether.net
>Betreff: Re: AW: [j-nsp] DHCP Relay on an VRF interface
>
>
>since 5.7 we do support vrf-tabel-label on plain Ethernet core links If you
>have  vlans  then  there  is only the option of having a tunnel pic to
>perform ip-lookup
>
>Friday, June 25, 2004, 12:20:08 PM, you wrote:
>
>SC> Hi,
>
>SC> thanks a lot for this hint. But in some cases we have GigE as
>SC> core-interface.
>SC> Regarding the manual, this won't work.
>SC> Any other ideas ??
>
>SC> Carsten
>
>SC> -----Ursprungliche Nachricht-----
>SC> Von: Elmar Kirchner [mailto:elmar at juniper.net]
>SC> Gesendet: Freitag, 25. Juni 2004 12:07
>SC> An: Strahler, Carsten; juniper-nsp at puck.nether.net
>SC> Betreff: Re: [j-nsp] DHCP Relay on an VRF interface
>
>
>SC> Hi Carsten,
>
>SC> try vrf-table-label. For more details have a look at the VPN manual and
>SC> search for this keyword.
>
>SC> /elmar
>
>
>
>
>SC> At 10:51 AM 6/25/2004, Strahler, Carsten wrote:
>>>Hi,
>>>
>>>i try to configure a DHCP Relay over a L3 MPLS-VPN. 
>>>The client on the remote site sent dhcp requests and the Juniper
>>>forwards them to the central DHCP server. In the log of the server I see
>>>the request and the assignment of the ip addresses. 
>>>But the client doesn't get the response. 
>>>My assumption is, that the DHCP server sent the response to the
>>>address of the VRF interface of the remote Juniper. But the Juniper
>>>isn't able to do the second lookup. I don't want to install a tunnel PIC
>>>and there is no server with a static IP address on the remote site.
>>>
>>>Any ideas ???  
>>>  
>>>
>>>------------------------------------------------------------
>>>Carsten Strahler
>>>
>>>IP Planning 
>>>
>>>Lambdanet Communications Deutschland AG (AS 13237)
>>>Guenther-Wagner-Allee 13
>>>D-30177 Hannover (Germany)
>>>
>>>Phone   +49 (0)511 / 84 88 12 57
>>>Mobile  +49 (0)173 / 629 1257
>>>Fax     +49 (0)511 / 84 88 12 59
>>>mailto:carsten.strahler at lambdanet.net
>>>
>>>web: www.lambdanet.net
>>>-----------------------------------------------------------
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>>juniper-nsp mailing list juniper-nsp at puck.nether.net
>>>http://puck.nether.net/mailman/listinfo/juniper-nsp 
>SC> _______________________________________________
>SC> juniper-nsp mailing list juniper-nsp at puck.nether.net
>SC> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
>