300-410: Implementing Cisco Enterprise Advanced Routing and Services (ENARSI) Certification Video Training Course

300-410: Implementing Cisco Enterprise Advanced Routing and Services (ENARSI) certification video training course by prepaway along with practice test questions and answers, study guide and exam dumps provides the ultimate training package to help you pass.

CCNP ENARSI (300-410) : NETWORK MAINTENANCE AND BEST PRACTICES

3. 3_3- Network Maintenance Services and Tools

In this section, we are going to talk about network maintenance services and tools. The first service we are going to take a look at is time services, and we need to use the NTP for problem-free time management. It's very important that the time is correct for proper interpretation of log recordings. For example, let's say that you have a failure on your router, and let's say that it's a really important device, that's a coreudder.

And let's say that the problem occurred at 14:00 p.m. The actual failure time is 14:00 p.m. However, if your router's time is showing another time, you may feel compelled to examine the logs of the devices by using the "Show log" command, only to discover that nothing has changed at 14:00 p.m. So please keep in mind that you need to use a proper NTP server for problem-free time management. And it's very important to follow the log messages and interpret them by default. You'll see a log message if you are connected via console cable to a device.

If you want to see the logs instantly when you are remotely connected to the device, you can use the terminal monitor command or the Show Log command, which is your best friend to check historical logs.

And we have some log message options. And here we can define a buffer for the log message. We are defining a log buffer in our memory. Logs on the device are kept up to 4096 bytes, and the log message printed on the console screen is set to warning or below with this command depending on the security level. And logs are being sent to an external syslog server by typing, logging, and the syslog server's IP address.

And as you know, we have some locks with different severity levels, and the level numbers are big, starting from zero, which is the most important level, and finishing with seven, which is the less important level. Level zero indicates that the system is inoperable, while level one indicates that immediate action is required. And here is the chart you can examine in more detail. And we have an example in here with a log message, as you can see. In the example, we see a log message that has a severity of 5, which is a notification level, as you can see.

If, for example, a VGP peering in your network fails, a log message with a series level of three is generated. And let's take a look at how we can back up our configurations right now. We can also backup our configuration by using external FTP servers to define an external FTP server. We go into configuration mode and define the username and password of the external FTP server. Then, when we type the copy runconfig to FTP with double columns, The iOS is asking us for the IP address of the remote STP server. And the only thing we are going to do is just type and hit the ender. Then we are defining a destination filename, and a backup is being written. As you can see, we can also take a backup by using SSH and SCP.

Actually, this is done by using the SCP. But if you want to use SCP backup, you should activate SSH, and SSH should be functional on your device. All right. When you configure SSH, as you can see, this is the SSH configuration. Cryptokeys generate RSA. Then the keys are generated. After we define an SSH timeout, SSH host authentication is retrieved, and the command we need to use for the SSSPsecure copy protocol is "Ipscp server enabled." By typing this, we are enabling the SCP protocol on our router.

Then the thing we are going to do is copy, for example, flash to the RSCP server. Then we are asking for this source file name, and we are defining a vimidhost address. And we are defining the username and password of the remote device too. We can also use the archive command to backup the configuration files too. And in here we have a router, as you can see.

And we have a remote FTP server on our router. We need to type up the archive. The command is just archive, and we're going to archive mode. The path, FTP username, FTP password, IP address, and file name are then used to define the FTP server. Then we are defining a time period in this section. That means in 1440 minutes, the latest state of the configuration is sent to the FTP server. Also, each time the right memory command is executed, the application is triggered, and a configuration backup file is sent to the FTP server.

4. 3_4- Integrating Troubleshooting To Network Maintenance Process

In this section, we are going to take a look at the integration of troubleshooting into the network maintenance process. Maintenance involves many different tasks, some of which are listed in previous slides. As you know, for some of these tasks, such as supporting users, responding to network failures, or disaster recovery, troubleshooting is a major component of the tasks.

Tasks that do not revolve around fault management, such as adding or replacing equipment, moving servers and users, and performing software upgrades, will regularly include troubleshooting processes too. Hence, troubleshooting should not be seen as a standalone process but as an essential skill that plays an important role in many different types of network maintenance tasks.

To troubleshoot effectively, you must rely on many processes and resources that are part of the network maintenance process. You need to have access to up-to-date and accurate documentation. You rely on good pickup and restore procedures to be able to roll back chains if they do not solve the problem you're trying to solve. You must have a good baseline of the network so that you know which conditions are considered normal on your network and which are considered abnormal.

Also, you need to have access to the logs that are properly time stamped to find out when particular events have happened. So in many ways, the quality of your troubleshooting process depends significantly on the quality of your network maintenance processes.

Therefore, it makes sense to plan and implement troubleshooting activities as part of your overall network maintenance process and to make sure that the troubleshooting processes and maintenance processes are aligned and support each other, making both processes more effective. The network documentation is expected to include the features we see on the screen right now. The first is a network diagram. We need to keep up-to-date with the physical and logical topologies of the network, and labelling of interfaces and cables is very important.

Also, sometimes the port description information may remain obsolete. It is very important to label the interface and cables in order to make it easier to detect errors when there is a physical problem, and device connection features should also be documented. It is useful to have a subdocument that summarises the connections of the internal devices to the outside, for example, with the service providers. And we need to have a hardware and software inventory as well. It is important to have an inventory of models, serial numbers, software versions, and licences for all devices used in a network. It is important to keep an addressing share where all IP blocks on the network take place to.

And last, we need to also document the device configurations. Copies of device configurations need to be archived. The only way to know what is normal for your network is to measure the network's behavior. continuously knowing what the measure is for each network in general. The more you know, the better it is. But obviously, this has to be balanced against the effort and cost involved in implementing and maintaining a performance management system.

The following list summarizes some useful data and establishes a baseline. The basic performance statistics interface load for critical network links, CPU load, and memory usage of routers and servers, for example, are critical statistics. Together, these values can be pulled and collected on a regular basis by using SNMP and Graft for visual inspection and accounting of the network. Traffic is also very important, and armor-removed monitoring, NBA network-based application recognition, or Netflix statistics can be used.

Profile different types of traffic on your network, and the measurement of the network performance characteristics should also be documented. The IPSA feature in Cisco iOS can be used to measure critical performance indicators such as delay and jitter across the network infrastructure. Change control is one of the most basic operations in network maintenance. There is no difference between making changes as part of the maintenance process or as part of the troubleshooting process. Change control procedures, urgency, necessity, impact, and risk balancing should always be addressed. Troubleshooting can be a perfect fit with well-defined and well-documented change processes.

CCNP ENARSI (300-410) : NETWORK TROUBLESHOOTING WITH DNA ASSURANCE AND IP SLA

1. NETWORK TROUBLESHOOTING WITH DNA ASSURANCE

In this section, we will talk about troubleshooting network problems with Cisco DNA Assurance, because the health of a network is paramount to its ongoing success. Gas and your network may include thousands of devices, including routers, switches, wireless LAN controllers, wireless access points, etc.

Troubleshooting the old-fashioned way does not provide the insights you need to keep up with today's network demands. It is important to have the ability to see the health of the network in its entirety and identify any potential issues that must be addressed. Cisco DNA Center Assurance is just one component of the Cisco DNA Center. With Cisco DNA Center assurance, you can predict problems more quickly thanks to proactive monitoring. Then you can gain insights from network devices, network applications, network services, and clients.

As a result, guys, you will be able to ensure that implemented policies as well as configuration chains achieve the desired business results and provide users with the experience they want, spending less time troubleshooting and more time waiting. As you can see on the screen, the first useful troubleshooting tool is the OverallHealth page. Also, you can reach this page by clicking on "Assurance" at the top of the Cisco DNA Center site. This page provides an overview of the overall health of the networks and clients in the environment, which can be displayed based on information gathered over the most recent 3 hours, 24 hours, or seven days.

You can view heat maps as well as hierarchical sitebuilding maps by clicking on the Hide and Show button. In the Network Devices area as well as the client area, you can get an overall network score based on the health of the network devices as well as the wired and wireless clients. The "top ten issues" area at the bottom of the page displays the issues that should be addressed. When you click on them, you will be taken to the issue details, including the impact of the issue and suggested actions to resolve it.

And another valuable troubleshooting tool is the Network Health page. You can see on the screen that you can reach this page in the Cisco DNA Center assurance by selecting Health and then the network. You can use the Network Health page to get a sense of the health of the network and the devices in it. You can leave the percentage of healthy devices in your overall network based on categories such as access, core, distribution, router, and wireless. Information can be displayed in five-minute intervals over the past 24 hours.

The Network Devices section lists all the devices on an individual basis and provides information such as the device type, address, OS, version, reachability, issue count, and location. In addition, it provides an overall health score. Anything with a health score of one to three is a critical issue, and it is displayed in red. Anything with a health score of four to seven is a warning and is displayed in orange and amber.

Anything with a health score of eight to ten signifies no errors or warnings and is displayed in green. A health score of zero indicates that no data is available and that it is displayed in gray. You can click on the device to get further details about it in Device 360. In addition, in Cisco DNA CenterAssurance, you can access the Client Healthpage by selecting Health and then Client. This page provides an overview of the operational status of the network and client devices that are part of the network.

If the devices have any issues, they are highlighted, and possible remediations are suggested. The Client Health page shows the health of wired and wireless clients. You can see the percentage of clients connected to networks that are healthy and unhealthy. A score is provided as a percentage, so you can quickly see the health of all the clients on the network. So you can see what's going on in here. The score is 27 healthy for the wireless clients, which means there are 27 of them. 27 percent of them have good connectivity, and the rest have fair connectivity.

But the score for the white clients is 100%, which means all of them have good connectivity. The next volleyball troubleshooting tools are Device 360 and Client 360. These features can be accessed by clicking on any of the devices or clients. These features drill down into the device or client and display information about topology, outputs, and latency from various times and applications, allowing you to get a detailed view of the specific device or client's performance over a specific period. With these tools, you have granular troubleshooting at your fingertips. In seconds.

You can see on the screen that there's a switch named Spine 1, ABC in. So this switch has an issue, guys, and the issue is shown here, and it says this device is reaching high memory utilization. If you simply click here, or on the issue, you will be given a description of the problem as well as possible solutions. So, when you click on the issue, you can see the suggested actions as well as the suggested action. one, switch to verifying which process is consuming high memory, and two, check the release notes for known bugs. If it is a known issue, check if SMU is available and apply it to the switch.

Finally, if you are unable to resolve the problem, contact Cisco Tech for assistance. As a result, the image on the screen depicts the Client 360 dashboard for the client with IP addresses 1010, 20 and 207. You can see the IP address here. So notice that the client is experiencing poor radio frequency conditions. So, as you can see, the wireless client is experiencing poor RF conditions on SSID Sandbox. OK, so the next troubleshooting feature in DNACenter assurance will make your life easier. Pat Trace. This feature is basically the ping-and-trace route you have always dreamed of. Guys. Path trace allows you to see graphically the path that applications and services running on a client will take through all network devices to reach a specific destination.

For example, with a few clicks, you can use this tool to do multiple troubleshooting tasks that would take you five to 10 minutes at the command line on the screen. You can see an example of using path trays between two devices. And we also have the Global Issues page. With the Global Issues page, you can access all open issues, resolved issues, and ignored issues in one place, as shown on the screen. You can access the Global Issues page from the Issue dropdown menu. And finally, if you need to leave all the issues that Cisco DNA Center assurance is capable of monitoring in your environment, select the All Issues option from the Issues drop-down menu as shown on the screen.

2. TROUBLESHOOTING WITH IP SLA

In this section, we will talk about the IPS LA. IPSec service level agreement is a great feature on Cisco iOS devices that can be used to measure network performance. Performance, guys, can be something simple like a Ping where we check the round trip time or something more advanced like a VoIP RTP packet where we check the delay jitter and calculate an MoS score that gives you an indication of what the voice quality will be like. Measuring network performance is pretty cool, but what makes IPS LA even more powerful is that you combine it with static routes, policy-based routing, and routing protocols like OSPF or EIGRP. So let's check how we configured the IPS.

So you can see topology in this section. In our topology, we have router one, router two, and router three. Router one is connected to router two, and that is the prime link. And router one is connected to router three. That is the second row Internet link that you can see on the screen. Okay, so when we check the configuration of router one, we can see that router one has two default routes. In the first step, you can see that the first default route is pointing to two, and that is here; that is the router two; and the second one is pointing to three, three, three, and that's here; that's the router three.

But there is a difference here, guys. You can see that the administrative distance for this route is set to ten. So that means the second route is the one that is not used, okay? That is only being used once the primary link fails. So this kind of configuration with just two floating static routes partially accomplishes our requirement as it will work only in this scenario where the routers' interfaces connected to the one link are in up-down or down-down status. But in a lot of situations, we see that even though the links remain up, we are not able to reach the gateway. This usually happens when the issue is at the ISP site. That means, what if there's a problem in here? Or what if there's a problem in here?

Okay, so in such scenarios, guys, Ipslee is the engineer's best friend. With around six additional iOS commands, we can have a more reliable automatic failover environment. Using Ipsol 8, the Cisco iOS gets the ability to use ICMP pinks to identify when a wide-ray network link goes down at the remote end, allowing the initiation of a backup connection from an alternate port. The reliable static routing backup using object tracking can ensure reliable backup in the case of several catastrophic events, such as Internet circuit failure or peer device failure. Ipslea is set to ping a target such as a publicly routable IP address or a target within the corporate network of your ISP router's next hop IP address. Okay, let's check the second step.

Now the second configuration defines and starts an IPSprobe, and that is starting with Ipslea 1. Okay, the ICMP Ecoprob sends an ICMP Eco packet to the next hop IP 2222, as shown here, and it is sent every 3 seconds, as defined by the frequency parameter shown here. So we have a timeout parameter in here as well. Timeout sets the amount of time in milliseconds for which the Cisco iOS IPS operation waits for a response from its request packet. So also, we have a threshold defined here. Threshold sets the rising threshold that generates a reaction event and stores history information for the Cisco iOS IPS operation. After defining the IPS operation, our next step is to define an object that tracks the SLA probe.

So that is the third step. Okay, you can accomplish this object tracking with the comments used in the third step, and this command will track the state of the IPS operation. If there are no pink responses from the next hop IP, the track will go down, and it will come up when the IP SLI operation starts receiving only pink response only. The last step is the first step. In here, you can see that the last step in the Ipsli reliable static route configuration is to add the track statement to the default routes pointing to the ISP routers, as shown in here. So you can see IP route000-2222 drag in here. One OK, that's the IPS op. So the track number keyword and argument combination specifies that the static route will be installed only if the state of the configured track object is updated up. Hence, if the track status is down, the secondary route will be used to forward all traffic.

Prepaway's 300-410: Implementing Cisco Enterprise Advanced Routing and Services (ENARSI) video training course for passing certification exams is the only solution which you need.