From: ttripp on 7 Oct 2008 14:38 On Oct 7, 2:31 pm, Artie Lange <spam...(a)jamiebaillie.net> wrote: > ttripp wrote: > > Multilink1 is down, line protocol is down > > Hardware is multilink group interface > > Internet address is y.y.y.94/30 > > MTU 1500 bytes, BW 4608 Kbit, DLY 100000 usec, > > reliability 255/255, txload 1/255, rxload 1/255 > > Encapsulation PPP, LCP Closed, multilink Closed, loopback not set > > Keepalive set (10 sec) > > DTR is pulsed for 2 seconds on reset > > Last input never, output never, output hang never > > Last clearing of "show interface" counters 00:04:28 > > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: > > 0 > > Queueing strategy: fifo > > Output queue: 0/40 (size/max) > > 5 minute input rate 0 bits/sec, 0 packets/sec > > 5 minute output rate 0 bits/sec, 0 packets/sec > > 0 packets input, 0 bytes, 0 no buffer > > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > > 0 packets output, 0 bytes, 0 underruns > > 0 output errors, 0 collisions, 1 interface resets > > 0 output buffer failures, 0 output buffers swapped out > > 0 carrier transitions > > conf t > int multilink1 > no shutdown > > just a guess?- Hide quoted text - > > - Show quoted text - Nope, that was the first thing I tried.
From: ttripp on 7 Oct 2008 16:20 On Oct 7, 2:38 pm, ttripp <ttr...(a)manh.com> wrote: > On Oct 7, 2:31 pm, Artie Lange <spam...(a)jamiebaillie.net> wrote: > > > > > > > ttripp wrote: > > > Multilink1 is down, line protocol is down > > > Hardware is multilink group interface > > > Internet address is y.y.y.94/30 > > > MTU 1500 bytes, BW 4608 Kbit, DLY 100000 usec, > > > reliability 255/255, txload 1/255, rxload 1/255 > > > Encapsulation PPP, LCP Closed, multilink Closed, loopback not set > > > Keepalive set (10 sec) > > > DTR is pulsed for 2 seconds on reset > > > Last input never, output never, output hang never > > > Last clearing of "show interface" counters 00:04:28 > > > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: > > > 0 > > > Queueing strategy: fifo > > > Output queue: 0/40 (size/max) > > > 5 minute input rate 0 bits/sec, 0 packets/sec > > > 5 minute output rate 0 bits/sec, 0 packets/sec > > > 0 packets input, 0 bytes, 0 no buffer > > > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > > > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort > > > 0 packets output, 0 bytes, 0 underruns > > > 0 output errors, 0 collisions, 1 interface resets > > > 0 output buffer failures, 0 output buffers swapped out > > > 0 carrier transitions > > > conf t > > int multilink1 > > no shutdown > > > just a guess?- Hide quoted text - > > > - Show quoted text - > > Nope, that was the first thing I tried.- Hide quoted text - > > - Show quoted text - Turns out our ISP (Sprint) never turned on multilink on their side. Link came up very quickly once they did. Thanks for the help, all.
From: Artie Lange on 7 Oct 2008 16:24 ttripp wrote: > Turns out our ISP (Sprint) never turned on multilink on their side. > Link came up very quickly once they did. Thanks for the help, all. "Oh! you wanted to use that circuit? OK one sec..." Is that how the call went?
From: ttripp on 8 Oct 2008 08:31 On Oct 7, 4:24 pm, Artie Lange <spam...(a)jamiebaillie.net> wrote: > ttripp wrote: > > Turns out our ISP (Sprint) never turned on multilink on their side. > > Link came up very quickly once they did. Thanks for the help, all. > > "Oh! you wanted to use that circuit? OK one sec..." > > Is that how the call went? They had the circuits turned up, but not bundled. For once, I had a telco actually listen to the problem and jump right on it, instead of trying to push it back on me or the LEC. Very quick turn-around, and I was up in 15 minutes.
First
|
Prev
|
Pages: 1 2 Prev: VPN Not Routing, Reboot Fixes it. Next: 802.11 b/g wireless lan pc card driver??? |