Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Merlin Legend Rel 7 V.10.0 ** Trouble connecting PRI

Status
Not open for further replies.

mardotek

Technical User
Nov 18, 2006
15
US
I hope some one can help me...

System description:
Merlin Legend Rel 7 V.10.0 - 2 cabinets
cabinet 1: Procesor and 5 408-cards
cabinet 2: 1 008-OPT card (w/8 VM ports), 3 408-cards, 1 016-S/L card and 1 100D-card
Paradyne 3160 external CSU

Problem:
PRI does not come up. Red light on 100D board

Signal is good up to the CSU
I did the programing for both the PRI board and the extensions.
unable to call in or out.


 
yes, I have followed those instruction already.

One thing I am not too sure about is the cable going from the CSU DTE port to the 100D card. This is a custom made cable. What should the pinout be?
 
OK, who is your provider?

We need to start there.

Also, print and post your PRI setup.
 
The provider is Cavalier (Virginia)

This the PRI config (I don't have a printer attached to the laptop i'm using to config the system)

* Slot: 10 (I swapped the 100D and 016S/L); card type: 100D; circuit type: PRI
* ESF / B8ZS
* Switch Type: 5ESS
* Ntwk Svc: CallByCal
 
We really need more info.

First off, when you print anything from SPM, you create a file.

So my suggestion is print the following:

PRI Info & the Error Log

Then, get them to a computer that you can use to post that info here.

 
Thanks merlinman, I hope this helps.
***********************************

WinSPM - Version 4.0
SYSTEM INVENTORY
Location: ***
Captured: 11/19/2006 11:37:00AM
Carrier: 1 .
Hardware Firmware Application
Slot Board Type Vintage Vintage Vintage Serial Number
0 Processor: CKE4 01
1 4O8GLM-U 11 42 30
2 4O8GLM-U 11 42 30
3 4O8GLM-U 11 42 30
4 4O8GLM-U 11 42 27
5 4O8GLM-U 11 42 31

Carrier: 2 .
Hardware Firmware Application
Slot Board Type Vintage Vintage Vintage Serial Number
6 OO8OPT 53 11
7 4O8GLM-U 11 42 27
8 408 GS/LS-MLX 02 28
9 4O8GLM-U 11 42 25
10 100D 2B 90
11 O16TRR 50 11 19


WinSPM - Version 4.0
EVENT LOG
Location: Captured: 11/19/2006 11:54:59 AM
Site Name User Name Type Date Time
admin Error 5/3/2006 5:34:34 PM
Entry Text :Exception
Error Text :Access violation at address 0041 DE46 in module ‘WinSPM.exe’. Read of address 01 4262D0
Annotation
admin Error 5/24/2006 6:10:23 PM
Entry Text :Exception
Error Text :Access violation at address 00403280 in module ‘WinSPM.exe’. Read of address 01 98AFD7
Annotation
admin Error 11/17/2006 5:28:14 PM
Entry Text :Exception
Error Text :Data transfer aborted!
Annotation
admin Error 11/17/2006 5:35:25 PM
Entry Text :Exception
Error Text :Key violation.
Annotation
admin Error 11/17/2006 6:29:41 PM
Entry Text :Exception
Error Text :ie_Dpen - device already open
Annotation
admin Error 11/18/2006 5:28:12 PM
Entry Text :Exception
Error Text :ie_Dpen - device already open
Annotation
admin Error 11/18/2006 6:21 :46 PM
Entry Text :Exception
Error Text :ie_Dpen - device already open
Annotation
 
Well, we were looking for the ERROR log, not the EVENT log.

Also, if you could print PRI Info, not System Info, that would get us going.

 
Did you do a "board renumber" after switching the locations of the 100 DS1 with the 016 T/R module? If not - you need to do so - for the cards to be properly recognized in their new slot locations.

Tom Daugirdas,
President
STCG, Inc.
stcg.com
 
Tom,
Yes, I did renum the boards and reconfig the PRI settings in the new slot
 
Question...
Can I bypass the CSU and go straight from the smart jack to the 100D board? just in case the csu is causing the problem.
 
As far as I know you can. The requirement to use a CSU - I believe is outdated - but may be "required" by the carrier. I would double-check with Merlinman - this is his area of expertise.

Tom Daugirdas,
President
STCG, Inc.
stcg.com
 
merlinman,
I hate to say it but when I try to see the ERROR log or the PRI Info, I get nothing. I did the data gathering before checking the logs but they come up empty.
 
Yes you can bypass the CSU for testing. It used to be the law that you needed one. I am not sure if that has changed but I always bypass it for testing when there is a problem.
 
You should be able to see these things when you get to the PRINT part of the MENU.

 
I appreciate everyones help. I got it working bypassing the csu.
Thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top