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

PDV Buffer Overflow

Status
Not open for further replies.

kodiak12

Vendor
Dec 5, 2007
28
US
I was wondering if anyone has seen the following error message and what it might mean:

Warning: PDV buffer for port# 1 may need to be changed
Too many Overflows: 2.


We have a Succession 1000 Version 2121 Rls 3.0
These messages have been printing out pretty regularly
for the past few weeks. Thanks
 
I've found this below for you.

These messages occur if the PDV buffer size is configured incorrectly.
Try increasing or decreasing the value for port (x)

Found on CSE1K X21 3.00

Use the command PRT PDV <port#> in LD 117 to display both the current size of the PDV buffer and the number of PDV underflows.
Then use the command CHG PDV <port#> <delay> to change the PDV buffer size.
The <delay> parameter can take values from 0.5 ms to 8 ms.
This value should be initially tested at the default setting.
Increase the <delay> parameter value by 0.5 ms increments if an unacceptable level of voice quality is experienced (“pops and clicks”).
Decrease this value if an echo is experienced.
The goal is to operate with the smallest buffer possible.


Also this note was found below.

make the clock track of Media gateway 1 on Succession 3.0

Symptom:
Warning: PDV buffer for port# 3 may need to be changed
Too many Overflows: 1.
Errors pop up throughout day, during low traffic and high traffic period.


Cause:
SSCK 0 shows clocking state to be locking not locked.
ld 60
DTI000
.ssck 0
DSBL

IP DB PORT 1 Locking
IP DB PORT 2 DSBL
IP DB PORT 3 DSBL
IP DB PORT 4 DSBL
CALL SERVER CLK SRC: CC


Fix:

1) Run the trck pll1 command to make the clock track of Media gateway 1.
2) Make call that uses TDM resource in MG1.
This will ensure clocking stays in locked state.

In this particular case, site had clock controller in MG1 and MG3. During system bootup it will would check MG1 first for clock then MG3.

Finally this was spotted (which I think may be your actual problem!)

Getting PDV buffer warning.
Warning: PDV buffer for port# 3 may need to be changed
Too many Overflows: 1.


Altered PDV value on port 3 from 1.0msec to 7.0msec but no change.
Changed IP daughter board, but that had no effect on the issue.

PDV warning message has shifted to port 1.
Warning: PDV buffer for port# 1 may need to be changed
% Too many Overflows: 1.

Replace SSC card on main cabinet





All the best

Firebird Scrambler
Meridian Programmer in the UK

If it's working, then leave it alone!.
 
Thanks for all the info...
We have actually changed the SSC card in the main cabinet last week(after multiple sysloads), but not the Daughterboard. I believe TAC also changed that buffer size. This morning we changed the SSC and Daughterboard in the middle cabinet, but these messages are still persisting.
I'm not sure what our next step should be...
 
But, what did the results of this show?
firebirdscrambler said:
Use the command PRT PDV <port#> in LD 117

[&copy;] GHTROUT.com [&hArr;] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too
 
WOW! You had a bunch of Sysloads on your CS1000M too, huh?? We had to replace our SSC and daughterboard as well after mulitple sysloads. I do still see PDV buffer overflow from time to time and I believe our vendor just increases the set value to 'clear' it.

We have had an issue lately where our MC32 went unpingable as well as our Symposium server and that is not a network issue :) There was talk by our vendor to replace the MAU on the back of our Call Server. Good luck getting it fixed.
 
In response to the command PRT PDV <port#> in LD 117

We saw the following:

No PDV value is configured in database
Default PDV value is 1.0 msec

I did discuss this with TAC and he told me he increased it,
but then why does it show no value?


 
Find out what version of SSC card was used in the main cabinet. I'm sure that it's not the latest one. Once my customer had the latest one put in the main cabinet, the problems slowed right down.

All the best

Firebird Scrambler
Meridian Programmer in the UK

If it's working, then leave it alone!.
 
The one that was replace in the main cab was a JA & it was replaced with an FA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top