|
|
!
ip subnet-zero
!
!
redundancy
!-- This command enables redundancy.
high-availability
!-- This command enables high availability.
single-router-mode
!-- This command enables SRM.
!
interface Vlan10
ip address 192.168.1.3 255.255.255.0
!-- Interface Vlan10 connected to interface Vlan10 on CAT1 via the trunk.
!
interface Vlan20
ip address 192.168.2.1 255.255.255.0
!-- Interface Vlan20 connected to AS20.
!
router bgp 4
no synchronization
bgp log-neighbor-changes
network 192.168.0.0 mask 255.255.0.0
neighbor 192.168.2.2 remote-as 20
!-- This command establishes eBGP peering with AS20.
neighbor 192.168.2.3 remote-as 4
!-- This command establishes iBGP peering with interface Vlan20 on CAT1.
neighbor 192.168.2.3 next-hop-self
!-- This command assigns a next-hop value to 192.168.2.1 !-- for updates sent to 192.168.2.3 (the iBGP peer).
!
ip classless
ip route 192.168.0.0 255.255.0.0 Null0
Troubleshoot
Now that you’ve verified the high availability SRM configuration, you need to verify the BGP MSFC on CAT1 and CAT2.
Use the show ip bgp summary command to verify the neighbor establishment.
The output below confirms successful eBGP and iBGP peering with AS10 and the CAT2 MSFC respectively.
MSFC-CAT1#show ip bgp summary
BGP router identifier 192.168.2.3, local AS number 4
BGP table version is 4, main routing table version 4
3 network entries and 4 paths using 435 bytes of memory
4 BGP path attribute entries using 240 bytes of memory
2 BGP AS-PATH entries using 48 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP activity 3/14 prefixes, 4/0 paths, scan interval 15 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
192.168.1.2 4 10 90 92 4 0 0 01:26:02 1
192.168.2.1 4 4 91 91 4 0 0 01:25:38 2
Verify the BGP state on the active MSFC in CAT2.
The output below confirms successful eBGP and iBGP peering with AS20 and CAT1 respectively
MSFC-CAT2#show ip bgp summary
BGP router identifier 192.168.2.1, local AS number 4
BGP table version is 4, main routing table version 4
3 network entries and 4 paths using 435 bytes of memory
4 BGP path attribute entries using 240 bytes of memory
2 BGP AS-PATH entries using 48 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP activity 3/0 prefixes, 4/0 paths, scan interval 15 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
192.168.2.2 4 20 110 112 4 0 0 01:46:43 1
192.168.2.3 4 4 101 101 4 0 0 01:35:09 2
In the event the designated MSFC (Mod 15 on CAT1) experiences a failure, the standby MSFC (Mod 16 on CAT1) takes
over the role of active MSFC. It is important to understand that with the failure of the designated MSFC and fail over
to the nondesignated MSFC,
packet switching will continue to work with the Cisco Express Forwarding (CEF) table programmed by the old designated
MSFC.The newly designated MSFC will eventually re-program the CEF table with its own entries and the old entries will expire.
Failure of designated MSFC is simulated by resetting Mod 15 on CAT1 as shown below.
CAT1> (enable) reset 15
This command will reset module 15.
Unsaved configuration on module 15 will be lost
|
.gif){kind=small}
.gif){kind=small}
.gif){kind=small}
.gif){kind=small}
您现在的位置： 
