![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2296164.1 : Realm QoS Stats do not Sync
QoS stats are not syncing between the SBCs in a HA pair for eg - Active - QoS R-Factor Avg=92.47; max=92.84 Standby - QoS R-Factor Avg=11.20; max=11.20 In this Document
Created from <SR 3-13600284741> Applies to:Acme Packet 4600 - Version S-Cz7.3.0 and laterInformation in this document applies to any platform. SymptomsQoS stats does not sync or match between the SBC's in an HA pair. For example, Active - QoS R-Factor Avg=92.47; max=92.84 Standby - QoS R-Factor Avg=11.20; max=11.20 CauseR-factor is obtained locally from the platform (on both active and standby systems). Thus the r-factor on the active systems will have a certain value, as it will be handling traffic .However since there is no rtp traffic on the standby system it will be 0. QoS stats do not sync between HA pairs. These are typically hardware counters and we don't show hardware stats from another machine. On the active, the r-factor is read at the end of the call and placed in windowed stat (peg counter) which is averaged over time with other calls. If nonzero r-factor is seen on the standby then it most likely is a leftover from when that box was active and it is aging out via the peg counter. So standby QoS r-factor will not be taken or will not sync with active SBC . If it is showing value it means that is from last time when this box was active .
SolutionQoS stats on the standby are undefined and, as such, it is not recommended to monitor them. This value on standby holds no useful data for us , so we should not monitor or be concerned about these values. One way to clear these counters is to reboot standby . This will clear all stray data and make QoS stats as zero on standby.
References<BUG:25077078> - QOS STATS ARE NOT SYNCING BETWEEN THE SBCS IN A HA PAIR.Attachments This solution has no attachment |
||||||||||||||||||
|