October 1999 - USR-TC - mailman.xmission.com

Re: (usr-tc) 2.0.60 HDM Code
by Todd Keister 21 Oct '99

21 Oct '99

ER or Engineering Release Code is only available by calling to Tech Support, and then WE (Tech Support) must get permission to release the code. This is done so that we can document the use of these special codes to see if the fix the specific issue they are supposed address, and also to see if the new fix for one issue causes issues with any other processes in the code or product. If you wish to contact us, we're here 24x7. 3Com Tech Support (800) 231-8770 (please note that after hours support does require an after hours contract). I hope this helps. Todd ;-} Curt Shambeau <curt(a)execpc.com> on 10/12/99 11:35:09 AM Please respond to usr-tc(a)lists.xmission.com Sent by: Curt Shambeau <curt(a)execpc.com> To: usr-tc Mailing List <usr-tc(a)lists.xmission.com> cc: (Todd Keister/MW/US/3Com) Subject: Re: (usr-tc) 2.0.60 HDM Code > Is anyone using HDM 2.0.60.0 code. It is an Engineering Release which > implements a DSP reset whenever the DSP goes idle on both ports. It is > a temporary fix to the hanging pair of modems problem, but I just wanted > some feedback, if any was available, before we put it on any of our > production modems. Is this code posted someplace, or is it available only by calling their tech support department? --------------------------------------------------------------------- | Curtis V. Shambeau | curt(a)execpc.com | Senior Vice President | | ExecPC, Inc. - A Voyager.net company - NASDAQ Symbol: VOYN | --------------------------------------------------------------------- - 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.

20 45

RE: (usr-tc) 3com Support Woes
by Stainforth, Matthew 21 Oct '99

21 Oct '99

Well let me add my vote in for the "disgruntled masses". I, for one, can tell you I will NEVER buy another service contract after the harassment I was put through last time by logistics. In the past two years, the I have only had to make one call to tech support, for which I paid 'per incident'. After two hours of 3Com yelling "TELCO ISSUE" and the telco yelling "YOUR EQUIPMENT", I ended up hanging up and finding the problem myself. Matthew > -----Original Message----- > From: Ed [mailto:ed@taylors.com] > Sent: Friday, October 15, 1999 12:03 AM > To: usr-tc(a)lists.xmission.com > Subject: (usr-tc) 3com Support Woes > > > I cannot believe how many people keep coming out of the > woodwork that feel > the same way about 3com's support issues. Seems like everyone > is disgruntled > about it. When you speak to 3com they tell you people are > happy and like the > changes being made and you are the only one complaining. What a smoke > screen. > > I believe 3com Executives and Stockholders should actually > read this list > sometime... > > > Ed > > ----- Original Message ----- > From: Richard Lorbieski <richard(a)alpha1.net> > To: <usr-tc(a)lists.xmission.com> > Sent: Thursday, October 14, 1999 10:40 PM > Subject: Re: (usr-tc) RE: (USR-TC) 2.0.60 HDM C > > > Sorry, but only people with service contracts can visit the > 3Com booth. > > Sheldon Koehler wrote: > > > > Maybe we should all gang up at ISPCon and do a mass > movement from the 3Com > > booth over to the Cisco booth and see if 3Com notices then... > > > > ----- Original Message ----- > > From: Brian <signal(a)shreve.net> > > To: <usr-tc(a)lists.xmission.com> > > Sent: Wednesday, October 13, 1999 8:50 PM > > Subject: Re: (usr-tc) RE: (USR-TC) 2.0.60 HDM C > > > > > > > > I had the same shit happen. She couldn't get it thru her > head that we > had > > > SOLD half the stuff they had us listed down for. We SOLD > it because it > > > was quad modem technology and its a good thing too, > because we would be > > > screwed had we not sold, and 3com doesn't make a support > contract to fix > > > you if you got a quad chassis.......not good enough > anyways, its all > > > EOL'ed. > > > > > > It took I want to say 18+ months of negotiations between > our 3com rep, > us, > > > and 3com support contract people. To this day we have > not been able to > > > get contracts because we can't come to an agreement on > how the stuff > > > should be priced. > > > > > > > > > On Wed, 13 Oct 1999, Charles Sprickman wrote: > > > > > > > > > > > On Wed, 13 Oct 1999, Jeff Binkley wrote: > > > > > > > > > Unless I am mistaken they do offer software only > contracts. I've > seen > > > > > them on Tech Data's price listing. They are > generally less than > half > > of > > > > > the full service contracts. > > > > > > > > They are still pricey. And on top of the price, we > started getting > > > > harrassing phone calls from some lackey in the 'service > contract' > > > > department saying: > > > > > > > > -rude 3Com lady: "Are you SUUUURE that you only have X chassis?" > > > > > > > > -me: "Yes. That's why I bought X contracts." > > > > > > > > -rude 3Com lady: "Well you HAVE to buy a contract for > each chassis" > > > > > > > > -me: "Yes." > > > > > > > > -rude 3Com lady: "You're SUUURE you only have X chassis?" > > > > > > > > -me: "Tell you what. Put me down for one, I'm selling > the rest of > this > > > > crap off." > > > > > > > > I didn't even buy direct from 3Com, but via a reseller. They > apparently > > > > have the time and money to put losers like this on the > phone to harass > > > > customers about the number of contracts they have > versus the number of > > > > chassis they've purchased in the last 3 years. What a > waste. What > > > > arrogance. > > > > > > > > I'll mention also that I have contracts (24x7x4) on our > high-end Cisco > > > > routers that cost LESS than putting full support with no > > > > "spare-in-the-air" support on all our TCH stuff. And > I've been told > by > > > > numerous Cisco employees; support, sales, engineering > that they let > > people > > > > slide on most support/software issues. They frown on 'version > jumping' > > > > where you go and thieve say IOS w/Firewall support when > you bought > basic > > > > IP, but I've had so many instances where I've received > support/software > > on > > > > equipment with no contract. I've even told the guy on > the phone "I > have > > > > no contract" and the basic response is "We want you to > be happy. Your > > > > hardware fried? We'll send you new... You need IOS > 12.x to fix this > > bug? > > > > Here it is." > > > > > > > > Why can't 3Com adopt at least some of this attitude? > It's not like > > > > Pilgrim is feature-packed like IOS, we're all just > looking for solid > > > > connects and standard routing features... > > > > > > > > Charles > > > > > > > > > Jeff Binkley > > > > > ASA Network Computing > > > > > > > > > > > > > > > U>I think Brian is on the right track here. Perhaps > 3COM can split > > their > > > > > U>service contracts into 2 categories - firmware > download only, and > > full > > > > > U>support with download and telephone support. > > > > > > > > > > U>Those of us new to the platform (myself included) > might benefit > from > > > > > U>the convenience of knowing that phone support is > available 24x7 > when > > > > > U>you're staring at a box not taking calls at 2AM. > But once you get > > the > > > > > U>hang of TC and know how to troubleshoot these > things on your own > (or > > > > > U>at least with the added help of those on this > list), you can drop > > the > > > > > U>tel support, and just pay for code updates. > > > > > > > > > > U>Does any of this matter to those on this list that > are complaining > > > > > U>about 3COM's lack of timely response to code > issues? Probably not. > > > > > U>Should 3COM redirect it's efforts to resolving > these issues? Yep. > > > > > U>Should they perhaps head-up a small team (1 person) > to field code > > > > > U>enhancement and bug fix requests, both from an > email/web input > area > > on > > > > > U>the 3COM ISP pages, but also through monitoring of > this list and > the > > > > > U>totalcontol newsgroups? Absolutely. 3COM may > already be doing this > > > > > U>"behind the scenes", quietly tracking and logging > this stuff, but > > it's > > > > > U>apparent that the people who need to know the most > that it's being > > > > > U>done and being worked on, the ISP customers, don't know that > someone > > > > > U>has acknowledged the problem and it has been placed into an > > > > > U>engineering queue. > > > > > > > > > > U>I think that things like this would greatly improve > 3COM's image > > among > > > > > U>it's ISP customers, and even more so if they acted > expediently on > > > > > U>these issues that trouble so many on this list. > Give the telephone > > > > > U>support staff access to the database created as a > result of these > > > > > U>pages (hell, give us access to these pages as well, > even WITHOUT a > > > > > U>contract). Tie the ER/SR releases to the database, > so it's easier > to > > > > > U>identify which bug is fixed with which release. And most > > importantly, > > > > > U>of allowing us to view this database to obtain the status a > > confirmed > > > > > U>of bug and it's up-to-date progress in getting > resolved would be > > > > > U>tremendous benefit. To know that someone is > actually WORKING on > > Jeff's > > > > > U>SNMP issue by simply searching the database is > comforting (knowing > > > > > that > > > > > U>it will be fixed QUICKLY is even better). Some of > this status > > > > > U>information may already be in the 3KB, but a > dedicated database > for > > TC > > > > > U>code issues and status reports would be really great. > > > > > > > > > > U>Scot > > > > > U>NJAccess > > > > > > > > > > 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. > > > > > > > > > > ----------------------------------------------------- > > > 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. > > -- > > Richard Lorbieski - richard(a)alpha1.net > Chief Technical Officer - Senior System Administrator > Alpha1 Internet http://www.alpha1.net > 409.731.8236 - 877.4.alpha1 (877.425.7421) > > - > 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.

1 0

RE: (usr-tc) badmodems.pl
by Jolliffe, Anu 21 Oct '99

21 Oct '99

Another quick question about this script. How exactly do I set the failure rate percentage, which triggers the notification? - 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) ISPCon/3Com Open Meeting
by Allen Marsalis 21 Oct '99

21 Oct '99

At 09:15 PM 10/15/99 -0400, Lon R. Stockton, Jr. wrote: >On Fri, 15 Oct 1999, Allen Marsalis wrote: > >> I have no regrets.. x2 was a big deal in our area (we certainly helped) >> and being the first 56k provider in our area was a big win for us. >> USR made that happen.. I liked USR.. It's 3com that I feel ill about. > >Agreed here too. Getting my TC rack was a big win for us, and having it >still is. We were first with x2, first with v.90, and our v.90 *still* >walks all over my competitions' PM-based dialup pools. And we're still >the only provider in town doing ISDN, which is the best thing you can >get here aside from a dedicated line. (and we're served by Sprint, who >has some really good ISDN BRI pricing...only about $5 more than two >regular phone lines and flat-rate to boot...not to mention that inbound >PRIs are about 1/2 the cost of CT1's). Same here. That's pretty much exactly how we feel about it. However we occationally find a user with a good sportster/3com modem who can't get v.90 on our TCS but can on our TNT (eval) and more importantly, can with our competitors. Users won't stay with 28.8 when they can get 48k elsewhere.. If there were no modem code issues, I'd be more than happy to send the eval back. Instead, I'll probably get an invoice... > >> Do we use 3com switches or routers? no we use cisco, foundry, etc.. > >I'm actually a fan of their switches. But one doesn't have the same >problems...either a ethernet switch works or it doesn't. If it's Well back when we started, we bought a superstack and it worked of course but when I found out it was half-duplex on all 10T ports, we sent it back and opted for a catalyst.. But nowadays I'm sure things are different. We outgrew the catalyst and now have a fastiron and we love it.. I realize that switches don't call for much support, but we did have some issues with the catalyst. Ciscos support as amazing and they even called back again just to make sure we were happy. 3com on the otherhand wanted to charge us for support on a 1 day old switch! I just wanted to double check to see that their was no fdx on the ports before sending it back. They could have cared less whether I returned it or not.. So I did! Allen - 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.

22 74

(usr-tc) NOTICE: HiPer ARC and HiPer DSP code
by Chuck Stace 21 Oct '99

21 Oct '99

3Com Customers, Due to various issues with prior versions of HiPer ARC and HiPer DSP code, 3Com is advising that all customers upgrade their HiPer ARC and HiPer DSP cards to one of the following versions of code: HiPerARC v4.1.59-6 Service Release for HiPer ARC 4.1.59-6 built from 4.1.72-7. Version 4.1.59-6 is an effort to combine many previous Engineering Releases into a generally available code release. It addresses a series of P1 and P2 issues identified with the previous HiPer ARC code release. HiPerARC v4.2.32-1 The HiPerARC v4.2.32-1 Maintenance Release replaces HiPerARC v4.2.29. This version fixes the upgrade issues from v4.1.59-6, HiPerBomb DoS (Denial of Service) attack, and SNMP security issues. If customers are using HiPerARC v4.2.29 on their Total Control chassis at this time, they are advised to upgrade to v4.2.32-1 as soon as possible. HiPerDSP v2.0.19 This is the released version of HiPer DSP T1 and T1/PRI, TCS 3.5. Please see the release notes accompanying the code prior to deployment. NS1500 PRI switch type is not supported in this release. EdgeServer/ESPro gateway cards have not been included or tested for compatibility with TCS 3.5 System release. Once compatibility has been verified and approved, this disclaimer will be removed and status will be updated on the Software Compatibility Matrix. HiPerDSP v2.0.81 This Service Release has the same functionality and limitations of v2.0.19, but also includes a number of P1 and P2 bug fixes. Please see the release notes accompanying the code for details on bug fixes and outstanding issues. Access the code and release notes in either of the following locations: http://totalservice.3com.com/cgi-bin/w3com/start?totalservice+latest ( posted under Total Control Hubs ) or http://totalservice.3com.com/cgi-bin/w3com/start?totalservice+software ( search by Total Control Hubs : Hiper DSP or Hiper ARC ) If there are any questions or concerns regarding these changes, please contact 3Com Technical Support toll-free at 1-800-231-8770. If you are calling from an area not handled by this number, the TotalService website has contact information for other countries and regions. Please go to the TotalService website and click on 'Contacting Tech Support' for more information. Chuck Stace Customer Service Product Planning Chuck_Stace(a)3com.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.

1 0

Re: (usr-tc) Licences for SAServer/RADIUS with Oracle
by Clayton Zekelman 21 Oct '99

21 Oct '99

They may have been referring to a "per seat" fee - for each user of THEIR software. IE each desktop in your company that will be using the database. At 09:13 AM 10/21/99 -0500, you wrote: > > >That's crazy. That's like Oracle telling a store owner they want a >license fee for each product they sell listed in the >database............"datums" should not have license fees :) > > >On Thu, 21 Oct 1999, Malcolm Dobson wrote: > >> We use version 6.0 of saserver with an Oracle backend. Recently Oracle >> (UK) have told us that we must pay an annual "Limited User Programs" >> Licence for each user in the users table. For our operation this would >> amount to some $40K (US) a year. We think this is totally outrageous. >> >> Has anyone else been asked to pay per-user licences by Oracle for >> this? >> >> Regards >> >> Malcolm >> >> Malcolm Dobson, Scotland On Line >> www.scotland.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. >> > >----------------------------------------------------- >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. > --- Clayton Zekelman Managed Network Systems Inc. (MNSi) 875 Ouellette Avenue Windsor, Ontario N9A 4J6 tel. 519-985-8410 fax. 519-258-3009 - 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) Licences for SAServer/RADIUS with Oracle
by Stainforth, Matthew 21 Oct '99

21 Oct '99

Then they obviously don't understand the nature of what you're doing. It might be more accurate to say that each chassis is a "client" of the database - but even that is stretching it. Matthew > -----Original Message----- > From: Malcolm Dobson [mailto:malcolm@beano.sol.co.uk] > Sent: Thursday, October 21, 1999 11:46 AM > To: usr-tc(a)lists.xmission.com > Subject: Re: (usr-tc) Licences for SAServer/RADIUS with Oracle > > > > > On Thu, 21 Oct 1999, Clayton Zekelman wrote: > > > They may have been referring to a "per seat" fee - for each > user of THEIR > > software. IE each desktop in your company that will be > using the database. > > > > Absolutely not - they figure a user being authenticated by the RADIUS > system is a user of the database. I kid you not! We already > pay for our > staff to use Oracle. > > > At 09:13 AM 10/21/99 -0500, you wrote: > > > > > > > > >That's crazy. That's like Oracle telling a store owner they want a > > >license fee for each product they sell listed in the > > >database............"datums" should not have license fees :) > > > > > > > > >On Thu, 21 Oct 1999, Malcolm Dobson wrote: > > > > > >> We use version 6.0 of saserver with an Oracle backend. > Recently Oracle > > >> (UK) have told us that we must pay an annual "Limited > User Programs" > > >> Licence for each user in the users table. For our > operation this would > > >> amount to some $40K (US) a year. We think this is > totally outrageous. > > >> > > >> Has anyone else been asked to pay per-user licences by Oracle for > > >> this? > > >> > > >> Regards > > >> > > >> Malcolm > > >> > > >> Malcolm Dobson, Scotland On Line > > >> www.scotland.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. > > >> > > > > > >----------------------------------------------------- > > >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. > > > > > --- > > Clayton Zekelman > > Managed Network Systems Inc. (MNSi) > > 875 Ouellette Avenue > > Windsor, Ontario > > N9A 4J6 > > > > tel. 519-985-8410 > > fax. 519-258-3009 > > > > - > > 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. > > > > Regards > > Malcolm > > Malcolm Dobson, Scotland On Line > www.scotland.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. > - 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) ISPCon/3Com Open Meeting
by Stainforth, Matthew 21 Oct '99

21 Oct '99

When a security problem became publicized about a particular version of IOS I called the Cisco TAC to request a new version of the firmware. I didn't have a contract and they had never heard from me before. Not only did I get the code emailed to me, a support engineer phoned me back to see if I needed any help getting the code into the routers. He spent an hour on the phone with me suggesting memory upgrades, where to buy said upgrades, and explaining every little thing I could think to ask about Cisco routers. Now THAT is service. Matthew > -----Original Message----- > From: Rick [SMTP:rallan@monmouth.com] > Sent: Wednesday, October 20, 1999 11:18 PM > To: usr-tc(a)lists.xmission.com > Subject: Re: (usr-tc) ISPCon/3Com Open Meeting > > I would have to agree with Allen when it comes to the quality of support > between 3com and ANYONE. We currently maintain maintenance agreements with > many > vendors (including cisco and lucent..aka ascend) and it is always > refreshing to > have to deal with both cisco and lucent of 3com engineers. Both cisco and > lucent are very willing to upgrade any firmware revision that has KNOWN > bugs. > If 3com would start to comprehend this subject I think it would help with > their > stock....., I mean image... > > :> > > Allen Marsalis wrote: > > > At 09:15 PM 10/15/99 -0400, Lon R. Stockton, Jr. wrote: > > >On Fri, 15 Oct 1999, Allen Marsalis wrote: > > > > > >> I have no regrets.. x2 was a big deal in our area (we certainly > helped) > > >> and being the first 56k provider in our area was a big win for us. > > >> USR made that happen.. I liked USR.. It's 3com that I feel ill > about. > > > > > >Agreed here too. Getting my TC rack was a big win for us, and having it > > >still is. We were first with x2, first with v.90, and our v.90 *still* > > >walks all over my competitions' PM-based dialup pools. And we're still > > >the only provider in town doing ISDN, which is the best thing you can > > >get here aside from a dedicated line. (and we're served by Sprint, who > > >has some really good ISDN BRI pricing...only about $5 more than two > > >regular phone lines and flat-rate to boot...not to mention that inbound > > >PRIs are about 1/2 the cost of CT1's). > > > > Same here. That's pretty much exactly how we feel about it. However > > we occationally find a user with a good sportster/3com modem who can't > > get v.90 on our TCS but can on our TNT (eval) and more importantly, > > can with our competitors. Users won't stay with 28.8 when they can > > get 48k elsewhere.. If there were no modem code issues, I'd be more > > than happy to send the eval back. Instead, I'll probably get an > invoice... > > > > > > > >> Do we use 3com switches or routers? no we use cisco, foundry, etc.. > > > > > >I'm actually a fan of their switches. But one doesn't have the same > > >problems...either a ethernet switch works or it doesn't. If it's > > > > Well back when we started, we bought a superstack and it worked of > course > > but when I found out it was half-duplex on all 10T ports, we sent it > back > > and opted for a catalyst.. But nowadays I'm sure things are different. > > We outgrew the catalyst and now have a fastiron and we love it.. > > > > I realize that switches don't call for much support, but we did have > > some issues with the catalyst. Ciscos support as amazing and they > > even called back again just to make sure we were happy. 3com on the > > otherhand wanted to charge us for support on a 1 day old switch! > > I just wanted to double check to see that their was no fdx on > > the ports before sending it back. They could have cared less whether > > I returned it or not.. So I did! > > > > Allen > > > > - > > 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. > > -- > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Rick Allan / rick(a)monmouth.com | Connect to a Backbone not a Wishbone > Head of Network Engineering | Monmouth Internet Corporation > 732-842-5366=====extension 102 | http://www.monmouth.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. - 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) USR vs Ascend (3com vs Lucent?) -Reply
by Campbell Simpson 20 Oct '99

20 Oct '99

Phillip When you talk about call failure rate, what do you actually mean? Is this based on the modem disconnection result or disconnection reasons from radius? Campbell Simpson - 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) USR vs Ascend (3com vs Lucent?)
by Aaron Nabil 20 Oct '99

20 Oct '99

One of my client ISP's has both USR hiperdsp's and Ascend MAX's. I've noticed that the Max's seem to perform better (ratio of successful connects, number of dropped connections) than the USR's, even when connecting to USR modems. About 2am this morning I had a flash of insight and drove into my office (I have a well-equipped home lab, but needed access to a 4-wire interface. Not much traffic at 2am, and no trouble finding a parking space downtown.) It was worth the trip, I think I hit pay dirt. What I tested was the level the server (ISP) modem was transmitting at. I was surprised to see that is was at -10dbm, which is quite hot. Beacuse of the way digital lines are coded, higher power levels have worse s/n ratios, there aren't at many quantitization bits available at higher powers. I plugged in my laptop, fired up tcm, and looked at the hiperdsp config. It was set for -11dbm. Hmmm. I set it for -15, and yup, I get -14 when I measure it. An off by one error someplace, no doubt. But it gets better. I call into our Max's and measured the level they were sending. Only -14dbm, much lower power, more what I was expecting. Telnet in and check to see what they are set to, -13dbm, another off by one, but this time in the opposite direction! Here's a summary: Configured for Actually sends USR HiperDSP -11dbm -10dbm Ascend Max -13dbm -14dbm I don't have any scripts in place that monitor failure ratios, but if someone does I'd be interested if they could set half their modems to -15dbm (for an output of -14dbm) and see what effect that has. -- Aaron Nabil - 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.

7 11