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

(usr-tc) Telco cluster fsck
by Brian 20 Oct '99

20 Oct '99

Battling with telco still over problematic CT1's in a remote pop. I found out they provisioned the lines as LINE SIDE (open mouth, insert gun, pull trigger) instead of TRUNK SIDE. Below is the email I sent them on how to provision the lines.........is their anything in it that would indicate I was asking for trunk side instead of line side service, because I know they are going to throw in my face "you didn't ask for TRUNK side specifically", so I am hoping that the provisioning info below would only be valid for trunk side service. I sent them: 1. Line Coding: B8ZS * AMI 2. Framing: ESF * SF 3. Trunk type: E&M II loop start ground start * 4. Trunk Start: wink immediate dial tone * 5. Dial-In address Acknowledgment Wink enabled disabled * 6. T1 Tone type (signalling) mf dtmf * 7. # of DTMF Tones: 4 8. DNIS sent: yes ANI sent: yes number of digits sent: 4 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.

3 3

(usr-tc) Netserver
by Dataheart 20 Oct '99

20 Oct '99

thanks the passwords for the NMC worked. Now how do I reset the passwordss on a Netserver PRI. its not Dip Switch 6? Thanks again, Aaron - 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) NMC NAC troubles + Passwords
by Robert von Bismarck 20 Oct '99

20 Oct '99

Password = read-write SNMP community string, if you enter the read-only string, you will be able to get into your NMC but you won't be able to modify anything ;-) To erase it go in the NMC console, select 1. Configuration and 14. PASSWORD Screen Enable/Disable then select 2. Disable. Then save the config to NVRAM. Robert > 2. I have a NMC with a password on the console. is there any way to > erase this password. > > Thank you all, > Aaron > > > - > 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) NMC NAC troubles + Passwords
by Steve Valiunas 20 Oct '99

20 Oct '99

You won't be able to use the dual v.35 nics behind an NMC- You might get the console up but I doubt if you'll ever get it to talk on the ethernet port. The Passwords are the community strings. They can be disabled after you get in with a menu option. If you can't get past the password then try flipping dipSwitch #6 up, that should bypass them. The red/green LED means that the NMC didn't see a network connection when it booted up. Steve Dataheart <lists(a)dataheart.net> on 10/20/99 06:12:25 AM Please respond to usr-tc(a)lists.xmission.com Sent by: Dataheart <lists(a)dataheart.net> To: usr-tc(a)lists.xmission.com cc: (Steve Valiunas/MW/US/3Com) Subject: (usr-tc) NMC NAC troubles + Passwords Howdy, 1. For my NMC I have a High Speed WAN/ Ethernet NIC, which has the console at the top then 2 v.35 then the 10BaseT at the bottom the seller told me that they were pulled from a working system, they mush have been used for Netservers because thats where the jumper was set to when they arrived. So I changed the jumper from NAC to NMC then inserted the NMC and it powers up with the Hub Status light red, the rn/fl light flashing between red and green and USR written on the 4 character display. I know the NMC works I have had it working in another rack. is there anything special I have to do when changing the High Speed WAN/Ethernet NIC from a netserver to a NMC. New code or something. Also when this is happening I get nothing on the console 2. I have a NMC with a password on the console. is there any way to erase this password. Thank you all, Aaron - 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) NMC NAC troubles + Passwords
by Dataheart 20 Oct '99

20 Oct '99

Howdy, 1. For my NMC I have a High Speed WAN/ Ethernet NIC, which has the console at the top then 2 v.35 then the 10BaseT at the bottom the seller told me that they were pulled from a working system, they mush have been used for Netservers because thats where the jumper was set to when they arrived. So I changed the jumper from NAC to NMC then inserted the NMC and it powers up with the Hub Status light red, the rn/fl light flashing between red and green and USR written on the 4 character display. I know the NMC works I have had it working in another rack. is there anything special I have to do when changing the High Speed WAN/Ethernet NIC from a netserver to a NMC. New code or something. Also when this is happening I get nothing on the console 2. I have a NMC with a password on the console. is there any way to erase this password. Thank you all, Aaron - 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) Hung Modems/What to do?
by Blake Fithen 19 Oct '99

19 Oct '99

is that 1.2.37? blake > -----Original Message----- > From: Brian [mailto:signal@shreve.net] > Sent: Monday, October 18, 1999 11:40 PM > To: usr-tc(a)lists.xmission.com > Subject: Re: (usr-tc) Hung Modems/What to do? > > > > > If you are talking about the situation where a modem goes out > and so does > the one next to it, that is supposedly addressed in a service release. > > > On Mon, 18 Oct 1999, Marshall Morgan wrote: > > > Much of the discussion over the past few days has been > quite interesting, but > > what are people doing with the modem+neighbor modem hung > problem in the field? > > We have many of our new DSPs doing this (2-4 DSPs running > CT1 and PRI). Also, > > we have had DSPs on PRI's hang the d-channel or T1 carrier > as well (maybe telco > > here). > > > > Running 2.0.81 HDM and 4.1.59-6 ARC code. > > > > BTW: Anyone at 3Com going to take us up on that offer for a > meeting? Gordon > > Biersch (http://www.gordonbiersch.com/) was fun, but what > about a serious > > discussion first! > > > > Thank you, > > > > 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 > > > > > > - > > 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.

1 0

(usr-tc) Radius attribute
by Tim Wolfe 19 Oct '99

19 Oct '99

Is there a radius attribute that can be passed to the TC that will limit a users session time? Similar to Livingston's Session-Timeout (which doesn't seem to do anything on the TC...) Thanks, -- Tim -------------------------------------------------- * Timothy M. Wolfe, Chief Network Engineer * * ClipperNet Corporation / It's a wireless world * * tim(a)clipper.net 800.338.2629 x 402 * * Sufficient for today = Inadequate for tomorrow * -------------------------------------------------- - 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) Cistron checkrad.pl script
by farber＠admin.f-tech.net 19 Oct '99

19 Oct '99

Hello fellow Total Control victems. My name is Paul... and I own an ARC chassis <group> Hi Paul Anyways... for everone out there using the most exellent Cistron Radius 1.5.4.3 daemon there is a bit of a problem with the checkrad.pl script that checks the simeltaneous-use on the ARC vi SNMP. When the radius acct packet comes in it has the port number prefixed with an S (S10, S1010) and the code did not strip out that letter before it built the OID to snmpget from the ARC. So basically is was never checking the arc to see if they were already logged in. So.. in all its glory... I give my fix... cut,paste,enjoy. sub usrhiper_snmp { # Somebody please verify???? # remove leading S from port # $_=$ARGV[2]; s/S//; my($slot) = $_; my($oidext) = $slot + 1256; my ($login); $login = snmpget($ARGV[1], "public", "$usrm.4.10.1.1.18.$oidext"); print LOG " snmpget info: $login\n" if ($debug); #($login) = /^.*\"([^"]+)".*$/; print LOG " user at port [S]$slot: $login\n" if ($debug); ($login eq $ARGV[3]) ? 1 : 0; } Wait... no warranties, not refunds, send free beer and pizza to the address below (anything other than Coors light will be proptly returned to sender). Paul Farber Farber Technology farber(a)admin.f-tech.net Ph 570-628-5303 Fax 570-628-5545 - To unsubscribe to usr-tc, send an email to "majordomo(a)xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.

1 0

RE: (usr-tc) Performance monitoring/ANI information from Dual T1 card running PRI
by Stainforth, Matthew 19 Oct '99

19 Oct '99

The attribute name I use is Calling-Station-ID. I can't remember if I had to add that to the dictionary or if it was in there already (I think it was in there but...). If you don't have it, let me know and I'll look it up. Matthew > -----Original Message----- > From: Scott Trautman [mailto:scottt@corp.gdinet.com] > Sent: Tuesday, October 19, 1999 2:43 PM > To: 'usr-tc(a)lists.xmission.com' > Subject: RE: (usr-tc) Performance monitoring/ANI information from Dual > T1 card running PRI > > > Beauty. That's what I thought. Now to confirm I have the right radius > attributes in there. > > -----Original Message----- > From: dciresi(a)defunct.ae.usr.com [mailto:dciresi@defunct.ae.usr.com] > Sent: Tuesday, October 19, 1999 12:18 PM > To: Scott Trautman > Cc: 'usr-tc(a)lists.xmission.com' > Subject: Re: (usr-tc) Performance monitoring/ANI information from Dual > T1 card running PRI > > > Scott, > > If you are terminating ISDN on the Munich daughterboard, you > will not be > able to view the Called/Calling-Number-info. This is > specifically located > on the modem. This information should be in the Netserver RADIUS > requests, however. > > Dominic > > On Tue, 19 Oct 1999, Scott Trautman wrote: > > > I'm guessing the answer is "can't get there from here" > unless it's modem > > calls. > > I'm interested in the calling number info that is coming in > on the PRI. > > > > I can view a modem call and get the calling number info, > but not on ISDN, > > which > > is all I'm running. Trying performance monitor on the T1, > nothing there > > like it. > > > > Using a Netserver with das Munich daughterboard und dual > T1, works really > > quite well. Might be a mighty cheap way for some of you to > do ISDN only > > traffic for dedicated customers. You can do the Dual PRI& > Netserver in > > same chassis as with a HiperARC & DSP's. Neat. > > > > I'm also wondering whether I can get via radius accounting > that "calling > > number" from a Netserver/or is it NMC??? > > > > Anybody be able to shed some light? > > > > SMT > > > > Scott M. Trautman 800-482-4638 > > Global Dialog Internet 608-240-4638,4637fax > > 2810 Crossroads, STE LL2 scott(a)gdinet.com > > Madison WI 53718 http://www.gdinet.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. > - 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) CT1 and Remote Pop
by andrew smith 19 Oct '99

19 Oct '99

This is slightly off-topic: I am looking to provide dial-up service to few rural towns outside of our local dialing area. These are *small* rural communities, 20, 30, and 60 miles away from our main office. I seriously doubt any of these communities will ever need more than 96 dial-up lines, and many will start out with just 24-48 lines. Because of their size, I don't particularly want to put a Total Control Chassis in a closet somewhere. I envision doing the following: 1. Having CT1s longhauled back to our main office so everything can be in a centralized location. Each of these towns are in US Worst's area except for one, so I don't see any type of foreign exchange fee between telcos. The one independent telco was going to charge us a small foreign exchange fee to link with US Worst. I know I will have to pay mileage fees on all the lines. My question is, how distance sensitive is a CT1? Has anyone else done this? Would a CT1 running 60 miles between telcos offer quality 56k access? What other technical issues, problems, or financial issues am I overlooking? - andrew - 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