- USR-TC - mailman.xmission.com

(usr-tc) I just HARCed up
by Lon R. Stockton, Jr. 12 Jan '00

12 Jan '00

The idea is to make a smooth transition from harc v4.0.30 to v4.1.22 by putting in my cold-spare harc card in the chassis and upgrading that. Then I can move dsps to it one at a time such that we're never down and nobody gets arbitrarialy disconnected. Before I stuck another harc in the chassis, tho, I figured I'd better make sure that the dsps were owned by the existing harc so the new one wouldn't try to grab 'em. So I go into my semi-trusty HARM (v1.0.8), pick "Tables->Chassis Configuration", and for each card, I select it, hit 'Edit', click the 'owner' checkbox, and hit 'Ok'. Then click 'Set' to configure the changes. And immediately knock off all current connections, and begin refusing calls with a fast busy. I quickly go back in and put things back, and everything returns to normal. So I guess my question is, "huh?". I guess I have another question too, one which I should pose before I do anything anyway. First, my relevant version numbers: s/w h/w HDSP: 1.2.5 0.49.0 HARC: 4.0.30 1.0.0 NMC: 5.5.5 6.0 TCMW: 5.5.1 HARM: 1.0.8 I want to give hdsp v2.0.51 a shot as well as the aforementioned upgrade of the harc to 4.1.22. I have a couple of concerns about this, however. First off, my versions of nmc, tcmw, and harm are not listed in the compatability lists in the release notes for the new harc/hdsp software releases. And of course, those upgrades are unavailable to me since I let my service contract expire last year. So, I'm stuck with those. I can either use my system as it was represented to me when I bought it and live with security problems on the harc (and relatively broken code on the hdsps)....or I can upgrade to these current software versions and lose the functionality of a nmc and windows-based management. Or maybe it's not all that bad? And is there an issue with the new hdsp version on v0.49.0 dsp hardware? What's the summary on that one? - 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) Disconnect reasons
by Greg owens 12 Jan '00

12 Jan '00

Looking at the Total Control It will list several types of disconnect reasons.....rcvdGatewayDiscCmd, NormalUserCallClear,v42DisconnectCm, along with several others...Where can I find a explanation of these reasons. Which ones other than CarrierLoss should alert me to problems other than the users just logged off. Thanks Greg Owens Magnolia Internet Services http://www.magnolia-net.com

2 1

RE; (usr-tc) DSP cards rebooting
by Greg owens 11 Jan '00

11 Jan '00

Cheryl...We have been running this code for about a month now and have not had to reset a modem since. Have not noticed any ill effects from the upgrade. We raised our carrier loss detect setting to 20 I believe the default is 6 or 7. Can't say it helped anything but has not done any harm either. Greg Owens Magnolia Internet Services http://www.magnolia-net.com ----- Original Message ----- From: Cheryl Johnson To: usr-tc(a)lists.xmission.com Sent: Tuesday, January 11, 2000 4:24 PM Subject: (usr-tc) DSP cards rebooting Anyone else have this problem using the 2.0.60 version on the HiPerDSP cards? This code is supposed to help with the modem pair problem. Although this problem has not been as noticeable as the past, I still have various modem problems and recently noticed DSP cards rebooting. I just recently upgraded the TC chassis to the code above and seem to having problems with it. I have also been experimenting with increasing the Carrier Loss Detect Delay on the DSP cards, anyone had any luck with increasing this setting? I am not sure if this may be causing problems or not. Cheryl Johnson netadmin(a)seidata.com SEI Data Network Services, Inc. Greg Owens Magnolia Internet Services http://www.magnolia-net.com

1 0

Re: (usr-tc) DSP cards rebooting
by Greg Coffey 11 Jan '00

11 Jan '00

I upgraded all of mine to 2.0.51 with no adverse effects so far. At 05:37 PM 1/11/00 -0500, you wrote: >If your cards are hardware revision 0.55 or 0.54, try loading 2.0.51 on >them... > > >Mike Andrews (MA12) * mandrews(a)dcr.net * http://www.bit0.com/ >VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY >Internet services for Frankfort, Lawrenceburg, Owenton, & Shelbyville >"It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." > >On Tue, 11 Jan 2000, Cheryl Johnson wrote: > > > Anyone else have this problem using the 2.0.60 version on the HiPerDSP > cards? This code is supposed to help with the modem pair problem. > Although this problem has not been as noticeable as the past, I still > have various modem problems and recently noticed DSP cards rebooting. I > just recently upgraded the TC chassis to the code above and seem to > having problems with it. I have also been experimenting with increasing > the Carrier Loss Detect Delay on the DSP cards, anyone had any luck with > increasing this setting? I am not sure if this may be causing problems or not. > > > > Cheryl Johnson > > netadmin(a)seidata.com > > SEI Data Network Services, Inc. > > > > >- > 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. Thanks, Greg Coffey <gcoffey(a)vcn.com> Visionary Communications V 307-234-5443 F 307-234-5446 100 N. Center #100, Casper, WY 82601 www.vcn.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

(usr-tc) WTB: Hiper DSP NAC/NIC Sets
by Steve Rivera 11 Jan '00

11 Jan '00

I am in the market to purchase up to 5 of these cards today. If you have them available please email me off the list. .................................................... Steve Rivera - http://www.ISP-NetworkHardware.com (WRCA) sales(a)wrca.net v-732-833-2111 cell/pgr-732-433-5890 ---WAN ACCESS SPECIALIST--- Cisco, Ascend, Livingston, USR, Microcom, Computone, Kentrox, Adtran...and more - 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) BETA: EdgeServer Pro v2.6 (estimated start date - 2/1/2000)
by Chuck Stace 11 Jan '00

11 Jan '00

3Com Customers, 3Com is now accepting applications for beta testers for the release of EdgeServer Pro version 2.6 This release has added performance and feature enhancements including support for Microsoft NT4 Service Pack 6. To apply for this beta, please go to the TotalService website at: http://totalservice.3com.com/ and click on 'Beta Program' and then 'Upcoming Beta Projects'. At this time, you will have to log into your TotalService account to enter into this beta. If you are a customer that does not currently have an account with TotalService, please apply for an account at: http://totalservice.3com.com/create.html Once your application has been completed and reviewed, you will receive email informing you of your status in the beta program and more details on how to participate once the EdgeServer Pro 2.6 beta begins field trials. For more information on Total Control EdgeServer ? Pro Integrated NT Server, you can visit our website at: http://www.3com.com/solutions/svprovider/products/rac/edgpro.html If you have any questions or comments on this beta, please email me at the address listed below, and if you have anyone that would be interested in participating in this program, please feel free to forward this email to their attention. Thank you for your time, Chuck Stace CSO Customer Service Product Planning Chuck_Stace(a)3Com.com

2 1

(usr-tc) NOTICE - HiPerARC Service Release 4.1.22 (posting complete)
by Chuck Stace 11 Jan '00

11 Jan '00

3Com Customers, HiPerARC Service Release v4.1.22 has been posted to the TotalService website ( http://totalservice.3com.com) and the Software Compatibility Matrix has been updated. HiPer ARC 4.1.22 resolves many problems found since 4.1.59-6 including HiPerbomb DOS Attack and SNMP community string security hole. For more information on the details of this Service Release, please reference the release notes. Both the code and release notes can be found on TotalService in the following location: http://totalservice.3com.com/cgi-bin/w3com/start?totalservice+software ( search by Total Control Hubs : Hiper ARC ) This code will be free for download for 90 days. After that 90 days, it will be only be available to customers with a valid service contract. 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.

17 21

(usr-tc) Software recommendations
by Charles Sprickman 11 Jan '00

11 Jan '00

Hi, I'm long overdue for an upgrade on a large number of chassis, and while I've been following the list, I've had a hard time coming up with what is a good, stable version of code to be running everywhere... I have HAs, HDSPs, and Quads in these chassis. I would like OSPF (took the time to learn more about it than RIP), but it's not a necessity. We currently have horrid problems with disconnects on most all modems, iMac troubles (although Mindspring does too; only really occurred for me when the connection was above 46.6K), and really BAD Global Village (blech, barf, erk) problems. We've not seen the "two modems hung" problem. So what's the recommended, stable code you folks are using? What is the rule with mixing DSP and ARC code? Can I run a newer DSP code (2.x) w/older ARC code (4.1)? Thanks, Charles -- =-----------------= = | Charles Sprickman Internet Channel | | INCH System Administration Team (212)243-5200 | | spork(a)inch.com access(a)inch.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) IAS accounting problem with HiperArc
by Steve Valiunas 10 Jan '00

10 Jan '00

Anu, That would have been primary-accounting-server-2, not secondary-server as I wrote, but I'm sure you checked that as well. What version of Harc code? If you want to capture a bit of MonitorRadius in hex mode (while sending Malformed packets of course), and send it to me along with the accounting sercret used, I can see see if anything looks whacky. Steve Valiunas steve_valiunas(a)3com.com USRobotics TC Mailing List <USRoboticsTCMailingList(a)imagenisp.com> on 01/10/2000 05:17:26 PM Please respond to usr-tc(a)lists.xmission.com Sent by: USRobotics TC Mailing List <USRoboticsTCMailingList(a)imagenisp.com> To: "'usr-tc @lists.xmission.com'" <usr-tc(a)lists.xmission.com> cc: (Steve Valiunas/MW/US/3Com) Subject: RE: (usr-tc) IAS accounting problem with HiperArc That's the first thing I did when I ran into the problem. I even verified the secrets on the HipeArc using the _show accounting radius secret. Anyone have any other suggestions? Anu Jolliffe Network Administrator Imagen Communications Inc. (250) 538-0406 FAX (250) 537-5820 -----Original Message----- From: Steve Valiunas [mailto:Steve_Valiunas@mw.3com.com] Sent: Monday, January 10, 2000 8:44 AM To: usr-tc(a)lists.xmission.com Subject: Re: (usr-tc) IAS accounting problem with HiperArc Check your secondary-server's shared secret. STeve Valiunas USRobotics TC Mailing List <USRoboticsTCMailingList(a)imagenisp.com> on 01/09/2000 03:01:53 PM Please respond to usr-tc(a)lists.xmission.com Sent by: USRobotics TC Mailing List <USRoboticsTCMailingList(a)imagenisp.com> To: "USRobotics TC Mailing List cc: (Steve Valiunas/MW/US/3Com) Subject: (usr-tc) IAS accounting problem with HiperArc I am having a problem with my HiperArc and accounting using Microsoft IAS. I have my first accounting server specified as the primary accounting server, and everything is working fine as is. The problem I'm having is related to my second server, which I intend to use as a backup in case the first one goes down. When my second server is set as the secondary server, everything works okay. However, when I have my second server set as the primary first backup, no accounting records are recorded and the NT event log is full of malformed packets. What is different about the packets when they are sent to the server configured as the primary first backup versus the secondary? My other chassis which runs a NSC has no problem at all with the second server. Thanks for your help. Anu Jolliffe Network Administrator Imagen Communications Inc. (250) 538-0406 FAX (250) 537-5820 - 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

(usr-tc) State of the Hub (part 2)(take 2)
by Jeff Mcadams 10 Jan '00

10 Jan '00

(cont. from previous message due to message size limitations) I have received no reports, either positive or negative about the current state of 3Com support contract rules. A perusal of relevant 3Com web sites seems to indicate that some progress has been made on this issue. If you go to 3Com's web site, to the support section, and click on 3Com Care service offerings, under Maintenance Services, you'll see a section entitled "Unbundled Services." There are sub-sections for InfoPak telephone support (which is at the time of this writing a broken link), software updates (all of the latest software upgrades for a year for one low price...this has promise), Advanced Hardware Replacement (one contract covers multiple pieces of equipment...new equip. can be added at a pro-rated cost...this has potential *if* you can pick and choose which hardware is covered and are not required to cover all your hardware with the same coverage), and Multi-Year Warranty (also a broken link at the time of writing). I have a call in to my great sales-rep Tom Goodman to get more in depth information about the requirements of these service offerings (and prices), and will post what information I get when I get it. This covers the major outstanding issues that I'm aware of. Some further discussion points that have been brought up in the past are discussed below. Customer involvement in software development. I've not seen much progress here, it seems that most software development on the TC equipment is still done with very little connection to customer requests (very cathedral style, with apologies to ESR). There has been recent calls for more participation on the beta list for TCS 4.0, I wholeheartedly encourage this...unfortunately, I haven't had the opportunity to work with the beta software as I would like. The beta list (and I'm under the beta NDA, so I need to be a little careful here ;) seems primarily to be a list for customer feedback to 3Com folks about the problems we're having. It would be nice, (and this isn't just restricted to the beta list) to have the possibility to be part of the discussion about how things get implemented. Had more customer input been solicited, perhaps we wouldn't have ended up with ip pool aggregation reserving a network and broadcast address unnecessarily, and similar types of issues...none are critical, but all would make the TC equipment that much nicer to use. Another access server type of feature request to be re-iterated (this has been a long term request)...the ability to define, by an administrator, what traffic will reset the idle timer on a port. The ability to set this via RADIUS would be an added bonus. Beaurocracy (and I'm still not sure if I'm spelling this right). There seems to have been made a *little* progress in this area, however, this requires a disclaimer. I, personally, apparently, have achieved some...ah...notoriety within 3Com...particularly in the Rolling Meadows facilities. As such, I must consider the possibility that I've been getting contact with people within 3Com that its not common to have direct customer contact with. :) Even this, however, is an improvement. Perhaps this gives me the opportunity to be a sort of liason between 3Com and 3Com's customers. I fear that I'm sounding cocky ("I have better contacts than you do"), and assure you that this isn't my intention. I'd rather people have direct contact...I have plenty of things on my plate to do that the time taken up being such a liason could be used elsewhere, but if I do have better contacts, and can be useful as a sort of liason, I'm certainly willing to do so for the betterment of 3Com-customer relations. :) Direction. Specifically with the HiPer Arc card (which is where I'm particularly knowledgeable within the TC product group), it seems that 3Com is beginning to see the possibilities that the HiPer Arc (at least) provides beyond just being a dial-up access server. Again, I have to be careful here because of the restrictions of the beta NDA...but the direction of the development seems to be towards making the HiPer Arc a full-fledged router. Some things that need to be worked on still: - 3500 route limit needs to be removed, or at least upped - more routing protocols...OSPF is a great start...more needed (BGP?) - OSPF needs to be able to be an ABR - more control over routing protocols...summarization, redistribution - route selection still somewhat buggy (Mike Andrews is the expert on these problems ;) And some things that I think are important, but not necessarily to the point of being *needed*: - bridging - QoS...this is apparently a company wide push for 3Com...so I suspect its going to be done in a big way - wider array of interface types And, just for kicks, a gee-whiz cool feature that the TC lends itself to: - packet bus interface...the ability to treat the internal packet of the chassis as an interface in the Arc...some cool things can be done when this is combined with bridging support above Even as an access server, the Arc needs to be developed to adapt to changing times. As modem and ISDN access becomes less and less prevelent with the proliferation of broadband, the Arc needs to adapt. There seems to be some work on this front (again, TCS 4.0 beta), the bridging support mentioned above is needed for this as many DSL providers transport DSP and other broadband access methods to ISP via a bridging over frame-relay or bridging over ATM. The Arc already has support for frame and ATM, but can't (from what I've seen) do bridging over top of it. I encourage people to submit their own feature requests, etc. to the list and/or me. I've been keeping some notes recently for inclusion into this and future "State of the Hub" messages. :) Like I said...I'm willing to take up the role of liason between 3Com and customers if that's necessary/desireable, let me know. I also encourage feedback to me and to this forum regarding this message and others of mine. My philosophy is that I own my words. I'll take responsibility for what I say, I encourage forwarding of my messages on to people who would benefit from my messages, all I ask is that you keep attribution and contact info in tact so that I can continue to take responsibility for my words. :) -- 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.

2 2