January 2000 - USR-TC - mailman.xmission.com

Re: (usr-tc) HiPerDSP stops at 21
by Jason A. Nunnelley 26 Jan '00

26 Jan '00

See if you telco capped your inbound available calls... JN ----- Original Message ----- From: "David Swearingin" <david(a)carolnet.com> To: <usr-tc(a)lists.xmission.com> Sent: Monday, January 24, 2000 12:00 AM Subject: (usr-tc) HiPerDSP stops at 21 > I have one HiPER DSP that has 21 active calls and then returns a busy signal, > even though there should be three more modems available. Any suggestions as > to why this is happening? > > David > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. > - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

3 2

RE: (usr-tc) DSPCode 2.0.51
by Stainforth, Matthew 26 Jan '00

26 Jan '00

I've been getting reports of non-winmodem sportsters and couriers having the same prob with 2.0.60 > -----Original Message----- > From: Scot Desort [SMTP:scot@njaccess.net] > Sent: Tuesday, January 25, 2000 6:20 PM > To: usr-tc(a)lists.xmission.com > Subject: Re: (usr-tc) DSPCode 2.0.51 > > I _think_ I've some improvement in disconnects running 2.0.51. Don't know > about Rockwell improvements. > > I had a USR Sportster 56K _non_ winmodem having handsaking problems this > morning on 2.0.81 and 2.0.19. He hit a 2.0.51 card and all was well. Could > have been a co-inki-dink. > > -- > Scot > > > > ----- Original Message ----- > From: Charles Sprickman <spork(a)inch.com> > To: <usr-tc(a)lists.xmission.com> > Sent: Tuesday, January 25, 2000 4:08 PM > Subject: Re: (usr-tc) DSPCode 2.0.51 > > > > On Tue, 25 Jan 2000, Brian wrote: > > > > > 2.0.51 is good for all DSP's > > > > How's it compare to 2.0.81? Better, worse, indifferent? > > > > Charles > > > > > On Tue, 25 Jan 2000, Cheryl Johnson wrote: > > > > > > > Is this code only recommended for hardware revisions .54 and .55 > only? > > > > I have .49 and was thinking of moving to the 2.0.51 from the 2.0.60 > > > > since I do not see too many improvements. And is this compatible > with > > > > NMC 6.1.17 and ARC 4.1.22? It seems to be getting more difficult to > > > > keep these things straight. > > > > > > > > -Cheryl Johnson > > > > SEI Data Network Services, Inc. > > > > A Division of SEI Communications > > > > > > > > > > ----------------------------------------------------- > > > Brian Feeny (BF304) signal(a)shreve.net > > > 318-222-2638 x 109 http://www.shreve.net/~signal > > > Network Administrator ShreveNet Inc. (ASN 11881) > > > > > > > > > - > > > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > > > with "unsubscribe usr-tc" in the body of the message. > > > For information on digests or retrieving files and old messages send > > > "help" to the same address. Do not use quotes in your message. > > > > > > > > > - > > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > > with "unsubscribe usr-tc" in the body of the message. > > For information on digests or retrieving files and old messages send > > "help" to the same address. Do not use quotes in your message. > > > > > - > To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" > with "unsubscribe usr-tc" in the body of the message. > For information on digests or retrieving files and old messages send > "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

4 3

(usr-tc) Rip Routing question
by Mark Thornton 26 Jan '00

26 Jan '00

We, like others tried to implement OSPF because it was supposed to be the holy grail of internal routing as far as 3Com was concerned. I had high hopes for it because we have occasional lapses in RIP2 propogation to the Cisco router. By that I mean occasionally the rip routes for a given chassis just disappear, then reappear after about 20 to 30 minutes. I had to place static routes to each chassis defining the space containing the assigned ip address pool to get consistent access for the majority of our clients. Dedicated ip clients still occasionally experienced the problem until I put a static route to one of the Arcs for each client. If the RIP was working it seemed to overide the static route, if not the traffic bounced of the Arc on to the correct Arc in most cases. 3Com was of abosolutely no help on this matter while we were under contract, hence no current contract. I never could get OSPF to work but that is probably because I have never worked with it before and the docs are a bit thin on application. Has anyone else experienced RIP problems? I thought it might be someone stuffing the Cisco with bad routes so I moved to authenticated RIP with no change in behaviour. I haven't removed the static routes since we got to 4.2.32-1 to see if the problem is still there. Mark Thornton San Marcos Internet, Inc. 512-393-5300 - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

2 1

(usr-tc) DSPCode 2.0.51
by Cheryl Johnson 26 Jan '00

26 Jan '00

Is this code only recommended for hardware revisions .54 and .55 only? I have .49 and was thinking of moving to the 2.0.51 from the 2.0.60 since I do not see too many improvements. And is this compatible with NMC 6.1.17 and ARC 4.1.22? It seems to be getting more difficult to keep these things straight. -Cheryl Johnson SEI Data Network Services, Inc. A Division of SEI Communications

6 6

(usr-tc) Missing Radius records... was Billing Software
by Mark Thornton 26 Jan '00

26 Jan '00

There has been a fair amount of discussion about missing radius records, specifically stop records as regards to concurrency control. I posted a question about this a week or so back and didn't get a response. In my case I have a single chassis that is prone to this problem, but the others are not. Any ideas why? Also, if getting the stop record is so unreliable how do those of you who do hourly billing keep the system working? In our case the session is lost and not billed for. I can live with that but it bothers me that it isn't reliable. Mark Thornton San Marcos Internet, Inc. 512-393-5300 - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

4 4

Re: (usr-tc) (USR-TC) MISSING RADIUS R
by Steve Valiunas 26 Jan '00

26 Jan '00

I've also seen cases where the NAS was talking to a remote radius server over shakey/saturated links, causing a lot of radius retransmissions- If the Radius server can't handle starts & stops coming in out of order, then session-limiting based on this will break. In at least a couple of cases things cleaned up by fixing the link. To see if this might be contributing to the problem, compare the count of retransmitted accounting packets between the working and not working Harcs ("show accounting counters"). It -might- be as simple as that. Of course this isn't likely if all the chassis are local. STeve jeff.binkley(a)asacomp.com (Jeff Binkley) on 01/26/2000 09:15:21 AM Please respond to usr-tc(a)lists.xmission.com Sent by: jeff.binkley(a)asacomp.com (Jeff Binkley) To: USR-TC(a)LISTS.XMISSION.COM cc: (Steve Valiunas/MW/US/3Com) Subject: (usr-tc) (USR-TC) MISSING RADIUS R U>There has been a fair amount of discussion about missing radius U>records, specifically stop records as regards to concurrency control. U>I posted a question about this a week or so back and didn't get a U>response. In my case I have a single chassis that is prone to this U>problem, but the others are not. Any ideas why? U>Also, if getting the stop record is so unreliable how do those of you U>who do hourly billing keep the system working? In our case the session U>is lost and not billed for. I can live with that but it bothers me U>that it isn't reliable. U>Mark Thornton U>San Marcos Internet, Inc. U>512-393-5300 Unfortunately it is a HiPerArc problem that crept in at a certain release of code. 3Com claims it has been fixed in the newer code but with the problems many folks have had, including myself, with the newer code, some folks are afraid to try it. I plan to try another HiPerArc upgrade soon. Jeff Binkley ASA Network Computing CMPQwk 1.42 9999 - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message. - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

Re: (usr-tc) Quad ana/dig modem not taking calls (another case of)
by Ray Whelan 26 Jan '00

26 Jan '00

Hi Dan , Am I correct in thinking from your original mail both Analog and Digital were failing, from your Debug you attached in you second mail Analog call connect. What I see from the Debug is a follows Working Analog calls Failed Digital Call Telco Nas Telco Nas I -3 -> I -3 -> A-1 <- A1 ( 5seconds) 0 A1 A-3 3 A1 3 A1 -----> Clear Fwd 3 A1 I-3 A3 ii-1 B6 <- Answer The problem is when a Digital calls comes form your telco, we get the first digit and we respond to it with a A-1, The telco should then should send the next digit but the NAS times out ( normal condition) as no other digits or recieved, the NAS then sends a digit complete , but the telco send a clear forward . Two issues to look into either telco not seeing our A-1 or there is a problem with the telco digital call service. Talk to your telco make sure you service can have a digital service. Regards Ray Whelan - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

2 1

(usr-tc) Motorola SM56
by Brian 26 Jan '00

26 Jan '00

I am having some clients report that they are having problems connecting with Motorola SM56 modems (we are on DSP 2.0.51). Has anyone else seen this? any known fixes? ----------------------------------------------------- Brian Feeny (BF304) signal(a)shreve.net 318-222-2638 x 109 http://www.shreve.net/~signal Network Administrator ShreveNet Inc. (ASN 11881) - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

2 1

(usr-tc) Re: usr-tc) Motorola SM56
by Greg owens 26 Jan '00

26 Jan '00

Brian...Had the same problem here a few weeks ago you might try some of the init strings found at http://www.motorola.com/networking/products/sm56_ac-l/index.html I finally got the modem to connect about 7 out of 10 trys. Thats the best we could ever do. Greg Owens Magnolia Internet Services http://www.magnolia-net.com I am having some clients report that they are having problems connecting with Motorola SM56 modems (we are on DSP 2.0.51). Has anyone else seen this? any known fixes? ----------------------------------------------------- Brian Feeny (BF304) signal(a)shreve.net 318-222-2638 x 109 http://www.shreve.net/~signal Network Administrator ShreveNet Inc. (ASN 11881)

1 0

(usr-tc) Problems with HiperARC 4.2.32
by Jorge Lozano 26 Jan '00

26 Jan '00

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have 4 Hiper ARC, three with 4.1.72 and just one with 4.2.32 software version Everyone work with my RADIUS server, but after a minutes... the hiper with 4.2.32 begin to send garbage in the password field.... I reboot the card and everything its ok again... for some minutes... :-) Can somebody help me with this anormal situation? Jorge Lozano -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.2 for non-commercial use <http://www.pgp.com> iQA/AwUBOI43zqp3oywyFVUlEQJL9gCg8VO0ZbhNleK4RwWYq/D/TByfwKMAoPh9 /JnaRqALsKyPCq/s4SnRk6jy =AK0h -----END PGP SIGNATURE----- - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0