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

(usr-tc) User problems completing session
by Cheryl Johnson 02 Feb '00

02 Feb '00

Anyone seen this before? Unexpected (IPCP) Layer Down, ID 1, Restarting Link 20963392, for <username>. It sounds like a modem issue on the user side. -Cheryl SEI Data Network Service, Inc A Division of SEI Communications

1 0

Re: (usr-tc) which Radius to use?
by Campbell Simpson 02 Feb '00

02 Feb '00

Nate We're using Merit RADIUS on Solaris 2.6. Depending on what options you need you can either get it for free, or pay a donation to Merit networks. It supports limiting multiple logins etc. www.merit.net We're quite happy with the features and reliability. Campbell >>> euro(a)citipage.com 02/01/00 08:33 >>> Hi, I'm trying to move Radius server that we are using now to a new server but I'm having some problems getting the current radius to run on the new server. So I was thinking of just reinstalling but the old network admin is no longer around and I can't figure out what version of radius we're running one the other box. All I get when I try to find out is: ./radiusd -v ./radiusd: RADIUS version 1.16.1 97/12/16 sun I would really like to use a radius that could check multiple logins. If anyone could point me in the right direction in which radius to use (on Sun Solaris 2.6) and where to get it I'd be much appreciative. Thanks, Nate - 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

Re: (usr-tc) 2.0.51 problems
by cygnus＠vsta.com 02 Feb '00

02 Feb '00

So none of you guys have had the "Local out of service" problem? I reset them in the morning when i come in. I check before i go home and they are out of service again. And it's never the same trunks. sometimes it two, sometimes its six, i've had up to 16 out of service. I would blame it on the telco but WE are the telco and the C.O. people don't have any explainations for this. They insist it's my equipment. RF At 12:50 PM 2/2/00 -0500, you wrote: >>From what I understand from the release notes is that .51 software is for >a specific chipset problem. No new features were added as far as fixes... >from the release notes anyway.... we did notice a pretty good drop in the >amount of disconnects in the 0-3 minute range. > >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.

2 2

RE: (usr-tc) Support Contract survey
by Stainforth, Matthew 02 Feb '00

02 Feb '00

Bear in mind, though, that some of the guys on this list could hire a 3Com engineer for what it would cost to cover all their Total Control equipment with a full service contract. And, to me, charging for software upgrades (read, bugfixes not feature enhancements) is borderline fraud. Charge me money to fix code that doesn't work right? Get real. Matthew Stainforth || Technical Services Manager || BrunNet Inc. > Before I had a contract all kinds of problems getting 3 Com's > help wanted to > kick Total Controls out door but with a contract no > complaints, keep in mind > I have the full support contract and I always get the help I > need or want. I > guess my case is an exception to the rule from what you are > saying, but it > works for me so I cannot complain. If it did not I would > complain believe > me. One thing I do now when I do need to call 3 Com for > support is I ask for > the same person which helps a lot as he knows who I am which expedites > things as he knows when I call we have already tried everything. - 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.

5 4

RE: (usr-tc) 2.0.51 problems
by Stainforth, Matthew 02 Feb '00

02 Feb '00

I know that starting with 2.0.60, the fix for the hung modem pairs problem was to do one of three things: busy out the trunk, reset the DSP chip, or both. I'd have a look and see if your cards are set to busy out the trunks if they detect a hung modem pair since it looks like you're always seeing this in even numbers. I set up my DSPs to just reset the DSP chip and get on with life. Matthew Stainforth || Technical Services Manager || BrunNet Inc. > -----Original Message----- > From: cygnus(a)vsta.com [mailto:cygnus@vsta.com] > Sent: Wednesday, February 02, 2000 1:57 PM > To: usr-tc(a)lists.xmission.com > Subject: Re: (usr-tc) 2.0.51 problems > > > So none of you guys have had the "Local out of service" > problem? I reset > them in the morning when i come in. I check before i go home > and they are > out of service again. And it's never the same trunks. > sometimes it two, > sometimes its six, i've had up to 16 out of service. > I would blame it on the telco but WE are the telco and the C.O. people > don't have any explainations for this. They insist it's my equipment. > > RF > > At 12:50 PM 2/2/00 -0500, you wrote: > >>From what I understand from the release notes is that .51 > software is for > >a specific chipset problem. No new features were added as > far as fixes... > >from the release notes anyway.... we did notice a pretty > good drop in the > >amount of disconnects in the 0-3 minute range. > > > >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. > - 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) Support Contract survey
by Stainforth, Matthew 02 Feb '00

02 Feb '00

Frankly I'm surprised she's still employed with 3Com. She's the reason I don't buy support contracts anymore. But maybe she's just a symptom of a much larger problem. Matthew Stainforth || Technical Services Manager || BrunNet Inc. > -----Original Message----- > From: Paul Farber [mailto:farber@admin.f-tech.net] > Sent: Wednesday, February 02, 2000 11:41 AM > To: usr-tc(a)lists.xmission.com > Cc: bruce_claflin(a)mw.3com.com; karl_swanson(a)mw.3com.com; > thomas_goodman(a)mw.3com.com; george_ebert(a)mw.3com.com; > glenn_gibney(a)mw.3com.com; irfan_ali(a)mw.3com.com > Subject: Re: (usr-tc) Support Contract survey > > > Add my results: > > NO I WILL NOT RENEW (see below) ANY SERVICE CONTRACT > > and > > NO I WILL NOT BE PURCHASING ANY NEW 3COM EQUIPMENT. > > I just got off the phone with Ms. Michelle Catalano who said my > $1200 support contract would not be honored... even though > they got the > money for it already. > > I have 3 chassis at 3 locations and only *want* coverage for > a specific > site with specific needs. It's a simple chassis, 2 DSP's, 1 > arc.... plain > jane setup. > > Needless to say I have contacted 3 ASCEND/LUCENT vendors and > will not be > purchasing ANY more 3Com equipment. Sorry 3Com.... that's 1 > new site you > won't be at (96 ports) and one site I will be converting (48 > ports). Does > the business unit understand that loosing $15K-20K over a > $1200 software > upgrade (who actually calls support anymore... I think we've > all learned > the 'value' of phone based support) > > Since this message is being CC'ed to (hopefully) some understanding > management at 3Com, there is a person on the xmission list (krish?) > that has been worth thier weight in gold.... give that person > a raise and > maybe learn a bit from how that person does support us. > > I will add the 2.0.51 DSP code seems to have calmed down the chassis a > bit... to bad it took the 2.0.60 and 2.0.81 'tries' to get it. > > Paul Farber > Farber Technology > farber(a)admin.f-tech.net > Ph 570-628-5303 > Fax 570-628-5545 > > On Wed, 2 Feb 2000, Jeff Mcadams wrote: > > > OK...here are initial results of the support contract > informal survey. > > I only heard from 13 people (including myself :)...a mere > fraction of > > the number of people on the list in total. Keep sending the > > information...I'll continue to tabulate and have more > updates as I hear > > from more people. > > > > The current count is 9 people don't have support contracts, > and 4 do. > > > > Some notes: > > > > - One "yes" only had software coverage even though they > would have liked > > to have greater coverage. They had to settle for software-only > > because of the cost > > > > - One "no" actually has coverage on a chassis, but only because that > > chassis was bought new and came with > coverage...apparently you can't > > buy a chassis anymore without coverage...interesting > loophole in the > > contract rules here. This person indicated that they > would rather > > have *not* gotten the coverage on the contract as they > thought it > > was a waste of money. > > > > Many of the people that emailed me as a "no" mentioned it > was the cost > > and/or the rules that prevented them from getting a contract. > > > > I will re-iterate that I believe that the root of the > problem stems from > > 3Com considering Customer Service as a "Business Unit". In > other words, > > they want Customer Service to be a revenue positive part of > 3Com. While > > my previous posting that discussed this was somewhat inaccurate (the > > Customer Service Organization, CSO, apparently doens't get > the revenues > > from the support contracts, the business unit that sells > the equipment - > > in the case of TC, its the Network Systems Business Unit - gets the > > revenues...the whole thought of trying to make Customer > Service revenue > > positive ends up with an attitude that ends up screwing the > customer. > > > > I just recently went through the process of trying to > obtain a service > > contract again...partially to try to determine if any > improvements had > > been made to the process...partially to find out if the "Unbundled > > Service Options" on 3Com's web site would be useful > here...and partially > > because we really would like to have some coverage on some of our > > equipment. The current status is that the support coverage > rules are > > still in place (contracts purchased per-chassis rather than > per-card, > > and all chassis at a site have to have the same coverage...of course > > last time we tried to have different coverage at different > sites 3Com > > didn't honor it), the support options listed as sold items (ie, not > > special deals that are made for specific instances) were largely the > > same as they've been for the past 3 years. The best I got from the > > discussion was that service options could be discussed (ie, > a special > > deal is how I understand this) if its "a sound business > case that makes > > sense for the customer and for 3Com." Let me suggest that a sound > > business case for 3Com would be to not lose their customers which is > > what is happening...3Com is verging towards losing us as a customer > > even...and we've been a USRobotics/3Com customer for at > least 5 years > > (35 Amp power supplied and dual analog 14.4 modems) > > -- > > Jeff McAdams Email: jeffm(a)iglou.com > > Head Network Administrator Voice: (502) 966-3848 > > IgLou Internet Services (800) 436-4456 > > > > - > > 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.

2 1

(usr-tc) 2.0.51 problems
by cygnus＠vsta.com 02 Feb '00

02 Feb '00

Hey guys, I've been lurking for a long time and using much of the advice that pertained to similar problems i had with my TC equipment. I've seen a lot of good talk about the 2.0.51 software and everyone seems to be happy with it. Has anyone had any trouble with it? I loaded 2.0.51 and 2.0.60 onto one chassis and have been having trouble with 2.0.51 making trunks go "local out of service". The cards with 2.0.60 are working well. I tried loading 2.0.60 into the cards with the .55 hardware but that caused different problems (mostly instant disconnects). Loading 2.0.81 makes the cards not answer calls at all. These are five new HiperDSP cards purchased in December and just installed. I find it hard to believe that i would get 5 bad DSP cards (I guess it's possible) Has anyone else had this type of problem with 2.0.51? BTW: I have two more chassis and experienced the same problem with the existing cards. I reverted back to 2.0.81 and all worked well again. Thanks for any info Rudy Ferguson VstaNet 1 3COM High-Density 24 Channel 1OQ 0.53.0 8192 2048 2.0.60 2 3COM High-Density 24 Channel 1OQ 0.53.0 8192 2048 2.0.60 3 3COM High-Density 24 Channel 1OQ 0.51.0 8192 2048 2.0.60 4 3COM High-Density 24 Channel 1OQ 0.49.0 8192 2048 2.0.60 5 3COM High-Density 24 Channel 1OQ 0.53.0 8192 2048 2.0.60 6 3COM High-Density 24 Channel 1OQ 0.55.0 8192 2048 2.0.51 7 3COM High-Density 24 Channel 1OQ 0.55.0 8192 2048 2.0.51 8 3COM High-Density 24 Channel 1OQ 0.55.0 8192 2048 2.0.51 9 3COM High-Density 24 Channel 3C4 0.49.0 8192 2048 2.0.60 10 3COM High-Density 24 Channel 1OQ 0.55.0 8192 2048 2.0.51 16 3COM HiPer ARC NAC 28B 19.0.0 131072 16384 4.2.32 17 3COM Network Management Card with clock 2DY00000 7.0 16384 8192 6.1.17 - 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) 2.0.51 problems
by Blake Fithen 02 Feb '00

02 Feb '00

We've had pretty good luck with 2.0.51. It has eliminated the two-modem failure problem, connect rates and throughput look about the same. We have it on about 50 DSP cards with several hardware revs. in 5 hiper arc chassis. blake -----Original Message----- From: cygnus(a)vsta.com [mailto:cygnus@vsta.com] Sent: Wednesday, February 02, 2000 11:08 AM To: usr-tc(a)lists.xmission.com Subject: (usr-tc) 2.0.51 problems Hey guys, I've been lurking for a long time and using much of the advice that pertained to similar problems i had with my TC equipment. I've seen a lot of good talk about the 2.0.51 software and everyone seems to be happy with it. Has anyone had any trouble with it? I loaded 2.0.51 and 2.0.60 onto one chassis and have been having trouble with 2.0.51 making trunks go "local out of service". The cards with 2.0.60 are working well. I tried loading 2.0.60 into the cards with the .55 hardware but that caused different problems (mostly instant disconnects). Loading 2.0.81 makes the cards not answer calls at all. These are five new HiperDSP cards purchased in December and just installed. I find it hard to believe that i would get 5 bad DSP cards (I guess it's possible) Has anyone else had this type of problem with 2.0.51? BTW: I have two more chassis and experienced the same problem with the existing cards. I reverted back to 2.0.81 and all worked well again. Thanks for any info Rudy Ferguson VstaNet 1 3COM High-Density 24 Channel 1OQ 0.53.0 8192 2048 2.0.60 2 3COM High-Density 24 Channel 1OQ 0.53.0 8192 2048 2.0.60 3 3COM High-Density 24 Channel 1OQ 0.51.0 8192 2048 2.0.60 4 3COM High-Density 24 Channel 1OQ 0.49.0 8192 2048 2.0.60 5 3COM High-Density 24 Channel 1OQ 0.53.0 8192 2048 2.0.60 6 3COM High-Density 24 Channel 1OQ 0.55.0 8192 2048 2.0.51 7 3COM High-Density 24 Channel 1OQ 0.55.0 8192 2048 2.0.51 8 3COM High-Density 24 Channel 1OQ 0.55.0 8192 2048 2.0.51 9 3COM High-Density 24 Channel 3C4 0.49.0 8192 2048 2.0.60 10 3COM High-Density 24 Channel 1OQ 0.55.0 8192 2048 2.0.51 16 3COM HiPer ARC NAC 28B 19.0.0 131072 16384 4.2.32 17 3COM Network Management Card with clock 2DY00000 7.0 16384 8192 6.1.17 - 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) Support Contract survey
by Stainforth, Matthew 02 Feb '00

02 Feb '00

Let me chime in here with a resounding "amen". I can tell you beyond a shadow of a doubt that I would go with a different vendor if I could do it all over again. But I inherited this mess and so I'm stuck with it. And I do the best I can. Matthew Stainforth || Technical Services Manager || BrunNet Inc. > sense for the customer and for 3Com." Let me suggest that a sound > business case for 3Com would be to not lose their customers which is > what is happening...3Com is verging towards losing us as a customer > even...and we've been a USRobotics/3Com customer for at least 5 years > (35 Amp power supplied and dual analog 14.4 modems) - 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) Support Contract survey
by Marty Elliott 02 Feb '00

02 Feb '00

Paul -- isn't mind-reading over the internet a bit unfair????!!!! ;~} hmmmmmmm Marty At 11:37 AM 02/02/2000 -0500, you wrote: >An EXELLENT business idea just hit me. If a vendor had 'Card Replacement >Plan'. IE, for X a month ($20-50) if your ARC/NMC/DSP goes south you call >them and they overnight you (i mean really overnight. next day incl sat.) >a replacement card while your's is under warranty repair. When you get >your's back you return the NIC/NAC and you are in business. > >Face it.. most of us just want the hardware replacement and all new gear >comes with 5 year warranty... unless you pay for support you have >to wait 2-4 weeks for the repair. > >We would win as we get the next day card from a vendor (who would keep the >code up to date) and the vendor would win cause $50 a month from 50 ISP's >is $2500 a month.. more than ehough to keep cards in stock and mail them >out. > >You pay $240-$600/year for your entire site coverage (for any/all cards) >and you get what you want.. minimal downtime. > >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. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Marty Elliott MARS, Inc. 2105 South 48th Street Suite 104 Tempe, AZ 85282 602-426-8272 602-454-0770 fax www.2assetrecovery.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - 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