I am opening new topic because the old one for my issue was unclearly explained.
OK, I have 2xT1 bundled in a PPP Multilink interface. Normally if one of this serial lines goes down the second has to keep the Multilink interface up but this is not the case in our network. When one of the lines goes down the OSPF between the Multilink interfaces on both sides is going down and I lose connection to the remote office for several seconds, then the adjacency comes back up. When the OSPF goes down all IP Phones reset which is unacceptable. These are the messages that I got in the router log:
Jan 20 16:39:49.170 EEST: %CONTROLLER-5-UPDOWN: Controller E1 0/1/1, changed state to down (LOF detected)
Jan 20 16:39:51.170 EEST: %CONTROLLER-5-UPDOWN: Controller E1 0/1/1, changed state to up
Jan 20 16:57:48.173 EEST: %OSPF-5-ADJCHG: Process 40, Nbr 192.168.x.x on Multilink1 from LOADING to FULL, Loading Done
A folk from the forum suggested âppp multilink minimum-links 1â command to be inserted under both multilink interfaces.
I worry about this LOF detected. What does it mean? What is the problem with this link?
From the log you sent, the ospf adjacency had gone down before the E1 went down. Also, the int Multilink1 didn't went down. Weird, isn''t it? Try to send the log for a longer period before and after the problem.
What the state of the multilink interface was in this very moment? Could you provide us with 'sh ppp multilink' command and the relevant config?
the OSPF hello packets are IP packets that need to go through the PPP multilink bundle.
PPP multilink usually performs per packet load sharing and also fragmentation when needed.
My guess is that in your case OSPF hellos follow the same physical path (in one direction) so when one link fails and until that link is declared unusable some time is needed: for example at least 30 seconds if it has to wait for 3 PPP keepalive missing and the OSPF dead interval can fail too.
I would try to use a PPP keepalive lower then default 10 seconds in the hope to be able to keep OSPF adjacency up.
Usually this kind of problems happens for example in etherchannel where a fixed load balancing rule is used.
There are 2 ways u can use to reduce the convergence time..
1) Remove the multilink and run ospf individually on both the links. The adjacency would be built over both the links in this case.. When one of the link fails, you will still some ping timeouts but the convergence is much faster than in multilink
2) enable OSPF fast hellos if the latency between the two routers is not much
OSPF uses the metric aCost, which is related to the bandwidth. If there are equal cost paths (the same bandwidth on both multilinks), OSPF installs both routes in the routing table. The routing table tries to use both links equally, regardless of the interface utilization. If one of the links in the first multilink fails, OSPF does not send all the traffic down the second multilink. If the first multilink peaks 100%, OSPF does not send any traffic down the second multilink because OSPF tries to use both links equally, regardless of the interface utilization. The second is used fully only when the first multilink goes down.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...