Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Cisco 3745 w/NM-HDV2-2T1/E1 Clocking Question

I inherited a Cisco 3745 with a NM-HDV2-2T1/E1 card with a VWIC2-2MFT-T1/E1 card installed. We currently have 3 PRI's connected to the router. 3/0 is a PRI from one carrier and 3/1 and 3/2 are PRI's from another carrier. Can someone please explain the correct clocking setup to me? Currently the router shows:

Network Clock Configuration

---------------------------

Priority Clock Source Clock State Clock Type

10 Backplane GOOD PLL

Current Primary Clock Source

---------------------------

Priority Clock Source Clock State Clock Type

10 Backplane GOOD PLL

"no network-clock-participate slot 3" is present as well.

All interfaces show some errors/slips periodically:

3/0:

Total Data (last 25 15 minute intervals):

0 Line Code Violations, 6 Path Code Violations,

0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 2 Degraded Mins,

2 Errored Secs, 2 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

3/1:

Total Data (last 25 15 minute intervals):

0 Line Code Violations, 7 Path Code Violations,

0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 2 Degraded Mins,

2 Errored Secs, 2 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

3/2:

Total Data (last 25 15 minute intervals):

1 Line Code Violations, 7 Path Code Violations,

1 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 2 Degraded Mins,

2 Errored Secs, 2 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

6 REPLIES

Re: Cisco 3745 w/NM-HDV2-2T1/E1 Clocking Question

Hi Jordan,

With one set of DSPs on the NM-HDV (all on slot 3/x), you won't be able to get two different clocks.

If you were to not network-clock-select the card, and get PVDM2-X on the motherboard, I believe you would be able to maintain two different clocks.

You may also have a physical problem - but 2 slips over 25 15 minute intervals is a very low number. I'd have to look a little further to find out what the proper clocking is specifically for the HDV since it's a little bit different.

hth,

nick

New Member

Re: Cisco 3745 w/NM-HDV2-2T1/E1 Clocking Question

Thanks Nick. Really the motivation behind this is the line noise/static problems posted in another message here. We found that we're getting a "blotchy" ring tone on the calls with bad static. Our carrier said our gear generates that ring tone (is that correct?) which would then imply that the problem could be on our side (even though we're still confident the issue is only with AT&T cell phones). We've had a ticket open for a week an our TAC engineer isn't returing our responses. Really just trying to get this resolved. I think today we're going to connect the PRI into an Adtran box with FXO ports and make test calls. If we can reproduce then we know 100% the problem is not with our infrastructure. If we can't reproduce the problem then we'll be sure its with our gear and may have to open another ticket to get a different engineer.

Re: Cisco 3745 w/NM-HDV2-2T1/E1 Clocking Question

Hi Jordan,

Generally speaking - it's the responsibility of the far-end gateway to generate ringback. This would be fairly easy to diagnose whether it is you or your provider generating ringback.

On a PRI, if the provider generates ringback it looks like this:

Q931: RX <- PROGRESS pd = 8 callref = 0xFE95

Progress Ind i = 0x8181 - Call not end-to-end ISDN, may have in-band info

If you are generating ringback, it would look this this:

Q931: RX <- PROGRESS pd = 8 callref = 0xFE95

--or--

Q931: RX <- ALERTING pd = 8 callref = 0xFE95

I don't think these slips are the generating of the static and ringback problems, but may be indicative of a larger physical problem.

You could also get a PCM capture of the problem - worth asking your current engineer about (if they don't know what you're referring to, ask for a requeue).

hth,

nick

New Member

Re: Cisco 3745 w/NM-HDV2-2T1/E1 Clocking Question

Great, what debug command enables the above? I'll check it out.

New Member

Re: Cisco 3745 w/NM-HDV2-2T1/E1 Clocking Question

Okay, so here is what I have from a call:

TSA-3745#debug isdn q931

debug isdn q931 is ON.

TSA-3745#

Jan 30 07:55:42: ISDN Se3/1:23 Q931: TX -> SETUP pd = 8 callref = 0x0AA4

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Display i = 'CLIENT NAME'

Calling Party Number i = 0x2081, 'xxxxxxx'

Plan:Unknown, Type:National

Called Party Number i = 0xA0, 'xxxxxxx'

Plan:Unknown, Type:National

Jan 30 07:55:42: ISDN Se3/1:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8AA4

Channel ID i = 0xA98397

Exclusive, Channel 23

Jan 30 07:55:46: ISDN Se3/1:23 Q931: RX <- PROGRESS pd = 8 callref = 0x8AA4

Progress Ind i = 0x8488 - In-band info or appropriate now available

Jan 30 07:55:47: ISDN Se3/1:23 Q931: RX <- PROGRESS pd = 8 callref = 0x8AA4

Progress Ind i = 0x8488 - In-band info or appropriate now available

Jan 30 07:55:47: ISDN Se3/1:23 Q931: RX <- ALERTING pd = 8 callref = 0x8AA4

Jan 30 07:55:58: ISDN Se3/1:23 Q931: TX -> SETUP pd = 8 callref = 0x0AA5

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98396

Exclusive, Channel 22

Display i = 'xxxxxxx'

Calling Party Number i = 0x2081, 'xxxxxxx'

Plan:Unknown, Type:National

Called Party Number i = 0xA0, 'xxxxxxx'

Plan:Unknown, Type:National

Jan 30 07:55:58: ISDN Se3/1:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8AA5

Channel ID i = 0xA98396

Exclusive, Channel 22

Jan 30 07:56:00: ISDN Se3/1:23 Q931: RX <- ALERTING pd = 8 callref = 0x8AA5

Progress Ind i = 0x8488 - In-band info or appropriate now available

Jan 30 07:56:02: ISDN Se3/1:23 Q931: RX <- CONNECT pd = 8 callref = 0x8AA4

Jan 30 07:56:02: ISDN Se3/1:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0AA4

New Member

Re: Cisco 3745 w/NM-HDV2-2T1/E1 Clocking Question

We just confirmed with 100% certainty this is an AT&T Wirless issue. We connected our PRI directly into a 3rd party box with an FXS card in it. Exact same problem. Thanks for all your help.

316
Views
5
Helpful
6
Replies
CreatePlease to create content