To get started with wired assurance, we will need to adopt our Brownfield Juniper switch. We’ll need to make sure it’s one of these supported platforms. In my case, I’ve got an EX2300, so let’s get started. It’s running 18.2 R3 already. So let’s get going. From the Mist UI, we go right to organization and inventory. And since this is a Brownfield switch, we all want to adopt it.
Here’s the code snippet automatically generated from my Oregon site. And I copied this to the clipboard. And then I’ll paste it into the switch CLI in configuration mode. And then commit it. So what does this code do? First, we enable SSH. Second, we create a mist user. Third, we create a client device ID and credentials so we can map the device to an org. Fourth, we set up the outbound SSH client and associated timers.
You will need to make sure the switch can reach the internet through either the ME0 management port or the IRB0 virtual port. In my case, I’m using the management port. After you commit the code, you should not need to reboot the switch. If there’s a firewall involved, you will need to open this port. And to make sure things are working correctly, let’s first ping the gateway. Then we’ll ping Google. And then OCfirstname.lastname@example.org just to see if the name resolves correctly. It will not answer a ping.
But in this case, it resolved correctly. Once the switch is connected to the cloud, you should be able to see it in inventory and then assign it to a site. So we see my switch is running and has a local DHCP address. Clicking into it, we can see a lot more data. Hover over a gig port, this happens to be my upstream port. And this one is a trunk port running to a switch upstairs to separate my IPv6 multicast streaming TV traffic.
And here is an AP41 pulling 11.6 watts. Moving through the window, we can see hovers for CPU, memory, temperature, PoE, power supplies, and fans. Of which, the 2300 doesn’t have. In the utilities pull down, you can reboot the switch or open up all these cool testing tools. Here, from the switch point of view, you can ping, run a traceroute, test a cable, bounce a port, or open a switch CLI window.
Going into switch insights, we can see the traffic and events during the course of the day, as well as graphs covering CPU and memory utilization, as well as bytes, port errors, and the power drawing over time. And moving lower in the window, we can see the current values as either a visual or a port list. Switching to the mist office, we can see a lot more switches, where the location tab is a lot more interesting, as you can visually see which APs are connected to a switch and what the proverbial blast radius would be if you had an outage. Obviously, we would suggest a bit more salt and pepper design to our customers if the cable plan allows for it.