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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Dual PRI - No D channel on second PRI

Status
Not open for further replies.

Schaef87

Vendor
Jan 19, 2017
26
US
System has a VCM32/PRI2 card and is getting PRI service from a "dialer" (as the customer puts it), and a newly connected PRI. The new PRI has a solid link light and the provider can see the connection, however there is no D channel.

I have set the clock to Network/Fallback and Fallback/Network on Ports 9/10 respectively and cannot get the D channel to come up. I also tried to test the trunk in SSA and I don't even get synchronization.

Any ideas?

_________________________________________

I'll come up with a good signature, someday.
 
If I am understanding, you have one working and one non-working PRI. Have you tried swapping them to verify it isn't a providor issue? Also PRI channels are Admin out of service by default.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
Falc 13 represents the PRI that was already active, Falc 14 represents the new PRI circuit that was installed. There was a loopback plug in port 10 (line 14) to test the card itself, and that was removed at 78037520mS and the cable from the provider equipment was plugged back in.

So I'm assuming that the provider, Centurylink in this case, has misconfigured something?

Code:
  78018179mS PRN: WARNING:
  78018179mS PRN: ****Reset Slip Store Falc 13 1 0 
  78018179mS PRN: 
  78018180mS PRN: WARNING:
  78018180mS PRN: 14:39:45 
  78018180mS PRN: 
  78025706mS PRN: Line 14: PRBS 15^2-1: Generation and Monitor - synchronised
  78032574mS PRN: Slot 4, Falc 14: LOCK RAI crc=1 set=0  FMR1=de  FMR2=68
  78032577mS PRN: Falc: LockToFalc: 13
  78032577mS PRN: MEZZ_PRI_CLOCK_CNTL: f1
  78032577mS PRN: FPGA_REC_CLK_SELECT: 0e
  78032577mS PRN: SetSlaveMode: 0d
  78032667mS PRN: Slot 4, Falc 13: LOCK RAI crc=1 set=0  FMR1=de  FMR2=60
  78032672mS PRN: Lock To Internal Clock, FPGA_REC_CLK_SELECT = 0x00
  78033520mS PRN: Falc 14 PRBS errors 15
  78034574mS PRN: Slot 4, Falc 14: YELLOW ALARM ON
  78035706mS PRN: Line 14: PRBS 15^2-1: Generation and Monitor - synchronised
  78037520mS PRN: Falc 14 PRBS lost synchronisation
  78042742mS PRN: Falc: LockToFalc: 13
  78042742mS PRN: MEZZ_PRI_CLOCK_CNTL: f1
  78042742mS PRN: FPGA_REC_CLK_SELECT: 0e
  78042742mS PRN: SetSlaveMode: 0d
  78045706mS PRN: Line 14: PRBS 15^2-1: Generation and Monitor - unsynchronised
  78047035mS PRN: Falc: LockToFalc: 14
  78047035mS PRN: MEZZ_PRI_CLOCK_CNTL: f3
  78047035mS PRN: FPGA_REC_CLK_SELECT: 0e
  78047035mS PRN: SetSlaveMode: 0e
  78049035mS PRN: Slot 4, Falc 14: YELLOW ALARM OFF
  78055706mS PRN: Line 14: PRBS 15^2-1: Generation and Monitor - unsynchronised
  78061520mS PRN: Falc 14 tristate transmitter
  78064520mS PRN: Falc 14 re-enable transmitter

_________________________________________

I'll come up with a good signature, someday.
 
Found the issue. The Dialer was setup with the CO setting, as it wasn't a "real" PRI.
The engineer just copied the settings for the new PRI circuit instead of setting it to CPE.

[banghead]

_________________________________________

I'll come up with a good signature, someday.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top