I suppose you guys are correct.... But my doubt came because in Juniper SRX firewall you can assign diffrent Ip address...... chekout this link :- http://www.juniper.net/techpubs/software/junos-security/junos-security10.0/junos-security-swconfig-security/cc_deployment_scenarios.html  and go in "Asymmetric Routing Chassis Cluster Scenario" section. Isn't all the kinds of firewall behaves in a same way as far as failover is concerned ?? ... View more

hi Ramraj, Thks for ur reply,,, If this is the case ,how can I terminate two separate links from the ISP on the ASA ?? ... View more

Hi jamil, Can u elborate  more what information u need from this out... I can tell below information from your output The prefix 8.8.8.0/24 belongs to AS-15169 which is google .. 7018 is AT&T AS no. , next hop is 12.123.134.124 which is AT & T ip. What else u need? ... View more

Great Nandan, You really resolved this mystery..... So its clear now that my toplogy and test results shared by John , listner command is not required since ther are few routers....., So the assumption we can draw here is that , it realy depneds on the toplogy , no. of routers , selection of RP & MP to decided wheather we need listner command or not ...But it is best practice to enable it on all the routers to avoid any issue later. i have on more doubt ,  r u shore that u have configured loopback of RA & MA in spare mode.?? What I think is that, the source interface of RA & MA should be configured in dense both ,, because 224.0.1.39 &  224.0.1.40 works in dense ,mode only  . So RA & MA communicate in dense and all other is spare when listener command is use. Correct me if i am wrong. ... View more

Hi nandan, good points and tests You may be correct with  the assumptions u r drawing with ur test results .. But have u tried keeping MA & RP on different router and then check .... because in my solution they are diffrent... ... View more

Nice to see john that ...our assumption is correct for 12.3 versions...... But my mind can't accept how its working with.. 12.4 .... Anyways thks for ur observation nd testing.... may be we should wait for someone else and share thier observation... ... View more

Hey john,, Good to see that my observation is correct. But I hav't seen any cisco doc which says that autolistener is enabled by default or we do not need it any more.. Even if u have seen workbooks for CCIE lab preparation ,,, they also insists on configure "ip autorp listner"" to  make auto RP work with spare mode... And i m using "-ADVIPSERVICESK9-M - 12.4 T vesion"" . Its not 15 which is newer one. Most of the people use 12.4 T only... and in CCIE lab too cisco is using 12.4T ... then how it is possible.....strange?/:( ... View more

Here is the output from RP nd receiver :- RP :- #sh ip mroute IP Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,        L - Local, P - Pruned, R - RP-bit set, F - Register flag,        T - SPT-bit set, J - Join SPT, M - MSDP created entry,        X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,        U - URD, I - Received Source Specific Host Report,        Z - Multicast Tunnel, z - MDT-data group sender,        Y - Joined MDT-data group, y - Sending to MDT-data group Outgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode (*, 224.10.10.10), 00:01:53/00:02:35, RP 150.1.5.5, flags: S   Incoming interface: Null, RPF nbr 0.0.0.0   Outgoing interface list:     FastEthernet0/0, Forward/Sparse, 00:01:53/00:02:35 (155.1.0.1, 224.10.10.10), 00:01:51/00:01:10, flags: T   Incoming interface: Serial4/0.100, RPF nbr 155.1.0.1   Outgoing interface list:     FastEthernet0/0, Forward/Sparse, 00:01:51/00:02:35 (*, 224.0.1.39), 00:21:24/stopped, RP 0.0.0.0, flags: DCL   Incoming interface: Null, RPF nbr 0.0.0.0   Outgoing interface list:     Loopback0, Forward/Sparse, 00:21:24/00:02:41     Serial4/1, Forward/Sparse, 00:21:24/00:02:55     Serial4/0.100, 224.0.1.39, Forward/Sparse, 00:21:24/00:02:46 (150.1.5.5, 224.0.1.39), 00:21:12/00:02:50, flags: LT   Incoming interface: Loopback0, RPF nbr 0.0.0.0   Outgoing interface list:     Serial4/0.100, 224.0.1.39, Forward/Sparse, 00:21:12/00:02:46     Serial4/1, Forward/Sparse, 00:21:12/00:02:55 (*, 224.0.1.40), 00:23:54/stopped, RP 0.0.0.0, flags: DCL   Incoming interface: Null, RPF nbr 0.0.0.0   Outgoing interface list:     Loopback0, Forward/Sparse, 00:21:25/00:02:42     Serial4/0.100, 224.0.1.40, Forward/Sparse, 00:23:54/00:02:48 (150.1.5.5, 224.0.1.40), 00:21:12/00:02:39, flags: LT   Incoming interface: Loopback0, RPF nbr 0.0.0.0   Outgoing interface list:     Serial4/0.100, 224.0.1.40, Forward/Sparse, 00:21:12/00:02:48 Receiver :- #sh ip mroute IP Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,        L - Local, P - Pruned, R - RP-bit set, F - Register flag,        T - SPT-bit set, J - Join SPT, M - MSDP created entry,        X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,        U - URD, I - Received Source Specific Host Report,        Z - Multicast Tunnel, z - MDT-data group sender,        Y - Joined MDT-data group, y - Sending to MDT-data group Outgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode (*, 224.10.10.10), 00:04:21/stopped, RP 150.1.5.5, flags: SJPL   Incoming interface: Vlan58, RPF nbr 155.1.58.5   Outgoing interface list: Null (155.1.0.1, 224.10.10.10), 00:00:07/00:02:56, flags: PLT   Incoming interface: Vlan58, RPF nbr 155.1.58.5   Outgoing interface list: Null (*, 224.0.1.39), 00:16:38/stopped, RP 0.0.0.0, flags: DC   Incoming interface: Null, RPF nbr 0.0.0.0   Outgoing interface list:     Vlan58, Forward/Sparse, 00:16:20/00:02:12 (150.1.5.5, 224.0.1.39), 00:16:40/00:02:25, flags: PTX   Incoming interface: Vlan58, RPF nbr 155.1.58.5   Outgoing interface list: Null (*, 224.0.1.40), 00:24:17/stopped, RP 0.0.0.0, flags: DCL   Incoming interface: Null, RPF nbr 0.0.0.0   Outgoing interface list:     Vlan58, Forward/Sparse, 00:24:18/00:02:12 (150.1.5.5, 224.0.1.40), 00:16:45/00:02:14, flags: PLTX   Incoming interface: Vlan58, RPF nbr 155.1.58.5   Outgoing interface list: Null ... View more

Hi Riazwan,, I have the exact same requirment .., I will create DMVPN with nhrp and check if the solution works. Thks for the help!! ... View more

i got a bit of it...as i havtn't done polict static nat before.... let me explain u the situation again... to make sure we are on the same page I am running a site to site ipsec vpn tunnel b/w HQ and 1 branch site say for e.g  Site 1 I am running also running a site to site ipsec vpn tunnel b/w HQ and 1 branch site(server site) say for e.g Site 2 nw the requirment is traffic coming from Site 1 to servers should terminate at HQ and afterthat HQ should redirect that traffic  to Site 2. Kindly note :- I am using single physical interface at HQ router for both the Vpns. ... View more

Hi rizwan, It is redirecting ipsec-encrypted traffic ... View more

My sugesstion is to use BGP in case of two ISP as BGP is more reliable protocol in case of two ISP connection :- You need to do the following to achieve this :- 1)In proposal 2 , have a back to back connection also in branch& HQ routers. This is required for IBGP session. 2) At both ends run BGP with each ISP. 3) Advertise half of LAN subnets on ISP1 & other half on ISP 2 and advertise summary address to both the ISP. 4)Keep local prefrence of one ISP to be higher. This will help to achieve redundany as well as load sharing.If any of the ISP link fails or whole ISP gets down., still you can use other ISP link for whole traffic. Let me know if u need any othe rinformation to achieve this. ... View more