I had a bit of a weird problem last night -- when trying to remove BGP from a VRF on a 7600 running 12.2(33)SRC2, I tried:
ar01.tn5(config)#router bgp 65302
ar01.tn5(config-router)#no address-family ipv4 vrf SRC2-TEST
ar01.tn5(config-router)#exit
ar01.tn5(config)#exit
One would expect that this would stop BGP redistributing the VRF routes for the VRF SRC2-TEST. In fact, what happens is that the VRF starts reporting 'debugging-style' messages:
ar01.tn5#sh run vrf SRC2-TEST
Building configuration...
% Topology SRC2-TEST::VPNv4 Unicast::base is currently being deconfigured.
% Topology SRC2-TEST::VPNv4 Unicast::base is currently being deconfigured.
% Topology SRC2-TEST::VPNv4 Unicast::base is currently being deconfigured.
% BGP context has not been initialized properly.
% Topology SRC2-TEST::VPNv4 Unicast::base is currently being deconfigured.
% BGP context not been initialized properly.
% Topology SRC2-TEST::VPNv4 Unicast::base is currently being deconfigured.
% Topology SRC2-TEST::VPNv4 Unicast::base is currently being deconfigured.
Current configuration : 340 bytes
ip vrf SRC2-TEST
description :c=CORE:x=rjs test for ar01.tn5 issues:
rd 5413:1020
export map EXPORT-MAP-SRC2-TEST
route-target export 5413:1020
route-target import 5413:1022
!
!
ip route vrf SRC2-TEST 10.0.0.0 255.255.255.0 Null0
!
router bgp 65302
!
address-family ipv4 vrf SRC2-TEST
redistribute static
exit-address-family
end
And you then can't get rid of the BGP from the VRF. It turns out the fix for this is to remove the VRF itself -- or, rather than removing the address-family itself, remove the contents of the address family. I'm not entirely sure that this is designed behaviour -- and I couldn't seem to find any further results for it. I guess it needs to be put into TAC as another Cisco weird.
|
