Wassim

These are my notes on configuring and testing a quick implementation of a free tacacs+ authentication and authorization server software on Windows and on Kali Linux. A quick review of TACACS+ Tacacs+ is used by network devices to authenticate users. Each user that logs on to a network device is checked against the Tacacs+ server database, before a decision is made. The decision can be something like: the user is authenticated but will have limited access to the network device the user is authenticated and will have full rights on the network device, the user is not authorized to access the network device and is kicked off. Tacacs.Net on Windows Installation and configuration Download the software from the official website Install the software. At some point, the system asks you to configure a shared secret. This key will be used for communications between Tacacs+ clients and the Tacacs+ server. Configuring authentication For Windows 7, the configuration files are in the following path...

Make sure to read about similar topics from the CCNP Collaboration track here . CUCM route lists, Route patterns and route groups trace the path of a call inside a company and outside of it. The Cisco best practice is: to point a route pattern to a route list to point a route list to one or more route groups to point a route group to one or more devices. To learn more about route lists before starting with the config, I suggest you check this good theoretical introduction . Implementation of the Example Setup I configured for HQ site: a CUCM route list named CorpHQ-RL a route group named CorpHQ-RG  that points to the HQ H.323 gateway. I configured the same for Branch1: a CUCM route list named Branch1-RL a route group named Branch1 – RG  that points to the Branch1 H.323 gateway. Let us start with HQ site: In my home lab, I pointed all route patterns to the same route list. For example, pattern 911: Now the branch site: The same pattern 911 in the Branch1 office ...

In this blog post I am going to describe the concept of Class of Service with an example based on the configuration of Calling Search Spaces (CSS). This post is part of my CCNP Collaboration series of articles. If you need an introduction or a refresher on partitions and Calling Search Spaces, you can read this . Lab setup HQ is in Pennsylvania, Branch1 is in Arizona. We have HQ phone with DN 1000. We have a configured emulation of PSTN with a couple of PSTN lines: local lines long distance lines international line emergency line The concept of local or national line is relative to the calling party. For example, for HQ phones, line 7175438411 is a local PSTN line, while for Branch1 phones the same line is considered long distance. We define the following partitions: CorpHQ-internal_PT CorpHQ-Local_PT CorpHQ-LD_PT CorpHQ-International_PT CorpHQ-EMS_PT And we define Calling Search Spaces: CorpHQ-Internal_CSS CorpHQ-local_CSS CorpHQ-national_CSS CorpHQ-international_CSS In the following...