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

Re: (usr-tc) trapped with snmp
by Steve Valiunas 06 Jan '00

06 Jan '00

The "Annotation" field can be used as a comment. You can check that the NMC is sending traps by pulling out or inserting a card (other than the NMC)- The card insert traps are enabled by default and are a quick test (as long as you have a card you can play with). The Fan Failure Trap is also enabled by default... HiperDSP trap or log settings at the modem level require a template refresh to take affect (a good reason to have been setting the modem parms using templates instead of directly on the modems). The Span level stuff should not need this though. See if you can get ANY trap out of the NMC to start with. STeve Valiunas "Lon R. Stockton, Jr." <lon(a)moonstar.com> on 01/06/2000 09:19:15 AM Please respond to usr-tc(a)lists.xmission.com Sent by: "Lon R. Stockton, Jr." <lon(a)moonstar.com> To: usr-tc(a)lists.xmission.com cc: (Steve Valiunas/MW/US/3Com) Subject: (usr-tc) trapped with snmp Now that I've (locally) discovered the use of perl and the Net:SNMP module to talk to my TC (HiPer) chassis, I've recently been feeling all godlike and stuff. Of course, when a human experiences a taste of godhood, the PowersThatBe quickly queue up a lesson in humility. Anyway, I'm trying to play with SNMP traps and I must be missing something obvious. Here's the deal: 1) I run snmptrapd (from cmu-snmp-utils-3.5-3) on a handy linux box, telling it to both print the trap and dump inbound packets. 2) I verify operation of #1 by running snmptrap to generate a couple of arbitrary traps. Works great. 3) I go into TCM, pick a HiPerDSP card (selecting the LEDs on the span), and click "Fault->Trap Settings" and select "Trap Enables" 4) There, I set a few choice ones to "enableTrap". Specifically, "Red Alarm", "Loss of Signal", and "Physical State Change". Then I click "Set" and "Ok" to set it and exit. 5) Next, I click "Fault->Trap Destinations", and add an entry for the aforementioned linux box running snmptrapd. 6) I physically unplug the span from the HiPerDSP. Amazingly enough, the LEDS suddenly reflect a Red Alarm. (: 7) The amazement turns to disappointment when I see that my snmptrapd didn't hear anything. Due to my lack of real understanding of the trap destination configuration (umm, not the need for, you understand *grin*), I tried a few different things there. Even though snmptrapd appears to not give a whit about the community string, I tried three: nothing, junk, and the same as my NMC's community. And since I can't find anything in the docs that explains the "Annotation" entry, I also tried nothing, an integer '1', and an arbitrary string. I also verified that the linux box had a listener on the udp:snmp-trap port. All else failed, so it was time to consult the documentation. (: The docs basically told me to do all the stuff I did already. And, typical of docs, stopped short from answering the real question (like WTF is expected for "Annotation"). So, before I scrap the whole idea for now (being unwilling to go to the bother of sticking a hub in between the TC and the linux box so I can stick another packet-sniffin' box in there (a PIA that needs to be done because my LAN is point2point switched ethernet...useless to sniff from other segments)), I thought I'd ask here in case there was anything obvious that I'm leaving out (like maybe the NAC needs a reboot for the trap destination change to take effect or some other tripe). Or if I'm falling into some sort of a hidden, umm, trap. If anyone can slap me with a clue stick, I'd be grateful. (: - 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) Management Bus Failures
by Phil Nass 06 Jan '00

06 Jan '00

Hello all, We have two TC chassis, one has 14 DSP's w/2 ARC's and the other has 6 DSP w/1 ARC. I am running all ISDN PRI's and all DSP's are at 2.0.60, 4.1.59-6 ARC's and the HiPer NMC's with 6.2.17. The DSP firmware of the DSP's ranges from .49 to .54. My problem is that we get sporadic Management Bus Failures - "in both chassis" and on different cards. When this happens the card re-boots itself and of course, drops those 23 online. The re-boots do not follow any sort of pattern and I went a couple of weeks without any and now have had 3 or 4 within the past week. I have switched DSP cards and PRI's. The newer version 2.0.19 does address the management re-boots but only for the .54 and .55 firmware. Anybody have or seen anything similar...??? Any other ideas..??? This is really driving me crazy and BTW: I received another this morning on SLOT 2 in the 218 chassis. ........... Phil(a)lakefield.net (920) 758-2211 Phil Nass - General Manger @ Lakefield Tel I have enclosed a portion of my alarm server text: Authentication Failure 0 INFORMATIONAL OPERATIONAL 01/01/00 21:05:08 206.40.97.218 12/31/69 16:00:01 10005 Authentication Failure 0 INFORMATIONAL OPERATIONAL 01/01/00 21:04:43 206.40.97.218 12/31/69 16:00:01 10005 6; Yellow Alarm (remote OOF) cleared on Slot 12, DS1 Channel 1 0 INFORMATIONAL OPERATIONAL 01/01/00 19:42:25 206.40.97.218 01/01/00 11:46:24 429050 5; Watchdog Timeout in Slot 12, Channel 0 0 MAJOR NONOPERATIONAL 01/01/00 19:42:12 206.40.97.218 01/01/00 11:46:11 429007 4; Yellow Alarm (remote OOF) on Slot 12, DS1 Channel 1 0 INFORMATIONAL OPERATIONAL 01/01/00 19:41:58 206.40.97.218 01/01/00 11:45:57 429022 3; Management Bus Failure in Slot 12, Channel 1 0 MAJOR NONOPERATIONAL 01/01/00 19:39:26 206.40.97.218 01/01/00 11:43:25 429008 2; Watchdog Timeout in Slot 6, Channel 0 0 MAJOR NONOPERATIONAL 01/01/00 17:33:48 206.40.97.218 01/01/00 09:37:47 429007 1; Management Bus Failure in Slot 6, Channel 1 0 MAJOR NONOPERATIONAL 01/01/00 17:42:59 206.40.97.218 01/01/00 09:37:43 429008 Authentication Failure 0 INFORMATIONAL OPERATIONAL 01/01/00 16:13:19 206.40.97.218 12/31/69 16:00:01 10005 Warm Start 1 INFORMATIONAL OPERATIONAL 12/29/99 18:03:44 206.40.97.219 12/31/69 16:00:01 12/29/99 18:26:15 10002 3; Yellow Alarm (remote OOF) cleared on Slot 1, DS1 Channel 1 1 INFORMATIONAL OPERATIONAL 12/29/99 16:44:06 206.40.97.219 04/27/29 04:14:35 12/29/99 16:44:12 429050 2; Watchdog Timeout in Slot 1, Channel 0 1 MAJOR NONOPERATIONAL 12/29/99 16:43:50 206.40.97.219 04/27/29 04:14:19 12/29/99 16:44:12 429007 1; Management Bus Failure in Slot 1, Channel 1 1 MAJOR NONOPERATIONAL 12/29/99 16:41:28 206.40.97.219 04/27/29 04:11:54 12/29/99 16:42:48 429008 - 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) trapped with snmp
by Lon R. Stockton, Jr. 06 Jan '00

06 Jan '00

Now that I've (locally) discovered the use of perl and the Net:SNMP module to talk to my TC (HiPer) chassis, I've recently been feeling all godlike and stuff. Of course, when a human experiences a taste of godhood, the PowersThatBe quickly queue up a lesson in humility. Anyway, I'm trying to play with SNMP traps and I must be missing something obvious. Here's the deal: 1) I run snmptrapd (from cmu-snmp-utils-3.5-3) on a handy linux box, telling it to both print the trap and dump inbound packets. 2) I verify operation of #1 by running snmptrap to generate a couple of arbitrary traps. Works great. 3) I go into TCM, pick a HiPerDSP card (selecting the LEDs on the span), and click "Fault->Trap Settings" and select "Trap Enables" 4) There, I set a few choice ones to "enableTrap". Specifically, "Red Alarm", "Loss of Signal", and "Physical State Change". Then I click "Set" and "Ok" to set it and exit. 5) Next, I click "Fault->Trap Destinations", and add an entry for the aforementioned linux box running snmptrapd. 6) I physically unplug the span from the HiPerDSP. Amazingly enough, the LEDS suddenly reflect a Red Alarm. (: 7) The amazement turns to disappointment when I see that my snmptrapd didn't hear anything. Due to my lack of real understanding of the trap destination configuration (umm, not the need for, you understand *grin*), I tried a few different things there. Even though snmptrapd appears to not give a whit about the community string, I tried three: nothing, junk, and the same as my NMC's community. And since I can't find anything in the docs that explains the "Annotation" entry, I also tried nothing, an integer '1', and an arbitrary string. I also verified that the linux box had a listener on the udp:snmp-trap port. All else failed, so it was time to consult the documentation. (: The docs basically told me to do all the stuff I did already. And, typical of docs, stopped short from answering the real question (like WTF is expected for "Annotation"). So, before I scrap the whole idea for now (being unwilling to go to the bother of sticking a hub in between the TC and the linux box so I can stick another packet-sniffin' box in there (a PIA that needs to be done because my LAN is point2point switched ethernet...useless to sniff from other segments)), I thought I'd ask here in case there was anything obvious that I'm leaving out (like maybe the NAC needs a reboot for the trap destination change to take effect or some other tripe). Or if I'm falling into some sort of a hidden, umm, trap. If anyone can slap me with a clue stick, I'd be grateful. (: - 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) Callback with DSP
by Jorge Lozano 05 Jan '00

05 Jan '00

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm the following configuration: HiperDSP (E1/PRI) with firmware 2.0.19 HiperARC with firmware 4.1.17 TCM 6.0.86 How can I setup the callback option for users using my RADIUS server (Radiator) or using the chassis userlist?? Thanks again... Jorge Lozano M. <jorge(a)andinet.com> "The security is not a solution, is a life style" Please visit, http://www.andinet.com -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.1 for non-commercial use <http://www.pgp.com> iQA/AwUBOHQEiqp3oywyFVUlEQJWxgCg+NvXumER1fTGqHsPApoIEWDzXaIAmgMj /kfGzONOL/Xzk0NPNSAbln7A =Zrdk -----END PGP SIGNATURE-----

1 0

(usr-tc) HiperTRAX, x.25 and POS
by Andres Kroonmaa 05 Jan '00

05 Jan '00

hi, Has anyone any experience or info about so called HiperTRAX for TC systems? Its for credit/debit card applications like point-of-sale connectivity, with X.25 support, etc. The only thing I can find on 3com web is this page: http://www.3com.com/products/dsheets/400444.html which really isn't very heplful. I can't really understand what hardware is needed for it, what software/firmware, what PN's should I use for pricing. Actually, is this a real thing or yet another marketing hype? anyone? ------------------------------------ Andres Kroonmaa <andre(a)online.ee> MicroLink Online Network Development Manager Tel: 6501 731, Fax: 6501 708 PÃ¤rnu mnt. 158, Tallinn, 11317 Estonia - 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) Flaky modem or telco problem?
by zip-usrtc＠ran.zipcon.net 05 Jan '00

05 Jan '00

I'm having a modem problem with a USR TC with DSP based modems. DSP is 2.0.51, ARC is 4.2.32. I'm having an odd problem where modem 24 is being troublesome quite often. It appears to work for short periods of time though (a few seconds). I'm unsure how to identify whether its the modem or a problem with the telco T1. Does anyone have any tips on a good way to test the modem or line within the ARC? Thanks, Dan - 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

(usr-tc) Problems with new HiperARC Code
by Jorge Lozano 05 Jan '00

05 Jan '00

Hi! I´m trying upgrade HiperARC firmware with TCM 6.0.86 to new version (4.2.32). But during the firmware transfer (65% aprox.), the TCM give me an error... Failed. TFTP error: Access violation Can you tell me why? Thanks for all your help! Jorge Lozano M. ------------------------------------------------ Este mensaje fue enviado usando Andinet WebMail. http://www.andinet.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) Dedicated IP pools
by Stainforth, Matthew 05 Jan '00

05 Jan '00

Without splitting the trunks you have no way of guaranteeing a call will or won't be delivered to slot:x/mod:y. The charge by our telco is tarrifed at $250 installation per trunk group affected plus $1.30/month per extra telephone number. I wouldn't think it would vary much by region but I guess you never know with telcos. Matthew Stainforth || Technical Services Manager || BrunNet Inc. > -----Original Message----- > From: Cheryl Johnson [mailto:netadmin@seidata.com] > Sent: Wednesday, January 05, 2000 12:56 PM > To: usr-tc(a)lists.xmission.com > Subject: Re: (usr-tc) Dedicated IP pools > > > Well, this is what I am trying to stay away from to avoid the > hefty charges > the telcos charge to split the trunks on an active circuit. > But maybe with > what I have will work as long as I have plenty of modems > available. I'll > keep digging for possibilities....thanks. > > Cheryl Johnson > netadmin(a)seidata.com > SEI Data Network Services, Inc. > > > ----- Original Message ----- > From: Stainforth, Matthew <MatthewS(a)staff.brunnet.net> > To: <usr-tc(a)lists.xmission.com> > Sent: Wednesday, January 05, 2000 9:33 AM > Subject: RE: (usr-tc) Dedicated IP pools > > > > > > if you want to have a set of modems to which only a select > group will have > > access, you will need to have the telco split up your > trunks into multiple > > trunk groups and assign separate numbers to each. Then you > would need to > do > > DNIS based authentication on the RADIUS side. Also confirm > with the telco > > that they are sending DNIS digits. > > > > Matthew Stainforth || Technical Services Manager || BrunNet Inc. > > > > > > > -----Original Message----- > > > From: Cheryl Johnson [mailto:netadmin@seidata.com] > > > Sent: Wednesday, January 05, 2000 10:13 AM > > > To: usr-tc(a)lists.xmission.com > > > Subject: Re: (usr-tc) Dedicated IP pools > > > > > > > > > Ok, configuring this through the ARC works quite well at > > > least for a limited > > > number of users. This doesn't actually set a specific modem > > > to the dedicated > > > user. I am trying to pull a modem...say > <slot:15:/mod:[24}> out of the > > > available pool on the DSP card and set this up for a > modem_group named > > > <dedicated> so this modem can only be used by a specific user > > > and not the > > > entire public pool. Although I haven't found the command set > > > to do this yet, > > > but think I am heading in the right direction. Theoretically, > > > yes the modem > > > should always have a modem to connect to if you set the > public ip_pool > > > <whatever> number less on the available number of modems, but > > > this is not a > > > true dedicated modem because the user may not always get the > > > same modem. > > > This would more helpful in troubleshooting, if problems > arise for a > > > dedicated user. > > > > > > > > > Cheryl > > > > > > ----- Original Message ----- > > > From: James Sewell <jsewell-lists(a)home.com> > > > To: <usr-tc(a)lists.xmission.com> > > > Sent: Tuesday, January 04, 2000 5:07 PM > > > Subject: Re: (usr-tc) Dedicated IP pools > > > > > > > > > > Two ways to do it: > > > > > > > > Set your users up in a RADIUS server. For those users who > > > need to get > > > > an address in the private pool, set RADIUS attribute #217 > > > > "Framed-IP-Addr-Pool-Name" to the name of the private pool. Any > > > > existing users who do not have anything set for this > parameter will > > > > continue to get an address from the original public pool. > > > This would > > > > also explain why you are currently only seeing the > public pool being > > > > used. > > > > > > > > > > > > The second way is to confugure the user accounts directly > > > on the HiPer > > > > ARC. It's more cumbersome to manage a user database > directly on the > > > > card, but if it's only s few users, it might be easier > to make the > > > > change here than in your RADIUS database. Add the user > > > account and set > > > > any other desired parameters as usual, then to set the > > > private IP pool > > > > use this command: > > > > > > > > add address_pool user <user_name> pool_name <pool_name> > > > > > > > > > > > > -James > > > > > > > > > Cheryl Johnson wrote: > > > > > > > > > > hello usr list fans...I got another project I am not sure > > > how to set > > > > > up. I am trying to set up a dedicated <private> pool for > > > only specific > > > > > users to use for a somewhat called dedicated modem. Now > > > the problem is > > > > > I set up two different pools one for public and one for > > > private but > > > > > only the public and be accessed. Using a T1, how do you > > > set this up? > > > > > > > > > > Any ideas, please reply. > > > > > > > > > > Thanks, > > > > > -C > > > > > > > > - > > > > 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. > - 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) Total Control Software Questions
by Scott Boggs 05 Jan '00

05 Jan '00

We also use Steel Belted RADIUS from Funk.com I like it a lot. Especially its ability to handle VSAs for multiple vendors. We have a TC and two ascend Maxs, and SBR serves both simultanesouesly. Their latest version has a command line adapter that can admin from dos prompt. Scott Boggs AccessUnited ISP Operations > -----Original Message----- > From: Greg Long [SMTP:greg@coastlink.com] > Sent: Wednesday, January 05, 2000 11:23 AM > To: usr-tc(a)lists.xmission.com > Subject: RE: (usr-tc) Total Control Software Questions > > We've got a Total Control Hub with 48 modems. Steel Belted Radius runs on > NT and allows you to monitor who is on. It also does a really nice job > with > accounting. www.funk.com > > -Greg > > -----Original Message----- > From: owner-usr-tc(a)lists.xmission.com > [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of meijin(a)vvm.com > Sent: Tuesday, January 04, 2000 10:06 PM > To: usr-tc(a)lists.xmission.com > Subject: (usr-tc) Total Control Software Questions > > > I am inheriting an older Total Control system with a total of (I believe) > 46 or 48 modems. I come from a background of Portmaster products. So, I am > curious about software. Is there a Radius server for NT that works with > this equipment? Also, is there something that is similar to PMVision? That > is, allows me to monitor the modems and who is on them and such from the > PC? All from an NT environment? Is this stuff bundled with the hardware or > is it sold extra? Any apps out on the net for this? Any help? > > Thanks! > > dr > > > - > 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) Dedicated IP pools
by Stainforth, Matthew 05 Jan '00

05 Jan '00

if you want to have a set of modems to which only a select group will have access, you will need to have the telco split up your trunks into multiple trunk groups and assign separate numbers to each. Then you would need to do DNIS based authentication on the RADIUS side. Also confirm with the telco that they are sending DNIS digits. Matthew Stainforth || Technical Services Manager || BrunNet Inc. > -----Original Message----- > From: Cheryl Johnson [mailto:netadmin@seidata.com] > Sent: Wednesday, January 05, 2000 10:13 AM > To: usr-tc(a)lists.xmission.com > Subject: Re: (usr-tc) Dedicated IP pools > > > Ok, configuring this through the ARC works quite well at > least for a limited > number of users. This doesn't actually set a specific modem > to the dedicated > user. I am trying to pull a modem...say <slot:15:/mod:[24}> out of the > available pool on the DSP card and set this up for a modem_group named > <dedicated> so this modem can only be used by a specific user > and not the > entire public pool. Although I haven't found the command set > to do this yet, > but think I am heading in the right direction. Theoretically, > yes the modem > should always have a modem to connect to if you set the public ip_pool > <whatever> number less on the available number of modems, but > this is not a > true dedicated modem because the user may not always get the > same modem. > This would more helpful in troubleshooting, if problems arise for a > dedicated user. > > > Cheryl > > ----- Original Message ----- > From: James Sewell <jsewell-lists(a)home.com> > To: <usr-tc(a)lists.xmission.com> > Sent: Tuesday, January 04, 2000 5:07 PM > Subject: Re: (usr-tc) Dedicated IP pools > > > > Two ways to do it: > > > > Set your users up in a RADIUS server. For those users who > need to get > > an address in the private pool, set RADIUS attribute #217 > > "Framed-IP-Addr-Pool-Name" to the name of the private pool. Any > > existing users who do not have anything set for this parameter will > > continue to get an address from the original public pool. > This would > > also explain why you are currently only seeing the public pool being > > used. > > > > > > The second way is to confugure the user accounts directly > on the HiPer > > ARC. It's more cumbersome to manage a user database directly on the > > card, but if it's only s few users, it might be easier to make the > > change here than in your RADIUS database. Add the user > account and set > > any other desired parameters as usual, then to set the > private IP pool > > use this command: > > > > add address_pool user <user_name> pool_name <pool_name> > > > > > > -James > > > > > Cheryl Johnson wrote: > > > > > > hello usr list fans...I got another project I am not sure > how to set > > > up. I am trying to set up a dedicated <private> pool for > only specific > > > users to use for a somewhat called dedicated modem. Now > the problem is > > > I set up two different pools one for public and one for > private but > > > only the public and be accessed. Using a T1, how do you > set this up? > > > > > > Any ideas, please reply. > > > > > > Thanks, > > > -C > > > > - > > 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