Thank you Mr.Burns, your video was a great help in deploying MSO 3.0 in large government site with ACI 5.0 and IOS 15.0...really appreciate you efforts.
Awesome end-to-end presentation/demo where presenter covers the installation, configuration, and stretched EPG/BD deployment on ACI Multi-Site, APICs, Switches, and IPN!
Because there is no gain. With broadcast you will have to worry about DR/BDR, high timers for convergence. Since it’s a point to point link with only 2 hosts, the choice is obvious.
Hi Robert, Thanks for sharing this video with a global end to end approach on how to implement multi site. It is of a great assistance ! I've a question about managing contracts with the MSC. The scope of your use-case in the video was too limited to show any details about contracts. Would it be possible to create and use contracts between schema's. Because now it looks like (in my lab running 1.1.2) contracts do not get exposed for reuse between schema's. (contracts or other network related objects, like BD, etc.) Where as using the APIC it is possible to do so. Thx
Thanks for the informative vid!! One clarification question: (around 5-min of the vid) both FAB5 and FAB6 are shown using the same Fabric ID 1 and infra VLAN 4093. Shouldn't those value to be different for the two sites? For example FAB3 is initialized with Fabric ID 1; Infra VLAN 4093 and FAB6 is initialized as Fabric ID 2; Infra VLAN 4094? OR It wont matter?
Great....There could not be better way to explain the Multipod deployments...Can I ask/request for these software to set up my own Lab on my system...please let me know
Hi Mr. Burns, Thanks for the presentation. I have serveral question regarding this. 1) . Does infra vlan need to be same for each sites. 2). For DTEP (ucast, mcast, mpod) and CPTEP address, is it must /32 address? or it can be any address on /24 or /27 segment?
Hello Robert, Thanks for this. Do you have a detailed document on what happens if you have multiple spines connecting to multiple IPN devices? Let's say your fabric consist of 2 spines in each site and you need to hook them to the IPN? Or you want to hook an already existing Multi-pod to a multi-site
you just need to add more ISN switches, add the corresponding configuration for those switches, then update you APIC spine profile, interface selectors etc... then from MSO add the ports and teps needed on your sites
Hi Robert, great video ! I have two questions - does the pod i.d need to be different in both the sites? (The default is always 1 when you start configuring a new site). Second - the BD subnet that you configured: 1.1.1.254/24, is that deployed on both the sites? In your video you have only shown it to be deployed in Fab3.
Hi Robert ..thanks for giving such wonderful video..... just need to know if you have any video like normal setup environment to ACI environment ...means traditional setup access switch then core switch and then fw then internet router and then outside world this setup converted into ACI setup....from scratch we need to know how data flow happen as i am looking for job for ACI support so that kind of videos will helpful..
Hi, Robert, this was beautifully presented well done! Having deployed MultiPod, it makes a lot of sense for Cisco to go this route for MultiSite. One question is will the MSC GUI interface be deployed or merged with the APIC GUI interface? I ask because Cisco should think about that as the MSC GUI is logical and easy to follow when the technology is well understood.
MSC and APIC will always remain separate. Each have their own purpose. APIC is far more feature rich at this point, whereas MSC is more based on Tenant policy stretching. There's much the MSC UI can't do yet, which is why it looks much more streamlined & simple. The upcoming improvements in 3.1 APIC will hopefully help address some of the UI challenges.
![[HD] Cisco ACI Brownfield Network Centric to Application Centric Migration](http://i.ytimg.com/vi/4gDOsAhCDEE/mqdefault.jpg)
![[HD] Cisco ACI Brownfield Network Centric to Application Centric Migration](/img/tr.png)
Thank you Mr.Burns, your video was a great help in deploying MSO 3.0 in large government site with ACI 5.0 and IOS 15.0...really appreciate you efforts.
Awesome end-to-end presentation/demo where presenter covers the installation, configuration, and stretched EPG/BD deployment on ACI Multi-Site, APICs, Switches, and IPN!
The Video is great with so much to learn, thanks.
Multisite well explained - Robert Burns - thank you for sharing...
Excellent Video. Thank you very much.
Great demo! Thanks. One question, why not use ospf network type broadcast, which is the default network type for dot1q interfaces?
Because there is no gain. With broadcast you will have to worry about DR/BDR, high timers for convergence. Since it’s a point to point link with only 2 hosts, the choice is obvious.
Hi Robert,
Thanks for sharing this video with a global end to end approach on how to implement multi site. It is of a great assistance !
I've a question about managing contracts with the MSC. The scope of your use-case in the video was too limited to show any details about contracts.
Would it be possible to create and use contracts between schema's. Because now it looks like (in my lab running 1.1.2) contracts do not get exposed for reuse between schema's.
(contracts or other network related objects, like BD, etc.)
Where as using the APIC it is possible to do so.
Thx
Thanks for the informative vid!! One clarification question: (around 5-min of the vid) both FAB5 and FAB6 are shown using the same Fabric ID 1 and infra VLAN 4093. Shouldn't those value to be different for the two sites? For example FAB3 is initialized with Fabric ID 1; Infra VLAN 4093 and FAB6 is initialized as Fabric ID 2; Infra VLAN 4094? OR It wont matter?
Great....There could not be better way to explain the Multipod deployments...Can I ask/request for these software to set up my own Lab on my system...please let me know
you don't need to set vrf on the physical interfaces on the IPN. Just set vrf on the subinterfaces where you configured the IP addresses.
Hi Mr. Burns, Thanks for the presentation. I have serveral question regarding this. 1) . Does infra vlan need to be same for each sites. 2). For DTEP (ucast, mcast, mpod) and CPTEP address, is it must /32 address? or it can be any address on /24 or /27 segment?
Hello Robert, Thanks for this. Do you have a detailed document on what happens if you have multiple spines connecting to multiple IPN devices? Let's say your fabric consist of 2 spines in each site and you need to hook them to the IPN? Or you want to hook an already existing Multi-pod to a multi-site
you just need to add more ISN switches, add the corresponding configuration for those switches, then update you APIC spine profile, interface selectors etc... then from MSO add the ports and teps needed on your sites
Hi Robert, great video ! I have two questions - does the pod i.d need to be different in both the sites? (The default is always 1 when you start configuring a new site). Second - the BD subnet that you configured: 1.1.1.254/24, is that deployed on both the sites? In your video you have only shown it to be deployed in Fab3.
Very well explained. .... thank you
Hi Robert ..thanks for giving such wonderful video.....
just need to know if you have any video like normal setup environment to ACI environment ...means traditional setup access switch then core switch and then fw then internet router and then outside world this setup converted into ACI setup....from scratch we need to know how data flow happen as i am looking for job for ACI support so that kind of videos will helpful..
Hi Naik, this will help you,,,ua-cam.com/video/2wdrQzaF5e8/v-deo.html
Awesome video
Can anyone explain, to which FAB the MSC controllers are connected (Fab3 or Fab6) ? .
it does not matter. Only it need to reach the apic mgmt interface.
Hi, Robert, this was beautifully presented well done! Having deployed MultiPod, it makes a lot of sense for Cisco to go this route for MultiSite.
One question is will the MSC GUI interface be deployed or merged with the APIC GUI interface? I ask because Cisco should think about that as the MSC GUI is logical and easy to follow when the technology is well understood.
MSC and APIC will always remain separate. Each have their own purpose. APIC is far more feature rich at this point, whereas MSC is more based on Tenant policy stretching. There's much the MSC UI can't do yet, which is why it looks much more streamlined & simple. The upcoming improvements in 3.1 APIC will hopefully help address some of the UI challenges.
thank u so much this video s th best
cool ever