At the 4 minute make you indicated that the WAN edge can receive any configurations from VManage. Is it not the responsibility of Vsmart to push configuration/policy updates down to the WAN edge from VManage?
SD-WAN Router will get routing updates and policies from vSmart (now called Cisco Catalyst Controller) and router configuration from vManage (now called Cisco Catalyst SD-WAN Manager). So, yes, you both are correct - SD-WAN router is getting routing updates / policies from vSmart and device-level config from vSmart. 🙂
@@NikolaiPitaev thank you for the clarification. I was looking at the SD-wan fabric as hierarchical. Vsmart >>>>Vmanage>>>edge where all changes and updates made at Vsmart is pushed to edges from Vmanage. Now I realize permanent connections are made to the edge from Vmanage/Vsmart. Thank you for the clarification. 👍🏾👍🏾👍🏾👍🏾
informative. But you did not cover how exactly a hole punching is done on the firewall to allow the connection and that would have cleared up vbond's role as a STUN server.
Precise and highly informative. Hits the points succinctly
At the 4 minute make you indicated that the WAN edge can receive any configurations from VManage. Is it not the responsibility of Vsmart to push configuration/policy updates down to the WAN edge from VManage?
SD-WAN Router will get routing updates and policies from vSmart (now called Cisco Catalyst Controller) and router configuration from vManage (now called Cisco Catalyst SD-WAN Manager). So, yes, you both are correct - SD-WAN router is getting routing updates / policies from vSmart and device-level config from vSmart. 🙂
@@NikolaiPitaev thank you for the clarification. I was looking at the SD-wan fabric as hierarchical. Vsmart >>>>Vmanage>>>edge where all changes and updates made at Vsmart is pushed to edges from Vmanage. Now I realize permanent connections are made to the edge from Vmanage/Vsmart. Thank you for the clarification. 👍🏾👍🏾👍🏾👍🏾
Concise and VERY informative.
Thank you.
Nicely done!
informative. But you did not cover how exactly a hole punching is done on the firewall to allow the connection and that would have cleared up vbond's role as a STUN server.
this is priceless ! thank you very much .