- USR-TC - mailman.xmission.com

Re: (usr-tc) 3com V90 Problems
by Allen Marsalis 17 Oct '99

17 Oct '99

At 04:22 PM 10/17/99 -0500, Brian wrote: >I would imagine, actually hope, that 3com's tests labs, have done many >tests against their own stuff and against competitors. I would think they >would not make a policy of releasing such data, unless of course 3com was >best in every case, which I doubt it was, but certainly coudln't have done >too poor. Conversely, I would imagine that ascend's test labs have done tests against their competitors.. And that they wouldn't release such data unless they were best.. IOW, you would think that one manufacturer (at least) would come out of the closet with data proving that they were the best. :) I've always been disappointed that so few tests have been done to rate 56k.. The only test I remember comparing x2 to kflex was the boardwatch fiasco.. nothing totally unbiased and largely scientific seems to be done on a regular basis.. What is keeping us from polling both chassis every hour and logging the actual connect speeds into an SQL database? If the scripts (telnet, snmp, whatever) could be written, they could be passed around by ISP's giving some pretty good 'real world' data to support or refute our perceptions of modem performance. Has anyone out there ever done anything like this? Allen > >Brian > - 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) More telco madness
by Brian 16 Oct '99

16 Oct '99

O, I forgot to mention in my previous post, that the telco who is blaming us for our problematic CT1, said the circuit was showing "high and wet" and that could only mean it was the end user that was at fault. What is high and wet, and does it really mean it has to be the end user? 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.

1 0

RE: (usr-tc) badmodems.pl
by Stainforth, Matthew 15 Oct '99

15 Oct '99

You could rewrite part of the script to make it output HTML directly to STDOUT so that it generates your stats real-time. I'm doing this with some other SNMP scripts I wrote but, depending on the stats, you might be sitting there a while waiting for it to do something. If you want to run it periodically you might want to consider using WINAT to schedule it if you're on NT. > -----Original Message----- > From: K Mitchell [SMTP:mitch@keyconn.net] > Sent: Friday, October 15, 1999 10:53 PM > To: usr-tc(a)lists.xmission.com > Subject: (usr-tc) badmodems.pl > > I got Eric Billeter's badmodems.pl script to work checking failure > rates, > but I'm having 2 issues with it; > 1. The output file isn't being named/placed correctly. The line > my $outputfile - "e:\inetpub\mrtg\modem-fail.htm"; > puts a file named inetpubmrtgmodem-fail.htm directly on the e:\ drive. > 2. I would like to either schedule it to run when called by a webpage link > or button, or, failing that, schedule it to run every so often. > Any ideas for either? > > Thanks, > > -- > Kirk Mitchell-General Manager mitch(a)keyconn.net > Keystone Connect Unlock Your World > Altoona, PA 814-941-5000 http://www.keyconn.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.

2 1

Re: (usr-tc) badmodems.pl
by K Mitchell 15 Oct '99

15 Oct '99

At 09:19 PM 10/15/99 -0500, Brian wrote: > >did you try escaping the backslashes like: > >my $outputfile = "e:\\inetpub\\mrtg\\modem-fail.htm"; I hadn't tried that, it worked. I had tried e:%\inetpub%\mrtg... and just ended up with the same name including %'s. Thanks a bunch, -- Kirk Mitchell-General Manager mitch(a)keyconn.net Keystone Connect Unlock Your World Altoona, PA 814-941-5000 http://www.keyconn.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.

1 0

(usr-tc) badmodems.pl
by K Mitchell 15 Oct '99

15 Oct '99

I got Eric Billeter's badmodems.pl script to work checking failure rates, but I'm having 2 issues with it; 1. The output file isn't being named/placed correctly. The line my $outputfile - "e:\inetpub\mrtg\modem-fail.htm"; puts a file named inetpubmrtgmodem-fail.htm directly on the e:\ drive. 2. I would like to either schedule it to run when called by a webpage link or button, or, failing that, schedule it to run every so often. Any ideas for either? Thanks, -- Kirk Mitchell-General Manager mitch(a)keyconn.net Keystone Connect Unlock Your World Altoona, PA 814-941-5000 http://www.keyconn.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

Re: (usr-tc) ISPCon/3Com Open Meeting
by Allen Marsalis 15 Oct '99

15 Oct '99

At 06:29 PM 10/15/99 -0400, Lon R. Stockton, Jr. wrote: >In other words, it's my theory that 3com is now more interested in big >telcos. Integrating the TC and phone switches and stuff like putting >ADSL and traditional dialup in the CO. $Billions is an understatement Bingo. Last year, our 3com rep told us that if they sold one contract to a single <unnamed> telco that they were working with, the sale would constitute as many ports as they have sold in their history to date.. I doubt the deal ever happened though.. During the 80's recession, our local government spent millions trying to lure McDonald Douglas into building a new factory at our city. We lost the 'beauty contest' hosted by a dozen cities. In fact, the new factory was never built at all. What about the little guy? The ones who really keep the city going? Where is our tax abatement? and other incentives? If only they had spend their efforts and money in a way that would have really helped people in our area... > >My only wish is that I didn't pick up on this earlier.... 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. USR designed nearly all the hardware before the merger. It's been nearly 2 years now.. What has 3com created or added to the mix to make it a good merger? OSPF? great! only took 3-4 years.. Where is the SS7 gateway? higher density modems per DSP? VoIP? cool PPC code features and all that jazz? Aren't 2 of the 3 PPC's on the board doing nothing? Do we use 3com switches or routers? no we use cisco, foundry, etc.. I just don't see the overall purpose/benefit of the merger.. Perhaps it's not only about humongous telcos on the one side, but about CPE on the other.. something we buy very little of.. and we are stuck in the middle... > >The other saving grace is this mailing list, and the handful of 3com >people that populate it. I actually hesitate in bashing 3com on here >because the 3com people that actually see it aren't the problem, and >they're more deserving of praise rather than seeing stuff that'll just >alienate them more and make 'em think I'm an ingrate. agreed. 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.

2 1

RE: (usr-tc) ISPCon/3Com Open Meeting
by Blake Fithen 15 Oct '99

15 Oct '99

What about "earn customers respect through display of competence"? The only change I've noticed in 3com's tech support over the past year is the fact that someone from 3Com calls me and asks me about how my tech support call was handled. "Do you feel the engineer was competent"? "Did the engineer fix the problem"?, etc... Tonight I called in to 3Com tech support because I have a problem of not remembering if channelized T1 can support ISDN. I had a 'feeling' that it would not but I wanted to get confirmation. I asked the tech said question to which he replied, "yes channelized T1 will support ISDN BRI calls, no problem." To which I said, "are you sure?" He went to "double-check" on this enigma and he came back and said "no, I'm sorry, your customer cannot dial-in to your CT1 circuit." At least he double-checked. The bottom line is that I think 3Com should be harshly confronted about the quality of their tech-support and the fact that it is not worth what they are billing customers. blake > -----Original Message----- > From: Ed [mailto:ed@taylors.com] > Sent: Friday, October 15, 1999 2:05 AM > To: usr-tc(a)lists.xmission.com > Subject: Re: (usr-tc) ISPCon/3Com Open Meeting > > > Marshall wrote: > "Buy customer's happiness through goodwill instead of ball parks" > > Thats a good one ;-) > > > Ed > > ----- Original Message ----- > From: Marshall Morgan <marshall(a)netdoor.com> > To: <usr-tc(a)lists.xmission.com> > Sent: Friday, October 15, 1999 2:10 AM > Subject: (usr-tc) ISPCon/3Com Open Meeting > > > Great Idea !! > > Why don't we all have a mass (OPEN) meeting with 3com at > ISPCon. The other > vendors will send people in as well and will get plenty of > ammo for their > executives that actually listen to their customer's > complaints. If 3com > changes > everything that night with a big announcement (hint hint) about cost > effective > hardware/technical support and software only support, then > everyone, except > the > snoops from other companies, will be happy! > > A win-win for everyone if 3C want's our continued business. > Buy customer's > happiness through goodwill instead of ball parks. > > Marshall Morgan > President > > Internet Doorway, Inc (aka NETDOOR) > http://www.netdoor.com > > 601.969.1434 x28 | 800.952.1570 x28 | 601.969.3629 x28 | Fax > 601.969.3838 > > > -----Original Message----- > > From: owner-usr-tc(a)lists.xmission.com > > [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of > Richard Lorbieski > > Sent: Thursday, October 14, 1999 9:41 PM > > To: usr-tc(a)lists.xmission.com > > 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... > > > > > > - > 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

Re: (usr-tc) Ah...what the heck...
by Steve Valiunas 15 Oct '99

15 Oct '99

If you were to enter 128.253.180.0 / 255.255.255.0 then only those IPs from 128.253.180.1 through 128.253.180.254 would be able to access the NMC. You can still, as you said, enter an particular IP address- 128.253.180.12 / 255.255.255.255 for example. Steve mmm3(a)cornell.edu on 10/15/99 02:02:41 PM Please respond to usr-tc(a)lists.xmission.com Sent by: mmm3(a)cornell.edu To: usr-tc(a)lists.xmission.com cc: (Steve Valiunas/MW/US/3Com) Subject: Re: (usr-tc) Ah...what the heck... >>Is it possible to restrict access to a subnet or subnets such that any >>machine on that subnet can access TCM? > > Yes, You are allowed up to ten entries, each containing an IP address and a >network mask. Right, but I was under the impression the IP address had to be of a specific node machine, not set to--for example--128.253.180.0/24 so that *any* machine, regardless of node address, could access TCM from that subNet. Or am I being dense here? > >If you mess up putting in the restrictions and can't get in from snmp/TCM >anymore, you can reset the list from the NMC Console port with Command | >ReinitializeAccessList, or just reboot the NMC if you'd like, since you hadn't >saved the config yet. Oh, I *never* mess up. 8-) ********************************************************* Michelle M. Mogil Network and Computing Systems 721 Rhodes Hall, Cornell University, Ithaca, NY 14853 vox: (607) 255-0516, fax: (607) 255-8420 email: mmm3(a)cornell.edu ********************************************** - 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

Re: (usr-tc) Ah...what the heck...
by Steve Valiunas 15 Oct '99

15 Oct '99

>Is it possible to restrict access to a subnet or subnets such that any >machine on that subnet can access TCM? Yes, You are allowed up to ten entries, each containing an IP address and a network mask. If you mess up putting in the restrictions and can't get in from snmp/TCM anymore, you can reset the list from the NMC Console port with Command | ReinitializeAccessList, or just reboot the NMC if you'd like, since you hadn't saved the config yet. STeve mmm3(a)cornell.edu on 10/14/99 04:00:34 PM Please respond to usr-tc(a)lists.xmission.com Sent by: mmm3(a)cornell.edu To: usr-tc(a)lists.xmission.com cc: (Steve Valiunas/MW/US/3Com) Subject: Re: (usr-tc) Ah...what the heck... >The NMC DOES have an Authorized Stations list, in which you can limit snmp >access to a given set of ip addresses. It would be probably be a good idea to >use it. WIthin TCM its uner Security | Authorized Stations. > >STeve Is it possible to restrict access to a subnet or subnets such that any machine on that subnet can access TCM? ********************************************************* Michelle M. Mogil Network and Computing Systems 721 Rhodes Hall, Cornell University, Ithaca, NY 14853 vox: (607) 255-0516, fax: (607) 255-8420 email: mmm3(a)cornell.edu ********************************************** - 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

Re: (usr-tc) ISPCon/3Com Open Meeting
by jeff.binkley＠asacomp.com 15 Oct '99

15 Oct '99

-> Alot of times its just customer reps there though.........they should send -> more execs and engineers to those things. But those folks feel this kind of stuff in their wallets. I suspect it would get some folks attention. Jeff Binkley ASA Network Computing - 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 6