Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
In this packet to trace a lab you need to configure both as a slug and NDP or network time protocol.
This lab consists of a Cisco router and a Cisco switch as well as a source log server A.P. server and
P.C. slug allows us to centralize log messages as well as store a historical backup of various log of
messages rather than just logging messages to the console of a router or switch or logging it to a limited
buffer.
We can centralize log messages on assist log server hard drive capacities in servers are much greater
than the memory or flash available in routers and switches so we can collate centralize and store log
messages on a six log server.
So that's what you're going to configure in this lab.
You're also going to make sure that your log messages have the correct time by setting up an A.P. Server
Network Time Protocol allows us to ensure that the devices throughout our network have the correct time
which is important when you're logging messages.
If you have a log message that says that an interface went down that it doesn't really help you if you
don't know when that event occurred did it happen yesterday.
Did it happen a year ago.
Did it happen five years ago.
It's important that you have timestamps on your log messages and that's why you need to configure a
network time protocol server or A.P. server.
What you need to firstly do is configure the source log server to accept assist log messages and then
configure wrote a one and switch one to log messages to the source log server to test this great day
loop back interface on Route 1 and verify that source log messages are displayed on the source log server
do various tests such as shutting down the loop back interface on the router and then re enabling the
loop back interface and make sure that to the source log messages are displayed on the source log server
shut as this interface on the switch and then re enable it.
And once again verify that to the source log messages are shown on the slug server setting up a source
log survey is very easy in package tracer.
Select your source log server go to services source log and enable the source log server once you've
configured your source log server you need to configure the A.P. server so ensure that ATP is enabled
on your server go to services A.P. and enable the A.P. service before you configure your devices to
get time from the A.P. server check what the time is on your devices as an example on the router show
clock shows us that this writer believes that it's the first of March 1993 that's obviously incorrect
also configured right to one and switch one to set timestamps in the source log messages sent to the
source log server and then configure right 1 and switch one to get to that time from the A.P. server
once you've done that verify that the clocks are properly set and then shut down the loop back interface
and re enable it on Route 1 and verify that your source logs server is receiving the source log messages
but in addition verify that the timestamps on the source log messages are set to correctly do the same
on the switch shut it down and no shut this interface and verify that the source log messages have the
correct timestamp applied it's important for you to know both so slug and A.P. for the CCMA exam as
well as for the real world so make sure that you know how to configure both source log and A.P. by downloading
the packet trace a file and configuring the network so can you complete the slab download the packet
trace a file and see if you can complete the lab yourself otherwise watch the next video where I complete
the lab.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.