[j-nsp] Hidden L3VPN Routes

Chris Staudt christoph.staudt at teresto.net
Fri Jun 17 02:08:15 EDT 2005


Hi,
the remote end is a cisco 73 box with the following config:
 no synchronization
 bgp router-id 217.24.235.15
 bgp cluster-id 9063
 bgp log-neighbor-changes
 bgp deterministic-med
 bgp graceful-restart restart-time 120
 bgp graceful-restart stalepath-time 360
 bgp graceful-restart
 neighbor PG_RRC peer-group
 neighbor PG_RRC remote-as 9063
 neighbor PG_RRC password xxxx
 neighbor PG_RRC update-source Loopback0
 neighbor PG_RRC route-reflector-client
 neighbor PG_RRC send-community both
 neighbor 217.24.235.28 peer-group PG_RRC
 no auto-summary
 !
 address-family vpnv4
 neighbor PG_RRC activate
 neighbor PG_RRC route-reflector-client
 neighbor PG_RRC next-hop-self
 neighbor PG_RRC send-community both
 neighbor 217.24.235.28 peer-group PG_RRC
 exit-address-family


ts-r4.6861#sh ip route 217.24.235.28
Routing entry for 217.24.235.28/32
  Known via "isis", distance 115, metric 1000, type level-2
  Redistributing via isis
  Last update from 217.24.235.167 on GigabitEthernet0/1, 12:03:28 ago
  Routing Descriptor Blocks:
  * 217.24.235.167, from 217.24.235.28, via GigabitEthernet0/1
      Route metric is 1000, traffic share count is 1

ts-r4.6861#


thanks,
chris

Erdem Sener <erdems at gmail.com> on Donnerstag, 16. Juni 2005 at 22:55 +0100
wrote:
>Hi,
>
>
> What's the remote end config and show route extensive ?
>
>
> Cheers,
> Erdem
>
>
>On 6/16/05, Chris Staudt <christoph.staudt at teresto.net> wrote:
>> gtate at juniper.net on Donnerstag, 16. Juni 2005 at 20:21 +0100 wrote:
>> >You LDP destination and bgp peering address need to be the same.
>> >Normally this would be the loopback.  It would be a great help if you
>> >could send your protocols configurations and a show route extensive for
>> >ht peering address of the iBGP session
>> >
>> >
>> >Gary
>> 
>> No prob:
>> 
>> 
>> routing-options {
>>    static {
>>        route 0.0.0.0/0 next-hop 217.24.235.15;
>>    }
>>    router-id 217.24.235.28;
>>    autonomous-system 9063;
>> }
>> protocols {
>>    mpls {
>>        interface fe-3/0/0.0;
>>        interface lo0.1;
>>    }
>>    bgp {
>>        traceoptions {
>>            file bgp size 500000;
>>            flag route detail;
>>        }
>>        group PG_TORR {
>>            type internal;
>>            local-address 217.24.235.28;
>>            family inet {
>>                unicast;
>>            }
>>            family inet-vpn {
>>                unicast;
>>            }
>>            peer-as 9063;
>>            neighbor 217.24.235.15 {
>>                authentication-key xxx; ## SECRET-DATA
>>            }
>>        }
>>    }
>>    isis {
>>        traceoptions {
>>            file isis size 500000;
>>            flag state detail;
>>            flag all detail;
>>        }
>>        lsp-lifetime 65535;
>>        level 2 {
>>            authentication-key xxx; ## SECRET-DATA
>>            authentication-type xxx; ## SECRET-DATA
>>            no-hello-authentication;
>>            wide-metrics-only;
>>        }
>>        interface fe-3/0/0.0 {
>>            level 2 metric 1000;
>>        }
>>        interface all {
>>            level 1 disable;
>>        }
>>    }
>>    ldp {
>>        interface all;
>>    }
>> }
>> 
>> 
>> root at juni> show route extensive 217.24.235.15
>> 
>> inet.0: 163884 destinations, 163884 routes (163870 active, 7 holddown, 0
>> hidden)
>> 217.24.235.15/32 (1 entry, 1 announced)
>> TSI:
>> KRT in-kernel 217.24.235.15/32 -> {217.24.235.165}
>>        *IS-IS  Preference: 18
>>                Level: 2
>>                Next-hop reference count: 3
>>                Next hop: 217.24.235.165 via fe-3/0/0.0, selected
>>                State: <Active Int>
>>                Local AS:  9063
>>                Age: 9:30       Metric: 1000
>>                Task: IS-IS
>>                Announcement bits (3): 0-KRT 1-LDP 5-Resolve inet.0
>>                AS path: I
>> 
>> root at juni>
>> 
>> 
>> 
>> thanks,
>> chris
>> 
>> 
>> i.V.
>> 
>> --
>> Christoph Staudt, Leiter Netze und Systeme / CTO
>> Cisco Certified Network Associate
>> 
>> teresto media Aktiengesellschaft - RWE Group
>> Trierer Strasse 223-225 - 66663 Merzig / Germany
>> Tel. +49-(0)6861-9312-234 - Fax +49-(0)6861-9312-199
>> mailto: christoph.staudt at teresto.net - http://www.teresto.net
>> 
>> 
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>




i.V.
 
-- 
Christoph Staudt, Leiter Netze und Systeme / CTO
Cisco Certified Network Associate

teresto media Aktiengesellschaft - RWE Group 
Trierer Strasse 223-225 - 66663 Merzig / Germany
Tel. +49-(0)6861-9312-234 - Fax +49-(0)6861-9312-199
mailto: christoph.staudt at teresto.net - http://www.teresto.net




More information about the juniper-nsp mailing list