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

(usr-tc) NMC Command Reference
by Brian 07 Oct '99

07 Oct '99

I am trying to get a handle on the Command Reference to use with HiperNMC 6.x. I don't see a HiperNMC 6.x command reference on TotalService. What I do see is: NMC version 5.0 parameter reference HiPer NMC Parameter Reference Errata Sheet HiPer NMC SNMP and MIB Reference Errata Sheet V6.0, 6.1, 6.2 That being said, are those the 3 files I should look at, or does a "HiperNMC version 6.0 parameter reference" exist somewhere? I am assuming you just go about using the 5.0 parameter reference with a few changes documented in the erattas........... 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

(usr-tc) pri dsp d-channel problem
by Steve McConnell 07 Oct '99

07 Oct '99

I have a new PRI (new DSP card for that matter) installed in an existing chassis. I am getting a LPBK/D-Chan red alarm on the new span. So I am obviously getting no calls being terminated on my equipment. When I pull up a com session into the DSP and do a display d-chan , I get span1> display d-chan Span1 D-channel Operational is: DOWN software: Software Version 2.0.19 Regulatory Version 1.0 Other than this all looks fine, it is supposedly configed the same as an existing circuit which is working fine. My DSPs are configged the same way. Sprint has dispatched a tech and says that all is fine as far as they can see. Is it possible that I have missed a setting somewhere that would cause this same reaction? steve Steve McConnell EMJI 919-303-3217 888-258-8959 - 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) pri dsp d-channel problem
by Stainforth, Matthew 06 Oct '99

06 Oct '99

If I remember correctly, I saw the same thing when I had the primary switch type set wrong on the card. There are not many things to verify for a PRI though - framing, coding, switch type, and NFAS settings if you use it. On Wednesday, October 06, 1999 2:28 PM, Steve McConnell [SMTP:stevem@emji.net] wrote: > I have a new PRI (new DSP card for that matter) installed in an existing > chassis. > > I am getting a LPBK/D-Chan red alarm on the new span. So I am obviously > getting no calls being terminated on my equipment. > > When I pull up a com session into the DSP and do a display d-chan , I get > > span1> display d-chan > Span1 D-channel Operational is: DOWN > > software: > Software Version 2.0.19 > Regulatory Version 1.0 > > Other than this all looks fine, it is supposedly configed the same as an > existing circuit which is working fine. > My DSPs are configged the same way. Sprint has dispatched a tech and says > that all is fine as far as they can see. > Is it possible that I have missed a setting somewhere that would cause > this same reaction? > > > > steve > > > Steve McConnell > EMJI > 919-303-3217 > 888-258-8959 > > > - > 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) Quad cards not answering analog calls
by Network Administrator 06 Oct '99

06 Oct '99

I am using the v.34 analog/digital Quad cards (v.5.6.7) with the Netserver card. I had six existing cards using the same version of software. I recently added 8 new lines to this box and two quad cards. The quads will not answer incoming calls. I have checked each modem individually as well as tried other cards and re-flashed the code to the cards. If anyone has any idea what may be the problem, please reply. -Cheryl Seidata Network Services, Inc. http://www.seidata.com

1 0

(usr-tc) Slow Busy on Dual PRI NAC
by Dataheart 06 Oct '99

06 Oct '99

Greetings, I have a wierd problem that I am unable to resolve, it goes a little something like this. I have a Total Control Chassis, It all appears to be configured correctly but when I dial into it, the line goes quies for about 10 seconds then a busy signal. I have followed the enable Debug routein but even then the Call control call stats show no dialins even after several attempts this got me thinking that it was a telco problem that was until I enabled Display Call Control Debug Info and then whenever I dialed in I got this on the console; :uccu_get_new_uccb: attach uccb to head of list. tcid: 0x1e ucid: 0x0000001e uccu_get_new_uccb: ALLOC tcid: 0x1e ucid: 0x0000001e, allocated = 1, dsl_id=1 sfn:ucc_null,evt:20-SETUP_IND,tcid:0x1e,ucid:0x0000001e ucc_setup_in_call: tcid: 0x1e, CRV: 38 (0x26) DNIS nums:2 cl type override nums:0 ucc_setup_in_call: ANI (calling_phnum) ><, len = 0, err = 0x31 ucc_setup_in_call: Info buffer allocated GetDS0SlotMapByte: mdm_id=0 span=1 ds0=32 octet=3 bitmap=80 GetDS0SlotMapByte: mdm_id=0 span=1 ds0=32 octet=2 bitmap=0 GetDS0SlotMapByte: mdm_id=0 span=1 ds0=32 octet=1 bitmap=0 GetDS0SlotMapByte: mdm_id=0 span=1 ds0=32 octet=0 bitmap=0 uccu_get_tncid_uccb: tcid = 0x1e, position in uccb list = 0, dsl = 1 sfn:ucc_s8_go_null,evt:15-CLEAR_IND,tcid:0x1e,ucid:0x0000001e uccu_releasing uccb: DE-ALLOC: tcid = 0x0, ucid = 0x0000001e uccu_release_uccb: Info buffer released uccidm_release_ds0: span = 1, ds0 = 32 uccu_release_bchs: DE-ALLOC ucid: 0x0000001e The first 1/2 happens when I dial then after the space is when it sends me the busy signal? Any Ideas? Thanks, 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.

1 0

(usr-tc) hiperarc and multicast
by Laszlo Vecsey 05 Oct '99

05 Oct '99

I have multicast available on my network, through a Cisco router. Will the hiperarc route multicast to dialup users, natively? Or does each dialup user have to run a program like 'mTunnel' or use another method to set up a unique tunnel, like with mrouted. lv. - 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) HiPer DSP and E1/R2
by Daniel Mpolokoso 05 Oct '99

05 Oct '99

Hi, I've been battling for a week trying to get HiPer DSP version 2.0.19 to interface with our telco's switch. They are using basic E1 R2 signaling as per ITU-T standards. I'd be grateful for anyone out there using E1 R2 signaling to give me pointers as to what version of software I should be running and examples of typical configurations. Thanks, Daniel. ------------------------------------------------------------------------ Daniel Mpolokoso - Technical Manager, Email: daniel(a)zamnet.zm ZAMNET Communication Systems Limited, Phone: +260 - 1 - 772516 P.O. Box 38299, Lusaka, Zambia. Fax: +260 - 1 - 224775 - 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) Microsoft VPN problems via TC
by GTI x2 Tech 05 Oct '99

05 Oct '99

Objective: To promote awareness of Microsoft Virtual Private Networking (VPN) problems experienced with USR Total Control Manager Terminal Servers. Test Equipment for Experiment #1: VPN Server: Microsoft NT 4.0 (SP5) Server 100base-T Ethernet VPN Client: Windows 98 Standard Modem 33.6 kbps Environment: a) An NT user account was created with logon locally services rights. b) MS-VPN and Remote Access (RAS) was configured for remote connectivity and VPN with 1 available network. c) Private class-c IPs were assigned to the VPN network for dynamically assigned addressing of remote clients. d) Network Domain was configured and named XYZ e) Win 98 machine was configured for Dial-up Networking including Dial-up adapter, TCP/IP and Microsoft Virtual Private Networking Dial-up adapter, and VPN Networking. f) Win 98 domain (workgroup) was set to XYZ. Dialup networking Test Results: (Livingston Port Master 2e) Using the standard Dial-up networking in Windows 98, I established an Internet connection to GTI using the analog Livingston Port Master 2e. I verified my connectivity by the use of such utilities as ping, traceroute and standard http, FTP and Telnet protocols. At that point I launched the VPN Dialup networking connection to the VPN server. The VPN server verified and authenticated my account and logged me in. I then ran a netstat utility to display my current Internet IP as well as the newly assigned private class-c IP provided by the VPN server. I could then go into Network Neighborhood and access every machine belonging to the XYZ domain, based on my account privileges previously configured at the VPN server user account manager. Test Results: (USR Total Control) Using the identical environments as above, I changed the dial-up node number to connect to the USR Total Control Terminal Server. The VPN authenticated my user account and logged me in, but there was absolutely NO connectively to the XYZ domain and the Internet connection completely stalled. Hypothesis: I believe the USR units are prohibiting the use of VPN somehow. Clients should be able to pass VPN packets regardless of what dialup they use. The Livingston 2e does not have a problem with VPN at all, so it looks like the USR is mis-configured somehow. Any insight would be appriciated. - 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) Netserver Code
by Dataheart List Email 05 Oct '99

05 Oct '99

Hi, Recently I decided to upgrade the firmware on me netserver card, I was send the code by the 3com technitian but it appears to be the wrong one? The code from the 3com tech starts with Li while TCM prompts me for Le code? can someone please send me the Le code? Thanks, 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.

3 2

(usr-tc) Dual channel ISDN problem.
by Horace Demmink 05 Oct '99

05 Oct '99

I have been trying to figure out a problem that one of my customers has been having. They are dialing up with a 3COM NetBuilder to our TC equipment. The first channel comes up fine, but the second one will not come up. The NetBuilder attempts to bring it up, fails, and waits a few seconds before trying again. ISDN is $.08 per call in this area so they are racking up quite a bill. I have never seen this before with any other customer, and as far as I know they are the only ones with a 3COM NetBuilder, so I am assuming that it is a problem or misconfiguration with their router. Is anyone else familiar with these things? Thanks very much in advance for any help or advice anyone can offer. We are running: ARC 4.2.32-1 DSP 2.0.81 Here is the relevant section of their radius entry: username Auth-Type = System Service-Type = Framed, Framed-IP-Address = xxx.xxx.xxx.xxx, Framed-IP-Netmask = 255.255.255.255, Framed-Protocol = PPP, Framed-Route = "yyy.yyy.yyy.yyy/30 0.0.0.0 1", Framed-Routing = None, Framed-MTU = 1500, Idle-Timeout = 0, Port-Limit = 2, Framed-Compression = Van-Jacobson-TCP-IP And the following is about a minutes worth of a dump of a monitor ppp from the arc: Decode tracing started, press ESCAPE to stop; press X for hex tracing. Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf d8 2e c8 68 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 00 00 00 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 00 00 00 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Outgoing PPP Data on interface: slot:15/mod:21 PAP ACK Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 00 00 00 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 00 00 00 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Outgoing PPP Data on interface: slot:15/mod:21 PAP ACK Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 00 00 00 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 00 00 00 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 18 d8 2e c9 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Outgoing PPP Data on interface: slot:15/mod:21 PAP ACK Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 00 00 00 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 50 68 6f 6e Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 00 00 00 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Outgoing PPP Data on interface: slot:15/mod:21 PAP ACK Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf d8 2e c8 68 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 00 00 00 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 65 6c 64 20 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Outgoing PPP Data on interface: slot:15/mod:21 PAP ACK Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 00 2e c8 68 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 54 48 49 53 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 6e 64 20 4a Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf d8 2e c8 68 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Outgoing PPP Data on interface: slot:15/mod:21 PAP ACK Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 81 d8 2e c9 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 39 36 36 3b Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf d8 2e c8 68 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Outgoing PPP Data on interface: slot:15/mod:21 PAP ACK Incoming PPP Data on interface: slot:15/mod:20 LCP ECHO_REQ 00 cc f7 cf 69 d8 2e c1 Outgoing PPP Data on interface: slot:15/mod:20 LCP ECHO_RPLY c4 56 fa 71 Tracing stopped, Return/Enter to re-start, ESCAPE to quit. -- Horace Demmink PathWay 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.

3 3