![]() End with CNTL/Z.īru-nas-02(config-controller)# no pri-group timeslots 1-31īru-nas-02(config-controller)# channel-group 0 timeslots 1-31 bru-nas-02# configure terminalĮnter configuration commands, one per line. If you are not using a channelized E1, proceed to step 4. If the E1 is configured as a PRI you need to remove the pri-group before using the channel-group command. To run the loopback test on channelized E1s (PRI or CAS) we need to use the channel-group E1 controller command to create one or more serial interfaces mapped to a set of timeslots in the channelized E1. Use the write memory command to save your router configuration. ![]() Insert the plug into the port in question. Twist the wires from pins 9 and 8 together.Ĭomplete these steps to prepare for the extended ping test: Twist the wires from pins 2 and 15 together. Use wire cutters to cut a working DB-15 cable that is 5 inches long with a connector attached. Creating the Loopback Plug for E1 on DB-15Ĭomplete the following steps to create a loopback plug for E1 on DB-15: Refer to the document on RJ-45 cables for more information. With the metal pins facing toward you, and the cable hanging down, pin 1 is the left-most pin. The pins on an RJ-45 jack are numbered from 1 through 8. Twist the wires from pins 2 and 5 together. Twist the wires from pins 1 and 4 together. Use wire cutters to cut a working cable that is 5 inches long with a connector attached. Creating the Loopback Plug for E1 on RJ-45Ĭomplete the following steps to create a loopback plug for E1: If you are working in a live network, ensure that you understand the potential impact of any command before using it. All of the devices used in this document started with a cleared (default) configuration. The information presented in this document was created from devices in a specific lab environment. The information in this document is based on the software and hardware versions below. There are no specific prerequisites for this document. Before You Begin Conventionsįor more information on document conventions, see the Cisco Technical Tips Conventions. If a router passes a hardware loopback plug test, then the problem exists elsewhere on the line. That address is always 127.0.0.1, and pinging it successfully lets you know that the network adapter on your computer (and the networking software in your OS) is working properly.The hardware loopback plug test is used to see if the router has any faults. If you can't successfully ping your router, but your router appears to be turned on and working, you can try pinging what's known as a loopback address. Ping your loopback address (127.0.0.1).A successful response lets you know that your local network is working okay, and that the problem reaching the internet location is somewhere out of your control. If you can't successfully ping an internet location, you can then try pinging your router. Ping your router to see if you can reach it.The ping tool shows you right at the top the IP address it's working with. If you want know the IP address for a particular URL, you can ping the URL. And if you're interested in exploring those routes further, you can use another networking tool named tracert to do just that. If you get a successful response, you know that all the networking devices between you and that destination are working, including the network adapter in your computer, your router, and whatever devices exist on the internet between your router and the destination. Ping a URL (like or IP address to see if you can reach an internet destination.Now that you know how to use the command, here are some interesting things you can do with it: The time it takes packets to return to you can help you identify a slow connection, or if you're experiencing packet loss. This can help you determine if a network problem is somewhere on your local network, or somewhere beyond. You can test whether your computer can reach another device - like your router - on your local network, or whether it can reach a device on the Internet. When it gets the response, the ping tool shows you how long each packet took to make the round trip - or tells you there was no reply. Your computer sends several packets of information out to that device, and then waits for a response. You issue the ping command along with a specific URL or IP address. On a computer network, a ping tool is built into most operating systems that works in much the same way. Ping comes from a term used in sonar technology that sends out pulses of sound, and then listens for the echo to return. It's a handy tool that you can use to quickly test various points of your network. The ping command sends packets of data to a specific IP address on a network, and then lets you know how long it took to transmit that data and get a response.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |