In the CCN a course we've been discussing the use of local usernames and passwords you know the words
to use the name and password information is stored on each router or switch individually.
So as an example when I log on to this radhe radhe one there's no with any cation.
But what we could do is create a username on the router and then go into the link console and specify
log in and either align logging or specify a local logging.
So now when we log on to the router we are prompted to enter the username and the password.
That works well when you have a small environment but as you scale it becomes a lot of work.
So as an example when I connect to router to there's no username and password.
So what I need to do now is create a separate username and password on route to and then I need to remember
to go to the line console and specify a log in local and I mustn't forget to do that on the Etiwanda
lines as well.
So logging back in I'm now prompted for my username and password on Rodda to but once again when I connect
to router 3 there's no use an admin password and I have to specify that again.
Now that's not the only problem that we have to configure passwords locally on every device.
So you've got to remember to do all that configuration.
But what you've also got to remember to do is to change your passwords on a regular basis.
To implement good security practices you should be changing your password on a regular basis.
That means that we have to go to every device in the network and change the password on each device
individually.
In this example of only got five devices.
But if you've got a hundred or a thousand network devices that's a lot of configuration that increases
because you don't want the users sharing the same username and password.
So if you've got another using your environment
you should set up that to use count on every router.
So as an example on broader one I can logon as Mary but I can't do that on a t.
Because I haven't configured a username Mary on rockety.
So the management of user names and passwords becomes very difficult when you have a local user names
and passwords configured on every device.
So it makes sense to centralize your usernames and passwords on a central server.
So in this example we've got a user called Edmon that we could add Mairi or David to this database and
then point every network device to the central Esaias server which means that we don't have to configure
a local username and password on every device for every user that needs to access that device.
The server can also be leveraged once again for a 2.1 X theni cation where you centralize the username
and password a vindication of users accessing the network through a triple a server or authentication
authorization an accounting server.