Ads 468x60px

Thursday, November 24, 2011

Maipu - Failover Configuration Using Static Route

Hi , I want to share one testing report with all of you. This is majorly focused on Fail over configuration with static routing.. Below are objectives for testings...

Objective - 
  • R1 Client Router both interface should be UP every time.
  • PC should ping 20.1.1.1 Loopback interface continuously.
  •  Auto Failover should happen.
  • One time one port should forward traffic to ISP router.
  • As the primary F0 links fails, The F1 should get active to forward traffic to ISP router.
  • After restoration of F0 links, The F0 should forward the traffic to ISP router.
Topology:





Configurations

(Client)R1-

interface fastethernet0
 ip address 10.20.20.2 255.255.255.0
 media-type fiber
 rate 100
 duplex full
 load-interval 30
 exit


interface fastethernet1
 ip address 10.20.30.2 255.255.255.0
 media-type fiber
 rate 100
 duplex full
 load-interval 30
  exit


interface vlan1
 ip address 10.1.1.1 255.255.255.0
 exit



ip route 0.0.0.0 0.0.0.0 fastethernet0
ip route 0.0.0.0 0.0.0.0 fastethernet1 10


(ISP)R2 –

interface loopback0
 ip address 20.1.1.1 255.255.255.0
 exit


interface fastethernet0
 ip address 10.20.20.1 255.255.255.0
 media-type fiber
 keepalive gateway 10.20.20.2 4
 rate 100
 duplex full
 load-interval 30
 exit


interface fastethernet1
 ip address 10.20.30.1 255.255.255.0
 media-type fiber
 keepalive gateway 10.20.30.2 4
 rate 100
 duplex full
 load-interval 30
 exit


ip route 10.1.1.0 255.255.255.0 10.20.20.2
ip route 10.1.1.0 255.255.255.0 10.20.30.2 10

Testing Scenarios – 

10.1.1.2  ping to Gateway to observe delay….


10.1.1.2  (PC) ping to 20.1.1.1 (Loopback interface in ISP Router)


Currently in this screen shot, both interface as UP. Primary link F0 is forwarding traffic to ISP router.


After Primary link is down –
You can see F0 is down and F1 is up, F1 is forwarding traffic to ISP router.


Below is ping snap shot from 10.1.1.2 (PC)  to 20.1.1.1 ( ISP loopback interface)


10.1.1.2 (PC) pinging to Gateway IP


After restoration of link
As the link is restored, F0 interface is active interface to forward traffic to ISP router.


The F1 forwarding is shifted to F0 interface.  PC (10.1.1.2) pinging to ISP router loopback (20.1.1.1)


PC pinging to Gateway 10.1.1.1




Above testing successfully demonstrates above objectives are successfully. 

Hope this information will help you. 

Thanks for reading.. 

For feedback. Plz comment with Name and Mail ID.. 








Thursday, November 3, 2011

Maipu 3840 MTU Details

Hi, Today one of my client raised a query about MP 3840 MTU details about all 4 Gig interface. 
As MP 3840 is aggregation router, some time we need to modify the MTU of interface as per requirement. 
So I would like share same details here, Which can be helpful for all. 
MP 3840 Gig 0, you can configure max MTU of 1800 under Gig 0  interface for any peer device.
But Gig 1/2/3 , if speed is configured as 100 M or negotiating with 100M peer device. Then it will support max MTU 1500. If negotiating with 1000M or configured as 1000M , then it can support max 1800 MTU.


Hope this information will help in some critical scenario. 


Thanks for reading...
Related Posts Plugin for WordPress, Blogger...