For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

LillyM_9417's avatar
LillyM_9417
Icon for Altostratus rankAltostratus
Jul 11, 2013

BGP Config

Hello,

 

Could you please share a BGP configuration example of viprions, which are working as an active / standby mode?

 

Thanks a lot.

 

config
design

2 Replies

  • tbledsoe_90582's avatar
    tbledsoe_90582
    Icon for Nimbostratus rankNimbostratus
    Aug 14, 2013
    Here’s the configuration for F5/NEXUS BGP interoperability.


Nexus Configuration:

  neighbor 172.26.8.11
    inherit peer RR_CLIENT_NEAR
    description PD-EL-01
    no shutdown
    no dynamic-capability <= no peering w/out this.

F5
[root@PD-EL-01:Active:Standalone] config  tmsh
root@(PD-EL-01)(cfg-sync Standalone)(Active)(/Common)(tmos) run /util imish -r 0

Looks very familiar:

PD-EL-01.net.com[0]>en
PD-EL-01.net.com[0]sh ip bgp summary

BGP router identifier 172.26.8.11, local AS number 65535
BGP table version is 83
16 BGP AS-PATH entries
0 BGP community entries

Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
10.26.255.1     4 65535   63536  126658       83    0    0 00:07:44      277
10.26.255.2     4 65535     294     299       83    0    0 00:00:35      290

Total number of neighbors 2
DFWDC-PD-EL-01.net.lpl.com[0]sh run
!
no service password-encryption
!
log file /var/log/zebos.log
no banner motd
!
interface lo
!
interface tmm0
!
interface DZ_RT_DFD_WEB
!
interface DZ_RT_DFD_DISTRIBUTION
!
interface DZ_RT_DFD_ADVISOR
!
interface DZ_RT_DFD_AUXILIARY
!
router ospf 111
timers spf exp 500 50000
network 172.26.8.0 0.0.7.255 area 0.0.0.0
network 172.26.16.0 0.0.7.255 area 0.0.0.0
!
router bgp 65535
bgp router-id 172.26.8.11
bgp log-neighbor-changes
bgp graceful-restart restart-time 120
network 172.26.8.0/21
network 172.26.16.0/21
timers bgp 10 30
neighbor 10.26.255.1 remote-as 65535
neighbor 10.26.255.1 description PD-CR-02
neighbor 10.26.255.1 soft-reconfiguration inbound
neighbor 10.26.255.2 remote-as 65535
neighbor 10.26.255.2 soft-reconfiguration inbound
neighbor 10.26.255.2 capability graceful-restart
!
line con 0
login
line vty 0 4
login
!
End

PD-EL-01.com[0]sho ip route 207.230.188.61
Routing entry for 207.230.188.61/32
  Known via "bgp", distance 200, metric 0, best
  Last update 00:12:45 ago
  * 192.168.255.206 (recursive via 172.26.8.1)
    • aj1's avatar
      aj1
      Icon for Nimbostratus rankNimbostratus
      Oct 30, 2014
      That looks like one F5 connected to two upstream routers. I am having the same scenario as OP - an active/standby viprion pair directly connected (full mesh) to two upstream routes via BGP, and its not working right. I am not using an floating-IPs (like its recommended internally) on the external VLANs. I would like to keep it that way and instead use some PBR (or IP SLA or BGP attributes or iRules) so that the upstream routers can detect the active and the standby unit and change the next-hop accordingly in the event of a failover. The zebos implementation for BGP4 on F5 does not seem to have IP SLA, so thats out of question, I guess. Is there a way I can have active/standby viprion pair, both connected to two upstream routers using a /30 links, and still get the right next-hop when the active unit goes down. And all of this w/o using floating-IPs. Any help appreciated.