Hi Nagendra,

i have taken the output at two different moments ,

1st moment :

MOF-PETRO#sh ip route vrf PAO 10.54.18.65
% Subnet not in table
MOF-PETRO#sh ip cef vrf PAO 10.54.18.65
0.0.0.0/0, version 4382, epoch 0, attached, default route handler
0 packets, 0 bytes
  via 0.0.0.0, 0 dependencies
    valid no route adjacency

2 nd moment :

MOF-PETRO#sh ip cef vrf PAO 10.54.18.65
10.54.18.64/26, version 4957, epoch 0, cached adjacency 10.23.255.73
0 packets, 0 bytes
  tag information set
    local tag: VPN-route-head
    fast tag rewrite with
        Recursive rewrite via 0.0.0.0/0, tags imposed {3591}
  via 10.255.246.74, 0 dependencies, recursive
    next hop 10.23.255.73, GigabitEthernet0/0
    valid cached adjacency
    tag rewrite with
        Recursive rewrite via 0.0.0.0/0, tags imposed {3591}
MOF-PETRO#sh ip route vrf PAO 10.54.18.65
Routing entry for 10.54.18.64/26
  Known via "bgp 4758", distance 200, metric 0, type internal
  Last update from 10.255.246.74 00:00:04 ago
  Routing Descriptor Blocks:
  * 10.255.246.74 (Default-IP-Routing-Table), from 10.255.254.1, 00:00:04 ago
      Route metric is 0, traffic share count is 1
      AS Hops 0

MOF-PETRO#sh ip bgp 10.54.12.0
BGP routing table entry for 10.54.0.0/17, version 265281
Paths: (1 available, no best path)
Flag: 0x820
  Not advertised to any peer
  Local
    10.255.240.245 (inaccessible) from 10.255.254.1 (10.255.254.1)
      Origin IGP, metric 0, localpref 100, valid, internal
      Originator: 10.255.240.245, Cluster list: 0.0.18.150

MOF-PETRO#sh ip bgp 10.54.18.65
BGP routing table entry for 10.54.0.0/17, version 275080
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Flag: 0x820
  Not advertised to any peer
  Local
    10.255.240.245 from 10.255.254.1 (10.255.254.1)
      Origin IGP, metric 0, localpref 100, valid, internal, best
      Originator: 10.255.240.245, Cluster list: 0.0.18.150

The route i am trying to reach is another CE's ip address.

Hi

Can you check the i-BGP neighbor & post the output for same & also check the i-BGP next hop Ip address  in routing table or check the connectvity between you i-BGP neighbors. May be you have an IGP issue so your update of VPNv4 are getting dropped.

Regards

Chetan Kumar

http://chetanress.blogspot.com

there is  one problem in this config , loopback ip address 10.255.246.209 is not announced anywhere .

can anyone suggest me how to announce this ip address. whether it will announced through BGP or through statis ip address ??

Hi,

        It seems you are not running IGP, only option is to have static route. And have check on rechability from PE's to the next-hop ips for the route you are receiving via M-BGP. And  if  problem is not solved,  upload the n/w diag with segments you are using that wud give clear picture on ur issue.

Regards,

V Dinesh Kumar

Hi

.

When you use update source with BGP then it use that IP as a source to form an neighbor ship & if that Source IP is not reachable then it won't form neighbor ship. In case of directly connected network it won't require any route becasue they can reach each other.

You have to use static route to reach loopback IP of both PE or else you need to run any IGP Protocol to achive the same

I suggest you to have any IGP to run  in production network becasue running static route is very tedious job & to maintain also & if you are in testing phase the i suggest you to go with static routing.

Regards

Chetan Kumar

http://chetanress.blogspot.com

Hi ,

You are correct , after announcing loopback ip address through IGP , my BGP session starts working and it remains stable.

What i didn't able to understand is i have not redistributed ospf in my BGP , neither BGP into ospf , then how come that we need ospf for proper BGP functionality , plz explain ....

also , why did announcing loopback into BGP didn't help ???

Hi

--------- > What i didn't able to understand is i have not redistributed ospf in my BGP , neither BGP into ospf , then how come that we need ospf for proper BGP functionality , plz explain

You was trying to configure BGP neighbour which are in different subnet ( Means using loop Back )

Take an example  :

PE1  --- 1.1.1.1 ( Loopback IP )  ----- 10.1.1.1  -- Physical interface IP  that connect tp PE2

PE2  --- 2.2.2.2 ( Loopback IP )  ----- 10.1.1.2  -- Physical interface IP  that connect to PE1

Here if you try to configure BGP neighbor using loopback IP , Then How both PE router will come that how to reach each other means Loopback IP's not physical IP's .What is the gateway to reach the loopback IP's

( Simply a part of routing  -- to check you can ping the loopback IP's but it won't ping  that's the reason that you need IGP to route loopback IP's .)

In BGP you can form neighbor when the destination or remote neighbor is reachable  & that is possible through IGP.

--------- > why did announcing loopback into BGP didn't help ???

Because if your BGP neighbor is not form then advertising BGP route will not prorogate to remote neighbor.

Regrads

Chetan Kumar

http://chetanress.blogspot.com