Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.
During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.
We apologize for the inconvenience while we perform important updates to the Community.
I am unable to find out origin of failure if two router is connnected to each other through p2p lease line.
Suppose i Sitted at Router1 location and my remote location (Router2) is Down due to some reason.
How can i find that what is exact thing responsible for failure. Plz explain with useful commands
may be Router2's Serial port (s0/1) is down
may be ISP lease Line is down but Router2 s1/0 port is ok
Plz see attached snap.jpg file for Rough Scenerio.
If you can't ping the other side of the leased line [IP on your router] then most likely your leased line is down. Depending upon technology used you should be able to determine the exact cause. Use 'show interface ser1/0' command to find out details.
You can check the kine protocols
Sh ip interface brief
Also if this is a serial connection via T1 +
Sh frame-relay lmi
Sh frame-relay map
Sent from Cisco Technical Support Android App
'show interface serial' on r1 if shows line protocol as down then you should get the idea that something is not right on the other side. Other than that you can run debugs to check for the status of the other. what is the encapsulation you've on both serial intefaces?
These all replies still not clear to me......
I want to know that how can i say that Router2 port is down OR p2p lease line is down ?
which router command tell me exact details about failover ?
Encapsulation = PPP
Second question, What does mean of this command "F0/1 is up, line protocol is down"
Can you run these commands as suggested and post the results!
Sent from Cisco Technical Support iPad App
You're running PPP on layer 2 and the " "F0/1 is up, line protocol is down" says the layer 1 is fine and layer 2 (which is PPP in your case as per your notes) is not being established. In this case, you don't need to run any of the Frame relay commands.
In case of PPP on layer 2, there is no show command which will tell you that the port is up or down otherthan There's only show interface <> output. You can run some PPP debug commands to check further about the issue but they can be little too much too handle at times. Commands are 'debug ppp negotiation' and 'debug ppp authentication' which can read about here:
More about your second question:
I do not have this type of network setup ....but i am planning to make same for my remote locations.
so those who faced this problem plz share commands with logs so that i can easily understand where
will occuring problem.....this is my very simple question
Have you even read what people have commented on your query rather than just blindly putting some redudandant posts? What is it that i've wirtten in my post not clear to you or not applied in your scenario? What is the setup? Please follow the guidelines when posting on this forum.
maybe some people would be interested and suggest you some solution but you did not provide any output of your router(s) .
pdriver want output of this commands:
Sh frame-relay lmi
Sh frame-relay map
If you can't provide any outputs of routers than it is very hard to troubleshoot your issue.
The short answer is you can't definitively define where the issue is without access to both ends of the link.
As you are saying you will be on site2/router 2 you can do a show interface serial*/* or ethernet*/* This can give an indication as to which end of the link the issue is at. if it is down/down then the issue is local to you. If up/down then the issue is at the far end. However this does not define whether the issue is ISP or router related. You would need someone to check the router at the far end since it could be as simple as an unplugged cable or router powered off. Before raising a case with an ISP the questions they will ask are:
Is the router powered on
Has it been power cycled
Has the cabling been checked.
The majority of the time these basic checks will resolve the issue.