Accepted Solutions
GOLF - is just one letter away from ROFL
But seriously, it stands for Giant OverLay Fabric. A VERY EARLY attempt at
- Providing a way of joining multiple ACI Fabrics
- Pretending there was some life left in those ancient Nexus 7000 and ASR9000 routers you may have paid a fortune for just before the Nexus 9000 series came out.
Essentially what it (supposedly) allowed you to do was connect those legacy routers to the spines as L3 Out connections, using OSPF between the Spines and the N7K/ASR9K and to provide a l3 EVPN service. Configuration was (supposedly) then able to be pushed from ACI to these devices using OpFlex (Open Flexible protocol). It was Cisco's hope to get other vendors to implement an OpFlex stack in their devices which would allow a SDN Controller (i.e an APIC) to push policy to the devices using an Imperative model rather than a Declarative model.
I only ever knew of one site (in 2016) that ever actually tried to implement it (because they'd recently - 2013 or so - spent $millions on Nexus 7K core routers). They spend weeks trying to get it to work, could get any of the OpFlex thing happening and had to manually configure everything and spent many hours with Cisco TAC before giving up and using new Nexus 9000 Routers.
There may be sites using it successfully, but it is NOT a feature you'd want to look into implementing UNLESS you have Nexus 7K/ASR9K kit hanging around that you want to use. And even then, if may not be worth the effort.
Hi @Suprit Chinchodikar ,
AHHHH - the old "hidden AS number" trick that the wizard forgot!
Probably worth asking this as a separate question with new topic, because it's a doozy!
To answer this, I'll steal a section of our BGP Lab guide where the L3Out is called ProductionVRF_BGP.L3Out
- The local AS value was not set as part of the L3Out wizard, so this needs to be completed manually. In your tenant, navigate to Networking > L3Outs > ProductionVRF_BGP.L3Out > Logical Node Profiles > ProductionVRF_BGP.L3Out_nodeProfile > Logical Interface Profiles > ProductionVRF_BGP.L3Out_interfaceProfile > BGP Peer x.x.x.x‑Node‑xxxx/1/xx
Local-AS Number: Set the AS number here
GOLF - is just one letter away from ROFL
But seriously, it stands for Giant OverLay Fabric. A VERY EARLY attempt at
- Providing a way of joining multiple ACI Fabrics
- Pretending there was some life left in those ancient Nexus 7000 and ASR9000 routers you may have paid a fortune for just before the Nexus 9000 series came out.
Essentially what it (supposedly) allowed you to do was connect those legacy routers to the spines as L3 Out connections, using OSPF between the Spines and the N7K/ASR9K and to provide a l3 EVPN service. Configuration was (supposedly) then able to be pushed from ACI to these devices using OpFlex (Open Flexible protocol). It was Cisco's hope to get other vendors to implement an OpFlex stack in their devices which would allow a SDN Controller (i.e an APIC) to push policy to the devices using an Imperative model rather than a Declarative model.
I only ever knew of one site (in 2016) that ever actually tried to implement it (because they'd recently - 2013 or so - spent $millions on Nexus 7K core routers). They spend weeks trying to get it to work, could get any of the OpFlex thing happening and had to manually configure everything and spent many hours with Cisco TAC before giving up and using new Nexus 9000 Routers.
There may be sites using it successfully, but it is NOT a feature you'd want to look into implementing UNLESS you have Nexus 7K/ASR9K kit hanging around that you want to use. And even then, if may not be worth the effort.
Hi @Suprit Chinchodikar ,
AHHHH - the old "hidden AS number" trick that the wizard forgot!
Probably worth asking this as a separate question with new topic, because it's a doozy!
To answer this, I'll steal a section of our BGP Lab guide where the L3Out is called ProductionVRF_BGP.L3Out
- The local AS value was not set as part of the L3Out wizard, so this needs to be completed manually. In your tenant, navigate to Networking > L3Outs > ProductionVRF_BGP.L3Out > Logical Node Profiles > ProductionVRF_BGP.L3Out_nodeProfile > Logical Interface Profiles > ProductionVRF_BGP.L3Out_interfaceProfile > BGP Peer x.x.x.x‑Node‑xxxx/1/xx
Local-AS Number: Set the AS number here
