The problem: i have my BGP AS, and i make ibgp peering between R1<->SW<->R2 and i am using for this my BGP AS network segment. In general this is dual multihoming. R1 - my main router. R2 - backup. at my SW - there are my BGP AS which presents like a vlans.
The question is:
When my R1 is UP -> i can't ping SW iBGP ip.
When R1 goes down and R2 is main router - the ping is accept.
router bgp AS bgp log-neighbor-changes network x.x.x.x mask 255.255.252.0 timers bgp 15 45 neighbor x.x.x.2 remote-as AS -iBGP peer neighbor x.x.x.2 next-hop-self neighbor x.x.x.3 remote-as AS - iBGP peer neighbor x.x.x.3 next-hop-self neighbor x.x.x.x remote-as AS - eBGP peer neighbor x.x.x.x soft-reconfiguration inbound neighbor x.x.x.x route-map ISP1_in in neighbor x.x.x.x route-map ISP2_out out
router bgp AS bgp log-neighbor-changes network x.x.x.x mask 255.255.252.0 neighbor x.x.x.x remote-as AS neighbor x.x.x.x soft-reconfiguration inbound neighbor x.x.x.x route-map ISP2_in in neighbor x.x.x.x route-map ISP2_out out neighbor x.x.x.1 remote-as AS - iBGP peer neighbor x.x.x.3 remote-as AS - iBGP peer
router bgp AS timers bgp 15 45 neighbor x.x.x.x remote-as AS neighbor x.x.x.x update-source Vlan185 neighbor x.x.x.x remote-as AS neighbor x.x.x.x update-source Vlan185
1. Log into CLI of DNAC:
ssh maglev@< DNAC appliance IP> -p 2222
2. Run this curl command to get token to get member id:
curl -X POST -u admin:<admin user password> -H -V https://<CLUSTER-IP>/api/system/v1/identitymgmt/token
Enterprise Switching Business Unit is glad to announce Beta release 16.12.2 for all Catalyst 9200/9300/9400/9500/9600 and Catalyst 3650/3850 Platforms. This release is made available to allow users to test, evaluate and share fee...
Do you currently have hands-on networking experience? If you do, we'd love to hear from you!
Your feedback will be reviewed and analyzed by our team to directly influence a networking management and monitoring product.
Take the 20-min or les...