BGP UPGRADE CLI

If you enter the BGP configuration and issue the command bgp upgrade-cli you will find out that the BGP configuration has been fully converted to the address family style of configuration. Outside any address-family stanzas, only the basic neighbor settings are configured like their addresses, AS numbers, update sources. However, all remaining per-address-family commands will be automatically moved into address-family stanzas. The behavior or operations of BGP do not change with this new style of configuration, only the configuration format is changed.



prima: configurazione 1
router bgp 300
 no synchronization
 bgp default local-preference 150
 bgp log-neighbor-changes
 network 10.1.1.26 mask 255.255.255.255
 neighbor 1.1.80.1 remote-as 200
 neighbor 1.1.80.1 password cisco
 neighbor 1.1.80.1 send-community both
 neighbor 172.16.15.2 remote-as 300
 neighbor 172.16.15.2 password cisco
 neighbor 172.16.15.2 send-community both
 neighbor 172.16.15.3 remote-as 300
 neighbor 172.16.15.3 password cisco
 neighbor 172.16.15.3 next-hop-self
 neighbor 172.16.15.3 send-community both
 no auto-summary

R26(config)#router bgp 300
R26(config-router)#bgp ?
  aggregate-timer               Configure Aggregation Timer
  always-compare-med      Allow comparing MED from different neighbors
  asnotation                        Change the default asplain notation
  bestpath                           Change the default bestpath selection
  client-to-client                 Configure client to client route reflection
  cluster-id                          Configure Route-Reflector Cluster-id (peers may reset)
  confederation                  AS confederation parameters
  dampening                      Enable route-flap dampening
  default                             Configure BGP defaults
  deterministic-med           Pick the best-MED path among paths advertised from
                                          the neighboring AS
  dmzlink-bw                    Use DMZ Link Bandwidth as weight for BGP multipaths
  enforce-first-as               Enforce the first AS for EBGP routes(default)
  fast-external-fallover      Immediately reset session if a link to a directly
                                          connected external peer goes down
  graceful-restart               Graceful restart capability parameters
  inject-map                      Routemap which specifies prefixes to inject
  log-neighbor-changes    Log neighbor up/down and reset reason
  maxas-limit                   Allow AS-PATH attribute from any neighbor imposing a
                                        limit on number of ASes
  nexthop                         Nexthop tracking commands
  redistribute-internal     Allow redistribution of iBGP into IGPs (dangerous)
  regexp                          Select regular expression engine
  router-id                       Override configured router identifier (peers will   reset)
  scan-time                      Configure background scanner interval
  soft-reconfig-backup    Use soft-reconfiguration inbound only when route-refresh is not negotiated
  suppress-inactive         Suppress routes that are not in the routing table
  transport                       global enable/disable transport session parameters
  update-delay                Set the max initial delay for sending update
  upgrade-cli                  Upgrade to hierarchical AFI mode  <<<<<<<-------------------

R26(config-router)#bgp upgrade-cli
You are about to upgrade to the hierarchical AFI syntax of bgp commands
Are you sure ? [yes]:
R26(config-router)#

la configurazione 1 si trasforma nella configurazione 2 (il comportamento del BGP rimane immutato)

dopo configurazione 2
router bgp 300
 bgp default local-preference 150
 bgp log-neighbor-changes
 neighbor 1.1.80.1 remote-as 200
 neighbor 1.1.80.1 password cisco
 neighbor 172.16.15.2 remote-as 300
 neighbor 172.16.15.2 password cisco
 neighbor 172.16.15.3 remote-as 300
 neighbor 172.16.15.3 password cisco
 !
 address-family ipv4
  no synchronization
  network 10.1.1.26 mask 255.255.255.255
  neighbor 1.1.80.1 activate
  neighbor 1.1.80.1 send-community both
  neighbor 172.16.15.2 activate
  neighbor 172.16.15.2 send-community both
  neighbor 172.16.15.3 activate
  neighbor 172.16.15.3 send-community both
  neighbor 172.16.15.3 next-hop-self
  no auto-summary
 exit-address-family

TEST 1
proviamo ad aggiungere un neighbor sotto router BGP 300 (quest'ultimo sarà automaticamente inserito anche in address-family ipv4)

R26(config)#router bgp 300
R26(config-router)#neighbor 1.1.1.1 remote-as 50

router bgp 300
 bgp default local-preference 150
 bgp log-neighbor-changes
 neighbor 1.1.1.1 remote-as 50
 neighbor 1.1.80.1 remote-as 200
 neighbor 1.1.80.1 password cisco
 neighbor 172.16.15.2 remote-as 300
 neighbor 172.16.15.2 password cisco
 neighbor 172.16.15.3 remote-as 300
 neighbor 172.16.15.3 password cisco
 !
 address-family ipv4
  no synchronization
  network 10.1.1.26 mask 255.255.255.255
  neighbor 1.1.1.1 activate                             <------------il neighbor è creato anche qui
  neighbor 1.1.80.1 activate
  neighbor 1.1.80.1 send-community both
  neighbor 172.16.15.2 activate
  neighbor 172.16.15.2 send-community both
  neighbor 172.16.15.3 activate
  neighbor 172.16.15.3 send-community both
  neighbor 172.16.15.3 next-hop-self
  no auto-summary
 exit-address-family

TEST 2
volendo aggiungere una network da annunciare , si nota che dovrà essere inserita sotto address family ipv4 (non vi è la posiibilità di inserirla sotto router bgp

R26(config)#router bgp 300              
R26(config-router)#n?
neighbor  no 

TEST 3
inserendo il comando "no bgp default ipv4-unicast " sotto router bgp   si impedisce l'automatismo
che replica i comandi router bgp  anche sotto address-family ipv4

R26(config-router)#no bgp default ipv4-unicast
provando adesso a creare un nuovo neighbor

R26(config-router)#neighbor 2.2.2.2 remote-as 20

router bgp 300
 no bgp default ipv4-unicast
 bgp default local-preference 150
 bgp log-neighbor-changes
 neighbor 1.1.1.1 remote-as 50
 neighbor 1.1.80.1 remote-as 200
 neighbor 1.1.80.1 password cisco
 neighbor 2.2.2.2 remote-as 20  <-------- il neighbor non verrà creato anche in addres-family ipv4
 neighbor 172.16.15.2 remote-as 300
 neighbor 172.16.15.2 password cisco
 neighbor 172.16.15.3 remote-as 300
 neighbor 172.16.15.3 password cisco
 !
 address-family ipv4
  no synchronization
  network 10.1.1.26 mask 255.255.255.255
  neighbor 1.1.1.1 activate
  neighbor 1.1.80.1 activate
  neighbor 1.1.80.1 send-community both
  neighbor 172.16.15.2 activate
  neighbor 172.16.15.2 send-community both
  neighbor 172.16.15.3 activate
  neighbor 172.16.15.3 send-community both
  neighbor 172.16.15.3 next-hop-self
  no auto-summary
 exit-address-family