|
0:00:14
|
So just looking at our topology that we will be using,
|
|
0:00:19
|
for this network module for the task that we are going to accomplish.
|
|
0:00:23
|
To begin with we've got our Corporate Headquarter site,
|
|
0:00:28
|
and we've got a CUCM pub,
|
|
0:00:31
|
a sub, and those are the two that we are going to be working with
|
|
0:00:34
|
today, we're not really going to be working with the other servers,
|
|
0:00:37
|
although we do have a Unity Connection version 7
|
|
0:00:40
|
Unified Contacts Center Express, and
|
|
0:00:43
|
presence, all versions 7.0.1 servers.
|
|
0:00:47
|
These are all on a server subnet of 177.1.10.0/24
|
|
0:00:55
|
that's going to be VLAN10 or the server VLAN.
|
|
0:00:58
|
We also have a voice VLAN of 177.1.11.0/24
|
|
0:01:05
|
and VLAN12 the data or PC MAC VLAN
|
|
0:01:10
|
it's going to be 177.1.12.0/24.
|
|
0:01:16
|
OK? So those are going to be in our this is a 35
|
|
0:01:21
|
that's a 3560 switch, could just as well be a 3750 switch.
|
|
0:01:27
|
In terms of everything we need to do,
|
|
0:01:29
|
in fact in terms of what we need to do
|
|
0:01:31
|
this lab, it could be a 3524 maybe with the exception of DFCP
|
|
0:01:36
|
OK?
|
|
0:01:40
|
We've got, in this lab we're gonna have one
|
|
0:01:43
|
phone here directly connected to the switch,
|
|
0:01:47
|
we're also going to have
|
|
0:01:51
|
actually let me, now that I have, send that, maybe clear that off,
|
|
0:01:59
|
we're going to have our Headquarter Router 1
|
|
0:02:05
|
here, we're going to have, we actually have a VPN
|
|
0:02:14
|
across out from the PSTN router
|
|
0:02:19
|
and this VPN connection here comes up to
|
|
0:02:22
|
your own self study router and when I
|
|
0:02:24
|
say you're own in this case, it's going to be my
|
|
0:02:27
|
remote VPN router and I'm going to be doing this the same way
|
|
0:02:30
|
that any of you might rent rack time from either us
|
|
0:02:35
|
ine or even another rack rental vendor,
|
|
0:02:38
|
whomever or possibly even be using your own
|
|
0:02:42
|
rack and have to sometimes or want
|
|
0:02:45
|
to study away from that rack.
|
|
0:02:47
|
So we have a few phones directly connected to each site switch
|
|
0:02:51
|
and or router.
|
|
0:02:53
|
And there's some phones that you'll see as soon as I
|
|
0:02:56
|
scroll down a bit.
|
|
0:02:58
|
But we also have phones that are over here
|
|
0:03:02
|
connected to your own remote site.
|
|
0:03:05
|
Now that's hardware phones being connected
|
|
0:03:08
|
to remote sites, it's going to be useful for studying.
|
|
0:03:11
|
Because you can actually interact with the phones
|
|
0:03:14
|
they're much faster than using remote control software,
|
|
0:03:17
|
and you can see and you know, obviosuly fully interact with everything,
|
|
0:03:21
|
hardware phones that is. Software phones,
|
|
0:03:23
|
they're going to be OK, but there's many features that
|
|
0:03:27
|
they don't support. The only Skinny based software phones
|
|
0:03:30
|
that I know of, or the IP Blue or the CIPC Cisco Communicator,
|
|
0:03:38
|
OK, so if you can have your own hardware IP phones over here,
|
|
0:03:40
|
that's going to be great. I do
|
|
0:03:43
|
and of course highly encourage you guys as well
|
|
0:03:46
|
all to have your own hardware phones. If you cannot,
|
|
0:03:51
|
then you can use remote control software,
|
|
0:03:54
|
to control any of the hardware phones that we have on our rack.
|
|
0:03:57
|
For every voice rack of hardware that we have,
|
|
0:04:01
|
we should have a 7960 phone and a 7961.
|
|
0:04:05
|
7961 is utilized for a lot of the newer features
|
|
0:04:12
|
so then we also have phones here, some are connected to our
|
|
0:04:20
|
for router 2, our Branch1 site.
|
|
0:04:24
|
We're going to have a 7961 that we're going to interact with
|
|
0:04:28
|
and then we really won't use this one connected to site 2.
|
|
0:04:31
|
We're really not going to be much with site 2 today.
|
|
0:04:34
|
Because we can do everything with Headquarter and Branch 1.
|
|
0:04:40
|
OK? So that's our basic topology
|
|
0:04:42
|
our routers are connected via frame relay, there's
|
|
0:04:45
|
a PBC that goes from
|
|
0:04:47
|
Router 1, or Headquarter to Branch1, and one that goes from
|
|
0:04:51
|
Router 1 to Router 3 or Headquarter to Branch 2
|
|
0:04:56
|
OK? There's a single physical interface for this though
|
|
0:04:59
|
and then two PVC sub interfaces.
|
|
0:05:03
|
And then in terms of, TDM circuits out to the PSTN,
|
|
0:05:07
|
each router has a T1PRI or in the case of
|
|
0:05:11
|
Branch 2 Router 3, and E1 PRI out to the PSTN router
|
|
0:05:17
|
that we won't be using too much, but certainly a little bit today.
|
|
0:05:22
|
OK?
|
|
0:05:24
|
If any one has any other questions about Topology,
|
|
0:05:27
|
now would be the time to ask.
|
|
0:05:30
|
Otherwise, we'll take a look at our tasks.
|
|
0:05:36
|
So our tasks that we're going to be looking through today
|
|
0:05:39
|
for network infrastructure, we're going to look at
|
|
0:05:43
|
VLANs at Corporate Headquarters.
|
|
0:05:45
|
We're gonna be told to set up the Headquarter switch to support
|
|
0:05:48
|
whatever IP phones can be found
|
|
0:05:50
|
connected to the switch, so we'll have to find a way to
|
|
0:05:53
|
discover those phones.
|
|
0:05:55
|
Configure VLAN 11 for the phone's internal voice
|
|
0:05:58
|
VLAN and 12 as the VLAN to be passed on to PC port.
|
|
0:06:02
|
Assure the phones are able to talk on the network as fast as possible.
|
|
0:06:07
|
And then for Branch1, set up the ethernet switch module installed
|
|
0:06:10
|
Branch1 router to support whatever IP phones can be found
|
|
0:06:14
|
same VLANs and same talk as fast as possible.
|
|
0:06:19
|
So the only difference being the ethernet switch module.
|
|
0:06:22
|
OK? Sol let's go ahead and begin with those tasks.
|
|
0:06:28
|
We'll bring up terminal client and the client and the CCI voice lab is secure CRT.
|
|
0:06:34
|
Or you can use that or you can use just regular CRT, which is I think
|
|
0:06:38
|
half the price, maybe $50 last time I checked
|
|
0:06:41
|
from vandykesoftware.com, I think it's juts vandyke.com
|
|
0:06:46
|
could be wrong, it's been a while since I used it, it's only on a PC.
|
|
0:06:50
|
I use ZOC which works for a PC or a Mac, and I'm on a Mac.
|
|
0:06:54
|
You could also use puddy or
|
|
0:06:59
|
anything else. It's a good idea if you're studying for the lab
|
|
0:07:01
|
to actually use the terminal client
|
|
0:07:03
|
for that lab environment like secure CRT just so you're familiar with.
|
|
0:07:09
|
Intimately familiar how it's going to work. Do I know what version they're using?
|
|
0:07:13
|
It's a good question.
|
|
0:07:15
|
I believe that they have upgraded to version 5, so I think
|
|
0:07:21
|
secure CRT is on 6 or 7 now.
|
|
0:07:23
|
But I think they've upgraded the 5 which introduced tabs.
|
|
0:07:27
|
When the last time I took a lab,
|
|
0:07:30
|
security lab it was still version 3 and there were no tabs,
|
|
0:07:34
|
but I don't really know for positive, I believe that they've upgraded.
|
|
0:07:40
|
OK. Let's go ahead and open a link to Router 1 and Switch 1
|
|
0:07:49
|
and to Router 2. OK, so if you remember
|
|
0:07:58
|
for our Topology for the Headquarter Corporate site,
|
|
0:08:02
|
we've got our phones that are directly connected to the actual switch.
|
|
0:08:08
|
OK and then for our Branch 1 site,
|
|
0:08:13
|
they are connected to the router itself.
|
|
0:08:16
|
OK, so that's what we will be looking at.
|
|
0:08:21
|
So for our Corporate Headquarter switch,
|
|
0:08:24
|
let's do a show CDP neighbor.
|
|
0:08:26
|
And we do go ahead and we see a phone immediately,
|
|
0:08:29
|
an SEP Cell CUC ethernet phone,
|
|
0:08:32
|
and that is connected to the local interface or port FA02.
|
|
0:08:39
|
OK, so we can go ahead and do a showrun, Interface FA02.
|
|
0:08:46
|
And we see a description, we see that it is not administratively shut down,
|
|
0:08:50
|
but that's about it. So we were told to
|
|
0:08:55
|
confiure this phone and everyone at this point can go ahead
|
|
0:09:00
|
and I think I have assigned
|
|
0:09:03
|
microphone rights to everyone, so anyone that would like to is welcome
|
|
0:09:08
|
if you have a quality mic to go ahead and
|
|
0:09:10
|
speak up ask questions or interact as I ask you
|
|
0:09:15
|
what it is we're going to be doing on a given task.
|
|
0:09:18
|
So we we're told to enable VLANS, let's see what VLANS exist first.
|
|
0:09:25
|
So we'll just do a show VLAN brief.
|
|
0:09:29
|
We do see that we have VLAN 10, 11, and 12
|
|
0:09:33
|
for servers, voice and data.
|
|
0:09:35
|
Names have been given, already been configured,
|
|
0:09:37
|
so we don't need to create them, they do exist.
|
|
0:09:40
|
And the reason I mentioned that you shouldn't just assume they exist earlier,
|
|
0:09:43
|
is let's say you assign a port to a VLAN or
|
|
0:09:47
|
you assign a device to a VLAN and the VLAN did exist,
|
|
0:09:51
|
but it had been deleted and it doesn't get automatically re-created,
|
|
0:09:54
|
well two devices that are in the same VLAN,
|
|
0:09:58
|
but the VLAN doesn't exist in the database which is a very possible scenario,
|
|
0:10:02
|
those devices will not be able to talk to each other.
|
|
0:10:06
|
Without that, even though a VLAN is just sort of an
|
|
0:10:09
|
theory or kind of an idea or concept,
|
|
0:10:12
|
without that concept existing in the database
|
|
0:10:14
|
those devices will not be able to talk to each other.
|
|
0:10:17
|
There's no logical medium for them to talk or speak IP across.
|
|
0:10:22
|
So we'll go into config T here, we'll jump into intarface FAS 02
|
|
0:10:27
|
and first of all, we're gonna hard code for it switch port mode access,
|
|
0:10:34
|
now if we look back at our PDF, let's see move that down,
|
|
0:10:42
|
we weren't told whether to use access or trunk mode,
|
|
0:10:46
|
So it's gonna be easiest to use access mode, less configuration.
|
|
0:10:51
|
And by the way, I'm not going to be looking at the
|
|
0:10:54
|
they'll be connect as often, so if you
|
|
0:10:56
|
want to ask a question, please go ahead and
|
|
0:10:59
|
either raise your hand so I can see that little icon or speak up.
|
|
0:11:02
|
I see the Joe ask the question during the lab, should we shut down the
|
|
0:11:05
|
interfaces our phones are connected to until we get a
|
|
0:11:08
|
good portion of the config done, we certainly have that option.
|
|
0:11:11
|
I'm not gonna do that in this setting,
|
|
0:11:14
|
well there might be times when I do that,
|
|
0:11:16
|
but I'm not going to do that from the beginning.
|
|
0:11:18
|
But there might be very valid times for doing that.
|
|
0:11:22
|
So we weren't instructed access or
|
|
0:11:25
|
trunk method, so we're gonna use access method.
|
|
0:11:27
|
So switch port mode access and we'll use switch port access VLAN,
|
|
0:11:34
|
we we're told 12 for the PC Port, and then switch port voice VLAN
|
|
0:11:43
|
was going to be 11.
|
|
0:11:45
|
And now what I will do, well actually we haven't
|
|
0:11:48
|
created any DHCP yet, so I'm not gonna go ahead and bounce this port
|
|
0:11:51
|
but if I wanted to get an IP address, then I might bounce the port.
|
|
0:11:56
|
Bounce meaning, power cycle shut no shut.
|
|
0:12:00
|
OK?
|
|
0:12:02
|
So show run, interface fas02 and we see everything there.
|
|
0:12:12
|
Actually, that was 2, yes that's the one.
|
|
0:12:19
|
OK? So notice, I believe if we scroll up, I don't believe that was configured.
|
|
0:12:24
|
Notice that spanning 3 port fast
|
|
0:12:26
|
automatically got added when we changed to switch port mode access.
|
|
0:12:31
|
So it helped us, in fact it went ahead and met the requirement of
|
|
0:12:38
|
the third bullet point, assure phones are able to talk as fast as possible.
|
|
0:12:45
|
So we did a WR enter or write.
|
|
0:12:50
|
Now it's back
|
|
0:12:54
|
which is the fastest way to do a copy run start,
|
|
0:12:58
|
and now we'll go ahead and switch to Router 2
|
|
0:13:01
|
which if we remember from the diagram, I'll bring the diagram back up,
|
|
0:13:05
|
our phones are directly connected to the ethernet switch module
|
|
0:13:09
|
here in router 2.
|
|
0:13:12
|
Router 2 which is at Branch1, I know a bit confusing.
|
|
0:13:21
|
OK?
|
|
0:13:26
|
OK, so back on the terminal, we'll do a show CDP neighbor,
|
|
0:13:33
|
and note that we only see Corporate HQ as a device ID
|
|
0:13:38
|
it's a 2811 router and it's our serial port. We don't see any phones.
|
|
0:13:43
|
Oh no, what could have happened?
|
|
0:13:46
|
Well let's do a show IP interface brief
|
|
0:13:51
|
and see that, we've got some ports that are administratively down.
|
|
0:13:56
|
Now we notice that these two ports, F00 and FA fast ethernet 01,
|
|
0:14:03
|
are labeled just 0 and 0/1.
|
|
0:14:06
|
But these fast ethernet ports have another
|
|
0:14:09
|
subset of port numberings so
|
|
0:14:14
|
0/1/0011 012 and 013.
|
|
0:14:20
|
Now if you're unfamiliar with the way that IOS routers number things,
|
|
0:14:26
|
One thing you can do is always show inventory,
|
|
0:14:30
|
and with show inventory we see that we've got a 2811 chasis
|
|
0:14:35
|
there's twwo T1 cards on slot 0, sub slot 0
|
|
0:14:40
|
OK? Slot 0 is the motherboard of the actual router, that's slot 0.
|
|
0:14:48
|
Slot indicates a network module slot.
|
|
0:14:51
|
But Slot 0 is the special one reserved for the mother board itself.
|
|
0:14:56
|
Subslot 0 is going to be the WIC or VWIC slots.
|
|
0:15:03
|
OK? So if I have four WIC slots on a mother board, I've got slot 0
|
|
0:15:12
|
sub slot 0, that's the first VWIC
|
|
0:15:19
|
and then subslot 1, subslot 2, and subslot 3,
|
|
0:15:24
|
say that four times fast
|
|
0:15:26
|
subslot 3 for a total of four subslots or WIC
|
|
0:15:31
|
slots counting canonically from 0.
|
|
0:15:35
|
OK? Then on top of that, I've got the sub port
|
|
0:15:41
|
within the slot/subslo/port, so if I have a two port
|
|
0:15:48
|
MFT or Multiflex Trunk T1,
|
|
0:15:51
|
then I basically got 0/0/ first one is 0
|
|
0:15:56
|
and then 0/0/ the second one would be one.
|
|
0:16:01
|
OK, so that's how we count. So then
|
|
0:16:03
|
I've got a four port, fast ethernet
|
|
0:16:06
|
switch on the slot 0, so the motherboard Subslot 1,
|
|
0:16:11
|
and there's four ports, so I'm going to have
|
|
0:16:15
|
if I just bring a notepad up here real quick,
|
|
0:16:23
|
crank the size of it up, I'm going to have
|
|
0:16:27
|
numbering 0/0/, what do we say for the T1 00011
|
|
0:16:36
|
OK, that's going to be multiflex trunk T1 number 1.
|
|
0:16:42
|
Then I'm gonna have
|
|
0:16:47
|
flash 1 for T1 number 2.
|
|
0:16:51
|
Then I'm gonna have 0/,
|
|
0:16:54
|
OK I've got my four port ethernet switch module subslot 0, subslot 1
|
|
0:17:00
|
so I've got 0/1/ and then I've got four ports,
|
|
0:17:04
|
so I've got 012
|
|
0:17:10
|
and 3 couting canonically for my four port
|
|
0:17:15
|
just call it ethernet switch module and then port number 1
|
|
0:17:23
|
port number 2, port number 3
|
|
0:17:30
|
and port number 4. OK, so that's the way we count.
|
|
0:17:35
|
And then just since we're here, I note that I have a daughtercard
|
|
0:17:38
|
for that WIC, VWIC or HWIC.
|
|
0:17:41
|
That's a four port ethernet switch module, power daughtercard.
|
|
0:17:47
|
And then I've also got some PVDMs. I've got a PVDM
|
|
0:17:51
|
version 2 with 32 channels on slot 0, so that's on the motherboard,
|
|
0:17:56
|
subslot 4, now wait a minute, I thought we said we only had
|
|
0:18:00
|
012 and 3, for a total of four slots.
|
|
0:18:06
|
Well that's true, so this would be, slot 4 is counting canonically slot
|
|
0:18:10
|
subslot 5, right? And that's labeled 4
|
|
0:18:14
|
and that's internal to the motherboard itself,
|
|
0:18:17
|
it's not an actual configurable external
|
|
0:18:21
|
slot for VWAN because it's a PVDM, so it makes sense.
|
|
0:18:29
|
So we've got two of these ethernet switch port,
|
|
0:18:33
|
ports that are down. Now we also have our main fast ethernet
|
|
0:18:37
|
0 and 1, however keep in mind if our phones are directly connected to
|
|
0:18:42
|
one of these ethernet switch module ports,
|
|
0:18:45
|
which we'll no shut them and find out,
|
|
0:18:47
|
a safe thing to do would be just to no shut everything, turn up everything.
|
|
0:18:51
|
But if they are connected to one of these ethernet switch
|
|
0:18:53
|
ports then we're going to have interface VLAN 11 and
|
|
0:18:57
|
12 so our SVI or Switch Virtual Interface,
|
|
0:19:02
|
that will be providing the layer 3 so,
|
|
0:19:05
|
in other words we won't need to turn up fas0,
|
|
0:19:08
|
0 and FE 01.
|
|
0:19:12
|
So let's go ahead and config T and jump to fas0/
|
|
0:19:18
|
What was it? 01 I believe, 0/1/0
|
|
0:19:23
|
a little keyword of interface might be nice to begin with.
|
|
0:19:27
|
And we'll no shut, in fact what we can do,
|
|
0:19:30
|
is just interface range fas0/1/0
|
|
0:19:38
|
to 1 and say no shut.
|
|
0:19:42
|
So we can no shut both of those or all
|
|
0:19:44
|
four of them at the same time if we wanted.
|
|
0:19:48
|
And now I am tel net in the router,
|
|
0:19:49
|
and I also have term mon turned on already.
|
|
0:19:53
|
In the real lab, you'll have the ability to either terminal
|
|
0:19:56
|
to tell net in or you can in through the
|
|
0:20:00
|
console port as you could of course
|
|
0:20:02
|
do here with our racks if you rented them.
|
|
0:20:05
|
I think it's fine to go in through the console initially, but when
|
|
0:20:07
|
once you have network connectivity up,
|
|
0:20:09
|
and if you're dealing with anything that's take down
|
|
0:20:11
|
that network activity, you'll obviously need console access
|
|
0:20:14
|
but otherwise, I would tel net in
|
|
0:20:16
|
especially for the rate of inputting characters
|
|
0:20:20
|
copying pasting, especially debugging, things of that nature.
|
|
0:20:26
|
So we brought this up and I gave it a little bit of time for CDP,
|
|
0:20:30
|
to broadcast and show CDP neighbor, in fact does show a phone
|
|
0:20:35
|
on fas01/0 and show IP interface brief,
|
|
0:20:40
|
I'll issue this, just to make sure that all of those ports are
|
|
0:20:46
|
administratively up and they are and only one has the protocol of up
|
|
0:20:50
|
and that was where we found the phone.
|
|
0:20:52
|
So we will go into configT,
|
|
0:20:55
|
jump into that port, F0/1/0, the first port.
|
|
0:21:00
|
And we will use our configuration.
|
|
0:21:04
|
Now again, we weren't instructed, for Branch1 whether to use
|
|
0:21:12
|
trunk method or whether to use access method.
|
|
0:21:15
|
So I'd love a little participation if you guys want to turn on your mics,
|
|
0:21:21
|
What should we use here on the ethernet switch module?
|
|
0:21:25
|
Well we can use the trunk method certainly
|
|
0:21:28
|
but we can also use the access method.
|
|
0:21:32
|
So in previous versions of IOS, with ethernet switch modules,
|
|
0:21:37
|
you did have to use the trunk method.
|
|
0:21:40
|
However at this point, let's do a do show version,
|
|
0:21:46
|
and we're running 12422 and then just T5 and the lab,
|
|
0:21:54
|
the lab says it's using 12 4T
|
|
0:21:58
|
train and they can really use any subtrain or subversion,
|
|
0:22:04
|
to 124 mainline as long as it's the T train.
|
|
0:22:09
|
We're using 22 the reason that we picked that 12420T
|
|
0:22:17
|
is the first version where CUCME switches over to
|
|
0:22:22
|
to 7.0 so the CCI voice lab has to be using at least 12420T
|
|
0:22:29
|
to be able to test what they say they are testing which is
|
|
0:22:33
|
CUCME or CME version 7.0
|
|
0:22:37
|
and then 12422 is where it gets into CME 7.0.1
|
|
0:22:42
|
which is in version parody with the other servers that are on the exam.
|
|
0:22:48
|
So 12420 or 12422 are a safe bet and both use support
|
|
0:22:57
|
both use support access port method for ethernet switch module.
|
|
0:23:00
|
So we'll just go ahead and use switch port mode access
|
|
0:23:05
|
switch port access VLAN 11,
|
|
0:23:09
|
now we forgot to check to see if that was created.
|
|
0:23:11
|
So we'll go back and make sure that it is created.
|
|
0:23:17
|
Switch port voice, you know what, I said access
|
|
0:23:21
|
VLAN 11, but I believe access VLAN should be 12,
|
|
0:23:24
|
the date of VLAN and then switchport voice VLAN 11.
|
|
0:23:31
|
The lab may have told you that they have already created them,
|
|
0:23:34
|
but it's very possible,
|
|
0:23:36
|
maybe even probable, but they would not tell you.
|
|
0:23:39
|
That they would just leave it to you to either,
|
|
0:23:42
|
create them, forget to create them,
|
|
0:23:45
|
you know they're certainly not going to tell you everytihng,
|
|
0:23:48
|
especially if a task is an implicit one,
|
|
0:23:50
|
in other words something they want you to do or,
|
|
0:23:53
|
more specifically something that you have to do,
|
|
0:23:55
|
in order to make the entire scenario work.
|
|
0:24:00
|
OK, so they will not necessarily walk you
|
|
0:24:02
|
through everything you need to do,
|
|
0:24:05
|
they're job, the CCI voice lab proctors and task job is not to
|
|
0:24:10
|
instruct you to what to configure but,
|
|
0:24:13
|
more to get something to work in the way that they want it to work,
|
|
0:24:18
|
and then you will very likely have implicit tasks.
|
|
0:24:27
|
OK? So do show run, actually I'll do show run interface,
|
|
0:24:33
|
fas0/1/0
|
|
0:24:38
|
and then also 1.
|
|
0:24:42
|
So far we've only configured switch port access,
|
|
0:24:45
|
and switch port voice VLANs and switch port mode access
|
|
0:24:49
|
which is implicit already
|
|
0:24:56
|
on the ethernet switch module ports, so we still need to add span 3
|
|
0:25:00
|
port fast.
|
|
0:25:03
|
And it just tells us that,
|
|
0:25:07
|
it's been configured, you shouldn't do it if,
|
|
0:25:10
|
blah blah, basically if you could possibly have a layer to loop
|
|
0:25:13
|
and then it will have no effect if it's, or it will only have an effect
|
|
0:25:16
|
as a non trunking code. Now we already stated that this
|
|
0:25:19
|
is in a pseudotrunk.
|
|
0:25:22
|
The access port, it's actually going to allow .1q header
|
|
0:25:25
|
with exactly and only VLAN ID equaling whatever this
|
|
0:25:30
|
VLAN ID happens to be
|
|
0:25:32
|
which it's called the Voice VLAN, sorry about that scroll.
|
|
0:25:35
|
Even though if not actually necessary that it's for voice,
|
|
0:25:40
|
but we will be using it of course for voice.
|
|
0:25:42
|
So I'll go ahead and end, show run interface fas010.
|
|
0:25:50
|
Alright.
|
|
0:25:52
|
Here's my configuration, let's do a show trunk.
|
|
0:25:58
|
Not show trunk, that CAT OS, CAT OS demands, show interface
|
|
0:26:05
|
S010 and then trunking.
|
|
0:26:09
|
And we'll see that the status shows not trunking.
|
|
0:26:13
|
OK, the VLAN's allowed on the trunk or 11 and 12 if
|
|
0:26:17
|
it were a trunk, but it's currently not trunking.
|
|
0:26:19
|
And if it were, it would be encapsulation 802.1q
|
|
0:26:23
|
but it's not trunking right? Well we know that is sort of has to be.
|
|
0:26:28
|
And we'll verify that if we hand out IP address
|
|
0:26:31
|
and we can web into
|
|
0:26:34
|
bring up a web interface into the phone and actually see the
|
|
0:26:40
|
the phone's VLAN that it's a part of.
|
|
0:26:42
|
OK, so we'll go ahead and write that configuraiton
|
|
0:26:45
|
and we'll go back to our tasks.
|
|
0:26:47
|
If anyone has any questions, please go ahead and stop me at any point.
|
|
0:26:57
|
Or NTP, we were told to configure the Corporate Headquarter
|
|
0:27:01
|
and Branch1 routers to synchronize their time
|
|
0:27:04
|
to the PSTN NTP master clock,
|
|
0:27:07
|
and we don't have an IP address for the PSTN here, however
|
|
0:27:11
|
we can look at our topology and we do see that the topology,
|
|
0:27:17
|
did in fact specify an IP address.
|
|
0:27:23
|
OK? So sometimes information
|
|
0:27:27
|
in the real lab will be given to you in different places.
|
|
0:27:31
|
Not necessarily at once or all in the same place.
|
|
0:27:36
|
The corporate headquarter router should use specific
|
|
0:27:38
|
timezone and should follow daylight savings.
|
|
0:27:41
|
The Branch1 router should use central timezone, GMT -6
|
|
0:27:45
|
and should follow daylight savings.
|
|
0:27:48
|
And then configure the CUCM server to synchronize it's time
|
|
0:27:52
|
to the Corporate Headquarter router.
|
|
0:27:54
|
So Corporate Headquarter and Branch1 routers
|
|
0:27:56
|
are to synchronize with the PSTN
|
|
0:27:59
|
but the CUCM server is to synchronize with Corporate Headquarter router.
|
|
0:28:04
|
So what does this mean?
|
|
0:28:06
|
This means that the corporate headquarter router is going to need
|
|
0:28:08
|
to be configured in client mode with the task
|
|
0:28:11
|
or the command and argument server, NTP server
|
|
0:28:15
|
and that it's also going to need to be an NTP master
|
|
0:28:17
|
to be able to hand out time.
|
|
0:28:20
|
Branch1 router will only need to be a client, so NTP server command.
|
|
0:28:28
|
OK, so know what we need to do, so let's go
|
|
0:28:30
|
ahead and go over and do it.
|
|
0:28:33
|
So we'll start at router 1,
|
|
0:28:37
|
Corporate Headquarter router, and we'll go into configuration T,
|
|
0:28:43
|
We we're told to set up NTP, let's just look back.
|
|
0:28:47
|
So the PSTN, NTP master clock, we have to assume that the PSTN
|
|
0:28:52
|
router is already set up.
|
|
0:28:54
|
So we'll look at the IP address and here we see that it
|
|
0:28:57
|
it's looped back, is 177.1.254.254/32.
|
|
0:29:05
|
So we will go ahead and make sure that we can ping that address.
|
|
0:29:17
|
And we can ping it.
|
|
0:29:20
|
OK, so David had a great question, which is, actually let me
|
|
0:29:23
|
get to Christopher's question first. In the real lab, do they give you
|
|
0:29:25
|
a printed lab guide or is it a PDF
|
|
0:29:27
|
that you constantly have to switch back and forth?
|
|
0:29:30
|
Currently, the voice lab is still in printed
|
|
0:29:35
|
three ring binder format.
|
|
0:29:37
|
The route switch lab has moved over to a PDF,
|
|
0:29:40
|
that you have to keep switching back and forth
|
|
0:29:41
|
to and you don't have a second monitor.
|
|
0:29:44
|
I don't know, certainly some things have changed in the CCIE lab,
|
|
0:29:49
|
and they always change with routing and switching track first,
|
|
0:29:52
|
and some thing's have changed and have not gone over well.
|
|
0:29:55
|
For instance, the open ended question or
|
|
0:29:57
|
for knowledge section for route switch and voice that got terminated.
|
|
0:30:01
|
Those aren't on the exam anymore, if anyone isn't familiar with that.
|
|
0:30:06
|
It was a few weeks back that those got taken off.
|
|
0:30:09
|
However, so certain things have changed
|
|
0:30:11
|
and they've gotten enough feedback to realize it wasn't a good idea.
|
|
0:30:15
|
The printed version of the lab, I think it's very useful
|
|
0:30:20
|
but they also have issues with sometimes
|
|
0:30:24
|
you know sheets of paper walking away from the lab, on other words
|
|
0:30:27
|
aka people tking them to try to cheat.
|
|
0:30:31
|
So they're trying to do things to curve that cheating
|
|
0:30:33
|
which everyone can certainly appreciate,
|
|
0:30:35
|
but restricting the access to a PDZ to where you
|
|
0:30:39
|
can't actaully look at it and your tasks.
|
|
0:30:43
|
You tasks and configuration at the same time can
|
|
0:30:46
|
be cumbersome and frustrating, I understand.
|
|
0:30:49
|
So currently the voice is still in
|
|
0:30:55
|
in printed form, how long it will stay that way,
|
|
0:30:57
|
I guess to answer the question, I'm not exactly sure.
|
|
0:31:00
|
I do hope that they keep it as a printed guide as well.
|
|
0:31:09
|
OK and then someone else asked, David asked, what's
|
|
0:31:11
|
stratum would you configure the corporate headquarter seeing that
|
|
0:31:14
|
it's pulling and sending NTP?
|
|
0:31:16
|
That's a perfect question, so first of all
|
|
0:31:18
|
before we know or can even possibly know what
|
|
0:31:22
|
we want to, what stratum to configure or
|
|
0:31:25
|
we need to configure to pull, and then we can,
|
|
0:31:31
|
just scrolling on the questions here, then we can decide what stratum
|
|
0:31:35
|
we're receiving from the PSTN
|
|
0:31:38
|
master clock and that's going to
|
|
0:31:41
|
play a very relevant role in what stratum we use
|
|
0:31:43
|
to serve ourself for NTP master, so good question.
|
|
0:31:47
|
So first well config T, we'll say NTP server.
|
|
0:31:53
|
And we'll point it to 177.1.254.254.
|
|
0:32:01
|
OK? We could use a source interface,
|
|
0:32:04
|
we could do something like NTP source
|
|
0:32:07
|
interface for loop back 0, if we have that which of course
|
|
0:32:12
|
IP Interafce, to shop IP interface brief.
|
|
0:32:16
|
Of course we should have a loopback 0 and if we don't
|
|
0:32:19
|
not a bad idea to configure one, we do.
|
|
0:32:21
|
So I'll go ahead and configure that.
|
|
0:32:24
|
So let's do, do show run | 2 include NTP.
|
|
0:32:32
|
And so now we can jump out and just say show NTP associations.
|
|
0:32:41
|
and then the other show command a status.
|
|
0:32:45
|
We can also debug NTP events.
|
|
0:32:49
|
So watch as NTP tries to synchronize,
|
|
0:32:53
|
we'll look at associations again, so what we see here,
|
|
0:32:56
|
is the address that we configured and we see until the
|
|
0:33:02
|
which says that it's been configured for the legend,
|
|
0:33:06
|
and we see a reference clock
|
|
0:33:09
|
which is better than no reference clock
|
|
0:33:11
|
and we see a stratum, we see a stratum of 10.
|
|
0:33:16
|
So what we know is we've already gotten some information from
|
|
0:33:19
|
and the debug NTP doesn't really provide very much
|
|
0:33:25
|
useful information, so it's almost.
|
|
0:33:29
|
See there's debug NTP packets would probably be your all
|
|
0:33:33
|
would probably be a better one but,
|
|
0:33:35
|
we're not seeing a lot of information come across
|
|
0:33:37
|
us and I do have ter mon turned on.
|
|
0:33:41
|
To verify if you have ter mon, you can do show logging.
|
|
0:33:44
|
See that monitor logging is at the level of debugging,
|
|
0:33:48
|
but it's enabled to begin with, it's at the level of debugging
|
|
0:33:51
|
and we're logging it out to VTY 514.
|
|
0:33:54
|
And we can do a show line and we can see that we are VTY 514
|
|
0:34:00
|
with a little asterisk indicating that that's us.
|
|
0:34:03
|
So we can see that we have logging turned on.
|
|
0:34:06
|
When you look back up,
|
|
0:34:09
|
to the configurations, so our show NTP associations shows
|
|
0:34:12
|
that it's configured, we pulled information or else
|
|
0:34:14
|
we wouldn't know that there is stratum 10.
|
|
0:34:16
|
However, we're not quite at
|
|
0:34:19
|
a system peer level, or a synchronized level.
|
|
0:34:22
|
But when we are, we'll see a little asterisk.
|
|
0:34:26
|
Here we go, now we sent a message,
|
|
0:34:30
|
and we received one, hopefully
|
|
0:34:35
|
we are synchronized now, show NTP association,
|
|
0:34:38
|
we're still not synchronized, but we're on our way to synchronizing.
|
|
0:34:42
|
So let's do a show clock,
|
|
0:34:44
|
and see what time we are, let's go ahead and set our
|
|
0:34:49
|
maybe because we haven't set our timezone,
|
|
0:34:51
|
what was our timezone supposed to be?
|
|
0:34:55
|
Timezone for corporate headquarter should be
|
|
0:34:57
|
Pacific Time zone which is GMT -8.
|
|
0:35:01
|
So wait for the screen to syncup here and let's do
|
|
0:35:06
|
clock timezone.
|
|
0:35:09
|
And we'll just give it a name, PST for instance
|
|
0:35:12
|
and then once it offsets from UTZ or offset from GMT, so -8.
|
|
0:35:19
|
There we go, before I ever hit enter,
|
|
0:35:23
|
OK so I haven't entered yet, now
|
|
0:35:25
|
now I see NTP core synchronized to 177.1.254.254
|
|
0:35:31
|
stratum 10. OK?
|
|
0:35:33
|
So just to verify, do show run | 2 section
|
|
0:35:37
|
or include for clock. I have not entered that command yet,
|
|
0:35:41
|
I never hit enter.
|
|
0:35:42
|
There's network clock participate, but that's it.
|
|
0:35:46
|
And then do show run I 2 include NTP
|
|
0:35:50
|
got that configured, do show NTP status.
|
|
0:35:54
|
Or association, I like that one better, it doesn't show associated yet.
|
|
0:35:58
|
Status still does show unsynchronized.
|
|
0:36:04
|
Well it did show synchronize here, let's go ahead and put in the
|
|
0:36:07
|
clock timezone.
|
|
0:36:12
|
PST and then -8 and then clock, time zone.
|
|
0:36:18
|
And we'll do, not clock time zone, but clock summer time
|
|
0:36:25
|
and give it a name, PDT for Pacific Daylight Time
|
|
0:36:29
|
and then reoccurring, or we can configure
|
|
0:36:31
|
an absolute date for it to occur on.
|
|
0:36:33
|
The reason we did that is because we were told
|
|
0:36:36
|
to configure it
|
|
0:36:39
|
and should follow daylight savings time.
|
|
0:36:41
|
So we were given that add on
|
|
0:36:44
|
OK? So let's jump out, show run I 2 include NTP or
|
|
0:36:51
|
bulean or | or clock.
|
|
0:36:55
|
If I can spell it right here we go and show NTP status or association.
|
|
0:37:03
|
Still now synchronized. OK, this could take a while.
|
|
0:37:08
|
We got another message, but it's still not synchronized,
|
|
0:37:12
|
we're gonna go ahead and write this configuration,
|
|
0:37:14
|
and we'll come back to it,
|
|
0:37:16
|
because I can tell you that it might take a while.
|
|
0:37:19
|
Let's do a show clock,
|
|
0:37:22
|
it says that its 5:18 Pacific Daylight Time
|
|
0:37:26
|
Monday. Let's just go ahead, you wouldn't be able to look at the
|
|
0:37:29
|
PSTN in the real lab so
|
|
0:37:32
|
We won't look at it here for that purpose, but we will
|
|
0:37:35
|
come back to this router.
|
|
0:37:39
|
OK, so let's go over to router 2 which is Branch 1.
|
|
0:37:46
|
Right, the asterisk said to make it faster, I need to
|
|
0:37:49
|
configure the time manually and that's what I was getting ready to
|
|
0:37:52
|
talk about as we could look at the PSTN, see what time it's set to
|
|
0:37:55
|
and then configure our headquarter router
|
|
0:37:58
|
to be very close to it, the thing is
|
|
0:38:01
|
you won't have access to the PSTN router if this is in a
|
|
0:38:04
|
in the real CCUIE voice lab so
|
|
0:38:07
|
it's probably best that we just leave it be for right now.
|
|
0:38:12
|
If it doesn't synchronize by
|
|
0:38:14
|
closer to the end of our session, then we certainly will manually.
|
|
0:38:18
|
Tell the clock on router 1 to be closer to what the PSTN is.
|
|
0:38:27
|
I like show NTP association, it's the quickest, I can just sit there
|
|
0:38:30
|
and real quickly look for that little asterisk.
|
|
0:38:34
|
OK? So over on router 2, we can do config T,
|
|
0:38:41
|
and NTP server, 177.1.254.254
|
|
0:38:48
|
NTP source,
|
|
0:38:51
|
just where it's gonna source it's request from, move back 0
|
|
0:38:56
|
and then go ahead and say clock, timezone.
|
|
0:39:00
|
We were told to do Central Time, I believe.
|
|
0:39:04
|
Central Time, and we are given the instructions
|
|
0:39:07
|
GMT -6 and to use daylight saving.
|
|
0:39:11
|
So we'll say clock timezone,
|
|
0:39:15
|
give it a name, CST which doesn't really mean much.
|
|
0:39:18
|
It's just a tag and then -6.
|
|
0:39:22
|
And then clock summer time,
|
|
0:39:26
|
CDT for Central Daylight Time reoccuring.
|
|
0:39:32
|
And we've gone ahead and show run | 2 include NTP,
|
|
0:39:37
|
or clock,
|
|
0:39:38
|
we've configured this bit here on Branch 1, Router 2.
|
|
0:39:46
|
So now we just need to wait for that to sync up show
|
|
0:39:48
|
NTP association. We can see that it's configured
|
|
0:39:53
|
We have a reference clock, we see it stratum 10, we're getting information,
|
|
0:39:57
|
but it's not quite fully synchronized. Do a show clock here,
|
|
0:40:01
|
and it's 7:25 CDT, so it's
|
|
0:40:07
|
probably closer, but you can go ahead and safely do.
|
|
0:40:11
|
Here we go, here we got core notice,
|
|
0:40:14
|
not just core info, the clock is synchronized.
|
|
0:40:17
|
There we go, show NTP association Corporate Headquarter.
|
|
0:40:20
|
Now we see 177.1.254.254 is a system peer we are synchronized.
|
|
0:40:27
|
And show NTP status,
|
|
0:40:31
|
Also shows a synchronized, we synchronized stratum 11, so we think
|
|
0:40:37
|
that it's at stratum 11. Sorry for the
|
|
0:40:41
|
accidental scroll. It hasn't a stratum of 10
|
|
0:40:47
|
but we see it as 11 because we're one hop from it.
|
|
0:40:51
|
OK? So this is where, who was it that brought up the question about,
|
|
0:40:57
|
let's scroll back and see.
|
|
0:41:00
|
David, what stratum would I configure the Corporate Headquarter as using
|
|
0:41:05
|
because it also needs to serve NTP,
|
|
0:41:08
|
we can go ahead and configure that now it's synchronized.
|
|
0:41:11
|
Well if it thinks that it's stratum 11,
|
|
0:41:15
|
Corporate Headquarter that is, thinks that the PSTN
|
|
0:41:18
|
as far as it's referential point of what view is
|
|
0:41:21
|
stratum 11, then it has to be, we have to essentially be
|
|
0:41:25
|
higher than that, or else, so a lower preferential stratum.
|
|
0:41:32
|
Or a less preferential stratum would be a better way to say it,
|
|
0:41:35
|
but a higher numerical value.
|
|
0:41:38
|
But go ahead and undebug all here in order to
|
|
0:41:42
|
serve time out to other people as NTP master.
|
|
0:41:46
|
And yet not take over as a more preferential time clock because,
|
|
0:41:50
|
watch this, if I do configT, we do show NTP association.
|
|
0:41:56
|
only see one clock there, right? The one we've configured.
|
|
0:42:01
|
But now let's set up NTP master and let's just say I
|
|
0:42:04
|
just enter NTP master, enter, that's it.
|
|
0:42:08
|
Now I do show NTP association and what do I have?
|
|
0:42:12
|
I've got 127 which 127.0.0.0/8
|
|
0:42:18
|
is the entire /8 network is reserved for loop back addresses.
|
|
0:42:25
|
So 127.127.1.1 is what the router uses
|
|
0:42:29
|
basically to make sure that you don't ever create a loopback
|
|
0:42:31
|
or something like that on that, at that high of a network
|
|
0:42:36
|
IP address, but 127.127.1.1 is it's own internal.
|
|
0:42:40
|
Referential clock is local and stratum 7.
|
|
0:42:44
|
Watch this, if I keep doing show NTP association or show NTP
|
|
0:42:49
|
show NTP association or show NTP status
|
|
0:42:53
|
I will eventually synchronize with myself,
|
|
0:42:57
|
because I am a lower stratum and therefore a better
|
|
0:43:01
|
trusted time source. It will take a little bit,
|
|
0:43:04
|
but I will synchronize with myself.
|
|
0:43:07
|
OK?
|
|
0:43:08
|
So I'd rather not do that but you know actually that
|
|
0:43:12
|
won't really hurt, I'll just go ahead and leave it there for right now
|
|
0:43:16
|
and you'll see that eventually I will synchronize
|
|
0:43:18
|
with myself because I'm a better stratum.
|
|
0:43:21
|
What we'll need to do once we see that we synchronize
|
|
0:43:23
|
with ourselves is we'll need to actually change it to
|
|
0:43:28
|
a higher value than 11.
|
|
0:43:35
|
OK? We'll just leave it there and we'll come back.
|
|
0:43:38
|
Back on Branch 1, Router 2.
|
|
0:43:42
|
Let's show NTP association, we're still not synchronized
|
|
0:43:45
|
with the PSTN yet, that's OK.
|
|
0:43:49
|
OK, before we move on to the CUCM server
|
|
0:43:52
|
and then later come back and change router 1 not to synchronize with itself,
|
|
0:43:56
|
once it actually does synchronize with itself.
|
|
0:44:00
|
But let's switch over to the CUCM router, to the CUCMck
|
|
0:44:07
|
web based user interface.
|
|
0:44:13
|
And we'll go ahead and log-in. Username is admin, password is cciecisco.
|
|
0:44:20
|
And actually, where we want to be is in the
|
|
0:44:26
|
OS administration, so we'll switch to Cisco Unified OS Administration and log back in.
|
|
0:44:36
|
And we will go to,
|
|
0:44:39
|
there it is, settings NTP servers.
|
|
0:44:48
|
And we see that we have 0 configured, so we were instructed to
|
|
0:44:53
|
synchronize this with the headquarter router,
|
|
0:44:57
|
and we sourced all of our traffic for NTP from the loopback.
|
|
0:45:02
|
So we'd probably be good to find out,
|
|
0:45:06
|
what is the loopback interface IP, so let's do show IP interface brief,
|
|
0:45:12
|
| 2 include loopback.
|
|
0:45:17
|
And we see that it's 177.1.254.1, so I'm just gonna go ahead and copy that.
|
|
0:45:25
|
OK? So I'll add in new server and I'll paste in what I had,
|
|
0:45:30
|
177.1.254, the loopback of router 1.
|
|
0:45:40
|
And so here we see it configured,
|
|
0:45:43
|
and we see the NTP service is not accessible.
|
|
0:45:48
|
That's about all we're gonna see whether not accessible or accessible,
|
|
0:45:54
|
from the web user interface, so we will SSH into the box
|
|
0:45:58
|
in a little bit. Let's go back to router 1,
|
|
0:46:02
|
and let's do show NTP association. We're still synchronized with the
|
|
0:46:07
|
PSTN. I'm gonna go ahead because this is probably gonna take a while.
|
|
0:46:13
|
I'm already configT, I'm gonna go ahead and say NTP master,
|
|
0:46:17
|
and put in a higher stratum value, let's say 12
|
|
0:46:21
|
then 10 or we thought as 11.
|
|
0:46:26
|
That way we just don't have to wait for this to
|
|
0:46:29
|
sit here and synchronize to ourself and then back all day.
|
|
0:46:34
|
So show NTP association, now I see
|
|
0:46:39
|
that if we are master 12, we look ourself as 11
|
|
0:46:45
|
so now we think, wait a minute, if 127.127.1.1
|
|
0:46:50
|
ourselves, our stratum 11 or at least kind of appears that way,
|
|
0:46:55
|
and show NTP status,
|
|
0:47:00
|
shows that the clock is currently synchronized to the PSTN at stratum 11,
|
|
0:47:05
|
a little bit, the possibility of getting into a
|
|
0:47:10
|
conflict here is there, so why don't we just change ourselves to 13.
|
|
0:47:16
|
So we'll change oursleves to 13, show NTP association.
|
|
0:47:21
|
Now it's 12, is the way we view our own self
|
|
0:47:26
|
referentially, so now we have no possibility of conflict and we will remain
|
|
0:47:33
|
synchronized with the PSTN loopback interface, the PSTN
|
|
0:47:38
|
master clock router. OK we'll go ahead write and save this configuration.
|
|
0:47:46
|
OK, so now let's open a session to
|
|
0:47:53
|
the CUCM publisher and SSH session, we can tel net
|
|
0:47:58
|
and in the real lab,
|
|
0:48:02
|
Iyaser asked a question, why do we need to use the
|
|
0:48:05
|
master key to make things work?
|
|
0:48:08
|
Or why do we use, need to use the master keyword
|
|
0:48:11
|
in order to make things work in the router 1?
|
|
0:48:13
|
Well because, If I do a show run | 2 section NTP,
|
|
0:48:18
|
if all I have configured is server, then I'm only a client.
|
|
0:48:24
|
I'm a client only.
|
|
0:48:27
|
The lab instructions told us to configure the CUCM server to synchronize
|
|
0:48:33
|
it's time or pull it's time from the Corporate Headquarter router.
|
|
0:48:38
|
So the problem is, back on the Corporate Headquarter router,
|
|
0:48:42
|
hopefully the screen refreshes or working for everyone.
|
|
0:48:47
|
You know what here, let me do this. We might be also be able to
|
|
0:48:53
|
optimize the screen sharing for better
|
|
0:49:01
|
faster images switching back and forth
|
|
0:49:05
|
OK, so if we have to enable or provision the CUCM
|
|
0:49:10
|
server to pull it's time from the headquarter router, it can't be in client
|
|
0:49:14
|
only mode, it has to also be in a serving mode.
|
|
0:49:17
|
So it needs to be a master, the master serves.
|
|
0:49:22
|
OK, so hopefully it ends with that question.
|
|
0:49:25
|
OK?
|
|
0:49:30
|
So and I began to say that in the real exam,
|
|
0:49:34
|
you will, you'll have an icon on your desktop for every
|
|
0:49:40
|
device that you need to, all the routers and switches.
|
|
0:49:44
|
And then in terms of your CUCM server,
|
|
0:49:48
|
or any servers that you need to connect to their command line,
|
|
0:49:52
|
you can only SSH and the way that you would actually do that,
|
|
0:49:56
|
your candidate desktop doesn't have IP connectivity into your lab,
|
|
0:50:01
|
it only has console access
|
|
0:50:05
|
to your lab environment and it's also got a web browser that can
|
|
0:50:09
|
view the real Cisco documentation website.
|
|
0:50:12
|
The real life website, but you don't have IP connectivity to your lab.
|
|
0:50:16
|
So instead, there's actaully a Windows XP
|
|
0:50:21
|
work station that is attached to you lab
|
|
0:50:25
|
attached to your rack via IP.
|
|
0:50:28
|
And you will RDP or Remote Desktop Protocol into that XP workstation,
|
|
0:50:34
|
and then from there you can do things like run Cisco Unified
|
|
0:50:38
|
personal communicator, the CUPC client
|
|
0:50:42
|
or SSH into any of your
|
|
0:50:46
|
COS servers, your call manager publisher,
|
|
0:50:50
|
Call Manager Subscriber, your Unity Connection Server, things of those natures.
|
|
0:50:55
|
OK?
|
|
0:50:57
|
Run the CAD desktop if you need to for UCCX, things like that.
|
|
0:51:02
|
OK? We have the same thing in our rack, we have a XP machine
|
|
0:51:06
|
that is connected directly, a virtual machine that you'll
|
|
0:51:09
|
RDP into, if you need to do anything like that.
|
|
0:51:14
|
OK? So admin from here, SSH of the publisher
|
|
0:51:18
|
CUCM server will do utils,
|
|
0:51:21
|
NTP and by the way inside, we're not going into the
|
|
0:51:26
|
too much of it, but that's actually covered on another day this week, but
|
|
0:51:30
|
inside the unified OS command line, you can use the
|
|
0:51:35
|
tab for command completions, like I did
|
|
0:51:37
|
UTI and then said tab to complete utils.
|
|
0:51:41
|
I can do question mark, that will either bring up contact sensitive help
|
|
0:51:47
|
or if I'm halfway done with the word, it will complete the word, like nt?
|
|
0:51:51
|
will complete ntp. What I cannot do,
|
|
0:51:55
|
is truncate word, so UTI does not have any ambiguity.
|
|
0:51:59
|
There is no other words or commands that could match.
|
|
0:52:03
|
But I cannot say UTI NTP status or ST.
|
|
0:52:08
|
I do actually do have to say utils NTP status.
|
|
0:52:17
|
Now I guess you could say, well that was because
|
|
0:52:19
|
that last one was ambiguous.
|
|
0:52:21
|
Well there's one that's not ambiguous, but it still didn't let me.
|
|
0:52:24
|
So once I issued the full command, not it will say
|
|
0:52:28
|
hey look at this, we are synchronized to 177.1.254.1
|
|
0:52:34
|
OK? Synchronized to the server at stratum 12
|
|
0:52:39
|
time is correct within 46 milliseconds of variation and deviation.
|
|
0:52:44
|
And I know what time it is, UTC and current time America
|
|
0:52:50
|
Los Angeles which means that this box must be configured currently
|
|
0:52:54
|
for Pacific time.
|
|
0:52:58
|
Pacific Daylight Time.
|
|
0:53:01
|
OK? So if I go back to the web broswer for CUCM,
|
|
0:53:05
|
and let's say I'll just
|
|
0:53:07
|
Click on NGP server again, refresh this page
|
|
0:53:11
|
now it says the NTP service is accessible.
|
|
0:53:13
|
So that's your visual indication, but it doesn't
|
|
0:53:18
|
OK? So if I go back to R1, of course I should still be synchronized
|
|
0:53:24
|
to the PSTN and I am, and R2 which is the
|
|
0:53:28
|
Branch1 router should probably by now and yes it is
|
|
0:53:32
|
actually be synchronized.
|
|
0:53:35
|
OK? So there was our NTP section,
|
|
0:53:39
|
does anyone have any questions on that before we move on to the next task?
|
|
0:53:47
|
OK? So looking at DHCP at Corporate Headquarters
|
|
0:53:52
|
and then we'll look at it at Branch1 and 2.
|
|
0:53:55
|
We're told to provision the headquarter corporate switch,
|
|
0:53:59
|
pay attention to wording, to distribute IP addressing and options via DHCP
|
|
0:54:05
|
to any IP phones to the corporate site,
|
|
0:54:06
|
as well as any PCs connected to these phones.
|
|
0:54:11
|
The subnet for the phones were given as 177.1.11.0,
|
|
0:54:14
|
if we weren't given it here, it is in our topolgy
|
|
0:54:18
|
and for the PCs is 177.1.12.0/24.
|
|
0:54:23
|
We're told to prevent the IP address ranges of
|
|
0:54:27
|
177.1.11.1229
|
|
0:54:32
|
and then also in the last octet, 129 through 147
|
|
0:54:36
|
from being distributed, so we have an exclusion range.
|
|
0:54:40
|
Phones should receive an option for TFTP server
|
|
0:54:44
|
in an IP address format, however using a DHCP option that will allow them
|
|
0:54:49
|
to later switch to DNS naming if they should so choose.
|
|
0:54:53
|
Does anyone want to connect your mic, turn mine off and
|
|
0:55:01
|
say what you think option bullet form might indicate?
|
|
0:55:14
|
Anyone at all have an idea?
|
|
0:55:16
|
Royal says, option 66, that's exactly correct.
|
|
0:55:21
|
So phone should receive a TFTP,
|
|
0:55:24
|
or an option for TFTP server in an IP addressing format
|
|
0:55:27
|
however using an option type that will later allow them to switch to
|
|
0:55:31
|
DNS naming if they should so choose, that's option 66.
|
|
0:55:36
|
IP phones, Cisco IP phones will respond
|
|
0:55:40
|
to both option 66 or option 150.
|
|
0:55:45
|
The difference being, option 66 can only be one IP address,
|
|
0:55:49
|
not multiple or an array.
|
|
0:55:52
|
And it can either be an IP address or a fully qualified domain name
|
|
0:55:56
|
or even just a host name as long as it's resolvable.
|
|
0:55:59
|
Option 150 on the other hand can only be IP addressing, not domain names
|
|
0:56:04
|
but it can have multiple IP addresses.
|
|
0:56:07
|
It can be an array and then also, watch for the wrap
|
|
0:56:11
|
on the next page. The PC should receive DNS server information,
|
|
0:56:14
|
the DNS server to be handed out is the IP address of 177.1.10.110.
|
|
0:56:21
|
OK?
|
|
0:56:22
|
So let's go over to our headquarter switch 1,
|
|
0:56:29
|
and we're told to provision it on switch 1.
|
|
0:56:31
|
So first of all, we need to look at the exclusion ranges.
|
|
0:56:36
|
We were told 177.1.11 last octet 1229,
|
|
0:56:41
|
and 129 through 47. We do not want those being handed out.
|
|
0:56:46
|
OK? we'll that's pretty straight forward.
|
|
0:56:50
|
Excluded address is 177.1.11.1
|
|
0:56:58
|
and then 29, 177.1.11.29
|
|
0:57:07
|
and then we also need another exclusion range from .129
|
|
0:57:15
|
to 177.1.11.147
|
|
0:57:21
|
OK? So those are two exclusion ranges,
|
|
0:57:23
|
watch the wording of the task, they might tell you what range
|
|
0:57:26
|
to hand out IPs in.
|
|
0:57:29
|
If they told you what ranges to hand out rather than,
|
|
0:57:32
|
which ones to exclude, you would need to make sure
|
|
0:57:35
|
that you only hand out up to the exclusio range and
|
|
0:57:40
|
or up to the IP. I should say you need to watch out
|
|
0:57:44
|
to make sure that you only exclude up to the IP,
|
|
0:57:47
|
that you should not be handing out the last one,
|
|
0:57:50
|
do not include the one you should be handing out.
|
|
0:57:54
|
So now we can create IP DHCP pool,
|
|
0:57:57
|
and we'll just call it Corporate Headquarter phones,
|
|
0:58:02
|
label it whatever you want,
|
|
0:58:05
|
and we have, now if I go ahead and begin issuing
|
|
0:58:09
|
IPs, it's possible that the IP address might get handed out before a TFTP
|
|
0:58:15
|
address gets handed out. So what I'm going to do at this
|
|
0:58:17
|
point is do show CDP neighbor,
|
|
0:58:22
|
and I'm going to jump in to interface fas02,
|
|
0:58:26
|
and shut it down. Thay way, I don't hand out an IP address
|
|
0:58:30
|
before I get the router or TFTP options configured.
|
|
0:58:35
|
OK? So IP, up a couple of times,
|
|
0:58:39
|
to get back to that pool and I'll issue network,
|
|
0:58:43
|
177.1.11.0. I could stop there, but I'm going to go ahead and
|
|
0:58:49
|
put in the subnet mask just so that I
|
|
0:58:52
|
don't have any confusion with classical boundary.
|
|
0:58:56
|
I'm going to issue a default router of 177.1.11.1
|
|
0:59:03
|
is the IP addressing if look at the topology.
|
|
0:59:07
|
And option and I can enter an option number 66,
|
|
0:59:11
|
as a code and then do I want to issue,
|
|
0:59:15
|
an IP address which is what I was instructed,
|
|
0:59:18
|
or if I was doing a host name then it would be asking text.
|
|
0:59:24
|
OK, but I'm gonna do IP in 177.1.10
|
|
0:59:29
|
.10 is the CUCM server from the topology.
|
|
0:59:37
|
OK? I was also instructed to create a pool for PCs
|
|
0:59:42
|
and that's at the range of 177.1.12.0/24
|
|
0:59:48
|
and give a DNS server, but that's for the PCs.
|
|
0:59:51
|
So I'll go ahead and create another DHCP pool,
|
|
0:59:54
|
and I'll just set up and play PCs.
|
|
0:59:59
|
Reusing commands like the up command or copy or paste whenever possible,
|
|
1:00:04
|
is a great idea.
|
|
1:00:07
|
Default router is 12.1, I've already checked on my topology.
|
|
1:00:11
|
And I was told to handout DNS servers,
|
|
1:00:15
|
so not domain name, but I need a name
|
|
1:00:24
|
name server, DNS server.
|
|
1:00:32
|
Name server, OK? DNS server is going to be 177.1.10.110
|
|
1:00:43
|
OK? Do show run | 2 section
|
|
1:00:47
|
for DHCP which on switch section doesn't work.
|
|
1:00:50
|
So I'll judt have to do begin with DHCP,
|
|
1:00:55
|
Now I've got my exclusion ranges and my pools
|
|
1:01:00
|
and now I'm going to go ahead and jump back into fas02 no shut it,
|
|
1:01:06
|
watch that come up,
|
|
1:01:08
|
and I'll check to make sure that I'm getting an IP address.
|
|
1:01:12
|
Now that could take a little while to come up,
|
|
1:01:16
|
show IP interface brief, make sure I
|
|
1:01:19
|
brought up the right interface, I did.
|
|
1:01:22
|
It's in a state of up up, that's good.
|
|
1:01:29
|
It says CDP neighbor,
|
|
1:01:32
|
I don't see it there yet, so it's going to take a little while
|
|
1:01:36
|
So we'll go ahead and write this configuration and
|
|
1:01:40
|
we'll come back and chick this in a little bit.
|
|
1:01:43
|
Especially important in the real lab is not sit there and wait,
|
|
1:01:47
|
for something to happen. Go and do something else.
|
|
1:01:51
|
In our demosntration, I certainly could wait,
|
|
1:01:53
|
but I don't want to waste your time just waiting.
|
|
1:01:56
|
So let's show CDP neighbor, it's back up.
|
|
1:01:58
|
Show CDP neighbor fas0/2 details,
|
|
1:02:03
|
I see that it does not yet have an entry address or an IP address.
|
|
1:02:07
|
So we will wait for it to get an IP address
|
|
1:02:10
|
but we won't wait, we'll move on to something else.
|
|
1:02:15
|
OK? So, by the way DHC pool for the PCs
|
|
1:02:19
|
there is no PC attached, you would just be
|
|
1:02:21
|
counted or checked on configuration,
|
|
1:02:24
|
there's no way to verify that properly.
|
|
1:02:27
|
OK?
|
|
1:02:29
|
So let's look at DHCP at Branch 1 and 2,
|
|
1:02:32
|
and we're told for those to provision the CUCM publisher server
|
|
1:02:36
|
to just distribute IP addresses and options via DHCP
|
|
1:02:39
|
to any IP phones that those two sites, were given the subnets.
|
|
1:02:43
|
We're not told anything about PCs and we're told,
|
|
1:02:46
|
the ranges of IP addresses
|
|
1:02:50
|
to watch from being distributed now.
|
|
1:02:55
|
We are not instructed anything about TFTP Or default routers,
|
|
1:03:02
|
that doesn't mean that we don't have to have them of course.
|
|
1:03:05
|
We of course have to have them if we want phones to ever register
|
|
1:03:09
|
via TFTP or be able to communicate
|
|
1:03:13
|
IP via their default gateway. So those were implicitly
|
|
1:03:18
|
stated or not stated, but implicit tasks, they do have to exist.
|
|
1:03:25
|
OK? So let's jump over to our CUCM interface.
|
|
1:03:29
|
and let's go up to
|
|
1:03:32
|
actually let's go to unified serviceability to begin with.
|
|
1:03:36
|
We'll log in and we'll check to make sure
|
|
1:03:40
|
that services are started that are necessary.
|
|
1:03:43
|
Now we would go to service activation
|
|
1:03:45
|
if they had not already been activated.
|
|
1:03:47
|
I know that they have and if you just want to check
|
|
1:03:49
|
and see if they have,you can certainly go to control center,
|
|
1:03:52
|
to both start or restart a service that might be stopped,
|
|
1:03:57
|
not to activate it, but if it's not activated,
|
|
1:03:59
|
it will tell you that it's not activated and you can move on from there.
|
|
1:04:03
|
So here's our DHCP monitor service,
|
|
1:04:07
|
it is started and acitvated and for later
|
|
1:04:10
|
if we can note the TFTP and call manager is also started and activated.
|
|
1:04:16
|
OK? So we'll go ahead and go back to Cisco unified
|
|
1:04:21
|
CM Call Manager administration.
|
|
1:04:30
|
OK, so at this point let's go ahead and we will,
|
|
1:04:34
|
come down to DHCP and we will first go the server,
|
|
1:04:39
|
We shouldn't find any, we did, we could delete them,
|
|
1:04:42
|
but we shouldn't have any.
|
|
1:04:45
|
So we'll create one and for the host server we have to
|
|
1:04:48
|
choose one of the two that have the service activated.
|
|
1:04:51
|
We're just gonna choose the publisher mainly because we were told to.
|
|
1:04:56
|
Now we've got some information in here,
|
|
1:04:58
|
The information in here is going to
|
|
1:05:03
|
take effect over all subnets unless there is something more specific,
|
|
1:05:08
|
created on a subnet or scope. OK so anything that,
|
|
1:05:12
|
pervades everything such as a TFTP address.
|
|
1:05:16
|
Either option 150 or 66
|
|
1:05:20
|
but we weren't told to do either so we'll just use 150.
|
|
1:05:23
|
That's gonna be the same on all, so we'll go ahead and enter that
|
|
1:05:25
|
here 177.1.10.10
|
|
1:05:29
|
Maybe a DNS server if we had one, but we weren't told to create one
|
|
1:05:33
|
or configure one, maybe a domain name. OK?
|
|
1:05:37
|
But we can go ahead and click save here
|
|
1:05:41
|
and the add is successful, you see it show up.
|
|
1:05:45
|
Now we can go ahead and create our DHCP subnet.
|
|
1:05:49
|
So click find first, we don't find any subnet, 0 records, that's good.
|
|
1:05:54
|
We'll click add new, we'll choose the server that we just configured,
|
|
1:05:59
|
and the subnet address is going to be 177.2.11.0
|
|
1:06:08
|
OK? The primary start IP address is here.
|
|
1:06:16
|
Now remember, we were told
|
|
1:06:20
|
to have exclusion ranges essentially.
|
|
1:06:24
|
So we were told not to allow the range of
|
|
1:06:31
|
177.2.11. last octet 1 through 10.
|
|
1:06:36
|
So while our subnet is .0, we need to start this
|
|
1:06:40
|
first IP at .11 and the ending IP can be wherever we want,
|
|
1:06:47
|
let's just make it 254, 55 would be the broadcast.
|
|
1:06:52
|
And we can even have secondary start IP addresses if we need
|
|
1:06:55
|
but we don't need to in this case, we were only told one exclusion range.
|
|
1:06:58
|
The other range was for our Branch2, Router 3 Branch2 site.
|
|
1:07:05
|
So we do need a router IP address, that'll be
|
|
1:07:09
|
177.2.11.1 from the topology.
|
|
1:07:15
|
TFTP has already been covered,
|
|
1:07:20
|
subnet mask, that will be a good idea, there it is.
|
|
1:07:24
|
255.255.255.0
|
|
1:07:29
|
This subnet mask is important. Also when you're using the web
|
|
1:07:34
|
interface, note that a number of different browsers,
|
|
1:07:38
|
Firefox being one of the key ones, it doesn't work
|
|
1:07:41
|
very wlel at all with Safari, I would never use Safari.
|
|
1:07:44
|
But Firefox sometimes, it won't show you add succesful, but instead
|
|
1:07:49
|
just see this information kind of sandwiched up here against the
|
|
1:07:52
|
save and delete, if that ever happens and you
|
|
1:07:58
|
don't see this entire section,
|
|
1:08:03
|
right here, make sure that you go and
|
|
1:08:08
|
save again.
|
|
1:08:12
|
Because if it doesn't show add successful
|
|
1:08:14
|
or update successful, then you can be sure it's not in the database.
|
|
1:08:19
|
OK? So now we'll add a new subnet,
|
|
1:08:22
|
and the server will be the same. The subnet address
|
|
1:08:26
|
will be 177.3.11.0 is what we're already instructed.
|
|
1:08:32
|
So start IP address, let's go take a look at our lab,
|
|
1:08:35
|
it actaully had a different start address, we were told to reserve 1 to 12.
|
|
1:08:40
|
So 13 is our start address,
|
|
1:08:44
|
and our ending address can be 254.
|
|
1:08:47
|
Our router is going to be 3.11.1 and our subnet mask,
|
|
1:08:54
|
it is a /24.
|
|
1:09:00
|
OK, the add was successful, now here's the problem,
|
|
1:09:05
|
We don't see any IP addresses being handed out.
|
|
1:09:08
|
OK, we actually just have to check the phones.
|
|
1:09:11
|
So it's really wasn't intended to be a DHCP server,
|
|
1:09:16
|
that was just kind of a nice add on as I mentioned earlier.
|
|
1:09:19
|
So we got the configuration in,
|
|
1:09:21
|
we're gonna have to check it in a little bit.
|
|
1:09:23
|
Let's switch back over to our Corporate Headquarter switch,
|
|
1:09:28
|
Look at the show CDP neighbor fas0/2 detail again,
|
|
1:09:33
|
we do see that we handed out an IP address of .30
|
|
1:09:37
|
OK? So now we should be able to take that IP address, copy it.
|
|
1:09:42
|
Bring our web browser back up.
|
|
1:09:47
|
Put that in, sure enough we'll add our phone 7961
|
|
1:09:51
|
let's go to network configuration over here on the left,
|
|
1:09:55
|
and see that operational VLAN ID is 11.
|
|
1:09:59
|
So we did in fact get our CUCM,
|
|
1:10:04
|
our voice VLAN through CDP.
|
|
1:10:09
|
OK?
|
|
1:10:15
|
OK. So let's switch back over and go to
|
|
1:10:20
|
Router 2 which is Branch1.
|
|
1:10:24
|
And let's do show CDP neighbor, we see that's at fas010
|
|
1:10:30
|
so we'll do that again, show CDP neighbor
|
|
1:10:35
|
fas010 details and we don't have an IP address.
|
|
1:10:41
|
Does anyone know why we might not ever at this
|
|
1:10:44
|
stage get an IP address?
|
|
1:10:47
|
Is there anything we've forgotten that was in the lecture?
|
|
1:10:55
|
Call for address.
|
|
1:11:01
|
That's correct Christian, the routing and switching side of things,
|
|
1:11:03
|
the IP helper address. We've got a broadcast over here
|
|
1:11:07
|
from this phone on a subnet.
|
|
1:11:10
|
Which subnet? Well let's take a look, show run interface,
|
|
1:11:14
|
fas010, the voice VLAN subnet.
|
|
1:11:18
|
OK, the access would be where the PC through the phone would request.
|
|
1:11:22
|
But the phone itself is on voice VLAN so 11,
|
|
1:11:26
|
so we need first make sure. Do we even have an SVI?
|
|
1:11:30
|
Show IP interface brief, VLAN 11.
|
|
1:11:35
|
We do, if we did not have an SVI,
|
|
1:11:38
|
We would have to create one with an IP address
|
|
1:11:40
|
or we would not know where to request the subnet from.
|
|
1:11:44
|
Even if it was on the same box,
|
|
1:11:47
|
in other words even if the DHCP scope was being
|
|
1:11:49
|
served by this Branch1 router, we still have to have a VLAN 11
|
|
1:11:55
|
interface and SVI, and we have to have an IP address, otherwise
|
|
1:12:00
|
what if we had four scopes being served from this router and 15 subnets
|
|
1:12:04
|
or 15 VLANS? How do I know which subnet, which layer 3 scope,
|
|
1:12:10
|
to hand out? That's why I need the SVI. So now we need to jump to
|
|
1:12:16
|
configT and interface VLAN 11,
|
|
1:12:21
|
and we can see the IP addresses is already set up,
|
|
1:12:24
|
so we need to configure IP helper address.
|
|
1:12:29
|
And course of putting in the address might be helpful,
|
|
1:12:31
|
177.1.10.10 is the publisher IP address.
|
|
1:12:36
|
Show run interface VLAN 11,
|
|
1:12:41
|
There's the configuration for that, so now what I'll do is I'll go over
|
|
1:12:46
|
to interface fas01/0 which shows CDP neighbor
|
|
1:12:55
|
010 and we'll just shut and no shut,
|
|
1:12:59
|
in order to kind of bump it or power cycle it,
|
|
1:13:03
|
to encourage it to get an IP address faster.
|
|
1:13:07
|
Write my router config,
|
|
1:13:14
|
show CDP neighbor.
|
|
1:13:20
|
OK, it's gone from CDP table,
|
|
1:13:26
|
with a little bit of time,
|
|
1:13:35
|
OK, now it's back so show CDP neighbor
|
|
1:13:41
|
fas010 detail and we see that it has an IP address
|
|
1:13:47
|
of 177.2.11.254, that's interesting.
|
|
1:13:53
|
CUCM is basically Linux and it's handing them out
|
|
1:13:59
|
in the way that Redhat Enterprise Linux would do so
|
|
1:14:02
|
which is inversely, so the router is gonna hand it
|
|
1:14:05
|
out from the bottom of the subnet.
|
|
1:14:09
|
Thinking or I guess speaking and saying
|
|
1:14:12
|
that the bottom of the subnet is .1 first.
|
|
1:14:16
|
We've got a TFTP server and we've got the operational VLAN ID.
|
|
1:14:22
|
So we're good to go, the right router ID,
|
|
1:14:25
|
so everything did work from the CUCM pub.
|
|
1:14:30
|
|
