Thanks Ashvin!!. I really appriciate your help.
Policy wasn't configured correctly on T1 and T2, That's why i wasn't able to traceroute to T1 and T2 from R5. Corrected the policy and i can see route for 120.120/16 and 130.130/16 from R5.
root@R5# run show route 120.120/16
inet.0: 30 destinations, 36 routes (30 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
120.120.0.0/16 *[BGP/170] 00:12:59, localpref 100
AS path: (65000) 65222 I, validation-state: unverified
> to 10.0.2.2 via ge-0/0/1.0
[BGP/170] 00:12:59, localpref 100, from 10.0.2.10
AS path: (65000) 65222 I, validation-state: unverified
> to 10.0.2.2 via ge-0/0/1.0
[edit]
root@R5# run show route 130.130/16
inet.0: 30 destinations, 36 routes (30 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
130.130.0.0/16 *[BGP/170] 17:45:09, localpref 100
AS path: (65000) 65222 I, validation-state: unverified
> to 10.0.2.2 via ge-0/0/1.0
[BGP/170] 17:45:09, localpref 100, from 10.0.2.10
AS path: (65000) 65222 I, validation-state: unverified
> to 10.0.2.2 via ge-0/0/1.0
root@R5# run traceroute 120.120.0.1
traceroute to 120.120.0.1 (120.120.0.1), 30 hops max, 40 byte packets
1 10.0.2.2 (10.0.2.2) 16.230 ms 19.230 ms 20.068 ms
2 172.16.0.14 (172.16.0.14) 30.458 ms !N 24.768 ms !N 30.504 ms !N
[edit]
root@R5# run traceroute 130.130.0.1
traceroute to 130.130.0.1 (130.130.0.1), 30 hops max, 40 byte packets
1 10.0.2.2 (10.0.2.2) 16.034 ms 20.610 ms 18.814 ms
2 172.16.0.18 (172.16.0.18) 30.151 ms !N 29.722 ms !N 20.103 ms !N
Thanks,
Jay