Juniper Apstra Demo: Manage multiple data center vendors with a unified tool

0:01 supply chain challenges continue what

0:04 are you doing to protect your business

0:07 how would you like to be able to easily

0:08 switch Network vendors

0:10 what if you could save money on your

0:12 next switch purchase

0:15 vendor lock-in sucks but adopting

0:17 multiple vendors is hard

0:19 staff is often trained on a single

0:21 vendor and they'd probably need a

0:22 Rosetta Stone to be able to decipher

0:24 Network device configs across vendors

0:27 what you really need is to be able to

0:30 design the best network for your

0:31 business needs regardless of the

0:33 underlying vendor

0:35 with Appster you have the tool you need

0:36 to make this possible

0:38 app store's intent based networking

0:40 platform is a multi-vendor design

0:41 deployment and operations tool that any

0:44 network engineer can use

0:45 they don't need to be experts on one

0:47 network operating system or really any

0:49 network operating system they just need

0:51 to understand networking

0:53 an app store's multi-vendor capabilities

0:55 allow you to insert the right device for

0:57 the job regardless of vendor

1:00 so you can choose a new Leaf switch not

1:02 just based on capabilities but also

1:04 based on lead time

1:06 in this demo we're going to deploy a new

1:08 virtual Network onto running data center

1:10 Fabrics in two different data centers

1:13 in the San Francisco data center we're

1:15 running a pair of spine switches a rack

1:17 with a redundant pair of leaf switches

1:19 and a second rack with a single leaf

1:21 switch all of these switches are from

1:23 Juniper Networks

1:24 we'll drill down into the stage menu to

1:26 create this virtual Network choosing

1:28 vxlan as a network type enabling DHCP

1:31 assigning a subnet and gateway address

1:34 creating a template for tagged

1:36 interfaces on the leaf switches and

1:38 choose which switches we're going to

1:39 deploy to

1:41 then we'll assign this virtual Network

1:43 to the available server-facing

1:44 interfaces on each Leaf switch

1:47 notice that we didn't enter any Juniper

1:49 syntax we simply entered the required

1:51 information needed to design this

1:53 virtual Network

1:54 apps that will validate that required

1:56 information as we go and will catch

1:58 mistakes and let us know if something is

2:00 missing before we move on to the next

2:01 step

2:03 then apps will render the Juniper

2:04 configuration Syntax for us

2:08 let's take a look at some of the

2:09 rendered configs that we're about to

2:11 push to the network

2:13 that looks like junos

2:16 now I love junos but I'm glad I didn't

2:18 have to type all that

2:21 finally we'll commit these changes and

2:23 Appster will push the configuration

2:25 changes onto the devices that we're

2:26 using for this service simple

2:29 now let's take a look at the Seattle

2:30 Data Center

2:32 here we're running a multi-vendor

2:33 network there's a rack with a couple of

2:35 redundant Arista Leaf switches a rack

2:37 with a single Cisco Leaf switch and a

2:40 couple of spine switches that are

2:41 running the Sonic OS

2:43 now I don't know about you but I would

2:45 have a really tough time configuring a

2:46 new virtual Network in this data center

2:48 if I had to do it manually even if I

2:50 knew my way around each of these Network

2:52 operating systems it'd be really

2:54 challenging to have to remember the

2:55 unique syntax of each without making

2:57 mistakes this kind of network seems

3:00 risky but not with abstra

3:03 we're going to follow the same workflow

3:05 that we used in the San Francisco data

3:07 center we'll create a new virtual

3:08 Network enter the same type of

3:10 information create the same type of

3:12 interface template

3:14 and follow the same steps to choose

3:15 which switches we deploy to

3:18 we'll follow the same process to assign

3:20 this network to Leaf switch interfaces

3:22 and we're done

3:24 again we didn't need to remember any

3:25 vendor-specific syntax

3:27 we didn't even need to care if it was an

3:29 Aristo or a Cisco Leaf node as we can

3:32 see by looking at the rendered configs

3:33 Appster took care of the vendor specific

3:35 stuff for us

3:37 Appster gives you a reliable way to

3:39 deploy networks and make changes across

3:41 any data center Network vendor's devices

3:43 you'll be able to shift to a different

3:45 vendor's device easily without worrying

3:47 about your team's expertise on any one

3:49 vendor's CLI

3:50 this is how you can short circuit supply

3:52 chain issues

3:54 and if you've got an achievable

3:55 multi-vendor strategy in place you'll be

3:57 in a much stronger position to negotiate

3:59 a better price when it comes time to

4:01 purchase your next data center switch

4:04 our customer refuse and even said that

4:05 they were able to name not one but three

4:07 Hardware vendors on their latest RFP and

4:10 told their purchasing department to just

4:11 buy from whoever can deliver first

4:15 with Appster you can free your data

4:16 center network from vendor lock-in and

4:18 short-circuit the supply chain crisis

4:20 [Music]