Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) 6.x dropping frame frequently
I am hoping a bunch will come out of the woodwork on this one... That seemed
to be the case when I starting pissing and moaning about 6.0.4 and the c=46
problems, but that's another unsolved ticket.
I have 5 maxes that seem to lockup and/or drop the frame lmi (time-outs)
frequently. I'm actually relieved to see a max fatally reset itself at this
point, saves me from having to call in on the PRI and do a reset. This seems to
be across the board in the 6.x version. 5.0Ap42 was considerably more stable
(using the Ascend gauge of stability) and I could go fishing on weekends
without the laptop tied to my backside (don't ask)... Anyway, I have now
upgraded to 6.0.4, downgraded to 6.0.0 on some of the more serious ones, and
now re-upgraded to 6.0.2. Its like dodging bullets...
Here's a whole run-down of the current setup:
M1 (6.0.2-tikm40 8packs) - moderate usage (maxes out occasionally) Max 4004
Bell Atlantic 2 PRI parms: NI-2, ESF, B8ZS,clock source = yes, Buildout=0
Bell Atlantic T1 Frame Relay parms: ESF,B8ZS,clock source=no,Buildout=15
Conditions: connectivity across framed connection is lost, FRLMI shows LMI
timeouts.Fixes: can be restored by disabling the T1, and re-enabling or
resetting max.
Conditions: connectivity across framed connection is lost, PRI's will answer
but no prompt appears. (We use a local profile to tcp-clear a telnet session to
127.0.0.1)
M2 (6.0.2-tikm40 8pack modems) - moderate usage (maxes out rarely) Max 4004
Bell Atlantic 2 PRI parms: NI-2, ESF, B8ZS,clock source = yes, Buildout=0
Bell Atlantic T1 Frame Relay parms: ESF,B8ZS,clock source = no, Buildout=0
Conditions: connectivity across framed connection is lost, FRLMI shows LMI
timeouts. Fixes: can be restored by disabling the T1, and re-enabling or
resetting max.
M3 (6.0.0-tikm40 16pack) - low usage - Max 4048
Bell Atlantic 1 PRI parms: NI-2, ESF, B8ZS,clock source = yes, Buildout=0
Bell Atlantic T1 Frame Relay parms: ESF,B8ZS,clock source=no, Buildout=15
Conditions: connectivity across framed connection is lost, FRLMI shows LMI
time-outs. Fixes: can be restored by disabling the T1, and re-enabling or
resetting max.
Conditions: connectivity across framed connection is lost, PRI's will answer
but no prompt appears. (We use a local profile to tcp-clear a telnet session to
127.0.0.1)
I just had to disable the T1 frame to get this info on M3. 1.7 Meg says
"pools -v".
M4 (6.0.2-timm40 12packv34) moderate usage (maxes out during peak times)
Bell Atlantic 2 PRI parms: NI-2, ESF, B8ZS,clock source = yes, Buildout=0
Bell Atlantic T1 Frame Relay parms: ESF,B8ZS,clock source = yes,
Buildout=15
Conditions: connectivity across framed connection is lost, FRLMI shows LMI
time-outs. Fixes: can be restored by disabling the T1, and re-enabling or
resetting max.
Conditions: connectivity across framed connection is lost, PRI's will answer
but no prompt appears. Max 4004
M5 (6.0.0-tikm40 16pack) moderate usage (rarely maxes out during peak times)
Bell Atlantic 2 PRI parms: NTI, ESF, B8ZS,clock source = yes, Buildout=0
Bell Atlantic T1 Frame Relay parms: ESF,B8ZS,clock source = no, Buildout=0
Conditions: connectivity across framed connection is lost, FRLMI shows LMI
timeouts. Fixes: can be restored by disabling the T1, and re-enabling or
resetting max.
Conditions: connectivity across framed connection is lost, PRI's will answer
but no prompt appears. (We use a local profile to tcp-clear a telnet session to
127.0.0.1)
This is a brand new unit (60 days or less). Max 4004
I believe all of these use the same switch, an AT&T 5ess.
My next circus stunt is to break out the Adtran & Motorola external CSU's and
give that a whirl. Also, I plan (worst case scenario) to try an external router
also, which would be ye'ol faithful Xyplex 3000.
Help!!! Any suggestions ? We have tried fclear, fsave, nvram... We tried
fclear, nvram and 30 minutes of reprogramming the max, neither worked. Example
of the fata-hist from M1:
OPERATOR RESET: Index: 99 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 10:37:56
NVRAM was rebuilt
SYSTEM IS UP: Index: 100 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 10:39:51
WARNING: Index: 175 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:01:20
Location: b0046814 b00b32f4 b0157b14 b00883ec b00887dc b0088830
WARNING: Index: 175 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:04:58
Location: b004678c b00b32f4 b00b9ae4 b00b231c b0157e14 b00896bc
WARNING: Index: 175 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:06:13
Location: b004678c b00b32f4 b00b9ae4 b00b231c b0157e14 b00896bc
WARNING: Index: 175 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:06:36
Location: b004678c b00b32f4 b00b9ae4 b00b231c b0157e14 b00896bc
WARNING: Index: 175 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:08:14
Location: b004678c b00b32f4 b00b9ae4 b00b231c b0157e14 b00896bc
WARNING: Index: 175 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:08:14
Location: b004678c b00b32f4 b00b9ae4 b00b231c b0157e14 b00896bc
WARNING: Index: 104 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:09:07
Location: b00f8d5c b0004e4c b00065a4 b0004aec b0112284 b0004b4c
WARNING: Index: 104 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:09:07
Location: b00f8d5c b0004e4c b00065a4 b0004aec b0112284 b0004b4c
WARNING: Index: 104 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:09:07
Location: b00f8d5c b0004e4c b00065a4 b0004aec b0112284 b0004b4c
WARNING: Index: 175 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:10:13
Location: b004678c b00b32f4 b00b9ae4 b00b231c b0157e14 b00896bc
WARNING: Index: 175 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:11:52
Location: b004678c b00b32f4 b00b9ae4 b00b231c b0157e14 b00896bc
WARNING: Index: 175 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:12:14
Location: b004678c b00b32f4 b00b9ae4 b00b231c b0157e14 b00896bc
FATAL ERROR: Index: 29 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:12:46
Location: b023e58c b0004dc4 b00065a4 b0004aec b0112284 b0004b4c
SYSTEM IS UP: Index: 100 Load: ftik.m40 Revision: 6.0.2
Date: 05/08/1998. Time: 17:15:26
Sorry about the long-winded message, you should have seen the rough draft.
-- Tim Connolly tec@mountain.net MountainNet, Inc.
-- (304) 594-9075 ext. 37 2816 Cranberry Square
-- fax (304) 594-9088 Morgantown, WV 26505
-- My signatures are getting longer and longer..
-- If you really want to see it... http://mountain.net/~tec
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>