All right, we don't want to use the built-in console in CML because it's small
and inconvenient.
I'd really rather use my preferred terminal platform of choice, whether that's
putty
or something else.
And so we can use the breakout tool in order to accomplish that.
The breakout tool is going to be this tool that we have to download.
And I'm going to come up to Tools, Breakout Tool in order to do this.
It's going to take me to some internal documentation pages.
I can read about it.
But what's important here is if I'm going to use, let's say, Putty, I'm going
to have
to use Telnet in order to gain access to these devices to say, oh, man, Telnet
's not secure.
Well, first of all, it's a lab environment.
Hopefully it's nothing too insecure that we're communicating, but it does write
a secure
TLS tunnel to get to the device.
So that problem is resolved for us as well.
So Telnet from Putty, through the breakout tool, across a TLS connection, right
into
the device that's in my-- now it's calling it Viral here.
That's an old name for CML.
We see it up here, CML2, Viral2.
Yeah, that's the same thing.
They need to update that image.
In order to download it, I'm going to come over here to the left to the
download link.
I'm going to download the appropriate file depending on what operating system I
'm running.
From here, I'm going to need to open up a command prompt.
And so here I'm going to go to where I downloaded it.
For me, I'm just going to go to the Downloads directory because that's where it
is.
And I'm going to type out the executable name, which is Breakout.dash, whatever
.
Again, it was on that page and you can reference the one that you downloaded.
But we also want to say space here and add the UI component because we want to
manage
this via the web GUI.
So I'm going to hit Enter here.
And we should see that it opens up the user interface on this URL, which we'll
notice is
just my own IP address and it's running on port 8080.
So we need to make sure that that port is available.
So I'm going to come out to my web browser here and enter in that we want to
call it
a URL.
It's just an IP address.
And we should see that it connects and we're connected.
Now keep in mind that sometimes I've had to use different web browsers to get
this to
work, it just depends on the configuration and you can try clearing cookies and
such.
But for example, if you use Edge or Chrome, you might need to use Firefox to
connect or
vice versa.
So just something to keep in mind, a little bit of troubleshooting that I've
come across
with this.
What we're going to see is we're going to see our active labs.
So I was running one called, well, I actually was running this unnamed one here
and SD-WAN
test is the one that we just spun up.
So if I click on this, we should see the three different devices that we were
just configuring.
Our one, our two, and switch one.
Furthermore, it's given them port IDs, but I haven't actually enabled this yet.
So what I can do here is say, all right, let's go ahead and connect to this lab
environment.
And now when I click on it, I can't edit the port numbers anymore.
So if I want to change the port numbers, I can, but for the most part, it's
arbitrary.
So notice that in order to connect now, I can tell not into my, it's a little
hard to read
here, but it's 127.0.0.1 and then colon with the port number that's here, 9,000
, 9,000,
1,9,000.
So if I were to pull up my Moba term here, and what we'll find is I've actually
got session
saved according to the port ID.
Could I save it according to like R1, R2 and switch one?
Yeah, I can, but it's going to change depending on the lab I'm connecting to.
And if I reset the lab and the devices come up in a different order, then maybe
9,000,
which was connected to R1 is now connected to R2 or switch one or something
like that.
So I've just got them labeled according to port ID.
And as we see here, it's just tell netting to 127.0.0.1 according to that port.
So I'm going to double click on 9,000 and hit enter.
And we see I'm connecting to that R1 now, which is absolutely wonderful.
Yes, it's extremely zoomed in for the sake of recording here.
But if I do a show run on the interface of gig one, we should see that IP
address of 10,
0, 0, 1 that I just configured previously.
So that is how we can use the breakout tool to connect to our devices using our
terminal,
normal terminal software packages can use whatever terminal software package
you want
at that point.
Just keep in mind that the breakout tool does take a little bit of finagling.
There might be some troubleshooting steps as far as making sure that it's
actually running
and that we were using a web browser that can connect to it.
You might have to refresh it a few times.
I've seen some issues with it from that perspective, but overall, once it's
running, it works
great.
And it's a beautiful thing to be able to log into my virtual lab environment
devices using
my putty or Mobiturm or secure CRT.