- USR-TC - mailman.xmission.com

Re: (usr-tc) static to dynamic
by david＠carolnet.com 26 Jan '00

26 Jan '00

You wrote: > From: D A Substanley <das(a)gol.com> > To: usr-tc(a)lists.xmission.com > Date: Thu, 27 Jan 2000 12:33:12 +0900 > Subject: Re: (usr-tc) static to dynamic > > > Enable nmc chassis awareness > > das Didn't work for me. 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.

1 0

(usr-tc) static to dynamic
by david＠carolnet.com 26 Jan '00

26 Jan '00

How do I "set chassis slot x type" from static to dynamic? David __________________________________________________ David Swearingin (david(a)carolnet.com) CARROLLTON INTERNET SERVICE (www.carolnet.com) First Financial Group, Inc. 11 N. Folger, Carrollton, MO 64633 660-542-3002 Fax 660-542-3003 - 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) 2.0.51 improvements
by Paul Farber 26 Jan '00

26 Jan '00

hello all... after the discussion of the 2.0.51 performance.. I'm gonna give it a shot. the release notes (we all read the release notes... don't we?) 3Com has 'resolved' MR2346: improved connections with Rockwell HCF modems with roundtrip delays of 30-40ms. Also v42 detection has been improved...... well there's 2 bits of good new. Paul Farber Farber Technology farber(a)admin.f-tech.net Ph 570-628-5303 Fax 570-628-5545 - 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) Ascend to 3com
by Scott Boggs 26 Jan '00

26 Jan '00

I use the TotCtrl chassis and Ascend Maxes (6000&4000) I have found that the Maxes are much more reliable for some user modem types. It is my Failsafe if the user cant connect to the 3com. Scott Boggs AccessUnited ISP > -----Original Message----- > From: Brian Burgmeier [SMTP:brianb@ntwrld.com] > Sent: Wednesday, January 26, 2000 6:07 PM > To: usr-tc(a)lists.xmission.com > Subject: (usr-tc) Ascend to 3com > > We are in the process of merging two ISPs. Our ISP runs on > the 3Com Hiper Arch Chassis the other ISP runs on Ascend. > Since we both use ELI for our Channelized T-1s we are > considering porting their dial in number over to our 3Com chassis > at our location.. > What problems should we anticipate moving customers from > an ASCEND unit to 3com? Both are using the "V90 standard." > protocol. Would we be better off using > their ASCEND equipment? Any feedback is appreciated. > > > Thanks -Brian > > << File: Card for Brian Burgmeier >> - 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

Re: (usr-tc) DSPCode 2.0.51
by Mark Lemmert 26 Jan '00

26 Jan '00

At 05:30 PM 1/25/00 -0600, Brian wrote: >I have seen more connection success rate with 2.0.51. I use to get 94-98% >connection success overall for all calls to a chassis for a 24 hour >period. > >I now see more like 96-98% average. How do you get those sorts of statistics? I have been having a very large number of complains from people saying the can't connect. I am running 2.0.81. Thanks. -MGL >On Tue, 25 Jan 2000, Charles Sprickman wrote: > > > 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. > > > >----------------------------------------------------- >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. Mark Lemmert CTO AthEnet Data Exchange 920-954-9799 mark.lemmert(a)athenet.net - 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) Global Access list on arc's
by Brian 26 Jan '00

26 Jan '00

Can you make a global access list on the ARC's, basically like an access list applied to its eth interface, so that it applies to all users? I don't want to enable it via radius, I just want to do this via CLI (its an access list to prevent stuff to our core). Brian ----------------------------------------------------- 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 2

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

26 Jan '00

Dan, A = active and C= configured this means that if you reset the cared the C becomes active, If both are the same this should not be an issue if you save the configuration. 30 second after reset is normal for this card to become active after reset. Ray Whelan Dan Borlovan <danb(a)dnttm.ro> on 26/01/2000 13:28:54 Please respond to usr-tc(a)lists.xmission.com Sent by: Dan Borlovan <danb(a)dnttm.ro> To: Ray Whelan <Ray_Whelan(a)eur.3com.com> cc: usr-tc(a)lists.xmission.com (Ray Whelan/IE/3Com) Subject: Re: (usr-tc) Quad ana/dig modem not taking calls (another case of) On Wed, 26 Jan 2000, Ray Whelan wrote: > 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 . You can call me stupid. Yes the e1/cas got the first digit, sent the A-1, but the telco didn't recognize the A-1 so it never sent the other digits. The problem: the e1/cas had the 'companding' setting on 'use modem country code'. Well, the digital modems are for europe (A-law) and the analog/digitals are for US (u-law). I wonder how an A-law encoded signal sounds after decoded with u-law. And viceversa. The 'companding' is set to A-law now, and all the modems are taking calls. Now an unrelated question: the e1/cas shows 'project id' as a=R2 q=Q412, but I can set only one value for 'project id'. As a result, each time I reset the e1/cas card, I have to do it twice, because after first reset the a= and c= values are incorrect (both Q421 or R2), and after the seconde reset it takes about 30s to detect the correct values and start taking calls. Is there anything that can be done? Dan -- Dan Borlovan <danb(a)dnttm.ro> System Administrator, Network Operation Center Dynamic Network Technologies - Timisoara, Romania Telefon: +40-56-204967 FAX: +40-56-220201 - 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) 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