PTS Alarms Reference Guide R7.40 C07

Sandvine Policy Traffic Switch Alarms
Reference Guide, Release 7.40
05-00262 C07
2016-11-26
Notices
The most current version of this document is available on the Sandvine Customer Support website at https://support.sandvine.com.
This document and the products described within are subject to copyright. Under copyright laws, neither this document nor the
product may be reproduced, translated, or reduced to any electronic medium or machine readable or other form without prior
written authorization from Sandvine.
Copyright 2016, Sandvine Incorporated ULC. All rights reserved. Sandvine™ is a trademark of Sandvine Incorporated ULC. All
other product names mentioned herein are trademarks of their respective owners.
Sandvine is committed to ensuring the accuracy of our documentation and to continuous improvement. If you encounter errors
or omissions in this user guide, or have comments, questions, or ideas, we welcome your feedback. Please send your comments
to Sandvine via email at https://support.sandvine.com.
Contacting Sandvine
To view the latest Sandvine documentation or to contact Sandvine Customer Support, register for an account at
https://support.sandvine.com.
See http://www.sandvine.com/about_us/contact.asp for a list of Sandvine Sales and Support offices.
2 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

05-00262 C07
Related Documentation
Related documentation is available from Sandvine’s Customer Support web site. All documents are in PDF format and can be
opened and read or printed using Adobe® Acrobat® Reader®. You can obtain a free copy of this software from the Adobe® web
site.
Document Part Number

Getting Started with Sandvine 05-00011
PTS Administration Guide 05-00192
PTS Alarms Reference Guide 05-00262
PTS CLI Reference Guide 05-00263
PTS Hardware Installation Guide 05-00185
PTS Software Installation and Upgrade Guide 05-00245
PTS SandScript Guide 05-00217
PTS Virtual Platform User Guide 05-00269
Sandvine API User Guide 05-00330
Subscriber Mapping User Guide 05-00209
Network Protection User Guide 05-00301
Web Content Intelligence User Guide 05-00325
Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 3

05-00262 C07
4 | Sandvine | TOC
Contents
1 Notifications................................................................................................................................................................14
1.1 Notifications.........................................................................................................................................................15
1.1.1 Sandvine Notifications..................................................................................................................................15
2 Key Performance Indicators.......................................................................................................................................18
2.1 General Resources.............................................................................................................................................19
2.1.1 Memory Resources......................................................................................................................................19
2.1.2 PTS Per Module General Resources...........................................................................................................19
2.2 Inspection Performance Monitoring.....................................................................................................................20
2.2.1 CPU Resource.............................................................................................................................................20
2.2.2 Memory Resource........................................................................................................................................20
2.2.3 Inspection Engine.........................................................................................................................................21
2.2.4 Flow Management........................................................................................................................................21
2.3 Interfaces.............................................................................................................................................................22
2.3.1 Bitrate Capacity............................................................................................................................................22
2.4 Subscriber Monitoring.........................................................................................................................................23
2.4.1 PTS Subscribers Count................................................................................................................................23
3 PTS Alarms................................................................................................................................................................24
3.1 Alarm Models......................................................................................................................................................27
3.2 Alarm Model 1: Faulted Hardware.......................................................................................................................27
3.2.1 Faulted Hardware.........................................................................................................................................28
3.2.2 Impact and Suggested Resolution, Alarm Model 1......................................................................................29
3.3 Alarm Model 2: Faulted Disk...............................................................................................................................30
3.3.1 Degraded Disk Notification...........................................................................................................................30
3.3.2 Faulted Disk Notification...............................................................................................................................31
3.3.3 Faulted Disk Cleared....................................................................................................................................31
3.4 Alarm Model 3: High Temperature.......................................................................................................................32
3.4.1 High Temperature - Notification....................................................................................................................32
3.4.2 High Temperature Cleared...........................................................................................................................33
3.5 Alarm Model 4: Faulted Fan................................................................................................................................35
3.5.1 Faulted Fan: Major Notification....................................................................................................................35
3.5.2 Faulted Fan: Clear Notification.....................................................................................................................36
3.6 Alarm Model 5: Faulted Power Supply................................................................................................................37
3.6.1 Faulted Power Supply - Major Notification...................................................................................................39

05-00262 C07
Sandvine | TOC | 5
3.6.2 Faulted Power Supply - Notification.............................................................................................................40

3.6.3 Faulted Power Supply Cleared.....................................................................................................................44
3.6.5 Suggested Resolutions for All Platforms, Alarm Model 5.............................................................................46
3.6.6 Suggested Resolutions for PTS 24000 and PTS 32000 Series Platforms...................................................47
3.7 Alarm Model 6: High Power Usage.....................................................................................................................47
3.7.1 High Power Usage – Notification..................................................................................................................47
3.7.2 High Power Usage Cleared..........................................................................................................................48
3.7.3 Power supply in non-redundant state - alarms.............................................................................................49
3.8 Alarm Model 7 : High Resource Usage...............................................................................................................49
3.8.1 Major Notification: High Resource Usage ...................................................................................................50
3.8.2 Minor Notification: High Resource Usage ...................................................................................................51
3.8.3 Warning Notification: High Resource Usage................................................................................................51
3.8.4 Clear Notification: High Resource Usage ....................................................................................................52
3.9 Alarm Model 8: Overloaded Processor...............................................................................................................61
3.9.1 Overloaded Processor – Notification............................................................................................................62
3.9.2 Overloaded Processor Cleared....................................................................................................................63
3.10 Alarm Model 9: Unavailable Processing Module...............................................................................................65
3.10.1 Unavailable Processing Module - Notification............................................................................................66
3.10.2 Unavailable Processing Module Cleared...................................................................................................66
3.10.3 Impact and Suggested Resolution, Alarm Model 9....................................................................................67
3.11 Alarm Model 10: Unavailable Service Component............................................................................................68
3.11.1 Unavailable Service Component: Major.....................................................................................................69
3.11.2 Unavailable Service Component: Clear......................................................................................................70
3.11.3 Background Service Processes..................................................................................................................70
3.11.4 Impact and Suggested Resolution: Alarm Model 10..................................................................................71
3.12 Alarm Model 11: Unavailable Bypass Group.....................................................................................................72
3.12.1 Bypassing Traffic – Notification..................................................................................................................73
3.12.2 Bypassing Traffic Cleared..........................................................................................................................74
3.12.3 Unavailable Bypass Group—Critical Alarms..............................................................................................75
3.13 Alarm Model 12: Network Interface Errors........................................................................................................76
3.13.1 Network Interface Errors –Major and Minor Notifications...........................................................................77
3.13.2 Network Interface Errors- Clear..................................................................................................................78
3.13.3 PTS—Impact and Suggested Resolution, Alarm Model 12.......................................................................79
3.13.4 SPB—Impact and Suggested Resolution, Alarm Model 12.......................................................................80
3.14 Alarm Model 13: Discarded Packets.................................................................................................................81

05-00262 C07
6 | Sandvine | TOC
3.14.1 Discarded Packets - Notifications...............................................................................................................82

3.14.2 Discarded Packets- Clear...........................................................................................................................83
3.14.3 PTS—Impact and Suggested Resolution, Alarm Model 13.......................................................................84
3.14.4 SPB—Impact and Suggested Resolution, Alarm Model 13.......................................................................86
3.15 Alarm Model 14: Network Interface Down.........................................................................................................87
3.15.1 Network Interface Down - Notification........................................................................................................87
3.15.2 Network Interface Down - Clear.................................................................................................................88
3.15.3 Network Interface Down - Major Alarms.....................................................................................................88
3.15.4 Impact and Suggested Resolutions for Alarm Model 14............................................................................89
3.16 Alarm Model 15: Unavailable Processing Module.............................................................................................89
3.16.1 Load Balancer Down - Notification.............................................................................................................89
3.16.2 Load Balancer Down - Clear......................................................................................................................90
3.16.3 Load balancer down - minor alarms...........................................................................................................91
3.16.4 Load balancer down - major alarms...........................................................................................................92
3.16.5 Load balancer down - warning alarms.......................................................................................................93
3.17 Alarm Model 17: Degraded Cluster...................................................................................................................93
3.17.1 Degraded Cluster - Warning.......................................................................................................................93
3.17.2 Degraded Cluster -Clear............................................................................................................................94
3.17.3 Impact and Suggested Resolution, Alarm Model 17..................................................................................95
3.18 Alarm Model 18: Disconnected SPB.................................................................................................................95
3.18.1 Disconnected SPB - Major.........................................................................................................................96
3.18.2 Disabled SPB - Minor.................................................................................................................................96
3.18.3 Disconnected SPB -Clear...........................................................................................................................97
3.18.4 Impact and Suggested Resolution: Alarm Model 18..................................................................................98
3.19 Alarm Model 19: Invalid Software License........................................................................................................98
3.19.1 Invalid Software License—Critical..............................................................................................................99
3.19.2 Expiring Software License—Major.............................................................................................................99
3.19.3 Expiring Software License—Minor...........................................................................................................100
3.19.4 Expiring Software License—Warning.......................................................................................................100
3.19.5 Invalid Software License—Clear..............................................................................................................100
3.19.6 Impact and Suggested Resolution, Alarm Model 19................................................................................101
3.20 Alarm Model 20: Overloaded Cluster..............................................................................................................102
3.20.1 Overloaded Cluster - Major......................................................................................................................102
3.20.2 Overloaded Cluster - Minor......................................................................................................................102
3.20.3 Overloaded Cluster - Clear.......................................................................................................................103
3.21 Alarm Model 21: Overloaded Subcluster.........................................................................................................104
3.21.1 Overloaded Subcluster - Major.................................................................................................................104
3.21.2 Overloaded Subcluster - Clear.................................................................................................................105

05-00262 C07
Sandvine | TOC | 7

3.22 Alarm Model 22: Misconfigured Network Awareness......................................................................................106
3.22.1 Misconfigured Network Awareness Alarm................................................................................................106
3.22.2 Misconfigured Network Awareness- Minor...............................................................................................106
3.22.3 Misconfigured Network Awareness - Clear..............................................................................................107
3.23 Alarm Model 23: Runtime SandScript Errors..................................................................................................108
3.23.1 Runtime SandScript Errors.......................................................................................................................109
3.23.2 Runtime SandScript Errors - Major .........................................................................................................110
3.23.3 Runtime Sandscript Errors - Minor...........................................................................................................110
3.23.4 Runtime Sandscript Errors - Clear...........................................................................................................111
3.23.5 Runtime SandScript Errors- Possible Instances......................................................................................112
3.23.6 SandScript Errors.....................................................................................................................................112
3.24 Alarm Model 24: High Network Interface Rx Rate...........................................................................................117
3.24.1 High Network Interface Rx Rate - Major...................................................................................................117
3.24.2 High Network Interface Rx Rate Cleared.................................................................................................118
3.25 Alarm Model 25: High Network Interface Tx Rate...........................................................................................120
3.25.1 High Network Interface Tx Rate- Major....................................................................................................120
3.25.2 High Network Interface Tx Rate Cleared..................................................................................................121
3.26 Alarm Model 26: Unavailable Disk..................................................................................................................122
3.26.1 Unavailable Disk.......................................................................................................................................123
3.26.2 Unavailable Disk Cleared.........................................................................................................................123
3.27 Alarm Model 27: Faulted Hardware.................................................................................................................125
3.27.1 Hardware fault..........................................................................................................................................126
3.27.2 Hardware no longer faulted......................................................................................................................127
3.28 Alarm Model 28: Discarded Subscriber State.................................................................................................127
3.28.1 Subscriber Mappings Cleared - Notification.............................................................................................128
3.28.2 Subscriber Mappings Cleared - Clear......................................................................................................128
3.28.3 Subscriber Mappings on SPB and PTS/SDE Cleared - Minor Alarm.......................................................129
3.29 Alarm Model 29: Disabled Subscriber Lookups..............................................................................................129
3.29.1 Disabled Subscriber Lookups...................................................................................................................130
3.29.2 Disabled Subscriber Lookups Cleared.....................................................................................................130
3.29.3 Subscriber Lookups Disabled—Minor......................................................................................................131

05-00262 C07
8 | Sandvine | TOC

3.30 Alarm Model 30: Delayed Subscriber Mapping...............................................................................................131
3.30.1 Delayed Subscriber Mapping...................................................................................................................131
3.30.2 Delayed Subscriber Mapping Cleared......................................................................................................132
3.31 Alarm Model 32: Disconnected Diameter Peer...............................................................................................134
3.31.1 Disconnected Diameter Peer...................................................................................................................134
3.31.2 Disconnected Diameter Peer Cleared......................................................................................................135
3.32 Alarm Model 33: Failed Power On Self Test....................................................................................................135
3.32.1 Failed Power On Self Test—Major...........................................................................................................136
3.32.2 Failed Power On Self Test—Clear............................................................................................................136
3.33 Alarm Model 34: High Traffic Discrepancy......................................................................................................137
3.33.1 High Traffic Discrepancy—Major..............................................................................................................137
3.33.2 High Traffic Discrepancy—Clear..............................................................................................................138
3.34 Alarm Model 35: Exhausted Resource............................................................................................................139
3.34.1 Exhausted Resource ...............................................................................................................................140
3.34.2 Exhausted Resource Cleared..................................................................................................................141
3.34.3 Exhausted Resource - Minor ...................................................................................................................144
3.35 Alarm Model 36: Faulted Form-factor Pluggable Module................................................................................150
3.35.1 Faulted Form-Factor Pluggable Module—Major......................................................................................150
3.35.2 Faulted Form-Factor Pluggable Module—Clear ......................................................................................152
3.36 Alarm Model 37: Faulted Blade.......................................................................................................................154
3.36.1 Faulted Blade—Major...............................................................................................................................155
3.36.2 Inactive Blade—Minor..............................................................................................................................156
3.36.3 Faulted Blade—Clear...............................................................................................................................156
3.37 Alarm Model 38: Diameter Error......................................................................................................................158
3.37.1 Unknown Diameter Session ID Error—Raise...........................................................................................158
3.37.2 Diameter Error—Clear..............................................................................................................................159
3.38 Alarm Model 39: Diameter Server Outgoing Message Age Exceeded Maximum Threshold..........................160
3.38.1 Diameter Server Outgoing Message Age Exceeded Maximum Threshold—Raise.................................161
3.38.2 Diameter Server Outgoing Message Age Exceeded Maximum Threshold—Clear..................................161

05-00262 C07
Sandvine | TOC | 9
3.39 Alarm Model 40: Diameter Peer Failed Back Over.........................................................................................162

3.39.1 Diameter Peer Failed Back Over - Raise.................................................................................................162
3.39.2 Diameter Peer Failed Back Over—Clear.................................................................................................162
3.40 Alarm Model 41: Diameter Server Connection with Client Peer Lost..............................................................163
3.40.1 Diameter Server Connection with Client Peer Lost—Raise.....................................................................164
3.40.2 Diameter Server Connection with Client Peer Lost—Clear......................................................................164
3.41 Alarm Model 42: Diameter Client Outgoing Message Age Reached Early Threshold....................................165
3.41.1 Diameter Client Outgoing Message Age Reached Early Threshold—Raise...........................................165
3.41.2 Diameter Client Outgoing Message Age Reached Early Threshold—Clear............................................165
3.42 Alarm Model 43: Diameter Client Outgoing Message Age Exceeded Maximum Threshold...........................166
3.42.1 Diameter Client Outgoing Message Age Exceeded Maximum Threshold—Raise..................................167
3.42.2 Diameter Client Outgoing Message Age Exceeded Maximum Threshold—Clear...................................167
3.43 Alarm Model 44: Diameter Server Outgoing Message Age Reached Early Threshold...................................168
3.43.1 Diameter Server Outgoing Message Age Reached Early Threshold—Warning......................................168
3.43.2 Diameter Server Outgoing Message Age Reached Early Threshold - Clear...........................................169
3.44 Alarm Model 50: Unknown Diameter Session-ID............................................................................................169
3.44.1 Unknown Diameter Session ID Error- Minor............................................................................................170
3.45 Alarm Model 51: Diameter Interface Error.......................................................................................................171
3.45.1 Raise and clear notifications....................................................................................................................171
3.45.2 Diameter Interface Error—Major..............................................................................................................172
3.45.3 Impact and Suggested Resolutions, Alarm Model 51..............................................................................173
3.46 Alarm Model 52: Diameter Missing Subscriber Information............................................................................174
3.46.1 Missing subscriber information—Minor....................................................................................................174
3.46.2 Missing subscriber information—Clear.....................................................................................................175
3.47 Alarm Model 53: Unknown Diameter Service..................................................................................................175
3.47.1 Unknown Diameter Service - Major..........................................................................................................176
3.47.2 Unknown Diameter Service - Clear..........................................................................................................177
3.48 Alarm Model 59: Unavailable BGP Master......................................................................................................179
3.48.1 Unavailable BGP Master - Major..............................................................................................................179
3.48.2 Unavailable BGP Master - Clear..............................................................................................................180

05-00262 C07
10 | Sandvine | TOC
3.49 Alarm Model 60: Disconnected BGP Peer......................................................................................................181

3.49.1 Disconnected BGP Peer - Minor..............................................................................................................181
3.49.2 Disconnected BGP Peer - Major..............................................................................................................182
3.49.3 Disconnected BGP Peer - Clear...............................................................................................................182
3.50 Alarm Model 61: Analyzer parse errors—DEPRECATED...............................................................................184
3.50.1 svAnalyzerParseErrorRateNotification—Minor notification......................................................................184
3.50.2 svAnalyzerNoParseErrorRateNotification—Clear notification..................................................................185
3.51 Alarm Model 62: Too Many Concurrent Analyzer Flows—DEPRECATED.....................................................186
3.52 Alarm Model 63: Shunting Traffic Inspection...................................................................................................187
3.52.1 Shunting Traffic Inspection- Major............................................................................................................188
3.52.2 Shunting Traffic Inspection - Clear...........................................................................................................188
3.53 Alarm Model 77: Misconfigured Network Interface..........................................................................................189
3.53.1 Misconfigured Network Interface- Minor...................................................................................................189
3.53.2 Misconfigured Network Interface - Cleared..............................................................................................190
3.54 Alarm Model 79: Failed Reload.......................................................................................................................191
3.54.1 svSysLastReloadFailedNotification: Failed Reload .................................................................................191
3.54.2 svSysLastReloadSucceededNotification: Failed Reload—Clear.............................................................192
3.54.3 Failed Reload—All Alarms.......................................................................................................................193
3.55 Alarm Model 82: Shunting Abusive IPs...........................................................................................................193
3.55.1 svLBHighUsageIPShuntedNotification: Shunting Abusive IPs.................................................................194
3.55.2 svLBHighUsageIPClearNotification: Shunting Abusive IPs Cleared........................................................195
3.56 Alarm Model 87: Failed Health Check.............................................................................................................196
3.56.1 svServerHealthCheckErrorNotification: Failed Health Check..................................................................196
3.56.2 svServerHealthCheckErrorClearNotification: Failed Health Check Cleared............................................197
3.57 Alarm Model 88: Failed Health Check.............................................................................................................198
3.57.1 svInlineHealthCheckErrorNotification: Failed Health Check—Minor........................................................199
3.57.2 svInlineHealthCheckErrorClearNotification: Failed Health Check—Clear...............................................200
3.58 Alarm Model 110: Subscriber Mapping timestamps are in the past................................................................201
3.58.1 Subscriber Mapping timestamps are in the past — Warning ..................................................................201
3.58.2 Subscriber Mapping timestamps are in the past — Clear .......................................................................202

05-00262 C07
Sandvine | TOC | 11
3.58.3 Impact and Suggested Resolution, Alarm Model 110..............................................................................203

3.59 Alarm Model 111: Subscriber Mapping timestamps are in the future..............................................................204
3.59.1 Alarm Model 111: Subscriber Mapping timestamps are in the future.......................................................204
3.59.2 Subscriber Mapping timestamps are in the Future — Warning................................................................204
3.59.3 Subscriber Mapping timestamps are in the Future — Clear....................................................................205
3.59.4 Impact and Suggested Resolution, Alarm Model 111...............................................................................206
3.59.5 Debugging Mapping Failure on the PTS..................................................................................................207
3.60 Alarm Model 114: Subscriber Mapping Overloaded........................................................................................207
3.60.1 ProvisionOverloadMajEvt: Provision Subsystem is Dropping Events......................................................208
3.60.2 ProvisionOverloadClearEvt: Provision Subsystem is Not Overloaded.....................................................209
3.61 Alarm Model 115: Invalid Subscriber Provisioning Parameters.......................................................................214
3.61.1 Invalid Subscriber Provisioning Parameters - Raise................................................................................215
3.61.2 Invalid Subscriber Provisioning Parameters - Clear.................................................................................216
3.62 Alarm Model 116: Discarded Subscriber Provisioning Update........................................................................218
3.62.1 Discarded Subscriber Provisioning Update - Raise.................................................................................218
3.62.2 Discarded Subscriber Provisioning Update - Clear..................................................................................219
3.63 Alarm Model 117: Delayed Mapping...............................................................................................................222
3.63.1 High Subscriber Provisioning Latency......................................................................................................222
3.63.2 Medium Subscriber Provisioning Latency................................................................................................223
3.63.3 Moderate Subscriber Provisioning Latency..............................................................................................224
3.63.4 Optimal Subscriber Provisioning Latency.................................................................................................225
3.64 Alarm Model 125: Subscriber Mappings have Stalled or Halted.....................................................................227
3.64.1 Number of Mapping Requests is Stalling.................................................................................................227
3.64.2 Number of Mapping Requests is Not Stalling - Clear...............................................................................228
3.65 Alarm Model 129: Disconnected Tee Destination............................................................................................229
3.65.1 svTeeDestinationDownNotification: Disconnected Tee Destination—Minor.............................................229
3.65.2 svTeeDestinationUpNotification: Disconnected Tee Destination—Clear..................................................230
3.66 Alarm Model 130: Disconnected Divert Destination........................................................................................231
3.66.1 svDivertDestinationDownNotification: Disconnected Divert Destination—Minor.....................................232
3.66.2 svDivertDestinationUpNotification: Disconnected Divert Destination—Clear..........................................233
3.67 Alarm Model 131: Disconnected Divert Sequence Destination.......................................................................234
3.67.1 svDivertSeqDestinationDownNotification : Disconnected Divert Sequence Destination.........................235

05-00262 C07
12 | Sandvine | TOC
3.67.2 svDivertDestinationSeqUpNotification:Disconnected Divert Sequence Destination—Clear....................235

3.68 Alarm Model 132: Worn Solid State Drive.......................................................................................................237
3.68.1 svEnvStorageSSDLifespanNotification:Worn Solid State Drive...............................................................237
3.68.2 svEnvStorageSSDLifespanClearNotification: Worn Solid State Drive Cleared.......................................238
3.69 Alarm Model 133: Misconfigured Cluster Name .............................................................................................240
3.69.1 svClusterInvalidNameErrorNotification:Misconfigured Cluster Name—Major.........................................240
3.69.2 svClusterInvalidNameClearNotification:Misconfigured Cluster Name—Clear.........................................241
3.70 Alarm Model 136: Misconfigured Load Balancer ............................................................................................242
3.70.1 svLBCConfigErrorNotification: Misconfigured Load Balancer—Major.....................................................243
3.70.2 svLBCConfigClearNotification: Misconfigured Load Balancer Cleared....................................................243
3.71 Alarm Model 146: Incompatible Blade ............................................................................................................245
3.71.1 Incompatible Blade- Critical .....................................................................................................................245
3.72 Alarm Model 154: Invalid Subscriber Operation Name ..................................................................................247
3.72.1 Invalid Subscriber Operation Name - Major.............................................................................................247
3.72.2 Invalid Subscriber Operation Name - Minor.............................................................................................248
3.72.3 Invalid Subscriber Operation Name - Clear..............................................................................................248
3.73 Alarm Model 157: Unavailable Accounting Server .........................................................................................249
3.73.1 svSystemAccountingQueueErrorNotification—Raise..............................................................................250
3.73.2 svSystemAccountingQueueClearNotification—Clear..............................................................................250
3.74 Alarm Model 167: Delayed Distribution Event.................................................................................................252
3.74.1 svDelayedShapingDistributionNotification—Major...................................................................................252
3.74.2 svDelayedShapingDistributionNotification—Minor...................................................................................252
3.74.3 svDelayedShapingDistributionNotification—Clear...................................................................................253
3.75 Alarm Model 168: High Login Failures............................................................................................................253
3.75.1 High Login Failures- Minor ......................................................................................................................254
3.75.2 High Login Failures- Clear .......................................................................................................................254
3.76 Alarm Model 175: License Service Unavailable..............................................................................................255
3.76.1 License Service Unavailable–Major.........................................................................................................256
3.76.2 License Service Unavailable–Clear..........................................................................................................256

05-00262 C07
Sandvine | TOC | 13
3.77 Alarm Model 187: SandScript Alarm...............................................................................................................257

3.77.1 SandScript Alarm Severity.......................................................................................................................258
3.78 Alarm Model 191: Overloaded Diameter Aggregator......................................................................................259
3.78.1 Overloaded Diameter Aggregator–Major.................................................................................................259
3.78.2 Overloaded Diameter Aggregator–Clear..................................................................................................260
4 Miscellaneous Traps.................................................................................................................................................262
4.1 Miscellaneous Traps..........................................................................................................................................263
4.1.1 coldStart Trap.............................................................................................................................................263
4.1.2 warmStart Trap...........................................................................................................................................263
4.1.3 Administratively Enabled Interface.............................................................................................................264
4.1.4 Administratively Disabled Interface............................................................................................................265
4.1.5 SNMP Agent Started..................................................................................................................................265
4.1.6 SNMP Agent Shutting Down......................................................................................................................266

05-00262 C07
Notifications
1
Notifications
• "Notifications" on page 15

05-00262 C07
Notifications
Notifications
1.1 Notifications
Notifications are the communication tool for alarms. They follow the structure derived from:
• RFC 3413 SNMP-NOTIFICATION-MIB
• RFC 3014 NOTIFICATION-LOG-MIB
• RFC 3413 SNMP-TARGET-MIB
• RFC 3877 Alarm MIB
Managers can review alarm models in the Alarm MIB to determine if a notification is of interest for alarm management. If there
are no entries in the alarmModelTable that match a particular notification, that notification is not relevant to the alarm models
defined.
Information in the alarm model, such as the Notification ID or the description, specify which error or warning condition the alarm
indicates. If the ITU-ALARM-MIB is also supported, additional information is provided via the probable cause.
Note:
Unless indicated to the contrary, all varbinds referenced in this document, with names beginning with sv, derive from
SANDVINE-MIB.
1.1.1 Sandvine Notifications

Sandvine notifications are raised and cleared in the Sandvine alarms suite.
All MIB references in notifications are from the SANDVINE-RAIDMON-MIB and SNMPv2-MIB.
1.1.1.1 Bad Logical Drive

This provides a notification on the health of logical drives. Good and bad logical drive notifications share these MIB references:
• sysName
• svSeverity
• svRaidMonDataLogicalDriveDeviceName
• svRaidMonDataLogicalDriveRaidLevel
• svRaidMonDataPhysicalDriveRaidState
A bad logical drive notification is sent when the state of the logical drive is anything other than optimal.
Severity Description
Warning The drive is rebuilding.
Major The drive is degraded.
Critical The drive is either failed or offline.
Profile Description
Trap Name svRaidMonLogicalDriveBadStateNotification

05-00262 C07
Notifications
Notifications
Profile Description
Varbinds svClusterConfigName
1.1.1.2 Good Logical Drive

A notification is sent when the logical drive returns to an optimal state.
Profile Description
Trap Name svRaidMonLogicalDriveGoodStateNotification
1.1.1.3 Faulted Physical Drive

This provides a notification on the physical drive. Faulted/not faulted physical drive notifications share these MIB references:
• sysName
• svSeverity
• svRaidMonDataPhysicalDriveChannelNumber
• svRaidMonDataPhysicalDriveDeviceNumber
The faulted physical drive notification is sent when a physical device enters a state other than online or hot spare.
Severity Description
Warning Drive is ready.
Minor Drive is rebuilding.
Major Drive is failed.
Profile Description
MIB reference SANDVINE-RAIDMON-MIB and SNMPv2-MIB
• sysName
• svSeverity
Trap Name svRaidMonPhysicalDeviceFaultedNotification

05-00262 C07
Notifications
Notifications
1.1.1.4 Physical Drive Not Faulted

This provides a notification on the physical drive. The physical drive not faulted notification is sent when a physical device enters
either the online or hot spare state.
Profile Description
MIB reference SANDVINE- RAIDMON-MIB and SNMPv2-MIB
• sysName
• svSeverity
Trap Name svRaidMonPhysicalDeviceNotFaultedNotification

05-00262 C07
Key Performance Indicators
2
• "General Resources" on page 19
• "Inspection Performance Monitoring" on page 20
• "Interfaces" on page 22
• "Subscriber Monitoring" on page 23

05-00262 C07
General Resources
2.1 General Resources

These are the general resources that are shared by different processes. These resources are listed as part of the host resources
storage table described in HOST-RESOURCES-MIB.
HOST-RESOURCES-MIB::hrStorageTable (.1.3.6.1.2.1.25.2.3).
2.1.1 Memory Resources

These resources are described in the host resource storage table with type hrStorageRam (1.3.6.1.2.1.25.2.1.2).
2.1.2 PTS Per Module General Resources

Different processes share these resources are shared on a per-module basis and described in the host resource storage table
with type hrStorageByModuleTable (1.3.6.1.4.1.11610.435.15747.1.25.2.4).
The table index is based on these values:
• The resource, such as Real Memory (2), Shaping memory (35), CPU Resource (67), PTS Subscriber Count (21), as indicated
in the output of the show system resources CLI command.
• The module ID—0 for controller and 1-10 for modules.
• The instance ID, which is the resource instance on the given module.
Memory Resources
Per module real memory is listed in host resources storage table under hrStorageIndex.2. These parameters provide usage
information:
• SANDVINE-MIB::hrStorageAllocationUnits.2 (1.3.6.1.4.1.11610.435.15747.1.25.2.4.1.6.2)
• SANDVINE-MIB::hrStorageSize.2 (1.3.6.1.4.1.11610.435.15747.1.25.2.4.1.7.2)
• SANDVINE-MIB::hrStorageUsed.2 (1.3.6.1.4.1.11610.435.15747.1.25.2.4.8.2)
• SANDVINE-MIB::hrStorageAllocationFailures.2 (1.3.6.1.4.1.11610.435.15747.1.25.2.4.1.9.2)
Per module shaping memory is listed in host resources storage table under hrStorageIndex.35. These parameters provide usage
information:
• SANDVINE-MIB::hrStorageUsed.35 (1.3.6.1.4.1.11610.435.15747.1.25.2.4.8.35)
Inspection Performance Monitoring

Per module CPU resource is listed in host resources storage table under hrStorageIndex.67. These parameters provide usage
information:

05-00262 C07
• SANDVINE-MIB::hrStorageUsed.67 (1.3.6.1.4.1.11610.435.15747.1.25.2.4.1.8.67)
Per module memory resource is listed in host resources storage table under hrStorageIndex.65. These parameters provide usage
information:
• SANDVINE-MIB::hrStorageUsed.65 (1.3.6.1.4.1.11610.435.15747.1.25.2.4.1.8.65)
2.2 Inspection Performance Monitoring

Inspection performance monitoring provides information on resources.
2.2.1 CPU Resource

These variables are used to monitor the CPU usage the inspection process consumes.
• SANDVINE-MIB::svPtsResourcesStatsCpu (1.3.6.1.4.1.11610.435.8374.1.7723.3.1). The current maximum percentage
utilization of the CPU by the process across all processing modules in the cluster.
• SANDVINE-MIB::svPtsResourcesStatsPeakcpu (1.3.6.1.4.1.11610.435.8374.1.7723.3.2). The peak CPU percentage that
the process has used since last reset.
2.2.1.1 Threshold
When SANDVINE-MIB::svPtsResourcesStatsCpu exceeds an average of 90%, it is best to contact Sandvine Customer Support
or its authorized partner to have them examine the system to determine the stability of the system. Generally, this number is
higher during peak load (often during peak hours).
Instantaneous peaks may occur under network failure conditions (massive number of new subscribers re-attach to the network
for example), so the intent is to trend this value over time.
2.2.2 Memory Resource

These variables are used to monitor how much memory usage the inspection process consumes.
SANDVINE-MIB::svPtsResourcesStatsMemory (1.3.6.1.4.1.11610.435.8374.1.7723.3.3). The percentage of memory that the
process is using.
SANDVINE-MIB::svPtsResourcesStatsPeakmemory (1.3.6.1.4.1.11610.435.8374.1.7723.3.4). The peak memory percentage
that the process has used since last reset.
2.2.2.1 Threshold
When SANDVINE-MIB:: svPtsResourcesStatsMemory exceeds an average of 90%, it is best to contact Sandvine Customer
Support to have them examine the system. Generally, this number is highest during peak load (often during peak hours).

05-00262 C07
2.2.3 Inspection Engine

SANDVINE-MIB::svPtsInspectionInspectTimeout (1.3.6.1.4.1.11610.435.8157.1.3.3.1)
This is a counter that counts the number of flows that have timed out while the PTS still inspects flows. Possible causes for
timeout are extremely short flows—as in unrecognised connection attempts from P2P sessions over either TCP or UDP, TCP
flows with no data after handshakes, and port scan attempts.
SANDVINE-MIB::svPtsInspectionNotInspected (1.3.6.1.4.1.11610.435.8157.1.3.3.2)
This is a counter that shows how many packets that the switch was not able to send for inspection because the inspection engine
was too busy and the packets queue was full.
SANDVINE-MIB::svPtsInspectionNoInspectionEngine (1.3.6.1.4.1.11610.435.8157.1.3.3.3)
This is a counter that shows how many packets that the switch was not able to send to the inspection engine because the daemon
did not exist at that time.
SANDVINE-MIB::svPtsInspectionEarlyDiscard (1.3.6.1.4.1.11610.435.8157.1.3.3.4)
This is a counter that shows the number of packets that were not sent from the switch to the inspection engine due to a limitation
in the free portion of the message queue.
Threshold
When any of the above values exceed 0, it is best to contact Sandvine Customer Support or its authorized partner to have them
examine the SandScript, as well as the other performance metrics, to understand whether additional capacity is needed.
2.2.3.1 Threshold
When any of the above values exceed 0, it is best to contact Sandvine Customer Support or its authorized partner to have them
examine the SandScript, as well as the other performance metrics, to understand whether additional capacity is needed.
2.2.4 Flow Management

SANDVINE-MIB::svPtsFlowsTotal (1.3.6.1.4.1.11610.435.8157.1.3.1.1)
This is the maximum number of flow states that the switch can support. This represents the maximum number of flows that the
policy traffic switch can manage, at any given time. This number is constant.
SANDVINE-MIB::svPtsFlowsAvailable (1.3.6.1.4.1.11610.435.8157.1.3.1.2)
This is a counter that shows how many more flows that the switch can manage before running out of memory (flow record space).
SANDVINE-MIB::svPtsFlowsMaxExceeded (1.3.6.1.4.1.11610.435.8157.1.3.1.4)
This is a counter that shows how many flows that the switch did not process due to running out of flow records space.
SANDVINE-MIB::svPtsFlowsNew (1.3.6.1.4.1.11610.435.8157.1.3.1.3)
This is a counter that shows how many flows the box has seen since it started. You can use this to calculate the rate of new flows
per second.
2.2.4.1 Threshold
When SANDVINE-MIB::svPtsFlowsAvailable divided by SANDVINE-MIB::svPtsFlowsTotal exceeds 70% or if
SANDVINE-MIB::svPtsFlowsMaxExceeded is greater than 0, contact Sandvine Customer Support or its authorized partner to
discuss an upgrade strategy.

05-00262 C07
Interfaces
Instantaneous peaks may occur on the number of flows due to malicious behavior (SYN flood? Flow flood) or handsets reattaching.
It is best to look at trends in these values over time. Polling the SANDVINE-MIB:: svPtsFlowsNew value to calculate a rate of
new flows per second will help understand the performance of the network. As the rate approaches and exceeds 100,000 new
flows per second, it is likely that you will see similar behavior in CPU usage. These two variables are correlated.
2.3 Interfaces
The interfaces table is part of the standard interfaces MIB that used to retrieve stats information such as ifInOctets and
ifSpeed. This table is located in IF-MIB::ifTable (1.3.6.1.2.1.2.2).
2.3.1 Bitrate Capacity

Aggregate throughput of the system is often a good indicator in wireline networks as to the capacity of the system. In mobile,
however, we have found that looking at trends compared to CPU, subscriber count, memory and new flows/second are all
required.
The interfaces table is part of the standard interfaces MIB and can be used to retrieve statistical information such as ifInOctets
and ifSpeed. This table can be found in IF-MIB::ifTable (1.3.6.1.2.1.2.2).
To retrieve the list of interfaces, their description and ifIndex, run:
snmpwalk -c public -v 1 localhost IF-MIB::ifDescr
You can then use the ifIndex to query on the specific interface.
In the interface table, the value ifInOctets can be sampled over a specific amount of time to calculate the receive rate of each
interface. The line rate can be compared to the maximum line rate provided by ifSpeed. The MIBs to use are:
MIB Description
IF-MIB::ifOutOctets (1.3.6.1.2.1.2. The total number of octets transmitted on the interface, including framing characters.
2.1.10)
IF-MIB::ifInOctets (1.3.6.1.2.1.2. The total number of octets received on the interface, including framing characters.
2.1.10)
IF-MIB::ifDescr (1.3.6.1.2.1.2.2.1. An estimate of the interface's current bandwidth in bits per second. For interfaces
2) which do not vary in bandwidth or for those where no accurate estimation can be
made, this object should contain the nominal bandwidth.
IF-MIB::ifHCInOctets (1.3.6.1.2.1. The total number of octets received on the interface, including framing characters.
31.1.1.1.6) This object is a 64-bit version of ifInOctets and should be used for interfaces that
are faster than 1 Gbps.
IF-MIB::ifHCOutOctets (1.3.6.1.2.1. The total number of octets transmitted out of the interface, including framing
31.1.1.1.10) characters. This object is a 64-bit version of ifOutOctets and should be used for
interfaces that are faster than 1 Gbps.
SANDVINE-MIB::svPortTopology To understand the aggregate throughput of the element, the bridge group information
is required.
Conversion from Bridge Group ID into Ifindex is available.

The delta of IfInOctets+ifOutOctets over time for all subscriber (or internet) facing ports will calculate the aggregate bitrate.

05-00262 C07
Subscriber Monitoring
2.3.1.1 Threshold
You should consider planning to upgrade when the aggregate bandwidth reaches 7 Gbps. There are a variety of factors that play
into the solution sizing — 7 Gbps with few subscribers and few flows is likely not near capacity, but lots of subscribers and flows
could be. Contact Sandvine Customer Support or its authorized partner to discuss an upgrade strategy.
2.4 Subscriber Monitoring

This section contains information useful for monitoring the current capacity of the subscriber handling feature.
2.4.1 PTS Subscribers Count

Resource PTS Subscriber Mappings, in the host resources storage table (HOST-RESOURCES-MIB::hrStorageTable
(1.3.6.1.2.1.25.2.3)), are used to calculate the current subscriber handling capacity. This resource is identified in this host resource
table with hrStorageIndex 21. This information presents the current and total sizes of memory used by subscriber handling:
• HOST-RESOURCES-MIB::hrStorageAllocationUnits.21 (1.3.6.1.2.1.25.2.3.1.4.21)
• HOST-RESOURCES-MIB::hrStorageSize.21 (1.3.6.1.2.1.25.2.3.1.5.21)
• HOST-RESOURCES-MIB::hrStorageUsed.21 (1.3.6.1.2.1.25.2.3.1.6.21)
• HOST-RESOURCES-MIB::hrStorageAllocationFailures.21 (1.3.6.1.2.1.25.2.3.1.7.21)
2.4.1.1 Threshold
When HOST-RESOURCES-MIB::hrStorageUsed.21 divided by HOST-RESOURCES-MIB::hrStorageSize.21 exceeds 70% or if
HOST-RESOURCES-MIB::hrStorageAllocationFailures.21is greater than 0, please contact Sandvine Customer Support or its
authorized partner to discuss an upgrade strategy.

05-00262 C07
PTS Alarms
3
PTS Alarms
• "Alarm Models" on page 27
• "Alarm Model 1: Faulted Hardware" on page 27
• "Alarm Model 2: Faulted Disk" on page 30
• "Alarm Model 3: High Temperature" on page 32
• "Alarm Model 4: Faulted Fan" on page 35
• "Alarm Model 5: Faulted Power Supply" on page 37
• "Alarm Model 6: High Power Usage" on page 47
• "Alarm Model 7 : High Resource Usage" on page 49
• "Alarm Model 8: Overloaded Processor" on page 61
• "Alarm Model 9: Unavailable Processing Module" on page 65
• "Alarm Model 10: Unavailable Service Component" on page 68
• "Alarm Model 11: Unavailable Bypass Group" on page 72
• "Alarm Model 12: Network Interface Errors" on page 76
• "Alarm Model 13: Discarded Packets" on page 81
• "Alarm Model 14: Network Interface Down" on page 87
• "Alarm Model 15: Unavailable Processing Module" on page 89

05-00262 C07
PTS Alarms
• "Alarm Model 17: Degraded Cluster" on page 93

• "Alarm Model 18: Disconnected SPB" on page 95
• "Alarm Model 19: Invalid Software License" on page 98
• "Alarm Model 20: Overloaded Cluster" on page 102
• "Alarm Model 21: Overloaded Subcluster" on page 104
• "Alarm Model 22: Misconfigured Network Awareness" on page 106
• "Alarm Model 23: Runtime SandScript Errors" on page 108
• "Alarm Model 24: High Network Interface Rx Rate" on page 117
• "Alarm Model 25: High Network Interface Tx Rate" on page 120
• "Alarm Model 26: Unavailable Disk" on page 122
• "Alarm Model 27: Faulted Hardware" on page 125
• "Alarm Model 28: Discarded Subscriber State" on page 127
• "Alarm Model 29: Disabled Subscriber Lookups" on page 129
• "Alarm Model 30: Delayed Subscriber Mapping" on page 131
• "Alarm Model 32: Disconnected Diameter Peer" on page 134
• "Alarm Model 33: Failed Power On Self Test" on page 135
• "Alarm Model 34: High Traffic Discrepancy" on page 137
• "Alarm Model 35: Exhausted Resource" on page 139
• "Alarm Model 36: Faulted Form-factor Pluggable Module" on page 150
• "Alarm Model 37: Faulted Blade" on page 154
• "Alarm Model 38: Diameter Error" on page 158
• "Alarm Model 39: Diameter Server Outgoing Message Age Exceeded Maximum Threshold" on page 160
• "Alarm Model 40: Diameter Peer Failed Back Over" on page 162
• "Alarm Model 41: Diameter Server Connection with Client Peer Lost" on page 163
• "Alarm Model 42: Diameter Client Outgoing Message Age Reached Early Threshold" on page 165
• "Alarm Model 43: Diameter Client Outgoing Message Age Exceeded Maximum Threshold" on page 166
• "Alarm Model 44: Diameter Server Outgoing Message Age Reached Early Threshold" on page 168
• "Alarm Model 50: Unknown Diameter Session-ID" on page 169
• "Alarm Model 51: Diameter Interface Error" on page 171
• "Alarm Model 52: Diameter Missing Subscriber Information" on page 174
• "Alarm Model 53: Unknown Diameter Service" on page 175
• "Alarm Model 59: Unavailable BGP Master" on page 179
• "Alarm Model 60: Disconnected BGP Peer" on page 181
• "Alarm Model 61: Analyzer parse errors—DEPRECATED" on page 184
• "Alarm Model 62: Too Many Concurrent Analyzer Flows—DEPRECATED" on page 186

05-00262 C07
PTS Alarms
• "Alarm Model 63: Shunting Traffic Inspection" on page 187

• "Alarm Model 77: Misconfigured Network Interface" on page 189
• "Alarm Model 79: Failed Reload" on page 191
• "Alarm Model 82: Shunting Abusive IPs" on page 193
• "Alarm Model 87: Failed Health Check" on page 196
• "Alarm Model 88: Failed Health Check" on page 198
• "Alarm Model 110: Subscriber Mapping timestamps are in the past" on page 201
• "Alarm Model 111: Subscriber Mapping timestamps are in the future" on page 204
• "Alarm Model 114: Subscriber Mapping Overloaded" on page 207
• "Alarm Model 115: Invalid Subscriber Provisioning Parameters" on page 214
• "Alarm Model 116: Discarded Subscriber Provisioning Update" on page 218
• "Alarm Model 117: Delayed Mapping" on page 222
• "Alarm Model 125: Subscriber Mappings have Stalled or Halted" on page 227
• "Alarm Model 129: Disconnected Tee Destination" on page 229
• "Alarm Model 130: Disconnected Divert Destination" on page 231
• "Alarm Model 131: Disconnected Divert Sequence Destination" on page 234
• "Alarm Model 132: Worn Solid State Drive" on page 237
• "Alarm Model 133: Misconfigured Cluster Name " on page 240
• "Alarm Model 136: Misconfigured Load Balancer " on page 242
• "Alarm Model 146: Incompatible Blade " on page 245
• "Alarm Model 154: Invalid Subscriber Operation Name " on page 247
• "Alarm Model 157: Unavailable Accounting Server " on page 249
• "Alarm Model 167: Delayed Distribution Event" on page 252
• "Alarm Model 168: High Login Failures" on page 253
• "Alarm Model 175: License Service Unavailable" on page 255
• "Alarm Model 187: SandScript Alarm" on page 257
• "Alarm Model 191: Overloaded Diameter Aggregator" on page 259

05-00262 C07
PTS Alarms
Alarm Models
3.1 Alarm Models

Sandvine alarm models follow the structural guidelines of RFC 3877 Alarm Management Information Base (MIB). Each model
is a group of alarms with different severities and their respective notifications. The severities include:
Severity Level Severity

1 Clear
2 Indeterminate
3 Critical
4 Major
5 Minor
6 Warning
Note:
The Unique Instance Identifier listed for many alarms, identifies (or specifies) the particular device type involved. Each
independently monitored device type is a separate alarm 'instance'.
3.2 Alarm Model 1: Faulted Hardware

This alarm is raised when a system first detects machine-check errors. These errors are usually uncorrectable or fatal, and can
have a severe impact on system operations, depending on the device on which they occurred.
All device types are monitored independently and failures in multiple devices result in multiple notifications. Uncorrectable
machine-check errors generate major notifications, and fatal errors generate critical notifications. Correctable machine-check
errors do not generate any notifications.
Note:
Alarm model 1 (Faulted Hardware) is not supported on the PTS Linux platform.
Profile Description
Severities Major
Critical
Raise Notification svEnvMachineCheckErrorNotification
Clear Notification svEnvMachineCheckErrorClearNotification
Triggers • MachineCheckFatal
• MachineCheckUncorrectable
• MachineCheckNoError
Unique Instance Identifier svMachineCheckDeviceType

05-00262 C07
PTS Alarms
Alarm Model 1: Faulted Hardware
Related CLI
show system hardware
3.2.1 Faulted Hardware

This notification is sent if the number of machine-check uncorrectable errors exceeds zero, and the number of machine-check
fatal errors is equal to zero.
MIB Reference Description

MIB SANDVINE-MIB
Trap Name svEnvMachineCheckErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.1
Varbind Name Varbind OID

svClusterConfigName 1.3.6.1.4.1.11610.435.5213.1.2.1
SNMPv2-MIB:sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svMachineCheckDeviceDescription 1.3.6.1.4.1.11610.435.11250.1.10.1.6
svMachineCheckDeviceType 1.3.6.1.4.1.11610.435.11250.1.10.1.2
svMachineCheckDeviceCorrectable 1.3.6.1.4.1.11610.435.11250.1.10.1.3
svMachineCheckDeviceUnCorrectable 1.3.6.1.4.1.11610.435.11250.1.10.1.4
svMachineCheckDeviceFatal 1.3.6.1.4.1.11610.435.11250.1.10.1.5
3.2.1.1 Degraded Hardware

This major notification indicates there is an uncorrectable machine-check error. There are non-zero entries in front of the specific
device/devices that raised the alarm. This notification is sent if machine-check uncorrectable errors exceed 0 and machine-check
fatal errors are equal to 0.
Profile Description
Frequency 8 seconds
Severity Major
Condition (SANDVINE-MIB::svMachineCheckDeviceUnCorrectable > 0) && (SANDVINE-MIB::svMachin
eCheckDeviceFatal) == 0
3.2.1.2 Faulted Hardware

This critical notification indicates a fatal machine-check error has occurred. There are non-zero entries in front of the specific
device/devices that raised the alarm. This notification is sent if machine-check fatal errors exceed 0.
Profile Description
Frequency 8 seconds
Severity Critical
Condition SANDVINE-MIB::svMachineCheckDeviceFatal > 0

05-00262 C07
PTS Alarms
3.2.1.3 Faulted Hardware Cleared

This notification is sent if machine-check errors for a particular device have stopped. This notification is sent only if there was a
previous svMachineCheckErrorNotification.

MIB SANDVINE-MIB
Trap Name svEnvMachineCheckErrorClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.2

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svMachineCheckDeviceDescription 1.3.6.1.4.1.11610.435.11250.1.10.1.6
svMachineCheckDeviceType 1.3.6.1.4.1.11610.435.11250.1.10.1.2
svMachineCheckDeviceCorrectable 1.3.6.1.4.1.11610.435.11250.1.10.1.3
svMachineCheckDeviceUnCorrectable 1.3.6.1.4.1.11610.435.11250.1.10.1.4
svMachineCheckDeviceFatal 1.3.6.1.4.1.11610.435.11250.1.10.1.5
3.2.1.4 machine-check clear errors

This alarm is cleared when machine-check uncorrectable errors are equal to 0 and machine-check fatal errors are equal to 0.
Profile Description
Frequency 8 seconds
Severity Cleared
Condition (SANDVINE-MIB::svMachineCheckDeviceUnCorrectable == 0) && (SANDVINE-MIB::svMachin
eCheckDeviceFatal == 0)
3.2.2 Impact and Suggested Resolution, Alarm Model 1

1. If there is an uncorrectable error, data has been corrupted and the hardware cannot fix it, but the failing interface is aware
that an error has occurred. Normal operation may be affected depending on where the error occurred.
It is recommended that the unit be removed, since it is no longer functioning properly.
Note:
A small number of correctable errors are normal and do not necessarily indicate a hardware problem. Performance
is not affected and corrective action is not required.
2. If there is a fatal error, data has been corrupted and the hardware cannot fix it, and the failing interface is not operating
properly. Normal operation will likely be affected depending on where the error occurred.
It is recommended that the unit be removed, since it is no longer functioning properly.

05-00262 C07
PTS Alarms
Alarm Model 2: Faulted Disk
3.3 Alarm Model 2: Faulted Disk

This alarm is raised when one or more severe errors have occurred on a disk. It is normal for a disk to develop growth errors.
Even uncorrectable read and write errors are normal and the RAID controller typically corrects it. Different hardware platforms
have different number of disks installed. Each disk can raise an instance of this alarm. Run the show system storage disk
CLI command to identify the faulted disk.
Note:
Alarm Model 2 (Faulted Disk) is not supported on the PTS Linux platform.
Profile Description
Severities • Major
• Clear
Raise Notification svEnvStorageDiskErrorNotification
Clear Notification svEnvStorageDiskNoErrorNotification
Triggers diskErrorsTrigger
Unique Instance Identifier svStorageDiskTableSlot
3.3.1 Degraded Disk Notification

This notification is sent if the disk has read or write errors.

MIB SANDVINE-MIB
Trap Name svEnvStorageDiskErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.3

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svStorageDiskTableSlot 1.3.6.1.4.1.11610.435.11249.1.12.1.9
svStorageDiskTableDescription 1.3.6.1.4.1.11610.435.11249.1.12.1.6
svStorageDiskTableGrowthDefects 1.3.6.1.4.1.11610.435.11249.1.12.1.14
svStorageDiskTableUncorrectableReadErrors 1.3.6.1.4.1.11610.435.11249.1.12.1.15
svStorageDiskTableUncorrectableWriteErrors 1.3.6.1.4.1.11610.435.11249.1.12.1.16

05-00262 C07
PTS Alarms
Alarm Model 2: Faulted Disk
3.3.2 Faulted Disk Notification

This notification is sent if the sum of the total accumulated read and write disk errors reaches or exceeds 2000.
Profile Description
Frequency 12 hours
Severity Major
Condition ((SANDVINE-MIB::svStorageDiskTableUncorrectableReadErrors + SANDVINE-MIB::svStorageD
iskTableUncorrectableWriteErrors) > 2000)
3.3.3 Faulted Disk Cleared

This notification is sent if a disk has less than 2000 errors.

MIB SANDVINE-MIB
Trap Name svEnvStorageDiskNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.4

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svStorageDiskTableGrowthDefects 1.3.6.1.4.1.11610.435.11249.1.12.1.14
svStorageDiskTableUncorrectableReadErrors 1.3.6.1.4.1.11610.435.11249.1.12.1.15
svStorageDiskTableUncorrectableWriteErrors 1.3.6.1.4.1.11610.435.11249.1.12.1.16

Service continues with decreased confidence in redundancy. The RAID controller corrects isolated read or write errors. Multiple
errors may signal the disk in question will soon become unreliable. Errors can happen if the temperature of the system has
become dangerously high, or if the drive has worn out faster than normal. Replacement of the drive is recommended. See the
PTS Hardware Installation Guide or the SPB Installation Guide for additional information.
Note:
The solid state drives (SSD) in the PTS 22000 and PTS 32000 can only be written a fixed number of times before the disk
begins to fail.

05-00262 C07
PTS Alarms
Alarm Model 3: High Temperature
3.4 Alarm Model 3: High Temperature

This alarm is raised if a component's internal operating temperature is too high. The alarm is triggered when the temperature is
o o
above 55 C. If the temperature increases beyond 80 C, the PPU modules shut themselves down, no further notification is sent
out, and a PTS crash is likely.
Note:
Alarm Model 3 (High Temperature) is not supported on the PTS Linux platform.
Profile Description
Severities Major
Raise Notification svEnvTemperatureHighNotification
Clear Notification svEnvTemperatureOkNotification
Triggers
CPUthermalwarningmoduleXBad
CPUthermalwarningmoduleXGood
Where X is the processing module index.
TemperaturediskNBad
TemperaturediskNGood
Where N is the disk number.

Unique Instance Identifier ENTITY-SENSOR-MIB:entPhySensorValue
3.4.1 High Temperature - Notification

This notification is sent if a CPU module overheats.

MIB SANDVINE-MIB
Trap Name svEnvTemperatureHighNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.5

svSeverity 1.3.6.1.4.1.11610.6799.1.10
ENTITY-MIB:entPhysicalDescr 1.3.6.1.2.1.47.1.1.1.1.2
ENTITY-MIB:entPhysicalIsFRU 1.3.6.1.2.1.47.1.1.1.1.16
ENTITY-MIB:entPhysicalParentRelPos 1.3.6.1.2.1.47.1.1.1.1.6
ENTITY-SENSOR-MIB:entPhySensorValue 1.3.6.1.2.1.99.1.1.1.4
ENTITY-SENSOR-MIB:entPhySensorOperStatus 1.3.6.1.2.1.99.1.1.1.5

05-00262 C07
PTS Alarms
3.4.1.1 Thermal Overheat

o
This notification is sent if the CPU module temperature is greater than 55 C.
Profile Description
Frequency 3600 seconds
Severity Major
Condition ENTITY-SENSOR-MIB::entPhySensorValue > 1
Platform CPU module or disk sensor number

All PTS elements 1<CPU#>02, where CPU# ranges from 00 to 10.
For example, module 5 temperature high would be sensor number 10502.
PTS 24000 12 (Disk 1), 13 (Disk 2)
PTS 22000 9
3.4.1.2 Hard Disk Temperature Error

This notification is sent if the hard disk temperature if any of the hard disks (1 and 2) is greater than 55 degrees.
Profile Description
Frequency 0 seconds (immediate)
Severity Major
Condition ENTITY-SENSOR-MIB::entPhySensorValue > 55
3.4.2 High Temperature Cleared

This notification indicates that the temperature of a component has returned to normal operating range.

MIB SANDVINE-MIB
Trap Name svEnvTemperatureOkNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.6

svSeverity 1.3.6.1.4.1.11610.6799.1.10

05-00262 C07
PTS Alarms

3.4.2.1 Thermal Overheat: Clear

This alarm is cleared when the count for all of the CPU thermal warning counter sensors is 0 over a 1 hour (3600 seconds) period.
Profile Description
Severity Cleared
Condition DELTA(ENTITY-SENSOR-MIB::entPhySensorValue) == 0
3.4.2.2 Hard Disk Temperature Error: Clear

This alarm is cleared when the Hard disk Temperature for any of the hard disks (1 and 2) is less than 55 degrees.
Profile Description
Severity Cleared
Condition ENTITY-SENSOR-MIB::entPhySensorValue < 55
The PTS 24000 conditions are:
ENTITY-SENSOR-MIB::entPhySensorValue < 55

Hard drives: Overheated disks are more likely to have errors or fail prematurely. Different hardware platforms have different levels
of redundancy in their disks, so the impact varies by platform. See Alarm Model 2: Faulted Disk on page 30 and Alarm Model
26: Unavailable Disk on page 122 for additional information.
CPUs/modules: When the ambient temperature gets too high, a CPU reduces its clock frequency to maintain its temperature at
a safe maximum. When the number of warnings increments, it indicates that the CPU temporarily reduced its clock frequency at
some time during the polling interval. This has an impact on performance, but the impact is only significant if the number of
warnings is constantly increasing.
• Check that the ambient temperature in the equipment rack where the unit is mounted is in accordance with the environmental
specifications for that unit. See the PTS Hardware Installation Guide for additional information. Additional cooling or increased
airflow may be required in the rack to maintain the proper ambient temperature.
• Check to see if there are any alarm notifications for the fans. If there are alarms, see Alarm model 4: Fan failure.
• Check all chassis fans and ensure they are operational. See the PTS Hardware Installation Guide and PTS Administration
Guide for additional information.
• If all checks are good, the hard drives or CPUs/modules may be faulty. If performance is being impacted, contact Sandvine
Support.
Note:
For hard drives in a RAID configuration, action may not be required until the drive actually fails. See Alarm Model 26:
Disk down.

05-00262 C07
PTS Alarms
Alarm Model 4: Faulted Fan
3.5 Alarm Model 4: Faulted Fan

This alarm is raised if one or more fans are running, or momentarily (as in the case of the PTS 32000) below the minimum required
speed, or they have stopped completely. This results in a high temperature condition in the system. (The speed is defined in
revolutions per minute or RPM.)
Note:
Alarm Model 4 (Faulted Fan) is not supported on the PTS Linux platform.
Profile Description
Severities Major
Raise Notification svEnvFanFailureNotification
Clear Notification svEnvFanOkNotification
Note:
In PTS 24000 platform, the internal software periodically checks the fan speed (in RPM) and raises the alarm. In PTS
32000 platform, the internal hardware checks the fan speed (in RPM) and raises a flag; consequently, the internal software
periodically checks the flag and raises the alarm.
3.5.1 Faulted Fan: Major Notification

This notification is sent if operational status is faulted for a chassis fan, or if operational status is okay but the sensor value for a
chassis fan's RPM is lower than the minimum value.
Profile Description
Severity Major
Condition This condition is for PTS 22000, and PTS 24000 platforms:
(ENTITY-SENSOR-MIB::entPhySensorOperStatus != [Ok]) || ((ENTITY-SENSOR-MIB::e
ntPhySensorOperStatus = Ok &&
(ENTITY-SENSOR-MIB::entPhySensorValue < minimum RPM ))
This condition is for PTS 32000 platform:
(ENTITY-SENSOR-MIB::entPhySensorOperStatus == [Ok]) &&
(ENTITY-SENSOR-MIB::entPhySensorValue == 2)
When viewed from the back of the unit, fan 5 is on the left and fan 1 is on the right. The chassis fan sensor numbers are:
Platform Sensor Number

PTS 32000 37 to 40 (fans 1 to 4)
PTS 24000 58 to 62 (fans 1 to 5)
PTS 22000 53 to 55 (fans 1 to 3)

05-00262 C07
PTS Alarms
Alarm Model 4: Faulted Fan
3.5.2 Faulted Fan: Clear Notification

This clear notification is sent if a failed fan has been replaced and is working correctly.
When this notification is sent, the operational status for a chassis is restored to okay, and/or the sensor value for a chassis fan
goes above the minimum RPM.
Profile Description
Severity Cleared
Condition This condition is for PTS 22000 and PTS 24000 platforms:
(ENTITY-SENSOR-MIB::entPhySensorValue > minimumRPM )
This condition is for PTS 32000 platform:
(ENTITY-SENSOR-MIB::entPhySensorValue == 1)

MIB SANDVINE-MIB
Trap Name svEnvFanOkNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.8

svSeverity 1.3.6.1.4.1.11610.6799.1.10

Loss of any cooling capacity translates to higher than normal operating temperature for some components. Long term operation
with a faulty fan is not recommended; replace faulty fans as soon as possible.
Fan blade obstructions or a total fan failure are common causes of this alarm. Inspect the unit for obstructions and replace the
fan if none are found.
This table provides the minimum RPM values and details of fans for different PTS hardware models, SPC 1000, and SRP
3000A/B/lite platforms.

05-00262 C07
PTS Alarms
Alarm Model 5: Faulted Power Supply
Platform Description
PTS 32000 Minimum RPM: 4000
This platform has 4 fans installed at the back of the chassis. The fans are 3+1 redundant, meaning
failure of a single fan will not affect the performance of the system.
Note:
When there is a fan fault, the PTS 32000 operates in a non-redundant fan operation mode, where
the system attempts to boost the speed of all of the chassis fans in order to compensate for a
faulted fan. The fan fault on the PTS is latched and does not get cleared until the PTS is rebooted.
Moreover, the fault may be re-triggered upon the next bootup if there is still a fault with the fan.
SPC 1000 Minimum RPM: 4000
This platform has 2 fans installed internal to the chassis. The fans are non-redundant and failure
of either of these fans will result in overheating and performance degradation.
SRP 3000A/B/lite Minimum RPM: 4000
These platforms have 6 fans installed internal to the chassis. The fans are redundant and the
system can tolerate a single-fan failure.
3.5.3.1 Replacing PTS or SRP 3000A/B/C/D/lite Fans

Fans for PTS 32000, 24000, and SRP 3000A/B/C/D/lite are field-replaceable:
1. Identify the faulty fan and its location.
2. Replace the fan. See the related PTS Hardware Installation Guide for specific procedures.
3. Run the show system environmental fans CLI command to verify that the new fan is operational. If the command
output indicates that the new fan is not operational, there may be a problem with the fan slot and you may have to replace
the system.
3.5.3.2 Suggested Resolution for SPC 1000

Fans in this platform are not field replaceable, therefore, you have to replace the system.
3.6 Alarm Model 5: Faulted Power Supply

This alarm is raised to indicate that there is an issue with the power supply.
Warning and minor notifications are generated for temperature-related issues, while major notifications are generated for a failed
power supply fan or loss of input power or output power. An input or output power notification typically indicates that one of the
power cords is not plugged in, or connected, and some of the power supplies are not active. Upon power restoration from a full
power loss, the element reboots without intervention.
Note:
Alarm Model 5 (Faulted Power Supply) is not supported on the PTS Linux platform.

05-00262 C07
PTS Alarms
Profile Description
Severities Warning, Major, Minor, and Clear
Raise Notification svEnvPowerFailureNotification
Clear Notification svEnvPowerOkNotification
Triggers for PTS 22000 • PSXcurrentbelowmaximumcriticBad
• PSXcurrentbelowmaximumcriticGood
• PSXcurrentbelowmaximumwarninBad
• PSXcurrentbelowmaximumwarninGood
• PSXfanstatusBad
• PSXfanstatusGood
• PSXinputpowerstatusBad
• PSXinputpowerstatusGood
• PSXoutputpowerstatusBad
• PSXoutputpowerstatusGood
• PSXpresenceBad
• PSXpresenceGood
• PSXtemperaturewithincriticalBad
• PSXtemperaturewithincriticalGood
• PSXtemperaturewithinwarningtBad
• PSXtemperaturewithinwarningtGood
• PSXvoltageaboveminimumcriticBad
• PSXvoltageaboveminimumcriticGood
• PSXvoltageaboveminimumwarninBad
• PSXvoltageaboveminimumwarninGood
• PSXvoltagebelowmaximumcriticBad
• PSXvoltagebelowmaximumcriticGood
• PSXvoltagebelowmaximumwarninBad
• PSXvoltagebelowmaximumwarninGood
Where X is the power supply number, either 1 or 2.
Triggers for PTS 24000 • PSXfanNBad
• PSXfanNGood
• PSXoutputpowerstatusBad
• PSXoutputpowerstatusGood
• PSXpresenceBad
• PSXpresenceGood
• PSXtemperaturewithincriticalBad
• PSXtemperaturewithincriticalGood

05-00262 C07
PTS Alarms
Profile Description
• PSXtemperaturewithinwarningtBad
• PSXtemperaturewithinwarningtGood
Where X is the power supply number from 1 to 4 and N is the fan number from 1 to 3.
Triggers for SRP 3000 • PSXfanBad
• PSXfanGood
• PSXpresenceBad
• PSXpresenceGood
• PSstatusBad
• PSstatusGood
Where X is a power supply number from 1 to 3.
The sensor numbers are:
Platform Supply Number Power Supply Power Supply Power Supply Power Supply Power Supply
Present Fan Failure Output Power Temperature Temperature
High Warning Critical
PTS 32000 (x 1 285 298 (1 fan) 290 296 297
supplies
maximum) 2 286 319 (1 fan) 309 317 318
PTS 24000 (4 1 14 25 to 27 (Fan 1 19 23 24
supplies to 3)
maximum)
2 15 35 to 37 (Fan 1 29 33 34
to 3)
3 16 45 to 37 (Fan 1 39 43 44
to 3)
4 17 55 to 57 (Fan 1 49 53 54
to 3)
PTS 22000 (2 1 11 24, Fan 1 16 22 23
supplies
maximum) 2 11 45, Fan 1 35 43 44
3.6.1 Faulted Power Supply - Major Notification

This notification indicates that a power supply is not installed or is faulty. It may also indicate a power outage. Because each
platform may have a different number of power supplies, their level of redundancy varies.
Run the show system environmental power CLI command to identify a faulty power supply.
Platform Description and impact

SRP 3000 A/B/lite - AC These platforms have 3 power supplies with a 2+1 redundancy. The unit is still operational with
no performance degradation if 1 power supply fails.
SRP 3000 A/B/lite - DC These platforms have 2 power supplies with a 1+1 redundancy. The unit is still operational with
no performance degradation if 1 power supply fails.

05-00262 C07
PTS Alarms
Platform Description and impact

PTS 24100, 24101 These platforms only require 2 power supplies with a 1+1 redundancy. The unit is still operational
with no performance degradation if 1 power supply fails. These supplies are installed in positions
1 and 3.
PTS 24300, 24500, 24700 These platforms are AC input power models that require 4 power supplies with a 2+2 redundancy.
The unit is still operational with no performance degradation if up to 2 of the power supplies fail.
PTS 24301, 24501, 24701 These are DC input power models that require 4 power supplies with a 2+2 redundancy. Each
inlet supplies 2 DC input power connections (input A powers supplies 1 and 2, input B powers
supplies 3 and 4). The unit is still operational with no performance degradation if up to 2 of the
power supplies fail.
PTS 22000 This platform has 2 power supplies with a 1+1 redundancy. The unit is still operational with no
performance degradation if 1 power supply fails.
PTS 32000 This platform has 2 power supplies maximum, with a 1 + 1 redundancy.
3.6.2 Faulted Power Supply - Notification

This notification is sent for individual power supplies if the entPhySensorValue for that power supply is set to bad (2).

MIB SANDVINE-MIB
Trap Name svEnvPowerFailureNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.9

svSeverity 1.3.6.1.4.1.11610.6799.1.10
3.6.2.1 Faulted Power Supply: Not present

This notification is sent if entPhySensor for a power supply is set to not present (value=2). When set to present (value= 1),
the power supply is present.
Profile Description
Severity Major
Condition ENTITY-SENSOR-MIB::entPhySensorValue == 2 (bad)

05-00262 C07
PTS Alarms
3.6.2.2 Faulted Power Supply: Fan Bad

This notification is sent if entPhySensorValue for a power supply fan is set to bad (value = 2).
Profile Description
Severity svSeverityMinor
3.6.2.3 Faulted Power Supply: Output Power

This notification is sent if entPhySensorValue for output power for a power supply is set to bad (value=2), even though the power
supply is physically present.
Profile Description
Severity Major
Condition ENTITY-SENSOR-MIB::entPhySensorValue == 2
3.6.2.4 Degraded Power Supply: Temperature high warning

This notification is sent if entPhysSensor Value for temperature high warning for a power supply is set to bad (value=2).
Profile Description
Severity Warning
Description This alarm is raised for individual power supplies.
3.6.2.5 Faulted Power Supply: Temperature critical

This notification is sent if entPhysSensor Value for temperature critical for a power supply is set to bad (value=2).
Profile Description
Severity Minor
3.6.2.6 Faulted Power Supply: Input power bad

This notification is sent if entPhysSensorValue for the status of the power supply input power stage is set to bad (value=2).
Profile Description
Severity Major

05-00262 C07
PTS Alarms
3.6.2.7 Faulted Power Supply: Over current warning

This notification is sent if entPhysSensorValue for the status of over current warning is set to bad (value=2). This happens if the
DC output current is close to the limit for activating over current protection.
Profile Description
Severity Major
3.6.2.8 Faulted Power Supply: Over current critical

This notification is sent if entPhysSensorValue for the status of over current critical is set to bad (value=2). This happens if the
DC output has been latched off due to an internal over current protection circuit. To restore power supply module output, input
power must momentarily be disconnected.
Profile Description
Severity Major
3.6.2.9 Faulted Power Supply: Over voltage warning

This notification is sent if entPhysSensorValue for the status of over voltage warning is set to bad (value=2). This happens if the
DC output voltage is close to the limit for activating over voltage protection. To restore power supply module output, input power
must momentarily be disconnected.
Profile Description
Severity Major
3.6.2.10 Faulted Power Supply: Over voltage critical

This notification is sent if entPhysSensorValue for the status of over voltage critical is set to bad (value=2). This happens when
the DC output has been latched off due to an internal over voltage protection circuit.
Profile Description
Severity Major
3.6.2.11 Faulted Power Supply: Under voltage warning

This notification is sent if entPhysSensorValue for the status of under voltage warning is set to bad (value=2). This happens if
the DC output voltage is close to the minimum for activating under voltage protection.

05-00262 C07
PTS Alarms
Profile Description
Severity Major
3.6.2.12 Faulted Power Supply: Under voltage critical

This notification is sent if entPhysSensorValue for the status of under voltage critical is set to bad (value=2). This happens when
the DC output has been latched off due to an internal under voltage protection circuit.
Profile Description
Severity Major
3.6.2.13 Faulted Power Supply Cleared: Input Power clear

This notification is cleared if entPhysSensorValue for the status of the power supply input power stage is set to good (value=1).
Profile Description
Severity Cleared
Condition ENTITY-SENSOR-MIB::entPhySensorValue == 1 (good)
3.6.2.14 Faulted Power Supply Cleared: Over current warning clear

This notification is cleared if entPhysSensorValue for the status of over current warning is set to good (value=1).
Profile Description
Severity Cleared
3.6.2.15 Faulted Power Supply Cleared: Over current critical clear

This notification is cleared if entPhysSensorValue for the status of over current critical is set to good (value=1).
Profile Description
Severity Cleared
3.6.2.16 Faulted Power Supply Cleared: Over voltage warning clear

This notification is sent if entPhysSensorValue for the status of over voltage warning is set to good (value=1).

05-00262 C07
PTS Alarms
Profile Description
Severity Cleared
3.6.2.17 Faulted Power Supply Cleared: Over voltage critical clear

This notification is sent if entPhysSensorValue for the status of over voltage critical is set to good (value=1).
Profile Description
Severity Cleared
3.6.2.18 Faulted Power Supply Cleared: Under voltage warning clear

This notification is sent if entPhysSensorValue for the status of under voltage warning is set to good (value=1).
Profile Description
Severity Cleared
3.6.2.19 Faulted Power Supply Cleared: Under voltage critical clear

This notification is sent if entPhysSensorValue for the status of under voltage critical is set to good (value=1).
Profile Description
Severity Cleared
3.6.3 Faulted Power Supply Cleared

This notification is sent when a power supply or one of its components has returned to normal operation.

MIB SANDVINE-MIB
Trap Name svEnvPowerOkNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.10

05-00262 C07
PTS Alarms

svSeverity 1.3.6.1.4.1.11610.6799.1.10
ENTITY-SENSOR-MIB:entPhySensorValue .1.3.6.1.2.1.99.1.1.1.4
3.6.3.1 Faulted Power Supply Cleared: Present

This alarm is cleared if entPhySensor Value for a power supply is set to good (value=1).
Profile Description
Severity Cleared
3.6.3.2 Faulted Power Supply Cleared: Good

This notification is sent if entPhysSensorValue for a power supply fan is set to good (value=1).
Profile Description
Severity Cleared
3.6.3.3 Faulted Power Supply Cleared: Output Power

This notification is sent if entPhysSensorValue for out power for a power supply is set to good (value=1), or the power supply is
physically not present (value=2).
Profile Description
Severity Cleared
Condition ENTITY-SENSOR-MIB::entPhySensorValue == 1 (good), ENTITY-SENSOR-MIB::entPh
ySensorValue == 2 (not present)
3.6.3.4 Faulted Power Supply Cleared: Temperature high warning clear

This notification is sent if entPhysSensor Value for temperature high warning for a power supply is set to good (value=1), or the
power supply is physically not present (value=2). There is no performance impact and the unit is still fully functional.

05-00262 C07
PTS Alarms
Profile Description
Severity Cleared
Condition ((ENTITY-SENSOR-MIB::entPhySensorValue == 1 (good)) || (ENTITY-SENSOR-MIB::ent
PhySensorValue == 2 (not present)))
3.6.3.5 Faulted Power Supply Cleared: Temperature critical clear

This notification is sent if the entPhysSensor value for temperature critical for a power supply is set to good (value=1).
Profile Description
Severity Cleared

The impacts include the unit over heating, or power outage to the unit.
3.6.4.1 Suggested Resolution for Alarm Model 5

1. Make sure all power supply fans are running and no there are no fan alarms. See Alarm Model 4: Faulted Fan on page 35
for additional information.
2. Make sure the ambient temperature of the equipment rack is in accordance with the environmental specification of that unit.
3. Verify that the air intake/exhaust ports are not blocked.
3.6.4.2 Suggested Resolution - High temperature on a power supply

This alarm indicates a high temperature on a power supply, this means the power supply has failed and the system is using
redundant power supplies:
• Make sure that all power supply fans are operational.
• Make sure the ambient temperature of the equipment rack is in accordance with the environmental specification of that unit.
• Verify that the air intake/exhaust ports are not blocked.
• Make sure that all chassis fans are operational.
3.6.5 Suggested Resolutions for All Platforms, Alarm Model 5

1. Make sure all the power supplies are installed and fully inserted in their slots.
2. Make sure input cables are properly connected and input power is present.
3. Verify that input power feed voltage is in the acceptable range for the type of facility power used.

05-00262 C07
PTS Alarms
Alarm Model 6: High Power Usage
3.6.6 Suggested Resolutions for PTS 24000 and PTS 32000 Series
Platforms
If two supplies fail at the same time (supplies 1&2 or supplies 3&4), it is likely that something happened to the corresponding
power input wiring:
1. Check the power input wiring.
2. If the problem is not resolved, replace the power supply.
3. Install new supplies and see if the problem still exists.

Chassis replacement is required if the problem is not resolved.
3.7 Alarm Model 6: High Power Usage

This alarm is raised to indicate that power supplies are at 90% of redundant capacity and the element no longer has power supply
redundancy.
Note:
Alarm Model 6 (High Power Usage) is not supported on the PTS Linux platform.
Profile Description
Severities Minor and Cleared
Raise Notification svEnvPowerLoadHighNotification
Clear Notification svEnvPowerLoadNormalNotification
Triggers • TotalCurrentMinor
• TotalCurrentClear
3.7.1 High Power Usage – Notification

This notification is sent if power supply load is high.

MIB SANDVINE-MIB
Trap Name svEnvPowerLoadHighNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.11
Where n is the row number for a given power supply:

svSeverity 1.3.6.1.4.1.11610.6799.1.10

05-00262 C07
PTS Alarms
Alarm Model 6: High Power Usage

ENTITY-SENSOR-MIB::entPhySensorType(for power supply 1.3.6.1.2.1.99.1.1.1.4.<n>
1)
2)
3)
4)
3.7.1.1 Current Draw 130A (14k —9700) limit: Raise

This notification is sent for a power supply (number 1 to 4) if entPhySensorValue total for all power supplies exceeds 130000.
Profile Description
Severity Minor
Condition (ENTITY-SENSOR-MIB::entPhySensorType(for power supply 1)) + (ENTITY-SENSOR-MIB::ent
PhySensorType(for power supply 2)) + (ENTITY-SENSOR-MIB::entPhySensorType(for power
supply 3)) + (ENTITY-SENSOR-MIB::entPhySensorType(for power supply 4)) > 130000
3.7.2 High Power Usage Cleared

This notification is sent if the total load on the power supplies return to normal range and the power supplies are fully redundant.

MIB SANDVINE-MIB
Trap Name svEnvTemperatureHighNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.12

SNMPv2-MIB:sysName .1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
ENTITY-SENSOR-MIB::entPhySensorType(for power supply 1.3.6.1.2.1.99.1.1.1.4.<index>
1)
2)
3)
4)

05-00262 C07
PTS Alarms
Alarm Model 7 : High Resource Usage
3.7.2.1 Current Draw: Clear

This notification is cleared for a power supply (number 1 to 4) if entPhySensorValue total for all power supplies is less than/equal
to 120000.
Profile Description
Severity Cleared
Condition (ENTITY-SENSOR-MIB::entPhySensorType(for power supply 1)) + (ENTITY-SENSOR-MIB::ent
PhySensorType(for power supply 2)) + (ENTITY-SENSOR-MIB::entPhySensorType(for power
supply 3)) + (ENTITY-SENSOR-MIB::entPhySensorType(for power supply 4)) <= 120000
3.7.3 Power supply in non-redundant state - alarms

A minor alarm indicates that the sum of all power supply currents exceeds 97% of power supply capacity.

If a minor alarm occurs, power supplies are supplying so much power that they are no longer in redundant mode. There is no
performance degradation, however the supplies are now 3+1 redundant, and both power inputs are required.
1. Run the show system environmental power CLI command to view the current draw.
2. If you can identify a power supply that is supplying significantly more current than the others, replace it:
a. Run the show system environmental power CLI command.
b. Compare the current supply from the power supplies.
c. If one of the power supplies is supplying significantly more current (>20%) than the others, replace it. Otherwise, it is
likely there is an internal hardware problem in the system and you should replace it.
3.8 Alarm Model 7 : High Resource Usage

This alarm is raised when there is an over usage of system resources due to issues such as system over-provisioning or software
that is not properly tuned. It can also indicate that the resource has allocation failures.
This alarm indicates that a system resource in the host resources table (hrStorageTable) is at 90% capacity or exceeds 90%
capacity. If a resource is at 90% capacity, a warning notification is sent. If a resource has allocation failures, a minor notification
is sent.
Profile Description
• Minor

05-00262 C07
PTS Alarms
Profile Description
• Warning
• Clear
Raise Notification svSystemResourceLowNotification

Clear Notification svSystemResourceOkNotification
Triggers hrStorageResourceTrigger<n>, where <n> is the resource ID.
Unique Instance Identifier • HOST-RESOURCES-MIB:hrStorageIndex
• SANDVINE-RESOURCES-MIB.txt
Resource Capacity Thresholds and Severities

Each resource is monitored for capacity and allocation failures. For example, if capacity is greater than 90%, an alarm is raised.
If resource allocation experiences failures then Alarm Model 35 is raised.
There is a trigger for each resource in the host resources table. The trigger is represented as hrStorageResourceTrigger<n>,
where <n> is the resource ID. For example, hrStorageResourceTrigger2 is real memory.
The show system resources CLI command lists resources to which this alarm applies. Listed resources depend on the
platform (PTS,SDE/SPB), release or configuration.
This table lists these resources, capacity thresholds, and allocation failure severities:
ID Description Capacity Thresholds Capacity Severity Allocation Failure Severity

(Rising and Falling)
2 Real memory 90,80 Warning Minor
3 Swap space 70-80, 80-90 Warning, Minor Major
4 Mbuf clusters 90,80 Warning Minor
6 Filesystem / (80,70)(95,80) Minor, Major Major
7 Filesystem /d2 (80,70)(95,80) Minor, Major Major
8 File descriptors 90,80 Warning Minor
18 Kernel address space 90,80 Warning Minor
19 Kernel memory 90,80 Warning Minor
80 PTS Map entries (90,80) (10,0) Warning Minor
3.8.1 Major Notification: High Resource Usage

A major notification is sent when a system resource (64 bit counter in the hrStorageTable) is at capacity or exceeds the
capacity mentioned in Alarm Model 7 : High Resource Usage on page 49 .

MIB SANDVINE-MIB
Trap Name svSystemResourceLowNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.1

05-00262 C07
PTS Alarms

svSeverity 1.3.6.1.4.1.11610.6799.1.10
HOST-RESOURCES-MIB:hrStorageIndex 1.3.6.1.2.1.25.2.3.1.1
HOST-RESOURCES-MIB:hrStorageDescr 1.3.6.1.2.1.25.2.3.1.3
HOST-RESOURCES-MIB:hrStorageSize 1.3.6.1.2.1.25.2.3.1.5
HOST-RESOURCES-MIB:hrStorageUsed 1.3.6.1.2.1.25.2.3.1.6
HOST-RESOURCES-MIB:hrStorageAllocationFailures 1.3.6.1.2.1.25.2.3.1.7
3.8.2 Minor Notification: High Resource Usage

A major notification is sent when a system resource (64 bit counter in the hrStorageTable) is at capacity or exceeds the
capacity mentioned in Alarm Model 7 : High Resource Usage on page 49 .

MIB SANDVINE-MIB
Trap Name svSystemResourceLowNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.1

svSeverity 1.3.6.1.4.1.11610.6799.1.10
3.8.3 Warning Notification: High Resource Usage

This notification is sent when a resource (64 bit counter) is equal to 90% capacity (value=90) in an interval of 8 seconds.
Profile Description
Frequency 8 seconds
Severity Warning
Condition ((HOST-RESOURCES-MIB::hrStorageUsed * 100)/ HOST-RESOURCES-MIB::hrStorageSize) >
90

05-00262 C07
PTS Alarms
3.8.4 Clear Notification: High Resource Usage

This alarm is cleared if a resource (64 bit counter) falls below 80% capacity in an interval of 8 seconds.
The clear notification is sent if a system resource that was over 90% capacity returns to below 80% capacity.
Profile Description
Frequency 8 seconds
Severity Cleared
Condition ((HOST-RESOURCES-MIB::hrStorageUsed * 100)/ HOST-RESOURCES-MIB::hrStorageSize) <
80

MIB • SANDVINE-MIB
• SANDVINE-RESOURCES-MIB
Trap Name svSystemResourceOkNotification
Trap OID • 1.3.6.1.4.1.11610.6799.3.4.0.2
• 1.3.6.1.4.1.11610.6799.3.25.1.2

svSeverity 1.3.6.1.4.1.11610.6799.1.10
HOSTRESOURCESMIB:hrStorageIndex 1.3.6.1.2.1.25.2.3.1.1

This alarm is tied to the aggregate sum of all modules in the system. As a result, the alarm might not occur even though a single
module's resource has exceeded 90% of its capacity. The alarm is cleared when resource usage settles below 80% of its capacity.
3.8.5.1 Impact of High Resource Usage Alarm

The impact of this alarm varies depending on the resource affected. This table provides the resource ID, description, and impact
details.
Note:
Resource IDs identified with an asterisk (*) apply to both the PTS and Virtual PTS platforms. Those without an asterisk
apply to the PTS platform only. In the PTS Linux platform, each resource in this table has the ID incremented by 1000.
For example:
ID has the value 1002 for Real memory;
ID has the value 1004 for Mbuf clusters, and so on.

05-00262 C07
PTS Alarms
ID Description Impact
2 Real memory Possible application failure/exit if usage continues to increase.
4 Mbuf clusters Packets may begin to drop if usage continues to increase.
5* Packet memory Packets may start to drop if usage continues to increase.
6 Filesystem / Loss of log files, and core files if usage continues to increase.
7 Filesystem /d2 Loss of log files, and core files if usage continues to increase.
8 File descriptors Applications may fail if usage continues to increase.
9 Filesystem /d3 Report data is lost if usage continues to increase.
18 Kernel address space Possible system failure if usage continues to increase.
19 Kernel memory Possible system failure if usage continues to increase.
20 * PTS Flows Packet inspection may cease if usage continues to increase.
21 * PTS Subscribers Packet inspection may cease if usage continues to increase.
22 DNS Users Packet inspection may cease if usage continues to increase.
23 PTS Subscriber stats counters User bandwidth detection may miss some abusers.
24 NPU MacVlan table space Inspection of packets with new MAC or VLAN ID may cease if usage continues to
increase.
31 WDTM Detection Session Packet inspection may cease if usage continues to increase.
32 WDTM Detection Session (on Packet inspection may cease if usage continues to increase.
CND)
33 WDTM Attack Object Packet inspection may cease if usage continues to increase.
34 * Attribute strings String attributes are not set (have NULL values) and SandScript may not function
as expected.
35 * PTS shaping memory Packets may drop out if usage continues to increase.
36 * PTS level distribution instances Shaping and Session Management may not function correctly; the PTS could
possibly shape too much and/or limit too many flows (resulting in dropped packets).
37 * PTS tee header entries Teeing may not function correctly (destinations may not see all expected packets).
38 * PTS or SDE measurement Measured statistics may be inaccurate or not collected altogether for certain
instances instances.
40 * Ipusermap webservices queue If usage continues to increase, Radius and/or DHCP packets (sub-ip mapping)
may drop and cannot reach the SPB.
41 * Ipusermap radius queue If usage continues to increase, Radius and/or DHCP packets (sub-ip mapping)
may drop and cannot reach the SPB.
42 * PTS demographic stats hosts Host reports in NDS is inaccurate.
43 * PTS or SDE classifier Classifiers are not assigned to the correct value and measurements/limiters/sh
instances apers unique by classifiers, will not have all the correct instances.
44 * PTS or SDE policy table row SandScript logic that uses SandScript tables will not function as expected.
memory
45 * TCP Reassembly Buffering Analysis of TCP flows for the purposes of populating Flow.Stream fields in
SandScript will cease, leaving those fields unpopulated.
46 * Stream Analysis Buffering Analysis of any analyzed flows for the purposes of populating Flow.Stream fields
in SandScript will cease, leaving those fields unpopulated.
47 NPU Diverted Source table Packets between a new pair of MACs are not inspected.
space

05-00262 C07
PTS Alarms
48 NPU Layer 2 Rewrite table Packets between a new pair of MACs are not inspected.
space
49 NPU Layer 3 Hairpin table New layer 3 hairpin destinations are not configured.
space
50 * Total Memory Possible application failure/exit if usage continues to increase.
51 * PTS or SDE Map instances All maps defined in the SandScript are limited to 400MB of memory. This is the
default configuration and it is recommended not to override this limit. There is a
possibility of application failure/exit if overridden.
52 * PTS Streaming Flows The TCP stream analyzer will not analyze some flows. Stream SandScript fields
for those flows will be null.
53 * PTS Primed Flow Classification New primes are rejected. Misclassification of new flows may result in SandScript
instances not applied.
54 * PTS Largest Flow New primes for certain source or destination IPs are rejected. Misclassification of
Classification Container new flows may result result in SandScript not applied.
55 * PTS IP Fragmentation Records Exhausting fragmentation records could impact recognition of large fragmented
UDP packets.
56 * External MAC address table There is no impact from this resource.
58 WDTM detection user The WDTM policy does not affect additional users.
59 * Statistic Records Statistics records sent to the SPB are discarded and the statistics are lost.
61 Reassembly Buffers (Small) All PTS releases starting with PTS 6.00.
62 Reassembly Buffers (Medium) All PTS releases starting with PTS 6.00.
63 Reassembly Buffers (Large) All PTS releases starting with PTS 6.00.
64 * RTMP Streaming Flows RTMP stream analyzer will not analyze some flows. Stream PAL fields for those
flows are null.
68 * HTTP Streaming Flows HTTP stream analyzer will not analyze some flows. Stream PAL fields for those
flows are null.
70 * PTS Policy Controller Server New unique by values passed to the policy controller will no longer create new
memory control systems. This will result in a shaper rate of the configured maximum for
this unique by instance.
71 * PTS Policy Controller Client New unique by values passed to the policy controller on the current PTSD no longer
memory creates new control systems. If there is traffic for these unique by instances on
other PTSDs then there is little or no impact. If on the other hand, all traffic for the
given unique by instance is seen at this module, then this results in a shaper rate
of the configured maximum for this unique by instance.
72 * BGPD subnets Some of the BGP subnet information may be dropped. Data used for traffic reports
may not be completely accurate.
73 * BGPD RIB memory Some of the BGP subnet information may be dropped. Data used for traffic reports
may not be completely accurate.
75 PTS policy table row memory Indicates that the SandScript defined policy tables require more memory than the
system currently lets them use. As a result, a row was not created in the table.
When a row is not created in a table, any values that should be stored in it, and
accessed in subsequent policy runs, are not available. Any business logic deployed
in SandScript that depends on the presence of a table row will fail, and the
SandScript is not applied as expected.
78 Dynamic shunted subnets Indicates that the database used to store subnets shunted for the IP Overload
Management features is nearly full. If the PTS cannot insert entries into this

05-00262 C07
PTS Alarms
database, additional abusive1 IP addresses that the PTS detects are not shunted.
This has the potential to impact inspection and the subscriber experience.
79 Subscriber NAT mappings Indicates that the system has reached the maximum supported number of subscriber
network-address-translation (NAT) mappings. As a result of this condition,
subscriber-aware policies cannot associate traffic to the transmitting subscriber
and, consequently, will under-count usage and otherwise treat traffic as though its
subscriber is unknown.
80 PTS map entries Reports the number of policy map entries that SandScript has loaded. When the
alarm is raised, it indicates that an attempt to reload a policy map has failed because
the number of map entries that the policy engine needs to load the map is larger
than the number of entries that the policy engine can use without affecting other
portions of the system. As a result, SandScript continues to run with the contents
of the map that were loaded prior to the attempt to reload the map.
81 Central LB IPv4 table rows Indicates that the table used to load-balance IPv4 addresses is nearly full. If the
PTS cannot find an entry in this table for a subscriber IP, it shunts packets with
that subscriber IP. Shunted packets are not inspected, meaning that the PTS will
not apply policy to them, nor will it count them beyond shunt statistics.
82 Subscriber Cache Tracks the number of subscribers allocated in the Subscriber Management
subsystem on the SDE.
84* PTS packet usage by all policy Tracks utilization of memory buffers available for queuing and delaying packets.
actions This is a subset of the total packet buffers in the system, but only a subset of these
are queued or delayed.
Note:
• Resource 39, 84 and 85 refer to the same packet pool.
• Resource 39 and 85 are displayed in the show system resource but do
not raise any alarm.
• Only Resource 84 raises an alarm for events.hrStorage.conf.
89 PTS detector memory Tracks the amount of memory that the Network Protection Detector Subsystem
uses on the PTS.
90 Mitigation Rules Tracks the number of mitigation rules issued to the Mitigation Rule Engine.
91 Central LB IPv6 table rows Indicates that the table used to load-balance IPv6 addresses with default prefix is
nearly full. If the PTS cannot find an entry in this table for a subscriber IP, it shunts
packets with that subscriber IP. Shunted packets are not inspected, meaning that
the PTS will not apply policy to them, nor will it count them beyond shunt statistics.
This alarm appears with these severities:
• Warning—The PTS raises a warning alarm when the number of entries in the
Central LB table exceeds 90% of the tables capacity.
• Minor—The PTS raises a minor alarm when the number of entries in the Central
LB IPv6 table exceeds 95% of the tables capacity.
The PTS clears the warning and minor alarms once the number Central LB IPv6
table rows drops below 80% of the tables capacity.
92 Central LB IPv6 LPM table Indicates that the tree used to load-balance IPv6 addresses with non-default prefix
rows is nearly full. If the PTS cannot find an entry in this table for a subscriber IP, it
shunts packets with that subscriber IP. Shunted packets are not inspected, meaning
that the PTS will not apply policy to them, nor will it count them beyond shunt
statistics.
This alarm appears with these severities:
1 The PTS module (PTSM) samples packets and generates per-user stats. Users that cross the threshold for new flow rate, packet rate, or bit rate, are reported
as 'abusive'. When a drop occurs, the load balancer shunts a number of abusive IPs on the associated module

05-00262 C07
PTS Alarms
• Warning— The PTS raises a warning alarm when the number of entries in the
Central LB table exceeds 90% of the tables capacity.
• Minor— The PTS raises a minor alarm when the number of entries in the Central
LB IPv6 table exceeds 95% of the tables capacity.
The PTS clears the warning and minor alarms once the number Central LB IPv6
table rows drops below 80% of the tables capacity.
93 PTS flow extension records TCP divert ceases to work for new flows. Few SandScript fields that expose flow
statistics are not set and have NULL values.
3.8.5.2 Suggested Resolutions for High Resource Usage Alarm

Suggested resolutions depend on which system resource has encountered the problem.
On multi-module hardware, it would be good to determine if any one module is more at fault than the others when the PTS is
deployed inline.
Between... Then...
Layer 2 Switches See the PTS Administration Guide to ensure that the configuration is correct for Layer 2.
Layer 3 Routers Review the external device configuration to reduce the number of Ethernet MAC addresses
passing through the PTS cluster.
Run the show system resources CLI command to review the breakdown of the resource. If the source of the problem cannot
be determined, run the techsupport CLI command to capture diagnostic information for the system. Contact Sandvine Customer
Support or its authorized partner for further assistance.
This table provides the suggested resolution for the different resources:
ID Description Suggested Resolutions

2 Real memory Check the configuration for an over-provisioning condition.
4 Mbuf clusters Check the configuration for an over-provisioning condition.
5 Packet memory Check the configuration for an over-provisioning condition.
6 Filesystem / Run the du command to search the file system for large files and remove the
unnecessary files.
7 Filesystem /d2 Run the du command to search the file system for large files and remove tee to
file captures, log files, or other unnecessary files.
8 File descriptors Run the fstat command to determine if any of the processes have an unusually
large number of files open.
18 Kernel address space Check the configuration for an over-provisioning condition.
19 Kernel memory Check the configuration for an over-provisioning condition.
20 PTS Flows Check the configuration for an over-provisioning condition.
21 PTS Subscribers Check the configuration for an over-provisioning condition.
22 DNS Users Check the configuration for an over-provisioning condition.
23 PTS Subscriber stats counters Check the configuration for an over-provisioning condition.

05-00262 C07
PTS Alarms

24 NPU MacVlan table space Check the deployment model and then:
• Reduce the number of VLAN IDs used in the network, or
• Only use the 2 port bridge-group deployment mode
31 WDTM Detection Session Check the configuration for an over-provisioning condition.

32 WDTM Detection Session (on CND) Check the configuration for an over-provisioning condition.
33 WDTM Attack Object Check the configuration for an over-provisioning condition.
34 Attribute strings Consider simplifying your SandScript to use fewer string attributes.
35 PTS shaping memory Check the configuration for an over-provisioning condition.
36 PTS level distribution instances Do not use level distribution when shaping, or limiting unique by something that
has a large number of instances cluster wide, such as subscribers. Consider
load balancing the shaping or limiting unique by activity. You can also disable
level distribution.
37 PTS tee header entries Verify if there is an overlap of three or more tee actions and resolve in SandScript.
38 PTS or SDE measurement instances Consider the size of the sets used in SandScript's measurement unique-by
specifications. If the sets are large (for example, measurement unique by
subscriber), consider removing some of these measurements from SandScript
and/or using measurements with fewer unique instances.
40 Ipusermap webservices queue Verify the tee/ipusermap policy.
41 Ipusermap RADIUS queue Verify the tee/ipusermap policy.
42 PTS demographic stats hosts Verify that network classes are properly configured. The problem is the result
of including too many IP addresses in an 'internal' network class. Ensure that
counting of external hosts is disabled.
43 PTS or SDE classifier instances Consider the number of different values that you can assign to the classifiers in
SandScript. For classifiers that can take on a broad range of values, such as
the client IP address, find a way to reduce the number of distinct values the
classifier can take on.
44 PTS or SDE policy table row memory Consider the size of the sets used in SandScript's table unique-by specs, and
how often you are writing to a table row. Reduce the number of rows you need
to persist to a SandScript table.
45 TCP Reassembly Buffering Check the configuration for an over-provisioning condition. Check configuration
for a scenario that can cause a large number of packets of every flow to route
somewhere other than through the PTS.
46 Stream Analysis Buffering Check the configuration for an over-provisioning condition. Check configuration
for a scenario that could cause a large number of packets of every flow to route
somewhere other than through the PTS.
47 NPU Diverted Source table space Check the deployment model. Try to have traffic flowing between fewer distinct
layer 2 destinations.
48 NPU Layer 2 Rewrite table space Check the deployment model. Try to have traffic flowing between fewer distinct
layer 2 destinations.
49 NPU Layer 3 Hairpin table space Configure fewer layer 3 hairpin destinations.

05-00262 C07
PTS Alarms

50 Total Memory Check that element is not over-provisioned. Also check to see if any application
on the modules in question has used an exceedingly large amount of memory.
This indicates that a mis-configuration, over-provisioning, or software error exists.
Run the show system processes * CLI command to identify how much
memory each process is using, on each module.
51 PTS or SDE map instances Check the SandScript map entries configured and remove entries from them to
reduce the memory usage to below 40Mb.
52 PTS Streaming Flows Verify that the PTS is not overloaded.
53 PTS Primed Flow Classification Check the configuration for an over-provisioning condition.
instances
54 PTS Largest Flow Classification Check the configuration for an over-provisioning condition.
Container
55 PTS IP Fragmentation Records Check the configuration for an over-provisioning condition. You need to either
disable fragmentation recognition or expand the deployment.
56 External MAC address table Switch to the Layer 2 (L2) mode. Review external switch configuration to reduce
number of Ethernet MAC addresses passing through the PTS cluster.
58 WDTM detection user Check the configuration for an over-provisioning condition and adjust the WDTM
policy as necessary.
59 Statistics Records Verify that the PTS is connected to the SPB and that the SPB is properly
configured to accept messages from the PTS.
64 RTMP Streaming Flows Check the configuration for an over-provisioning condition.
68 HTTP Streaming Flows Check the configuration for an over-provisioning condition.
70 PTS Policy Controller Server memory Decrease the total memory footprint of the policy controller subsystem. To do
this, decrease the number of:
• Controllers defined through SandScript.
• SandScript metrics.
• Histogram bins for the output_histogram parameter.
• Histogram bins for a metric data parameter.
Run the show policy controller CLI command to check that the total
number of unique by instances is not high. This displays the total number of
instances on the current PTS, and compares that against the stated platform
limits. If this is the case, ensure all of the unique by instances are actually active.
Perform a CND restart, to reset the total memory, if there are several unused
unique by instances.
71 PTS Policy Controller Client memory Decrease the total memory footprint of the policy controller subsystem. To do
this, decrease the number of:
• Controllers defined through SandScript.
• SandScript metrics.
• Histogram bins for the output_histogram parameter.
• Histogram bins for a metric data parameter.

05-00262 C07
PTS Alarms

72 BGPD subnets Increase the BGP subnet limit using the set config service bgp
subnet-limit CLI command. If the maximum limit is reached, then apply
filters on the peer routers to filter the BGP subnet information that is sent to the
element.
73 BGPD RIB memory Increase the BGP subnet limit using the set config service bgp
rib-memory limit CLI command. If the maximum limit is reached, then apply
filters on the peer routers to filter the BGP subnet information that is sent to the
element.
74 BGPD client RIB memory Increase the BGP subnet limit using the set config service bgp
rib-memory limit CLI command. If the maximum limit is reached, then
consider applying filters on the peer routers to filter the BGP subnet information
that is sent to the element.
81 Central LB IPv4 table rows To identify the cause and resolve this alarm:
1. Check if the PTS has raised Alarm Model 22: Misconfigured Network
Awareness, for external addresses on subscriber ports exceeds threshold,
and resolved it.
2. Ensure that the subscriber database is not sending spurious login notifications
to the cluster. Such logins cause the PTS to load-balance the associated IP
addresses and if the cluster never sees those addresses they end up wasting
resources.
Use jms Capture of the messages from the SPB to view logins. The PTS
processes login notifications for IP addresses in an internal subnet. Remove
those subnets with IP addresses that the cluster does not see (such as when
multiple clusters share the same SPB), from internal subnets to reduce the
number of entries created in the table.
3. Split subscriber traffic over multiple PTS clusters. A PTS cluster can handle
a maximum of 16 million IPs.
4. Run the set config service load-balancer mode CLI command
and, provided the policy-based load-balancing is not required to either
static or ip-hash.
Both static and ip-hash modes do not track individual IPs. They can
hash the entire space of IPv4 addresses, and therefore do not have a limit
on the number of IPs they can load-balance.
Note:
Run the restart service scfd CLI command to change the
load-balancing mode.
5. Run the clear service load-balancer CLI command to clear the
Central LB IPv4 table of stale entries if:
• The set of subscriber IP addresses that the PTS inspects has changed
significantly, and
• The PTS does not receive subscriber logouts from the subscriber
database.
Note:
Running this command can cause the traffic to shunt until all IP addresses
are re-learned.
6. Contact Sandvine Customer Support, or its authorized partner, if this does
not resolve this issue

05-00262 C07
PTS Alarms

84 PTS packet usage by all policy actions Check the configuration for an over-provisioning condition.
Note:
• Resource 39, 84 and 85 refer to the same packet pool.
• Resource 39 and 85 are displayed in the show system resource but do
not raise any alarm.
• Only Resource 84 raises an alarm for events.hrStorage.conf.
91 Central LB IPv6 table rows To identify the cause and resolve this alarm:
1. Check if the PTS has raised Alarm Model 22: Misconfigured Network
Awareness, for external addresses on subscriber ports exceeds threshold,
and resolved it.
resources.
Use jms Capture of the messages from the SPB to view logins. The PTS
processes login notifications for IP addresses in an internal subnet. Remove
those subnets with IP addresses that the cluster does not see (such as when
multiple clusters share the same SPB), from internal subnets to reduce the
number of entries created in the table.
static or ip-hash.
Note:
significantly, and
database.
Note:
are re-learned.
92 Central LB IPv6 LPM table rows To identify the cause and resolve this alarm:
resources.

05-00262 C07
PTS Alarms
Alarm Model 8: Overloaded Processor

Ensure that the subscriber database is not sending spurious login notifications
with non-default IPv6 prefix length to the cluster. Logins cause the PTS to
load-balance the associated IP addresses and, if the cluster never sees
those addresses they will waste resources.
static or ip-hash.
Note:
significantly, and
database.
Note:
are re-learned.
3.9 Alarm Model 8: Overloaded Processor

This alarm is raised if processors are operating at an overloaded rate over a 2.5 minute or 150 second interval. This is typically
due to over-provisioning of the system.
A warning, minor, or major notification is sent for these overload percentages over a 2.5 minute interval:
• warning—80% overloaded
• minor—90% overloaded and failed inspection of 1000 packets
• major—95% overloaded and failed inspection of 2000 packets
It is cleared when the CPU utilization of all overloaded modules drops below 75% over 2.5 minutes.
Profile Description
Severities • Warning
• Minor
• Major
Raise Notification svSysProcessorOverLoadNotification

Clear Notification svSysProcessorLoadOkNotification

05-00262 C07
PTS Alarms
Profile Description
Triggers • ptsdResStatsWarningCpu
• ptsdResStatsMinorCpu
• ptsdResStatsMajorCpu
• ptsdResStatsCpu
3.9.1 Overloaded Processor – Notification

MIB SANDVINE-MIB
Trap Name svSysProcessorOverLoadNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.3

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPtsResourcesStatsProcessorLoad 1.3.6.1.4.1.11610.435.8374.1.7723.3.13
svPtsResourcesStatsDeltaTooBusy 1.3.6.1.4.1.11610.435.8374.1.7723.3.14
svPtsResourcesStatsLatestCpu 1.3.6.1.4.1.11610.435.8374.1.7723.3.15
3.9.1.1 PTS Daemon CPU busy: Warning

This notification is sent if the CPU utilization of one or more modules exceeds 80% over 2.5 minutes or 150 seconds. It is cleared
when the CPU utilization of all overloaded modules drops below 75% over 2.5 minutes or 150 seconds.
Profile Description
Frequency 8 seconds
Severity Warning
Condition SANDVINE-MIB::svPtsResourcesStatsProcessorLoad = processorLoadHigh(2)
3.9.1.2 PTS Daemon CPU busy: Minor alarm

This notification is sent if the CPU utilization of one or more modules exceeds 90% over 2.5 minutes or 150 seconds, and the
PTS has failed inspection of 1000 packets in that time.
Profile Description
Severity Minor
Condition SANDVINE-MIB::svPtsResourcesStatsProcessorLoad = processorLoadSevere(3)

05-00262 C07
PTS Alarms
3.9.1.3 PTS Daemon CPU busy: Major

This notification is sent if the CPU utilization of one or more modules exceeds 95% over 2.5 minutes or 150 seconds. The PTS
has also failed to inspect 2000 packets in that time.
Profile Description
Frequency 8 seconds
Severity Major
Condition SANDVINE-MIB::svPtsResourcesStatsProcessorLoad = processorLoadCritical(4)
3.9.2 Overloaded Processor Cleared

This notification is sent when the CPU utilization of all overloaded modules drops below 75% over 2.5 minutes or 150 seconds.

MIB SANDVINE-MIB
Trap Name svSysProcessorLoadOkNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.4

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPtsResourcesStatsProcessorLoad 1.3.6.1.4.1.11610.435.8374.1.7723.3.13
svPtsResourcesStatsDeltaTooBusy 1.3.6.1.4.1.11610.435.8374.1.7723.3.14
svPtsResourcesStatsLatestCpu 1.3.6.1.4.1.11610.435.8374.1.7723.3.15

Modules that are experiencing periods of prolonged CPU utilization in excess of 95% have degraded packet inspection performance.
As a result, some new and existing flows may be bypassed for inspection to avoid congestion, latency, as well as possible packet
loss. And so the integrity of the traffic is maintained at the cost of not performing full packet inspection.
If packets are reported as “not inspected”, even a small number, the alarm severity is upgraded to minor alarm. If you receive
this alarm, it may indicate a variety of underlying problems. For suggested resolutions, see Minor alarms and suggested resolutions
for this alarm.
3.9.3.1 Overloaded Processor Alarms

Modules that are experiencing periods of prolonged CPU utilization in excess of 95% have degraded packet inspection performance.
As a result, some new and existing flows may be bypassed for inspection to avoid congestion, latency, as well as possibly packet
loss. So, the integrity of the traffic is maintained at the cost of not performing full packet inspection.
Since packet inspection is impacted, this can result in the following side effects. The severity of these side effects depends on
the SandScript that is deployed on the PTS, how long this overload condition exists, and how many modules are impacted:

05-00262 C07
PTS Alarms
• NDS reports may show lower than expected bandwidth in all bandwidth-based reports other than Bandwidth by Interface, for
the periods where the alarm was raised.
• Flow-specific SandScript is not applied to all new or existing flows that impact shaping, protocol tracking, detection (malicious
and otherwise), and similar situations.
• Subscriber mapping may stall when all new flows are not inspected.
3.9.3.2 Identifying Overloaded Modules

1. Run the show service load-balancer master CLI command to locate the cluster's master load-balancer.
2. Run the show service load-balancer modules detail CLI command to identify the overloaded modules, on the
master load-balancer.
3. Run the CLI command: show policy inspection and examine the PacketNotInspected field for the number of packets
that are not inspected.
3.9.3.3 Alarm Time-line

For this type of alarm, it is important to identify when it first occured, and when notifications were sent and/or cleared. To view
this information, use the show alarms history [Id] CLI command.
Once a timeline is established, augment it with information related to:
• Recent PTS software upgrades.
• Recent topology changes in the network.
• Recent changes to SandScript and subnets on the PTS.
• Recent features enabled/disabled on the PTS.
If there is a strong correlation between any of these recent changes and the alarm time-line, focus the root cause investigation
there. For example, if SandScript was recently modified, you should investigate the impact/intent of those changes more thoroughly.
3.9.3.4 Alarm Frequency

Along with the alarm time-line, alarm frequency information can also provide insight into root cause:
• If the alarm occurs, but is cleared at a fairly consistent frequency, then this is a strong indicator that the alarm is associated
with time-of-day traffic, and possibly that there is SandScript that is utilized more frequently at those times. For example, the
alarm occurs (perhaps multiple times) during peak hours only. To verify, correlate the alarm time-line with the NDS reports
that span that time-line. Note the bandwidth consumption of protocols from the NDS reports and determine if there is any
specific SandScript that is in action on the higher bandwidth consuming protocols.
• If the alarm is occurs, but is cleared sporadically (independent of peak hours), it may indicate the overload is related to
malicious traffic in the network. Check NDS reports for unusual spikes. Also, if WDTM is enabled, be sure to check NDS
reports for malicious activity.
• If the alarm recurs for a long period of time with no clearing, it may indicate that the PTS is under-provisioned. You can check
bandwidth utilization in real time using the show interface rate command.
3.9.3.4.1 Traffic Captures

It is often useful to take traffic captures on the affected modules before the alarm is active and while it is active. It is even better
if you can catch the transition point. This can be difficult if the alarm is sporadic and the overload condition moves between
modules. Traffic captures can often provide key insights into whether or not the overload alarm is related to specific traffic.
3.9.3.5 Load Balancing

The PTS load-balancing modes include:

05-00262 C07
PTS Alarms
Alarm Model 9: Unavailable Processing Module
• Static load-balancing, using the 8-bit mode.

• Dynamic load-balancing, using centralized load-balancing.
In both modes it is acceptable for some inspection modules to have elevated loads while others do not. However, if using static
load-balancing, and some modules are consistently running at elevated levels, the inspection rates could be approaching the
limits of the cluster. If using central load-balancing, running the clear service load-balancer CLI command provides an
immediate re-distribution of bundle assignments. Bundle assignments are automatically redistributed when a module's load
reaches a critical threshold, before that threshold traffic is inspected as expected.
In the event of a module failure, possibly caused from a software or hardware failure, traffic to that module is immediately shunted
to prevent interrupting the subscribers traffic. If the module does not come back into service after 5 minutes, the IP addresses
which it was inspecting are redistributed to the remaining modules.
3.9.3.5.1 Module Overloaded

When centralized load balancing detects that a module is overloaded (see Alarm Model 8: Overloaded Processor on page 61),
it adaptively rebalances bundles off of that module and redistributes them across the elements until the overload condition is
resolved. So it is not abnormal to see the occasional overload alarm when centralized load balancing is being used. However,
depending on the duration and frequency of the overload alarm, this can indicate a few possible issues.
If the elements are under-provisioned for the volume of traffic, removing load from one module can lead to overloading another
module. It should also be evident from Alarm Time-line and Alarm Frequency that overload bounces between modules or elements.
You may need another element to dilute the per module load.
If centralized load balancing bundling is not defined by IP--subscriber attribute, cost class, and the related definitions--then the
bundling may be too coarse. This means that there may be too many IPs per bundle. Perform a quick estimate of the IP to bundle
ratio with show service load-balancer stats.
In this case, if a module overload occurs and the centralized load balancer begins rebalancing bundles from that module across
the elements, it would be moving traffic for 1639 IPs for every bundle it moved.
Use Alarm Timeline and Alarm Frequency to validate this scenario. The overload alarm bounces between modules or elements.
In order to resolve this, the IP to bundle ratio needs to be reduced in order to reduce per bundle load. For example, if bundles
are defined by subscriber attribute, then more attribute values are needed to reduce the ratio.
3.9.3.5.2 Module Offline

When a modules status transitions from “up” to any other status, the central load balancer arms a timer. If the status of associated
modules does not return to up before the timer expires, all bundles are removed from that module and redistributed throughout
the cluster.
The default timeout for the timer is five minutes. If all of the other modules are already at high load then this could cause overload
on those modules. You can check for these types of events using the CLI command show service load-balancer modules
detail.
3.10 Alarm Model 9: Unavailable Processing

Module
This alarm is raised if one of the modules in the system has gone down. If this occurs during system boot-up, the most likely
cause is a hardware problem with the module that prevents it from booting.
If it occurs some time after a module has been up and running for a period of time, it is more likely caused by a fatal operating
system error that caused the module to restart itself. In this case, the module should come back up in a few minutes and the
svEnvModuleUpNotification is sent out, which includes the module reboot cause in the trap information (varbinds).
Note:
Alarm Model 9 (Unavailable Processing Module) is not supported on the PTS Linux platform.

05-00262 C07
PTS Alarms
Profile Description
• Clear
Raise Notification svSysModuleDownNotification
Clear Notification svSysModuleUpNotification
Triggers • ppumgrOperStatusDown
• ppumgrOperStatusUp
Unique Instance Identifier svModuleControllerModuleDescription
3.10.1 Unavailable Processing Module - Notification

MIB SANDVINE-MIB
Trap Name svSysModuleDownNotification
Trap OID .1.3.6.1.4.1.11610.6799.3.4.0.7

SNMPv2-MIB:sysName .1.3.6.1.2.1.1.5
svSeverity .1.3.6.1.4.1.11610.6799.1.10
svModuleControllerModuleDescription .1.3.6.1.4.1.11610.435.10084.1.10.1.8
svModuleControllerModuleAdminStatus .1.3.6.1.4.1.11610.435.10084.1.10.1.3
svModuleControllerModuleOperStatus .1.3.6.1.4.1.11610.435.10084.1.10.1.4
3.10.1.1 Unavailable Processing Module

This notification is sent if the admin status of a module controller is up (value=1) but the operational status of that module is either
initializing (value=1) or faulted (value=3).
Profile Description
Frequency 0 seconds (Immediate)
Severity Major
Condition (SANDVINE-MIB::svModuleControllerModuleAdminStatus == 1 (up)) && ((SANDVINE-MIB::svModu
leControllerModuleOperStatus == 2 (Initializing)) || (SANDVINE-MIB::svModule
ControllerModuleOperStatus == 3 (faulted)))
3.10.2 Unavailable Processing Module Cleared

This notification is sent if a module showing a “down” status, but is now operational. It also includes the module reboot cause in
the trap information (varbinds).

05-00262 C07
PTS Alarms

MIB SANDVINE-MIB
Trap Name svSysModuleUpNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.8

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svModuleControllerModuleDescription 1.3.6.1.4.1.11610.435.10084.1.10.1.8
svModuleControllerModuleAdminStatus 1.3.6.1.4.1.11610.435.10084.1.10.1.3
svModuleControllerModuleOperStatus 1.3.6.1.4.1.11610.435.10084.1.10.1.4
svModuleControllerModuleRebootCause 1.3.6.1.4.1.11610.435.10084.1.10.1.7
3.10.2.1 Unavailable Processing Module Cleared

This notification is sent when the admin status of a module controller is up and the operational status of that module is also up
(value=1).
Profile Description
Severity Cleared
Condition (SANDVINE-MIB::svModuleControllerModuleAdminStatus == 1 (up)) && (SANDVINE-MIB::
svModuleControllerModuleOperStatus == 4 (up))

Depending on the load balancing method that is being used, the module may not be used for any traffic processing. If the module
continues to transition between up and down, it should be administratively disabled until Sandvine Customer Support or its
authorized partner can assist with the issue.
3.10.3.1 Unavailable Processing Module Alarm

Depending on the load balancing method used, the module may not be processing any traffic. If a module continues to transition
between up and down, disable it administratively until Customer Support or its authorized partner can assist with the issue.
In general, this alarm may indicate a kernal crash on the module that went down, or that there is a hardware issue on that module.
Contact Customer Support for assistance.
3.10.3.2 Load Balancing

The PTS load-balancing modes include:
• Static load-balancing, using the 8-bit mode.
• Dynamic load-balancing, using centralized load-balancing.
In both modes it is acceptable for some inspection modules to have elevated loads while others do not. However, if using static
load-balancing, and some modules are consistently running at elevated levels, the inspection rates could be approaching the
limits of the cluster. If using central load-balancing, running the clear service load-balancer CLI command provides an

05-00262 C07
PTS Alarms
Alarm Model 10: Unavailable Service Component
immediate re-distribution of bundle assignments. Bundle assignments are automatically redistributed when a module's load
reaches a critical threshold, before that threshold traffic is inspected as expected.
In the event of a module failure, possibly caused from a software or hardware failure, traffic to that module is immediately shunted
to prevent interrupting the subscribers traffic. If the module does not come back into service after 5 minutes, the IP addresses
which it was inspecting are redistributed to the remaining modules.
3.10.3.2.1 8-Bit Load Balancing

When a module is unavailable any traffic destined for that module is rebalanced among the remaining modules in the cluster.
This increases the traffic processing load of the other modules. Traffic is rebalanced again when the module comes back online.
In the case of static load balancing all traffic on all modules is rebalanced.
3.10.3.2.2 Centralized Load Balancing

When a module is unavailable any traffic destined for that module is shunted for a period of up to five minutes and no new traffic
is assigned to the module. If the module comes back online before the five minute period expires, traffic is again sent to that
module. If the module does not come back online within the five minute period, all traffic assigned to the module is rebalanced
among the remaining modules in the cluster.
3.11 Alarm Model 10: Unavailable Service

Component
The alarm is raised when if any of the service components fails due to administrative reasons or fatal error.
Unless this is resolved administratively, all service components restart automatically.
Note:
Alarm Model 10 (Unavailable Service Component) is not supported on the PTS Linux platform.
Profile Description
• Clear
Major Notification svSysServiceComponentOfflineNotification
Clear Notification svSysServiceComponentOnlineNotification
Triggers • ServiceComponentDownTrigger
• ServiceComponentUpTrigger
Unique Instance Identifier svServiceComponentName
These tables explain the MIB Reference names and Varbind Names for this alarm.

MIB SANDVINE-MIB
Trap Name svSysServiceComponentOfflineNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.5


05-00262 C07
PTS Alarms

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svServiceComponentName 1.3.6.1.4.1.11610.435.11281.1.11.1.3
svServiceComponentAdminStatus 1.3.6.1.4.1.11610.435.11281.1.11.1.5
svServiceComponentOperStatus 1.3.6.1.4.1.11610.435.11281.1.11.1.6
svServiceComponentFaults 1.3.6.1.4.1.11610.435.11281.1.11.1.12
3.11.1 Unavailable Service Component: Major

The major notification is sent if the administrative status of a service component is up (value=1) but its operational status is:
• stopped (value=1)
• unlicensed (value=3)
• faulted (value=4)
• degraded (value=8)
This table explains the different statuses.
Operational status Description of service

stopped The service is not running.
disabled The configuration has disabled the service.
unlicensed A services license is invalid (PTS only).
faulted Service has failed and is not providing some or all of its functionality to the system. Restart the
system.
initializing The service is initializing itself.
starting The service is starting itself.
reloading The service is reloading itself.
degraded The service is online on some, but not on all, modules.
online The service is online.
This table describes the trigger information for the alarms raise (major) notification.
Profile Description
Severity Major
Condition (SANDVINE-MIB::svServiceComponentAdminStatus ==1 (up)) && ((SANDVINE-MIB::svServ
iceComponentOperStatus == 1 (stopped))) || (SANDVINE-MIB::svServiceComponentOperStatus
== 3 (unlicensed)) || (SANDVINE-MIB::svServiceComponentOperStatus == 4 (faulted)) || (
SANDVINE-MIB::svServiceComponentOperStatus == 8 (degraded)))

05-00262 C07
PTS Alarms
3.11.2 Unavailable Service Component: Clear

This notification is sent when the administrative status of a service component returns to up (value=1) and its operational status
is online (value=9).
Profile Description
Severity Cleared
Condition • (SANDVINE-MIB::svServiceComponentAdminStatus ==1 (up)) &&
• (SANDVINE-MIB::svServiceComponentOperStatus == 9 (up))
3.11.3 Background Service Processes

The background service processes monitored on the PTS are:
Name Full Name Description Applicability

SFCD Switching Fabric Control This daemon handles the configuration and management All releases
Daemon of internal layer 2 switching for the PTS.
The SFCD handles configuration and management of the
switch fabric and interface modules (for example, SFP+).
In addition, the SFCD also handles the discovery and
distribution of traffic to all local and cluster-wide modules.
PTSD Policy Traffic Switch Daemon This daemon inspects packets, identifies protocols, and All releases
applies SandScript policy on new flows for PTSM to enforce.
The PTSD application is responsible for many functions
including L3-L7 protocol recognition, host and URL filtering,
and HTTP redirection.
PTSM Policy Traffic Switch Kernel This module provides bridging of all flows within the kernel, All releases
Module and functions such as traffic shaping.
CND Central Node Daemon This daemon connects and sends statistics (which include All releases
published expressions and other data available in NDS
reports) to the reporting platform.
This daemon is also involved in mapping of subscribers
and dynamically adjusting shaping/session management
rates, and can be used in load-balancing.
SCDPD Sandvine Cluster Discovery This daemon coordinates communication among all All releases
Protocol Daemon applications on a single box and within a cluster; also acts
as the SNMP daemon.
SVBGPD Sandvine Border Gateway This daemon learns routes from routers through the BGP All releases
Protocol Daemon protocol and communicates those routes to other PTS
processes such as PTSD and CND.
MSD Management Server Daemon This daemon provides services for CLI and Control Center. Release 6.0 and up

05-00262 C07
PTS Alarms
3.11.4 Impact and Suggested Resolution: Alarm Model 10

Typically, any service that exits unexpectedly restarts automatically, so this alarm can appear and then clear itself. If that does
not happen, restart the affected service manually to resolve the issue. Also if a service is stopped for administrative reasons,
restart the service manually.
• Run the restart service <service-name> command to restart an active process.
•
The impact of this alarm is dependent on the specific service process. This table provides the impact of failure for the service
processes.
Name Impact of Service Failure

CND The impact when the CND services stops:
• The system cannot upload statistics to the reporting platform (PTS only).
• The CND stops mapping subscribers, but, existing subscriber mappings remain active.
• The CND stops dynamically adjusting shaping and session management rates. Some, or all, dynamic
shapers in the cluster are reset to the configured maximum rate.
• If CND is the load-balancer master, the load-balancing state is cleared. The loadbalancing element
retains the last rate(s) from before the cnd was stopped.
MSD Existing CLI sessions are disconnected from the server and new CLI sessions are unable to connect
until the service is restored. Control Center is not able to monitor or deploy to the element until the
service is restored.
PTSD The PTSD element stops inspecting traffic and shunts traffic until the service restarts. During the restart,
there may be short periods where packets are dropped.
PTSM Stops the PTS from inspecting traffic and can cause it to drop packets.
SCDPD Prevents clustering from working and in the case of a PTS can result in preventing traffic inspection. The
CLI and SNMP interfaces will also fail.
SVBGPD If enabled, this service stops the subnets.txt file from updating and leads to no SandScript application
to some subscribers (PTS only).
ECD Unable to establish the connection between SandScript and shell (command-line).
SFCD For informations, refer to the Impact of Restarting SFCD Services in the PTS Alarms Reference Guide.
Run these CLI commands to diagnose the problem further:

• show system services
• show service load-balancer modules
Run the show system log CLI command to diagnose the reason when services exit unexpectedly or fail to start.
Alternatively, you can also search the /var/log/svlog for reasons, if a service exits unexpectedly or fails to start up.
3.11.4.1 Impact of Restarting SFCD Services

Considerable system impact can result from restarting SFCD services.
Possible impact includes:
• The SFCD process is stopped.
• Traffic in buffers within the switch fabric is lost.
• The switch fabric cannot receive additional traffic.

05-00262 C07
PTS Alarms
Alarm Model 11: Unavailable Bypass Group
• The NPUs shunt traffic.

• If there is a bypass card, traffic is now in bypass for this unit and no inspection is done.
• While traffic is in bypass, no mappings take place as Radius traffic is passed through the system.
• Mappings during the entire duration of the restart, and for this specific unit, are ignored.
• Potential impact can affect the reporting interval in demographic statistics. This is dependent on how long it takes for the
system to complete the restart.
• The SFCD process comes back.
• The NPU immediately starts sending traffic to the switch fabric.
• Traffic is now inspected on the modules.
• RADIUS traffic is teed to the SPB so that mapping takes place.
3.11.4.2 Impact of Restarting CND

Considerable system impact can result from restarting CND services.
Possible impact includes:
• The CND process stops.
• Traffic is unaffected.
• Any statistics queued in the CND and on their way to the SPB are lost.
• Any subscriber lookups queued in the CND and on their way to the SPB are lost.
• If the CND is the master central load balancer, a new master is elected. The new master maintains original balancing.
• The CND is restarted.
3.12 Alarm Model 11: Unavailable Bypass Group

This alarm is raised when a set of interfaces that are in a bypass group have gone into the bypass state. This could happen
because the group was administratively put into bypass mode, or if software detected a critical processing error.
Note:
This alarm applies to both the internal bypass on the PTS 24000 as well as the external bypass chassis configuration. As
a result, there are different triggers and MIB references for each configuration.
Profile Description
Severity • Critical
• Major
• Clear
Raise Notification svIfBypassGroupInBypassNotification
Clear Notification svIfBypassGroupActiveNotification
Triggers Internal bypass:
• portTopologyBypassMode
• portTopologyActiveMode
External bypass:
• extActiveMode
• extBypassMode
• hbFaultMode

05-00262 C07
PTS Alarms
Profile Description
Unique instance identifier svBypassGroupGroupTableOperStatus
3.12.1 Bypassing Traffic – Notification

MIB SANDVINE-MIB
Trap Name svIfBypassGroupInBypassNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.1
Internal bypass

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svBypassGroupGroupTableDescription 1.3.6.1.4.1.11610.435.10470.1.30.10.1.7
svBypassGroupGroupTableOperStatus 1.3.6.1.4.1.11610.435.10470.1.30.10.1.3
svBypassGroupGroupTableAdminStatus 1.3.6.1.4.1.11610.435.10470.1.30.10.1.2
External bypass

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPortTopologyBypassChassisDescription 1.3.6.1.4.1.11610.435.10470.1.30.6
svPortTopologyBypassChassisOperStatus 1.3.6.1.4.1.11610.435.10470.1.30.2
svPortTopologyBypassChassisAdminStatus 1.3.6.1.4.1.11610.435.10470.1.30.1
3.12.1.1 Bypassing Traffic - Internal Bypass

This notification is sent if the bypass group table operational status sets to bypass mode (value=0).
Profile Description
Severity Major
Condition SANDVINE-MIB::svBypassGroupGroupTableOperStatus == 0 (bypass)
3.12.1.2 Bypassing Traffic - External bypass

This notification is sent when bypass group table operational status sets to bypass mode (0).

05-00262 C07
PTS Alarms
Profile Description
Severity Major
Condition SANDVINE-MIB::svPortTopologyBypassChassisOperStatus == 0 (bypass)
3.12.1.3 Unavailable Bypass Group - External bypass

This notification is sent when contact with the bypass chassis has been lost and proper operation of the bypass chassis is no
longer guaranteed.
Profile Description
Severity Critical
Condition SANDVINE-MIB::svBypassGroupGroupTableOperStatus == 4 (hb_fault)
3.12.2 Bypassing Traffic Cleared

This notification is sent when a set of interfaces that were previously in the bypass state are now active. It is an Interfaces Active
alarm.

MIB SANDVINE-MIB
Trap Name svIfBypassGroupActiveNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.2
Internal bypass

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svBypassGroupGroupTableDescription 1.3.6.1.4.1.11610.435.10470.1.30.10.1.7
svBypassGroupGroupTableOperStatus 1.3.6.1.4.1.11610.435.10470.1.30.10.1.3
svBypassGroupGroupTableAdminStatus 1.3.6.1.4.1.11610.435.10470.1.30.10.1.2
External bypass

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPortTopologyBypassChassisDescription 1.3.6.1.4.1.11610.435.10470.1.34.6
svPortTopologyBypassChassisOperStatus 1.3.6.1.4.1.11610.435.10470.1.34.2

05-00262 C07
PTS Alarms

svPortTopologyBypassChassisAdminStatus 1.3.6.1.4.1.11610.435.10470.1.34.1
3.12.2.1 Bypassing Traffic Cleared—Internal Bypass

This notification is sent when the bypass group table operational status sets to active (value=1).
Profile Description
Severity Cleared
Condition SANDVINE-MIB::svBypassGroupGroupTableOperStatus == 1 (active)
3.12.2.2 Bypassing Traffic Cleared—External Bypass

This notification is sent when bypass group table operational status sets to active (value = 1).
Profile Description
Severity Cleared
Condition SANDVINE-MIB::svPortTopologyBypassChassisOperStatus == 1 (active)
3.12.3 Unavailable Bypass Group—Critical Alarms

This alarm indicates that the bypass chassis has stopped sending heartbeats.
The bypass chassis stops sending heartbeats when it has lost power, the serial cable has become disconnected, or it has detected
a hardware fault on the chassis or blade.
3.12.3.1 Impact and Suggested Resolution, Alarm Model 11

Traffic is not inspected. Suggested resolutions:
1. Use the show interface bypass-chassis CLI command to inspect the status of the bypass chassis.
2. If the OperStatus shows as hb_fault Inspect the serial cables and ensure that they are securely fastened to both the PTS
24000 and the bypass chassis.
3. Check the LEDs on the bypass chassis for failure mode.
3.12.3.1.1 Bypassing Traffic

This alarm indicates that the bypass functionality of a bypass group is either enabled administratively or through software after
detecting a critical processing error.
Bypass Operation State Alarm Comment

active Clear Packets are inspected.
bypass Major Either a software fault was detected warranting a bypass event or the user
forced bypass via the admin status. In this state, packets are not inspected.

05-00262 C07
PTS Alarms
Alarm Model 12: Network Interface Errors
Bypass Operation State Alarm Comment

hb_fault Critical Loss of communication with bypass chassis. In this state, packets are not
inspected.
Bypass Administration State Comment

software Default mode (internal bypass blade) - allows the software to decide when to transition into
bypass and active state. Bypass mode is triggered in the event that scdpd, sfcd, or lbcd
daemons are stopped. Active mode is triggered when all daemons are operating normally.
bypass Remains in bypass mode regardless of software state. In this state, packets will not be
inspected
active Remains in active mode regardless of software state. In this state, packets may be dropped
if the PTS is rebooted or power cycled.
down Default mode (external bypass chassis) - no bypass chassis is connected
Run the show interface bypass CLI command to view the bypass group state.

In the event of an alarm:
• Packet inspection is bypassed.
• No statistics are gathered while the alarm is raised.
1. Allow the element to complete the boot up sequence.
2. Run the show config interface bypass CLI command to check that BypassAdminMode is not configured (for internal
bypass blades).
3. Verify, for an external bypass chassis, that the BypassAdmin mode is configured to software.
a. Run the show config interface bypass external CLI command
4. Check that all services are running. The bypass alarm is triggered if any of these services are not running: SFCD, SCDPD,
LBCD. Run the show system services CLI command to check services.
3.13 Alarm Model 12: Network Interface Errors

This alarm is raised when physical errors are detected on an interface (ifInErrors or ifOutErrors).Typical errors are FCS and
alignment errors. Cabling issues are the usual causes of these types of errors.
Profile Description
Severities Minor and Major
Raise Notification svIfErrorNotification
Clear Notification svIfNoErrorNotification
Triggers ifNetworkErrorsX
Where X is the interface index (iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifIndex)
.

05-00262 C07
PTS Alarms
Profile Description
Note that this model is only valid for interfaces with type (iso.org.dod.internet.mgmt.mib-2.interfaces.
ifTable.ifEntry.ifType) PropMultiplexor or EthernetCsmacd. So for an interface with the index
21106692, the trigger name would be ifNetworkErrors21106692.
Unique Instance Identifier IF-MIB:ifIndex
3.13.1 Network Interface Errors –Major and Minor Notifications

MIB SANDVINE-MIB
Trap Name svIfErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.3

svSeverity 1.3.6.1.4.1.11610.6799.1.10
IF-MIB:ifIndex 1.3.6.1.2.1.2.2.1.1
IF-MIB:ifDescr 1.3.6.1.2.1.2.2.1.2
IF-MIB:ifInErrors 1.3.6.1.2.1.2.2.1.14
IF-MIB:ifOutErrors 1.3.6.1.2.1.2.2.1.20
svIfDeltaStatsIfDeltaTableIfInErrors 1.3.6.1.4.1.11610.435.10470.1.3.4.10.1.3
svIfDeltaStatsIfDeltaTableIfOutErrors 1.3.6.1.4.1.11610.435.10470.1.3.4.10.1.5
svThresholdDelta 1.3.6.1.4.1.11610.6799.1.15
3.13.1.1 Network Interface Errors - Major

This notification is sent if the sum of ifInErrors and ifOutErrors exceeds 1000 within an interval of 1 hour (3600 seconds).
Profile Description
Severity Major
Condition PTS—DELTA (IF-MIB::ifInErrors + IF-MIB::ifOutErrors) > 1000
When the major alarm occurs on a PTS 32000 model, the condition is DELTA (IF-MIB::ifInErrors
+ IF-MIB::ifOutErrors) > 1000
SPB—DELTA (IF-MIB::ifInErrors + IF-MIB::ifOutErrors) >= 1000
3.13.1.2 Network Interface Errors- Minor

This notification is sent if the sum of ifInErrors and ifOutErrors falls below 20, or rises above 10, within an interval of 1 hour (3600
seconds).

05-00262 C07
PTS Alarms
Profile Description
Severity Minor
Condition PTS—If the Major alarm was raised: DELTA (IF-MIB::ifInErrors + IF-MIB::ifOutErrors) <10
Otherwise: DELTA (IF-MIB::ifInErrors + IF-MIB::ifOutErrors) > 10
When the alarm occurs on a PTS 32000 model, the condition is:
DELTA (IF-MIB::ifInErrors + IF-MIB::ifOutErrors) <200000
Otherwise: DELTA (IF-MIB::ifInErrors + IF-MIB::ifOutErrors) > 10
SPB—When the alarm occurs on a SRP, the condition is, DELTA (IF-MIB::ifInErrors + IF-MIB::
ifOutErrors) >= 10 but < 1000
3.13.2 Network Interface Errors- Clear

This notification is sent when no physical errors have been observed on an interface for at least an hour.

MIB SANDVINE-MIB
Trap Name svIfNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.4

svSeverity 1.3.6.1.4.1.11610.6799.1.10
IF-MIB:ifIndex 1.3.6.1.2.1.2.2.1.1
IF-MIB:ifDescr 1.3.6.1.2.1.2.2.1.2
IF-MIB:ifInErrors 1.3.6.1.2.1.2.2.1.14
IF-MIB:ifOutErrors 1.3.6.1.2.1.2.2.1.20
svIfDeltaStatsIfDeltaTableIfInErrors 1.3.6.1.4.1.11610.435.10470.1.3.4.10.1.3
svIfDeltaStatsIfDeltaTableIfOutErrors 1.3.6.1.4.1.11610.435.10470.1.3.4.10.1.5
Specifically, the clear notification is sent if the sum of ifInErrors and ifOutErrors equates to 0 within an interval of 1 hour (3600
seconds).
Profile Description
Severity Cleared
Condition DELTA (IF-MIB::ifInErrors + IF-MIB::ifOutErrors) == 0

05-00262 C07
PTS Alarms
3.13.3 PTS—Impact and Suggested Resolution, Alarm Model 12

Discarded packets can adversely affect subscriber traffic.
General resolutions include:
• Faulty fiber/copper patch cable.
• Faulty interface modules.
• port speed and duplex mismatch.
Perform these resolution steps for Alarm Model 12:
1. Run the show interface counters CLI command to confirm which interfaces are experiencing interface errors.
2. Run the show interface configuration CLI command to confirm that the port speed and duplex match.
PTS> show interface configuration
Port AdminStatus OperStatus MTU Medium IfAlias Function LagPort Shunt

---- ----------- ---------- ------ ---------- ------- ------------ ------- -------
2-11 [up] [down] 15,796 10GBase-LR [subscriber] none [false]
3. If the errors are seen on external ports:

a. Replace the fiber/copper patch cables with known good fiber/copper cables.
b. Replace the interface modules with known good modules.
Another possible cause is a link failure due to receiving link-faults from the opposing connected port. Link-fault messages occur
when a neighbor device connected to the PTS is no longer receiving a signal, which may indicate a failure of the optical interface
(SFP+) or a break in the fiber optic cable, and the neighbour device is sending remote faults to the PTS.
When the PTS receives a link-fault signal:
• The OperStatus of the port is brought down.
• This alarm is raised.
• Run the show interface modules <interface> CLI command for the down port to identify normal Rx and Tx levels.
In this situation, confirm the receive power levels on the neighbor device and correct any link-path issues between the two devices.
PTS> show interface modules 2-11
Port : 2-11
ModuleType : [SFP+]
AdminStatus : [up] <- Note admin status is up and module status is up
ModuleStatus : [up]
SerialNumber : AAA00A0
VendorName : FINISAR CORP.
VendorRevision : A
DataCode : 011111
Medium : 10GBase-LR
Temperature : 31.00 C
TxPower : -1.5989 dBm
RxPower : -7.3424 dBm <- Correct yet interface is operDown. This is due to link-fault.
Connector : LC
SupportedInterfaces: 10GBase-LR
SerialEncoding : 64B/66B
NormalBitRate : 10300 Mbits/s
UpperBitRate : Not Specified
LowerBitRate : Not Specified
Options : Loss of Signal implemented TX_FAULT signal implemented TX_DISABLE implemented
The suggested resoultions for specific errors are:
Error Suggested resolution

AlignErr Possibly due to bad/dirty fiber or bad SFP/XFP modules. Or network cabling is too long. Or network
segment is noisy.

05-00262 C07
PTS Alarms

FCSErr FCS errors indicate that frames of data are being corrupted. Check the cable and cable connections
for breaks or damage. Occasionally the problem may be caused by interference from other cables
or machinery.
SingleCol Collisions indicate that two devices detect that the network is idle and are trying to send packets
at exactly the same time.
MultiCol Collisions indicate that two devices detect that the network is idle and are trying to send packets
DeferTx N/A
LateColl Late collisions indicate that two devices have transmitted at the same time, but cabling errors (
most commonly, excessive network segment length or repeaters between devices) prevent either
transmitting device from detecting a collision.
ExcessColl Excessive collisions indicate that 16 consecutive collisions have occurred, usually a sign that the
network is becoming congested. For each excessive collision count (or after 16 consecutive
collisions), a packet is dropped. If you know the normal rate of excessive collisions, then you can
determine when the rate of packet loss is affecting your network's performance.
MacTxErr N/A
SenErr N/A
LongErr This is a check on all packets against the MTU size on the interface. This does not indicate that
packets are being discarded.
MacRxErr N/A
SymErr Possibly due to bad/dirty fiber or bad SFP/XFP modules. If errors are seen on the wf.x.x interfaces,
this indicates that the switching fabric chip is defective.
3.13.4 SPB—Impact and Suggested Resolution, Alarm Model 12

Discarded packets can adversely affect performance, and could cause statistics lag or subscriber mapping issues if severe.
General resolutions include:
• Faulty fiber/copper patch cable.
• Faulty interface modules.
• Port speed and duplex mismatch.
Perform these resolution steps for Alarm Model 12:
1. Run the show interface counters CLI command to confirm which interfaces are experiencing interface errors.
2. Run the show interface configuration CLI command to confirm that the port speed and duplex match.
show interface configuration
Port AdminStatus OperStatus MTU Medium IfAlias Function LagPort Shunt

---- ----------- ---------- ------ ---------- ------- ------------ ------- -------
2-11 [up] [down] 15,796 10GBase-LR [subscriber] none [false]
3. For errors are seen on port, replace the fiber/copper patch cables with known good fiber/copper cables.
When the SPB receives a link-fault signal:

05-00262 C07
PTS Alarms
Alarm Model 13: Discarded Packets
• The OperStatus of the port is brought down.

• This alarm is raised.
In this situation, confirm the receive power levels on the neighbor device and correct any link-path issues between the two
devices.
The suggested resolutions for specific errors are:

AlignErr Possibly network cabling is too long. Or network segment is noisy.
FCSErr FCS errors indicate that frames of data are being corrupted. Check the cable and cable
connections for breaks or damage. Occasionally the problem may be caused by interference
from other cables or machinery.
SingleCol Collisions indicate that two devices detect that the network is idle and are trying to send packets
MultiCol Collisions indicate that two devices detect that the network is idle and are trying to send packets
DeferTx N/A
LateColl Late collisions indicate that two devices have transmitted at the same time, but cabling errors
(most commonly, excessive network segment length or repeaters between devices) prevent
either transmitting device from detecting a collision.
ExcessColl Excessive collisions indicate that 16 consecutive collisions have occurred, usually a sign that
the network is becoming congested. For each excessive collision count (or after 16 consecutive
collisions), a packet is dropped. If you know the normal rate of excessive collisions, then you
can determine when the rate of packet loss is affecting your network's performance.
MacTxErr N/A
SenErr N/A
LongErr This is a check on all packets against the MTU size on the interface. This does not indicate
that packets are being discarded.
MacRxErr N/A
SymErr Possibly due to bad/dirty fiber or bad SFP/XFP modules. If errors are seen on the wf.x.x
interfaces, this indicates that the switching fabric chip is defective.
3.14 Alarm Model 13: Discarded Packets

This alarm is raised if the packets are discarded on the PTS interface (ifInDiscards or ifOutDiscards). This happens if
the incoming traffic is too bursty or the system is over-provisioned.
This alarm is raised if the packets are discarded on the SPB interface (ifInDiscards or ifOutDiscards). This happens if
the incoming traffic is too bursty or the system is overloaded.
Profile Description
• Minor
• Clear

05-00262 C07
PTS Alarms
Profile Description
Raise Notification svIfDropNotification
Clear Notification svIfNoDropNotification
Triggers interfaceDrops
(iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifIndex).
Note that this alarm model applies to all interface types except PropMultiplexor.
3.14.1 Discarded Packets - Notifications

MIB SANDVINE-MIB
Trap Name svIfDropNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.5

svSeverity 1.3.6.1.4.1.11610.6799.1.10
IF-MIB:ifIndex 1.3.6.1.2.1.2.2.1.1
IF-MIB:ifDescr 1.3.6.1.2.1.2.2.1.2
IF-MIB:ifInDiscards 1.3.6.1.2.1.2.2.1.13
IF-MIB:ifOutDiscards 1.3.6.1.2.1.2.2.1.19
svIfDeltaStatsIfDeltaTableIfInDiscards 1.3.6.1.4.1.11610.435.10470.1.3.4.10.1.2
svIfDeltaStatsIfDeltaTableIfOutDiscards 1.3.6.1.4.1.11610.435.10470.1.3.4.10.1.4
3.14.1.1 Discarded Packets- Major

This notification is sent if the change in the sum of ifInDiscards and ifOutDiscards exceeds 1000 within an interval of fifteen (15)
minutes.
Profile Description
Severity Major
Condition DELTA (IF-MIB::ifInDiscards + IF-MIB::ifOutDiscards) > 1000

05-00262 C07
PTS Alarms
3.14.1.2 Discarded Packets- Minor

This notification is sent if the change in the sum of ifInDiscards and ifOutDiscards rises above 10 or falls below 20 within an
interval of fifteen (15) minutes.
Profile Description
Severity Minor
Condition PTS—If the Major alarm has raised: DELTA (IF-MIB::ifInDiscards + IF-MIB::ifOutDiscards) <20
Otherwise: DELTA (IF-MIB::ifInDiscards + IF-MIB::ifOutDiscards) > 10
SPB—If the Major alarm was raised: DELTA (IF-MIB::ifInDiscards + IF-MIB::ifOutDiscards) has
recently fallen below 20 and remains above 10 and below 1000.
Otherwise: DELTA (IF-MIB::ifInDiscards + IF-MIB::ifOutDiscards) > 10 and is < 1000
3.14.2 Discarded Packets- Clear

This notification is sent when an interface that was previously discarding packets has not discarded any packets for at least fifteen
(15) minutes.

MIB SANDVINE-MIB
Trap Name svIfNoDropNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.6

svSeverity 1.3.6.1.4.1.11610.6799.1.10
IF-MIB:ifIndex 1.3.6.1.2.1.2.2.1.1
IF-MIB:ifDescr 1.3.6.1.2.1.2.2.1.2
IF-MIB:ifInDiscards 1.3.6.1.2.1.2.2.1.13
IF-MIB:ifOutDiscards 1.3.6.1.2.1.2.2.1.19
svIfDeltaStatsIfDeltaTableIfInDiscards 1.3.6.1.4.1.11610.435.10470.1.3.4.10.1.2
svIfDeltaStatsIfDeltaTableIfOutDiscards 1.3.6.1.4.1.11610.435.10470.1.3.4.10.1.4
Profile Description
Severity Cleared
Condition DELTA (IF-MIB::ifInDiscards + IF-MIB::ifOutDiscards) == 0

05-00262 C07
PTS Alarms
3.14.3 PTS—Impact and Suggested Resolution, Alarm Model 13

The type of traffic that the PTS discards may adversely affect the subscriber traffic. Packet discards can also occur due to a
variety of reasons on the different port locations/types within the PTS.
Types of Traffic causing Packet Discards PTS Port Locations for Packet Discards
• Data • External
• Cluster • Network Processing Unit (Load Balancing)
• Service • Internal Fabric (Workfarm, Switch, Fabric)
• Control • Packet Processing Modules
• Management • Policy
Alarm 13 Resolution Steps

1. Identify the type of traffic that PTS discards and the location of packet discards. Note that the possible locations are
specific to the PTS platform and the installed blades under consideration.
These commands provide more information about the type of traffic and location of packet discards:
a. Run the show alarms CLI command to see the traffic type and location of packet discards.
b. Run the show interface configuration CLI command to correlate the function of an external port with its
configuration.
c. Run the show interface drops CLI command to gather additional information on interface packet discards.
When using the show interface drops|non-zero CLI command, consider narrowing your the search with the
non-zero filter. The output from this command validates the location of packet discards within the system.
2. Once you have identified the type of traffic and location, investigate the packet discards on egress links.
Packet discards on egress links are most often attributed to system under provisioning or bursty traffic conditions.
These are some of the examples for packet discards on egress links:
Packet Discards on External Interfaces
Traffic Type Reason for Packet Discard CLI command For Diagnosis/ Resolution
Data System under-provisioning for data show system blades
intersect. show interface rate data
An excess of flooded packets may be show interface bridge-group

due to improper cabling for fan-in /
fan-out (multiplex). That is, when there
are greater than two interfaces in a single
bridge group. For example, 10 G sending
to 1 G.
If the interface is in a multi-port
bridge-group, verify that there is no
excess of flooded packets.
Cluster System under-provisioning for cluster Revisit guidelines for cluster deployment
element interconnectivity or poor cluster recommendations.
topology.

05-00262 C07
PTS Alarms
Traffic Type Reason for Packet Discard CLI command For Diagnosis/ Resolution
Improper trunk distribution configuration. • show config interface
trunk-distribution
• show interface rate
link-aggregation-group
Improper load balancing configuration. Use these CLI commands to see if the PTS is
inspecting an unbalanced amount of traffic:
• show config service load-balancer
• show interface rate
link-aggregation-group
Service Under-provisioning for divert/tee • show interface rate cluster

functionality and throughput:
• show policy destination
• Persistent drops: under-provisioning
• Periodic drops: bursts to destination
Packet Discards on Internal Fabric

Interface drops on internal aggregate fabric data may occur on the switching fabric chip connected to the data interfaces of
the processing module.
Possible causes include:
• Uneven distribution of subscriber IPs across elements in the cluster.
• Over-provisioned cluster
• Bursty traffic to the modules.
Interface drops on internal aggregate fabric core may occur when the links are saturated.
• Cluster is not a full mesh.
• Uneven distribution of traffic between elements in the cluster.
• On the PTS 22000, the number of cluster links on the blade exceeds the number of cluster links on the chassis.
See section 6.4.2 PTS 22000: Connecting Cluster Interfaces in the PTS Hardware Installation Guide, for more information.
Contact Sandvine Technical Support, for resolution of issues due to packet discards on internal fabric.
Packet Discards on Network Processing Units (NPU)
The packet discards on NPUs are heavily dependent on the installed blade.
There are two classes—link-side and switch-side.
Type of NPU Packet Reason for Packet Discard CLI command For Diagnosis
Discard
Link side For PTS 14520, BLD 24040, and BLD 24080, the reason
for packet discard is same as that for Data Traffic Type
in the table Packet Discards on External Interfaces.
Improper NPU assignment or NPU link assignment.
This can be due to over subscription of an NPU or an NPU
link.

05-00262 C07
PTS Alarms
Type of NPU Packet Reason for Packet Discard CLI command For Diagnosis
Discard
Switch-Side System under-provisioning can lead to processing module Validate NPU and NPU link
egress bursts. assignments via the show
interface npu assignment
CLI command.
Packet Discards on Packet Processing Modules

This may due to:
• Improper load balancing configuration.
• Improper tunneling configuration (that is, IP-in-IP).
• High usage subscriber exceeding the limitations of a single module.
3. Investigate the packet discards on ingress links.

Ingress packet discards on a cluster or service port may be due to an unknown destination flood. Example: A change in the
network path to a tee destination host. This may also be indicative of a topology loop for service/cluster ports. Sometimes
packet discards may be due to severe errors in the packets, due to physical link layer reasons.
Interface drops on internal aggregate module ptsm_data1/ptsm_data2 may occur if the ingress packet rate to the
processing module exceeds the packet processing/inspection rate. Normally, these discards occur as a result of high
CPU utilization on the processing module.
• Cables are not seated properly.
• Under-provisioned cluster.
• Sharp increase in new sessions.
• Large number of subscribers.
• Uneven distribution of subscriber IPs across elements in the cluster.
• Attack traffic—syn-flood attacks/address-scan attacks.
• Overly complex SandScript.
4. Check whether the cables are firmly seated.
5. Check the traffic rates to the modules and see if the traffic rates are getting distributed evenly in the modules.
Run the show service load-balancer modules CLI command for more information.
6. Determine whether the load-balancing algorithm used is appropriate for the deployment.
Consider using centralized load-balancing by locality, if the network is experiencing extreme asymmetric traffic.
7. Remove the SandScript policy and those policies that cause the packet discards.
3.14.4 SPB—Impact and Suggested Resolution, Alarm Model 13

Discarded packets will affect performance and might delay subscriber mapping.
Identify the port on which the traffic was discarded.

05-00262 C07
PTS Alarms
Alarm Model 14: Network Interface Down
These commands provide more information about the type of traffic and location of packet discards:
a. Run the show alarms CLI command to see the location of packet discards.
b. Run the show interface drops CLI command to gather additional information on interface packet discards.
If the SRP needs to discard outgoing packets, it is due to a sustained load exceeding the link speed. It may be necessary
to split the cluster and allocate an SRP to each part of the resulting pair of clusters. It is possible that policy on the attached
PTS is calling for too much information from the SRP during traffic inspection. Revise the policy to cache some of the
information or to not use such complex table structures.
3.15 Alarm Model 14: Network Interface Down

This alarm is raised to indicate that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one
of its communication links is about to enter the down state from some other state (but not from the notPresent state). This other
state is indicated by the included value of ifOperStatus.
Profile Description
Severities Major
Raise Notification linkDown
Clear Notification linkUp
Triggers • linkDownTrigger
• linkUpTrigger
Note:
This model is only valid for interfaces with type (iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.
ifEntry.ifType) EthernetCsmacd.
3.15.1 Network Interface Down - Notification

This notification is sent if the administrative status of the interface is up but the operational status changes from Up to Down. It
is also sent if, with both administrative and operational status' are Down, the administrative status changes from Down to Up

MIB IF-MIB
Trap Name linkDown
Trap OID 1.3.6.1.6.3.1.1.5.3

ifIndex 1.3.6.1.2.1.2.2.1.1
ifAdminStatus 1.3.6.1.2.1.2.2.1.7
ifOperStatus 1.3.6.1.2.1.2.2.1.8
ifDescr 1.3.6.1.2.1.2.2.1.2

05-00262 C07
PTS Alarms
Alarm Model 14: Network Interface Down

svInterfacesIfOperStatusUpAndStable 1.3.6.1.4.1.11610.435.15747.1.2.2.1.33
Profile Description
Frequency 8 seconds
Severity Major
Condition (svOperStatusUpAndStable == 2(false)) && (IF-MIB::ifAdminStatus == 1(up))
If a physical interface is down, for example, a cable is removed from an interface. The alarm displays the name of the physical
interface from where the cable is removed.
3.15.2 Network Interface Down - Clear

The clear notification is sent when the interface's ifOperStatus changes from Down to Up, while ifAdminStatus is Up, or when
ifAdminStatus changes from Up to Down while ifOperStatus is Down.

MIB IF-MIB
Trap Name linkUp
Trap OID 1.3.6.1.6.3.1.1.5.4

ifIndex 1.3.6.1.2.1.2.2.1.1
ifAdminStatus 1.3.6.1.2.1.2.2.1.7
ifOperStatus 1.3.6.1.2.1.2.2.1.8
ifDescr 1.3.6.1.2.1.2.2.1.2
svInterfacesIfOperStatusUpAndStable 1.3.6.1.4.1.11610.435.15747.1.2.2.1.33
Profile Description
Frequency 8 seconds
Severity Cleared
Condition (svOperStatusUpAndStable == 1(true)) || (IF-MIB::ifAdminStatus == 2(down))
3.15.3 Network Interface Down - Major Alarms

This alarm indicates that the administrative status of the interface is up but the operational status is down.

05-00262 C07
PTS Alarms
3.15.4 Impact and Suggested Resolutions for Alarm Model 14

This alarm can impact subscriber traffic if the affected interfaces are used for the intersection of traffic or clustering elements:
1. Run the show interface configuration <interface> CLI command to verify that the interface is administratively
enabled, but Down.
2. Run the set config interface <interface> enabled <true|false> CLI command to disable the port if the
interface is not for use under normal operation.
3. If the interface is a form-factor pluggable module, such as SFP+ or XFP, run the show interface modules <interface>
CLI command to inspect the status of the module and the link.
4. Ensure that the cables are properly seated on the element and on the switch/router.
5. Run the show log command to inspect the system logs for possible failures, errors, or warnings against the specific interface
which is showing as "down".
6. If Alarm Model 16 is also raised, see the associated Impact and Suggested Resolutions section for further analysis.
3.16 Alarm Model 15: Unavailable Processing

Module
This alarm is raised to indicate a problem with the operational status of the packet processing Load Balancer.
Note:
Alarm Model 15 (Unavailable Processing Module) is not supported on the PTS Linux platform.
Profile Description
Severities Warning, Minor, Major
Raise Notification svLBOperStatusDownNotification
Clear Notification svLBOperStatusUpNotification
Triggers • lbcStatusOperationDegraded
• lbcStatusTrigger
Unique Instance Identifier svLoadBalancerStatsOperStatus
3.16.1 Load Balancer Down - Notification

This notification is sent whenever a load balancer OperStatus is down. This typically indicates that one of the modules to which
it is forwarding data is no longer available.

MIB SANDVINE-MIB
Trap Name svLBOperStatusDownNotification

05-00262 C07
PTS Alarms

Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.1

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svLoadBalancerStatsOperStatus 1.3.6.1.4.1.11610.435.8377.1.3.3
3.16.1.1 Load Balancer is Degraded

This notification is sent if load balancer operational status is degraded (value=3).
Profile Description
Severity Minor
Condition SANDVINE-MIB::svLoadBalancerStatsOperStatus == 3 (degraded)
3.16.1.2 Load Balancer is Down

This notification is sent if the load balancer operational status down (value=2).
Profile Description
Severity Major
Condition SANDVINE-MIB::svLoadBalancerStatsOperStatus == 2 (down)
3.16.2 Load Balancer Down - Clear

This notification is sent if the load balancer OperStatus is Up. This occurs if all of the processing modules, to which it is forwarding
data, are available.

MIB SANDVINE-MIB
Trap Name svLBOperStatusUpNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.2

svSeverity 1.3.6.1.4.1.11610.6799.1.10

05-00262 C07
PTS Alarms

svLoadBalancerStatsOperStatus 1.3.6.1.4.1.11610.435.8377.1.3.3
3.16.2.1 Load Balancer is Operational

This notification is sent when the load balancer operational status is up (value=1).
Profile Description
Severity Cleared
Condition SANDVINE-MIB::svLoadBalancerStatsOperStatus == 1 (up)
3.16.3 Load balancer down - minor alarms

This notification indicates one or more modules in a PTS cluster are not up. When a module exits the up state, all traffic assigned
to the module is shunted. If the module does not reenter the up state after five minutes, all of the traffic assigned to the modules
is rebalanced to other modules.
Run the show service load-balancer modules CLI command to view the status of the modules. Run the show interface
rate modules CLI command to see if a module is processing traffic.

During the shunting interval, traffic assigned to the failed module is not inspected. In general, this alarm indicates:
• Certain processes are not online.
• There are communication issues in the PTS cluster.
• Modules are overloaded due to traffic inspection.
To narrow down the root causes of the problem:
a. Run the show system services CLI command to verify that the services are online.
b. Run the show system modules and show system resources CLI commands to verify that the PTSD, SFCD,
and SCDPD processes are online and resources are available:
c. Run the show interface configuration [interface] CLI command to verify that there are no interface down
alarms for cluster ports.
d. Run the CLI> ping <port Ip> CLI command to verify communication between ports in a PTS cluster.
The IP you want to ping depends on the cluster compatibility mode. The show interface network command
displays the ExternalService and InternalService IPs.
Note:
If the PTS is configured with cluster compatibility version 1, then ping the ExternalService IP. If it is configured
with cluster compatibility version 2, then ping the InternalService IP.
e. Validate that no single module receives heavy traffic:

show interface rate module
show interface rate module

05-00262 C07
PTS Alarms
• Run the show interface rate module CLI command.

• Run the show interface load-balancer modules CLI command to check any downed instances:
• Run the PTS> show interface counters data CLI command, on the respective PTS, to check any dropped
packets on the connected interfaces.
f. Run the show interface spanning-tree vlans CLI command to verify that the same set of VLANs and MSTP
instances are used in the PTS cluster.
g. Run the show service load-balancer master CLI command to determine the master load balancer. Then run
the show service load-balancer modules detail command on the master load balancer to verify that no
modules are overloaded. See the PTS Administration Guide for additional information.
3.16.4 Load balancer down - major alarms

This notification indicates that there are no modules available to inspect traffic. Previously discovered modules that are not up
are not used to inspect traffic. To view module states in a cluster, use the show service load-balancer modules CLI
command.

If this alarm occurs, all traffic that is intersecting with the PTS is not inspected.
In general, this alarm may indicate:
• Certain processes are not online.
• There are communication issues in the PTS cluster.
• Modules are overloaded due to traffic inspection.
To narrow down the root causes of the problem:

a. Verify that modules are not administratively been brought down. Use the show system modules CLI command.
b. Verify that the PTSD, SFCD, and SCDPD processes are online and resources are available:
show system modules

show system resources
c. Verify that no interfaces connecting the cluster (interfaces with function [cluster]) are down. Use the show interface
configuration [interface] CLI command.
d. Verify communication between SERVICE ports in a PTS cluster: PTS> ping <SERVICE port Ip>
e. Verify that the same set of VLANs and MSTP instances are used in the PTS cluster: show interface
spanning-tree vlans
f. Verify that no modules are overloaded, run this CLI command show service load-balancer master and then
show service load-balancer modules. For more information, see the PTS Administration Guide.

05-00262 C07
PTS Alarms
Alarm Model 17: Degraded Cluster
3.16.5 Load balancer down - warning alarms

This notification is sent to indicate one or more modules in a PTS cluster cannot be brought up because another PTS is running
a version of the firmware that cannot address those modules if they are up.This warning persists until all modules on the cluster
are addressable by all PTS elements. To view module states in a cluster, run the show service load-balancer modules
CLI command.

This alarm indicates clusters with mixed firmware versions. This typically occurs during rolling firmware upgrades, when PTS
elements with different firmware versions are found on the same cluster.
Ensuring that all PTS elements in a cluster are running the same firmware version ensures that all elements are addressable
from modules that support the new firmware.
This alarm can now be raised because of an incompatible configuration:
• Layer2 mode
• Hash Mode
• LoadBalancing Mode
• Ipv4 Window
• Ipv6 Window
See the show service load-balancer cluster compatibility command for a summary of the cluster's configuration
and whether it is compatible.
3.17 Alarm Model 17: Degraded Cluster

This alarm is raised when the Sandvine Cluster Discovery Protocol (SCDP) encounters a receive or transmit error. Possible
causes of this alarm include:
• Incompatible software versions between cluster elements.
• Multi-cast routing not configured properly on switch/router connecting PTS cluster elements.
• Clustering services are not running.
Note:
Alarm Model 17 (Degraded Cluster) is not supported on the PTS Linux platform.
Profile Description
Severities Warning, Clear
Raise Notification svClusterSCDPErrorNotification
Clear Notification svClusterSCDPNoErrorNotification
Triggers scdpClusterCommunication
Unique Instance Identifier svScdpStatsSent
3.17.1 Degraded Cluster - Warning

This notification is sent if the sum of send errors and received errors exceeds 10, within an interval of 1 hour (3600 seconds).

05-00262 C07
PTS Alarms
Alarm Model 17: Degraded Cluster
Profile Description
Severity Warning
Condition DELTA (SANDVINE-MIB::svScdpStatsSendErrors + SANDVINE-MIB::svScdpStatsReceiveErrors)
> 10

MIB SANDVINE-MIB
Trap Name svClusterSCDPErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.5.0.1

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svScdpStatsSent 1.3.6.1.4.1.11610.435.4550.1.3.1
svScdpStatsReceived 1.3.6.1.4.1.11610.435.4550.1.3.2
svScdpStatsReceiveErrors 1.3.6.1.4.1.11610.435.4550.1.3.4
svScdpStatsSendErrors 1.3.6.1.4.1.11610.435.4550.1.3.5
3.17.2 Degraded Cluster -Clear

This notification is sent when SCDPD has not encountered any receive or transmit errors for at least one hour, after previously
having encountered an error.

MIB SANDVINE-MIB
Trap Name svClusterSCDPNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.5.0.2

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svScdpStatsSent 1.3.6.1.4.1.11610.435.4550.1.3.1
svScdpStatsReceived 1.3.6.1.4.1.11610.435.4550.1.3.2
svScdpStatsReceiveErrors 1.3.6.1.4.1.11610.435.4550.1.3.4
svScdpStatsSendErrors 1.3.6.1.4.1.11610.435.4550.1.3.5

05-00262 C07
PTS Alarms
Alarm Model 18: Disconnected SPB
This alarm is cleared when sum of send errors and received errors equates to 0 within an interval of 1 hour (3600 seconds).
Profile Description
Severity Cleared
Condition DELTA (SANDVINE-MIB::svScdpStatsSendErrors + SANDVINE-MIB::svScdpStatsReceiveErrors)
== 0

Some traffic may be shunted or dropped. Gaps or unknown/other traffic may show up in reports. Policy functions may not work
as expected. There may be subscriber service interruptions:
Suggested resolution steps:
1. Confirm each node is running the same version of svscdp from the command line pkg_info on all cluster elements, or use
the CLI command show system version detail.
2. Verify multi-cast configuration on the switch/router.
3. Verify that the element is communicating with all other cluster elements, using the CLI command: show service
cluster-discovery elements.
This list shows the state of all successfully communicating units in the virtual cluster as [connected]. This list does not show
the local element, but if this table is empty, in a cluster greater than one, then this unit is not communicating with any other
element.
4. Verify the SCDP multicast/broadcast address using the CLI command: show service cluster-discovery config
Note the MCastAddrRun/BroadCast address. Run tcpdump on the PTS and confirm that PTS is seeing 239.0.1.0
multi-cast traffic, if it is using default.
5. Confirm that scdpd is running.

This can be done by attempting to run show system services; although scdpd is not running on the controller, the CLI
command fails.
6. Restart scdpd by executing /usr/local/etc/rc.d/svscdpd.sh restart. Check /var/log/svlog and /var/log/scdpd.log

for errors.
3.18 Alarm Model 18: Disconnected SPB

This alarm is raised when connections to one or more SPBs are lost. The statistics database handles all outbound statistics
logging, subscriber-based communication, and all incoming SPB notifications.
Profile Description
• Minor
• Clear

05-00262 C07
PTS Alarms
Profile Description
Raise Notification svSpbDisconnectedNotification
Clear Notification svSpbConnectedNotification
Unique Instance Identifier N/A
3.18.1 Disconnected SPB - Major

This notification is sent when the connection to one or more SPBs is either offline or the connection is unusable due to an error
in exchanging capability information with the SPBs. This may result in discarded statistics and degraded subscriber awareness.

MIB SANDVINE-MIB
Trap Name svSpbDisconnectedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.3.0.3

svDatabaseStatsDisconnectedSPB 1.3.6.1.4.1.11610.435.7192.1.3.11
svDatabaseStatsDisabledSPB 1.3.6.1.4.1.11610.435.7192.1.3.12
svDatabaseCapabilityExchangeError 1.3.6.1.4.1.11610.435.7192.1.30.2
svFaultDetectorStatsFaultDetectorNodeRole 1.3.6.1.4.1.11610.435.21254.1.3.101.1
Where:
• svDatabaseStatsDisconnectedSPB—The number of connections to the SPBs that have operational status as not connected.
• svDatabaseStatsDisabledSPB—The number of connections to the SPBs that are disabled administratively.
• svDatabaseCapabilityExchangeError—Capabilities exchange did not occur. This indicates a database interaction problem,
which can occur if the database is unavailable, configured incorrectly, or the exchange has timed out.
• svFaultDetectorStatsFaultDetectorNodeRole—Whether the SDE is the active node or the passive node. This varbind is for
SDE only. Possible values of the varbind are:
• 1—The node role is unknown.
• 2—The node role is active.
• 3—The node role is passive.
Profile Description
Severity Major
Condition (svDatabaseStatsDisconnectedSPB greater than 0 and svDatabaseStatsDisconnectedSPB greater
than svDatabaseStatsDisabledSPB) or (svDatabaseCapabilityExchangeError is equal to true (1))
3.18.2 Disabled SPB - Minor

This notification is sent when the connections to one or more SPBs are disabled administratively, and the rest of connections
which are enabled administratively (if any) are in connected state.

05-00262 C07
PTS Alarms

MIB SANDVINE-MIB
Trap Name svSpbDisconnectedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.3.0.3

Profile Description
Severity Minor
Condition svDatabaseStatsDisabledSPB greater than 0 and svDatabaseStatsDisconnectedSPB equal to
svDatabaseStatsDisconnectedSPB
3.18.3 Disconnected SPB -Clear

This notification is sent when the connection to an external SPB is re-established. The connection to all the configured SPBs is
online and capability information is successfully exchanged.
Note:
When you run the service sde restart command on the SDE, the output of the show alarms history CLI
command includes this notification. This is a known behavior and no action is required.

MIB SANDVINE-MIB
Trap Name svSpbConnectedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.3.0.4

Profile Description
Severity Clear
Condition (svDatabaseStatsDisconnectedSPB = 0 and svDatabaseStatsDisabledSPB = 0 and
svDatabaseCapabilityExchangeError = false(2))

05-00262 C07
PTS Alarms
Alarm Model 19: Invalid Software License
3.18.4 Impact and Suggested Resolution: Alarm Model 18

The potential impact of Alarm Model 18:
• Loss of statistics records.
• Suppression of subscriber lookups. New subscribers are not accounted for until the connection is re-established (PTS only).
• SPB notifications (such as subscriber login, log out, and attribute change notifications) do not reach the PTS/SDE.
• The PTS/SDE and SPB cannot exchange capabilities or the PTS/SDE cannot use the exchanged capabilities.
3.18.4.1 Possible Resolutions for Alarm Model 18

Run these CLI commands to verify the connections/configurations:
• Run the show service spb connections CLI command to verify your connections.
• Run the show service spb capabilities-exchange CLI command to verify that all the capabilities used are either
configured or negotiated.
If the connections do not have their OperStatus in the [connected] state, then it can be related to one of these issues:
Issue Resolution
Network outage, routing issue, or client process Run the show service spb connections CLI command
on the PTS/SDE to check for network outages or routing issues,
and resolve them if they exist.
Middleware services not functioning on the SPB Run the show service message-broker status CLI
command on the SPB to verify that middleware services are
functioning on the SPB. See the SPB Administration Guide for
troubleshooting instructions.
Firewall misconfiguration If a firewall or packet filter exists between the PTS (or SDE)
and SPB, confirm that there are rules in place to allow for TCP
connections on port 2507 from the PTS (or SDE) to the SPB.
3.19 Alarm Model 19: Invalid Software License

The element sends out the warning alarm notification, if a module license is about to expire or is currently invalid. A critical alarm
occurs if the license is currently invalid. A major alarm occurs if the license expires within 30 days, a minor alarm occurs if the
license expires within 60 days, and warning alarm occurs if the license expires within 90 days.
Profile Description
Severities Critical, Major, Minor, and Warning
Raise Notification svSysLicenseExpiredNotification
Clear Notification svSysLicenseValidNotification
Triggers licenseStateTrigger
Unique Instance Identifier svLicenseName

MIB SANDVINE-MIB
Trap Name svSysLicenseExpiredNotification

05-00262 C07
PTS Alarms

Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.9

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svLicenseName 1.3.6.1.4.1.11610.435.7534.1.10.1.2
svLicenseStartDate 1.3.6.1.4.1.11610.435.7534.1.10.1.6
svLicenseExpirationDate 1.3.6.1.4.1.11610.435.7534.1.10.1.7
svLicenseDaysToExpiry 1.3.6.1.4.1.11610.435.7534.1.10.1.8
The license states are:

• 1—Invalid
• 2—Expired
• 3—Valid
3.19.1 Invalid Software License—Critical

This notification is sent if that module's license state is not valid (3), that is either invalid (1) or expired (2).
Profile Description
Severity Critical
Condition SANDVINE-MIB::svLicenseState != 3 (valid)
3.19.2 Expiring Software License—Major

This notification is sent if the number of days for that module's license to expire is less than or equal to 30 days and license state
is valid (3). That is, the alarm is raised when the license is valid for less than or equal to 30 days.
Profile Description
Severity Major
Condition (SANDVINE-MIB::svLicenseDaysToExpiry <= 30 (days)) && (SANDVINE-MIB::svLicenseState
== 3 (valid))

05-00262 C07
PTS Alarms
3.19.3 Expiring Software License—Minor

This notification is sent if the number of days before the module's license expires is less than or equal to 60 days but greater
than 30 days and license state is valid (3). In other words, the alarm is raised when a license is valid for more than 30 days, but
less than or equal to 60 days.
Profile Description
Severity Minor
Condition (SANDVINE-MIB::svLicenseDaysToExpiry <=60 (days)) && (SANDVINE-MIB::svLicens
eDaysToExpiry >> 30 (days)) && (SANDVINE-MIB::svLicenseState == 3 (valid))
3.19.4 Expiring Software License—Warning

This notification is sent if the number of days before the module's license expires is less than or equal to 90 days but greater
than 60 days and the license state is valid. In other words, the alarm is raised when a license is valid for more than 60 days, but
less than or equal to 90 days.
Profile Description
Severity Warning
Condition (SANDVINE-MIB::svLicenseDaysToExpiry <=90 (days)) && SANDVINE-MIB::svLicenseD
aysToExpiry >> 60 (days)) && (SANDVINE-MIB::svLicenseState == 3 (valid))
3.19.5 Invalid Software License—Clear

This notification is sent if a module license that was previously invalid or about to expire is now valid.

MIB SANDVINE-MIB
Trap Name svSysLicenseValidNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.10

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svLicenseName 1.3.6.1.4.1.11610.435.7534.1.10.1.2
svLicenseStartDate 1.3.6.1.4.1.11610.435.7534.1.10.1.6
svLicenseExpirationDate 1.3.6.1.4.1.11610.435.7534.1.10.1.7
svLicenseDaysToExpiry 1.3.6.1.4.1.11610.435.7534.1.10.1.8
05-00262 C07
PTS Alarms
This alarm is cleared when days to expiry for that module's license is greater than 90 days and the license state is valid (3).
Profile Description
Severity Cleared
Condition (SANDVINE-MIB::svLicenseDaysToExpiry > 90 (days)) && (SANDVINE-MIB::svLicenseState ==
3 (valid))

An alarm is raised if the licenses are invalid, about to expire, already expired, or if the element uses a cached copy of a license.
Note that:
• When the license expires, the element continues to function normally. It does not take any action until it is restarted or reloaded.
For example, the PTS daemon continues to inspect packets and function normally until it is restarted or reloaded. At that time
it detects that the license is invalid and stops inspecting packets.
• If a new set of licenses is available for the license server, the element detects it only when it is restarted or reloaded.
The suggested resolutions for alarm model 19 are:
• If the alarm is not critical, run the show system licenses CLI command to identify the licenses that will expire, and contact
the Sandvine Account Team to renew the licenses.
• If the alarm is critical and you do not use a license server, and the license is either expired or missing on the element, then
run the show system licenses CLI command to identify the license that has the Valid column set to false. Contact
Sandvine Customer Support or its authorized partner for further assistance.
• If the license is of type [network] with the Valid column set to false, then the license was lost, most likely due to a
communication error with the license server. In this case, confirm that you have not started more elements than the network
license allows. If you have, shut down one to let the element receive the license.
• If the license is of type [unknown], it means that during a reload or restart of the element, the license is lost. Confirm that
the license server is operational and that the element can connect to the license server. If it does, confirm that you have not
started more elements than the network license allows. If you have, shut down one to let the element receive the license or
consider acquiring additional licenses by contacting your Sandvine Account Team.
• If the license type is [cache], then run the show system licenses CLI command to identify the license that has the
Valid column set to false. Contact Sandvine Customer Support or its authorized partner for further assistance.
• Run the show config service license-server CLI command to determine the connected license server.
An output similar to this appears displaying the connected license servers based on your configuration:
primary
host: licenseserver1
port: 6200
first-redundant
port: 6200
second-redundant
port: 6200
The alarms, triggers, and events associated with licenses are defined in these files:
/usr/local/sandvine/etc/alarms/license.alarm.conf
/usr/local/sandvine/etc/events/events.license.conf
05-00262 C07
PTS Alarms
Alarm Model 20: Overloaded Cluster
3.20 Alarm Model 20: Overloaded Cluster

This alarm is raised if all modules on a PTS cluster have exceeded their designed maximum target load threshold or the
cost space is insufficient.
Note:
Cost Space is the maximum cost limit that is assigned to a PTSD instance when load balancer is configured to balance
by “cost” . This value is specified in the load-balancing policy or set by the respective policy package.
A single, multi-module PTS is considered a cluster, and if all the modules on the PTS element exceed the target load
threshold, this can trigger the major alarm. The default value of the target load threshold is 90%.
If cost space is insufficient for all the modules, this can trigger the minor alarm. The alarm is cleared when one module is below
the target load threshold and one module has sufficient cost space.
Note:
Alarm Model 20 (Overloaded Cluster) is not supported on the PTS Linux platform.
Profile Description
Severities Major, Minor, Clear
Raise Notification svLBClusterOverloadNotification
Clear Notification svLBClusterOverloadClearNotification
Triggers clusterOverloadTrigger
Unique Instance Identifier none – applies to the entire PTS
3.20.1 Overloaded Cluster - Major

MIB SANDVINE-MIB
Trap Name svLBClusterOverloadNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.3

svSeverity 1.3.6.1.4.1.11610.6799.1.10
3.20.2 Overloaded Cluster - Minor

MIB SANDVINE-MIB
Trap Name svLBClusterOverloadNotification
05-00262 C07
PTS Alarms
Alarm Model 20: Overloaded Cluster

Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.3

svSeverity 1.3.6.1.4.1.11610.6799.1.10
3.20.3 Overloaded Cluster - Clear

This notification is sent when one module is below the target load threshold and one module has sufficient cost space,
which implies that the cluster is no longer overloaded.

MIB SANDVINE-MIB
Trap Name svLBClusterOverloadClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.4

svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Frequency 8 seconds
Severity Clear
Condition At least one module is below the target load threshold and one module has sufficient cost
space.

If this alarm occurs, all the modules have a significant load in trying to inspect the traffic delivered to them. The size of the cluster
is underrated for the traffic that is inspected.
While this alarm is active, new IP traffic discovered by the load balancer is shunted (not inspected). Run the show service
load-balancer modules detail CLI command to identify the maximum load threshold. If the load of a module exceeds a
maximum load threshold (default setting is 95%), some of the traffic on the module is rebalanced to bring its load below the target
load threshold. While this alarm is active, the rebalanced traffic is shunted. Note that in both cases the shunting is temporary and
IPs are discovered after a timeout period. If the alarm persists then the load balancer will perpetually be discovering and shunting
the same set of IPs.
If the amount of traffic that the cluster is receiving can be reduced, then it would be the best option. Review the load of the modules
using show service load-balancer modules. If more PTS elements are added to the cluster, you can force a rebalance
across the cluster using clear service load-balancer.
05-00262 C07
PTS Alarms
Alarm Model 21: Overloaded Subcluster
This alarm may also be triggered if there are communications problems on the cluster links. If this alarm is seen in combination
with high Rx, Tx cluster link, or cluster link interface drop alarms, this indicates that there is insufficient cluster network capacity
for the given network load. If the drops become excessive the system starts placing modules into temporary shunt to help alleviate
the network congestion. In this case, the resolution is to reduce the data intercept traffic for the cluster or to increase the number
of cluster links.
Troubleshooting Cost Space Configuration
When configured to load-balance by cost, run the show service load-balancer modules detail CLI command from
the CLI operational mode for troubleshooting cost space configuration. The AssignedCost % column shows the cost assigned
per module. If the AssignedCost % is greater than 90 % for any module, a minor alarm is triggered.
3.21 Alarm Model 21: Overloaded Subcluster

This alarm indicates that load balancer discovered new traffic, but could not assign it to a module in the subcluster where the
traffic was discovered. It is sent when all modules in a subcluster are down, or have exceeded their target load threshold.
All modules in a subcluster have module loads that exceed a target load threshold. The default value for the target load
threshold setting is 90%.
If there is another subcluster with modules below the target load threshold, then the traffic is assigned to one of its subclusters.
Alarm Model 20 (Overloaded Cluster) is triggered whenever a subcluster is unavailable
Note:
Alarm Model 21 (Overloaded Subcluster) is not supported on the PTS Linux platform.
Profile Description
Severities Major, Clear
Raise Notification svLBSubClusterOverloadNotification
Clear Notification svLBSubClusterOverloadClearNotification
Triggers • SubclusterModuleOverload
• SubclusterOverloadClear
Unique Instance Identifier svLoadBalancerAssignmentSubClusterOverloaded
3.21.1 Overloaded Subcluster - Major

This notification is sent if the load balancer indicates that the locality of a subcluster is violated, which implies that the subcluster
is overloaded.

MIB SANDVINE-MIB
Trap Name svLBSubClusterOverloadNotification
Trap OID .3.6.1.4.1.11610.6799.3.6.0.5

05-00262 C07
PTS Alarms
Alarm Model 21: Overloaded Subcluster

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svLoadBalancerAssignmentSubClusterOverloaded 1.3.6.1.4.1.11610.435.8377.1.3.14.14
Profile Description
Frequency 8 seconds
Severity Major
Condition SANDVINE-MIB::svLoadBalancerAssignmentLocalityViolated == 1 (true)
3.21.2 Overloaded Subcluster - Clear

This notification is sent when one module is below the target load threshold and one module has sufficient cost space,
which implies that the cluster is no longer overloaded.

MIB SANDVINE-MIB
Trap Name svLBClusterOverloadClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.4

svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Frequency 8 seconds
Severity Clear
Condition At least one module is below the target load threshold and one module has sufficient cost
space.

The system assigns IP bundles to another subcluster in order to compensate. Traffic that is re-balanced while the box is in this
state is not identified.
To view all the modules in a subcluster, run these CLI commands:
show service load-balancer modules
show service load-balancer stats
05-00262 C07
PTS Alarms
Alarm Model 22: Misconfigured Network Awareness
3.22 Alarm Model 22: Misconfigured Network

Awareness
This alarm is raised if the number of external-netclass addresses seen on a subscriber interface within 5 minutes, has exceeded
the rising threshold. See Alarm Model 77: Misconfigured Network Interface on page 189 for additional information.
Profile Description
Severities Minor, Clear
Raise Notification svIfExternalAddressesOnSubscriberInterfaceNotification
Clear Notification svIfExternalAddressesOnSubscriberInterfaceClearedNotification
Triggers extrenalAddrsOnInternalPorts
3.22.1 Misconfigured Network Awareness Alarm

This alarm is raised if the PTS detects more than 15% of the total packets in either of these conditions:
• A packet arrives on a subscriber-facing interface containing an external source IP address, or
• Both client and server have non-zero packet count.
A non-zero count in this field can be due to these reasons:
• All the internal subnets are not defined in the subnets.txt file.
• Bridge-group configuration has changed, which affects where the data intersect cables are connected.
3.22.2 Misconfigured Network Awareness- Minor

This notification is sent if the sampled percentage of external addresses seen on internal ports during a 5-minute interval has
increased to 15% or more.
Profile Description
Severity Minor
Condition delta(svPortTopologyStatsExternalAddressesOnInternalPorts) * 100 / delta(svPortTopologyStats
CheckedExternalAddressesOnInternalPorts) >= 15

MIB SANDVINE-MIB
Trap Name svIfExternalAddressesOnSubscriberInterfaceNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.9

05-00262 C07
PTS Alarms
Alarm Model 22: Misconfigured Network Awareness

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPortTopologyStatsExternalAddressesOnInternalPorts 1.3.6.1.4.1.11610.435.10470.1.3.1
svPortTopologyStatsCheckedExternalAddressesOnInternalPorts 1.3.6.1.4.1.11610.435.10470.1.3.201
svPortTopologyDebugProcessedMissingSubnetList 1.3.6.1.4.1.11610.435.10470.1.9.3
3.22.3 Misconfigured Network Awareness - Clear

This notification is sent when the sampled percentage of external addresses seen on internal ports during a 5-minute interval
has fallen below 7%.

MIB SANDVINE-MIB
Trap Name svIfExternalAddressesOnSubscriberInterfaceClearedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.10

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPortTopologyStatsExternalAddressesOnInternalPorts 1.3.6.1.4.1.11610.435.10470.1.3.1
svPortTopologyStatsCheckedExternalAddressesOnInternalPorts 1.3.6.1.4.1.11610.435.10470.1.3.201
Profile Description
Severity Cleared
Condition delta(svPortTopologyStatsExternalAddressesOnInternalPorts) * 100 / delta(svPortTopologyStats
CheckedExternalAddressesOnInternalPorts) < 7

Interface functions may not be operating correctly, as the traffic may not be correctly classified. Any subscriber-specific policy
rules may not be properly applied and reporting (especially subnet-based and subscriber-based) may not be accurate. Traffic in
the external subnets seen on subscriber interfaces may not be managed as expected, or at all, by the configured policy.
1. Ensure that all PTS ports are wired correctly.
2. Inspect the missing subnets list using the show interface ip-address-tracking CLI command.
• If this accurately describes a subscriber subnet, then this value should be added to subnets.txt under the internal
cost class (See the SandScript Configuration Guide, for more information on configuring the subnets.txt file. ).
05-00262 C07
PTS Alarms
Alarm Model 23: Runtime SandScript Errors
• If the missing subnets list is either too specific, or not specific enough, it is likely that for your network, the network size
used for aggregation needs adjustment. This value represents the subnet prefix that should be used while populating
IPs into a CIDR list.
3. Verify that the interface functions have been correctly defined using the show interface configuration CLI command.
An Internet-facing port falsely configured as a subscriber-facing port could trigger this alarm.
4. If the subnets.txt has been modified, perform an svreload.
3.22.4.1 Adjusting Network Aggregation

You may need to adjust the number of top-level bits used for subnets.
1. Set the network size to the number of top-level bits used for subnets on your subscriber networks.
For example, for IPv6, set the network mask width to 48 with the command:
PTS# set config interface address-tracking network-mask width ipv6 48
Or, for IPv4, set the network mask width to 48 with the command:
PTS# set config interface address-tracking network-mask width ipv4 20
2. Perform an svreload.
3. To inspect the missing subnets list, run the show interface ip-address-tracking CLI command. Check that it now
accurately describes a subscriber subnet.
4. If the subscriber subnet is now accurately described, add to subnets.txt.
3.22.4.2 Additional Information

These files define the alarms, triggers, and events for this alarm:
• /usr/local/sandvine/etc/alarms/interfaces.alarm.conf
• /usr/local/sandvine/etc/events/events.ptsm.conf
3.23 Alarm Model 23: Runtime SandScript Errors

This alarm is raised when SandScript errors are detected as shown in the SandScript error table.
Profile Description
• Minor
• Warning
• Clear
Raise Notification svPolicyRuntimeErrorNotification
ClearNotification svPolicyNoRuntimeErrorNotification
Triggers • policyErrorMajor
• policyErrorMinor
05-00262 C07
PTS Alarms
Profile Description
Unique Instance Identifier svPolicyErrorsPolicyErrorCount
3.23.1 Runtime SandScript Errors

An alarm is raised for one of the SandScript policy error instances, if the counter increments. The alarm is cleared only if the
counter is not incremented for 1 hour or more. The actual time to clear the alarm ranges between 1 to 2 hours. The condition
whereby each alarm counter is raised is different for each instance.
Instance Name Possible Cause

Analyze "dpm" action issued on ReadOnly flow The analyze "dpm" action is not issued on every SandScript
call on a flow, causing the flow to drop to read-only mode.
Demographic stats flow skipped interval A flow was not visited in a stats-publishing interval, so the flow's
demographic statistics for that interval is reported in the
subsequent interval.
Enumerated classifier assigned an invalid value An enumerated classifier is assigned with an invalid value.
Expression stats max columns exceeded A published expression stat exceeds a field, column, or
classification limit.
Http_response actions issued on ReadOnly flow A read-only flow is actioned with http_response in the
SandScript.
Http_response action issued with a null payload expression A http_response action is issued with a payload string that
evaluated to NULL in the SandScript.
Max Measurements Per Flow Exceeded Flows are measured up to four connections with four bitrate
measurements at a time. When SandScript exceeds this limit,
an alarm is triggered.
Maximum shapers per flow has been exceeded Up to six shapers any given time can shape flows, and an alarm
is triggered when SandScript exceeds this limit.
Maximum ports per SMTP host have been exceeded Each Simple Mail Transfer Protocol (SMTP) host is monitored
to detect spammers and this detection is done on a per-port
basis. The maximum number of ports monitored per host is
configurable using the rc.conf variable
spam_max_ports_per_smtp_host. An alarm is triggered
when this limit is exceeded.
Max tee destinations per flow exceeded One or more flows are not tee-d to all desired destinations
because the maximum number of tee destinations was
exceeded.
Measurement memory allocation failure A measurement with a new unique-by key was not allocated
due to lack of available memory.
Overloaded, IP shunting A burst of traffic that exceeds the packet processing and
inspection rate; the PTS applies SandScript.
Overloaded, UDP shunting A burst of UDP traffic that exceeds the rate that UDP packet
processing and inspection rate; the PTS applies SandScript.
Stat was not written to the SPB due to an error During statistics integration, a condition prevents adding a
statistic to the database. Counters in PDB provide further
05-00262 C07
PTS Alarms
Instance Name Possible Cause

information as to why this alarm is raised. They are under
devices/statsIntegration/1/stats. Currently only
histogramDefinitionNotPresent raises this alarm. This
means that the bin definition for a histogram stat did not arrive.
Infinite loop detected The current policy includes a foreach that can end up looping
infinitely. An Inifinite loop detection triggers when used with a
Range, when the Range's:
• start > ends with a positive step.
• end > starts with negative step.
• Step is zero.
DNS Modification of read only flow A DNS packet modification is issued on a read-only flow.
DNS modification of fragmented packets A DNS modification is issued on a fragmented DNS packet.
DNS modification of TCP stream A DNS modification was issued on a DNS flow that uses TCP.
3.23.2 Runtime SandScript Errors - Major

MIB MIB - SANDVINE-MIB
Trap Name svPolicyRuntimeErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.1

SNMPv2-MIB::sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPolicyErrorsPolicyErrorName 1.3.6.1.4.1.11610.435.8083.1.3.2.10.1.2
svPolicyErrorsPolicyErrorCount 1.3.6.1.4.1.11610.435.8083.1.3.2.10.1.3
This notification is sent if the SandScript error count exceeds 1 within an interval of 1 hour (3600 seconds).
Profile Description
Severity Major
Condition DELTA(SANDVINE-MIB::svPolicyErrorsPolicyErrorCount) && SANDVINE-MIB::svPolicyEr
rorsPolicyErrorSeverity == 4
3.23.3 Runtime Sandscript Errors - Minor

This notification is sent if runtime sandscript error count exceeds 1 within an interval of 3600 seconds.
05-00262 C07
PTS Alarms

MIB MIB - SANDVINE-MIB
Trap Name svPolicyRuntimeErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.1

svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Severity Minor
Condition DELTA(SANDVINE-MIB::svPolicyErrorsPolicyErrorCount) && SANDVINE-MIB::svPolicyEr
rorsPolicyErrorSeverity == 5
3.23.4 Runtime Sandscript Errors - Clear

This notification is sent to indicate a previously detected SandScript error.

MIB SANDVINE-MIB
Trap Name svPolicyNoRuntimeErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.2

svSeverity 1.3.6.1.4.1.11610.6799.1.10
This alarm is cleared when the SandScript error count equals 0 within an interval of 1 hour (3600 seconds).
Profile Description
Severity Cleared
Condition DELTA (SANDVINE-MIB::svPolicyErrorsPolicyErrorCount) == 0
05-00262 C07
PTS Alarms
3.23.5 Runtime SandScript Errors- Possible Instances

The possible SandScript errors are:
Name Applicability
Max Measurements Per Flow Exceeded PTS 5.20.08 and up on 5.2 stream, PTS 5.40.03 and up on
newer streams.
Maximum shapers per flow has been exceeded PTS 5.20.08 and up on 5.2 stream, PTS 5.40.03 and up on
newer streams.
Maximum ports per SMTP host have been exceeded PTS 5.20.08 and up on 5.2 stream, PTS 5.40.03 and up on
newer streams.
Overloaded, IP shunting PTS 5.40.03 and up.
Overloaded, UDP shunting PTS 5.40.03 and up.
Measurement memory allocation failure PTS 5.51 and up.
Demographic stats flow skipped interval PTS 5.51 and up.
Enumerated classifier assigned an invalid value PTS 5.51 and up.
Expression stats max columns exceeded PTS 5.51 and up.
Max tee destinations per flow exceeded PTS 5.51 and up.
Http_response actions issued on ReadOnly flow PTS 5.51 and up.
Stat was not written to the SPB due to an error PTS 5.51.09 and up.
Http_response action issued with a null payload expression PTS 5.51.12 and up.
Analyze "dpm" action issued on ReadOnly flow PTS 5.60.06 and up.
Policy Controller overloaded on ppu PTS 6.10 and up.
Policy Controller degraded on ppu PTS 6.10 and up.
Policy Controller degraded on control processor PTS 6.10 and up.
Infinite loop detected PTS 7.35 and up.
DNS modification of read only flow PTS 7.35 and up.
DNS modification of fragmented packets PTS 7.35 and up.
DNS modification of TCP stream PTS 7.35 and up.
Run the show policy errors CLI command to display errors.
3.23.6 SandScript Errors

These are the possible types of SandScript errors:
3.23.6.1 http_response Action Issued on ReadOnly Flow

Flows are actioned only with the http_response action if it is writeable. A flow is writeable if each SandScript run for that flow
result in a set Flow.Stream.ReadOnly = false action.
05-00262 C07
PTS Alarms
If any SandScript run for a flow does not result in this action, the flow irreversibly becomes read-only and the http_response
action on the flow results in this SandScript error.
To resolve this alarm, edit SandScript such that any flows for which you want http_response action are always previously
actioned with set Flow.Stream.ReadOnly = false.
3.23.6.2 Max Measurements per Flow Exceeded

Up to four connections with four bitrate measurements can measure flows. An alarm occurs when SandScript exceeds this limit.
For example:
measurement "A" connections where true
measurement "B" connections where true
measurement "C" connections where true
measurement "D" connections where true
measurement "E" connections where true
The first four measurements measure flows correctly, while the fifth measurement triggers an alarm.
3.23.6.3 Max Shapers per Flow Exceeded

Up to four shapers can simultaneously shape a flow and an alarm is triggered if SandScript exceeds this limit.
For example:
shaper "A" 100Mbps
shaper "B" 100Mbps
shaper "C" 100Mbps
shaper "D" 100Mbps
shaper "E" 100Mbps
if true then \
shape to client shaper "A" \
shape to client shaper "B" \
shape to client shaper "C" \
shape to client shaper "D" \
shape to client shaper "E"
The first four measurements measure flows correctly, while the fifth triggers an alarm.
3.23.6.4 Max Ports per SMTP Host Exceeded

Each SMTP host is monitored to detect spammers and this detection is done on a per-port basis.
The maximum number of ports that are monitored per host is configurable using the rc.conf variable
spam_max_ports_per_smtp_host. Spammers are detected on any port that detects SMTP traffic before reaching this
maximum limit. If SMTP traffic is detected on any port after this limit is reached, that traffic is not inspected to determine if it is
spam.
05-00262 C07
PTS Alarms
3.23.6.5 PTSM IP Shunting (PTS Only)

If the incoming packet rate exceeds the rate packets that the PTSM processes, then PTSM goes into the IP shunting mode such
that all packets are bridged rather than processed and inspected.
For example, a 64-byte UDP packet at 50% of line rate of interface with the Rx queue triggers shunting.
3.23.6.6 PTSM UDP Shunting (PTS Only)

If the incoming UDP packet rate exceeds the rate packets that the PTSM inspects, then PTSM goes into the UDP shunting mode
such that all UDP packets are bridged rather than inspected.
For example, a 64-byte UDP packet at 25% of line rate of interface with Rx queue triggers shunting.

The impact is different for each instance of this alarm.
Instance name Impact

Max Measurements Per Flow Measurements may not work as expected.
Exceeded
Maximum shapers per flow has been Shapers may not work as expected.
exceeded
Maximum ports per SMTP host have If SMTP traffic is detected on any ports after the limit is reached then that traffic is not
been exceeded inspected to determine spam.
Overloaded, IP shunting The PTS goes into the IP shunting mode where all the packets are bridged instead of
processed. This happens at a packet level- so it does not matter if the packet belongs to
a flow where SandScript is applied. The determination is made that the latency becomes
excessive and the probability of dropping packets goes up if further processing is done.
Thus the packet is not shaped, nor does it have any other SandScript applied to it. It is
not counted in the statistics for the subscriber, any protocol, or classification. For statistical
purposes, it is counted with the protocol set to 'shunted'. When the burst of traffic has
subsided, the system automatically detects when to return to normal processing.
Overloaded, UDP shunting The PTS goes into the UDP shunting mode where all the UDP packets are bridged instead
of processed. This happens at a packet level thus it does not matter if the packet belongs
to a flow that had SandScript applied to it. The determination is made that the latency
becomes excessive and the probability of dropping packets goes up if further processing
is done. Thus the packet is not shaped, nor does it have any other SandScript applied
to it. It is not counted in the statistics for the subscriber, any protocol, or classification.
For statistical purposes, it is counted with the protocol set to 'shunted'. When the burst
of traffic has subsided, the system automatically detects when to return to normal
processing.
Measurement memory allocation Measurements may not work as expected.
failure
Demographic stats flow skipped The demographic statistics of the flow are reported in the incorrect interval.
interval
Enumerated classifier assigned an Classifiers may not work as expected. Some flows may not get classified correctly.
invalid value
05-00262 C07
PTS Alarms
Instance name Impact

Expression stats max columns Not all subscriber measurements that are expected to be reported persist. As a result
exceeded these measurements are not available in the reports.
Max tee destinations per flow Flows are not teed to all destinations.
exceeded
Http_response actions issued on A flow in the SandScript to send an HTTP response is not actioned.
ReadOnly flow
Stat was not written to the SPB due Some statistics data is missing from the SPB.
to an error
Http_response action issued with a A flow in the SandScript to send an HTTP response is not actioned.
null payload expression
Analyze "dpm" action issued on A flow in the SandScript is not analyzed.
ReadOnly flow
Policy Controller overloaded on Messages between the server and client are incomplete due to message size limitations.
module This means that the control system is missing information for some unique 'by instances'
because of one of these reasons:
• Having more unique 'by instances' than recommended in the sizing guidelines.
• Using too many metrics or having too many histogram bins for a metric data definition.
Policy Controller degraded on module The SandScript controllers on a module do not process all related messages. Depending
on how many messages are not processed, this degrades controller functionality and
results in incomplete information for controller processing. This can occur if the module
is under very heavy load.
If this alarm instance is raised, monitor that for some time and consider this as an issue
only if it persists or repeats.
Policy Controller degraded on control The SandScript controller server is unable to process all related messages from the
processor clients. This results in degraded behavior, where the control system actions incomplete
information. This can occur when the controller is under heavy load.
Infinite loop detected The infinite foreach statement is not run.
DNS modification of read only flow The DNS modification is not applied to the flow.
DNS modification of fragmented The DNS modification is not applied to the packet.
packets
DNS modification of TCP stream The DNS modification is not applied to the flow.
The suggested resolutions for each instance of the alarm are:
Instance name Suggested resolutions

Max Measurements Per Flow Adjust the measurements configuration in the SandScript so that the documented
Exceeded maximums are not exceeded.
Maximum shapers per flow has been Adjust shaper policies so the number of shapers in a SandScript do not exceed the
exceeded documented maximum.
Maximum ports per SMTP host have There is a default limit of 5 ports that a mail server can receive SMTP traffic. You can
been exceeded run the set config network-protection max-ports-per-smtp-host CLI
command to change the default value. Before doing this, Sandvine recommends you to
verify that the ports are valid for this email server and are not used for spam or email
05-00262 C07
PTS Alarms

redirection server. If the SMTP traffic is detected on any ports, after the limit is reached,
the traffic is not inspected for spam.
Overloaded, IP shunting This alarm resolves itself within 1 to 2 hours after the burst subsides. Run the clear
alarms counters CLI command to clear all the counter-based alarms to manually
clear the alarm. If the burst sustains or re-occurs then the alarm is raised again after it is
cleared. Systems that continually encounter this alarm are likely under-provisioned, apply
expensive SandScript, or subject to some sustained change in the process of heavy
traffic. Increase the cluster capacity to resolve this issue.
Overloaded, UDP shunting This alarm resolves itself within 1 to 2 hours after the burst subsides. You can run the
clear alarms counters CLI command to clear all the counter-based alarms to
manually clear the alarm. If the burst sustains or re-occurs then the alarm is raised again
after it is cleared. Systems that continually encounter this alarm are likely
under-provisioned, apply expensive SandScript, or subject to some sustained change in
the process of heavy traffic. Increase the cluster capacity to resolve this issue.
Measurement memory allocation Consider the cardinality of the unique-by keys used in the measurements and adjust
failure SandScript to reduce the number of measurement instances.
Demographic stats flow skipped The system is busy and cannot evaluate SandScript on all flows. Reduce the amount of
interval traffic that the PTS is processing or simplify SandScript.
Enumerated classifier assigned an Check SandScript to ensure that enumerated classifiers are set to the correct enumerated
invalid value classifier values.
Expression stats max columns Check published subscriber measurements that are unique-by (subscriber, classifier)
exceeded and ensure that the set is small.
Max tee destinations per flow Adjust the tee configuration in the SandScript so the documented maximums are not
exceeded exceeded.
Http_response actions issued on To action a flow with http_response, provide a set Flow.Stream.ReadOnly =
ReadOnly flow false action on the flow each time SandScript is run on that flow. This keeps the flow
out of the read-only state.
Stat was not written to the SPB due histogramDefinitionNotPresent: The CND or PTSD / CMT buffer is probably
to an error overloaded causing histogram instances to arrive after the statistic is written to the SPB.
Check that an excessive number of instances (>10000) for the histogram measurements
is not getting published.
Http_response action issued with a Adjust the SandScript such that it is not possible to issue an http_response action
null payload expression with a NULL payload string.
Analyze "dpm" action issued on Analyze "dpm" must be issued on every DNS SandScript call leading up to and including
ReadOnly flow the current one for the flow to remain writable.
Policy Controller overloaded on Decrease the total memory footprint of each unique by instance. To do this, decrease
module one of:
• The number of policy metrics.
• The number of histogram bins for the output_histogram parameter.
• The number of histogram bins for a metric data parameter.
Policy Controller degraded on module Ensure that each new flow is sampled no more than once for QoE. If the PTS is regularly
under very heavy load, then it is advisable to only sample a subset of the total number
of flows (for example, every second flow). Systems that continually encounter this alarm
are likely under-provisioned, apply expensive SandScript, subject to some sustained
05-00262 C07
PTS Alarms
Alarm Model 24: High Network Interface Rx Rate

change in process heavy traffic, or subject to sustained changes in process heavy traffic.
Increase the cluster capacity to resolve this issue.
Policy Controller degraded on control Decrease the number of unique by instances that the cluster supports. Systems continually
processor encountering this alarm are likely under-provisioned, apply expensive SandScript, subject
to some sustained change in process heavy traffic, or subject to sustained changes in
process heavy traffic. Increase the cluster capacity to resolve this issue.
Infinite loop detected Identify the foreach statement that has parameters that result in an infinite loop.
Inifinite loop detection is triggered when a Range's:
• start > end with positive step.
• end > starts with a negative step.
• step is zero.
Fix the foreach range parameters so that they do not satisfy the condition above.
DNS modification of read only flow Provide a set Flow.Stream.ReadOnly = false action on the flow every time
SandScript is run on that flow. This keeps the flow out of the read-only state.
DNS modification of fragmented Use Flow.Application.DNS.IsModifiable to determine if a modification of a
packets particular DNS packet is supported. Avoid performing any DNS modifications when the
value of this field is false.
DNS modification of TCP stream Use Flow.Application.DNS.IsModifiable to determine if a modification of a
particular DNS packet is supported. Avoid performing any DNS modifications when the
value of this field is false.
3.24 Alarm Model 24: High Network Interface Rx

Rate
This alarm is raised when an interface port is receiving data at a rate that exceeds 90% of its capacity. It includes the current
rate, max rate, utilization percentage, and description of the associated interface port. If the data rate drops below 80% then a
clear notification is generated. Note that this notification is only sent for cluster interface ports.
Profile Description
Severities Major
Raise Notification svSysIfPortRxRateHighNotification
Clear Notification svSysIfPortRxRateNormalNotification
Triggers ifPortRxRateTrigger
Unique Instance Identifier svPortTopologyPortRateDescription
3.24.1 High Network Interface Rx Rate - Major

MIB SANDVINE-MIB
05-00262 C07
PTS Alarms

Trap Name svSysIfPortRxRateHighNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.11

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPortTopologyPortRateRxRate 1.3.6.1.4.1.11610.435.10470.1.40.1.1
svPortTopologyPortRateMaxRate 1.3.6.1.4.1.11610.435.10470.1.40.1.3
svPortTopologyPortRateRxUtilization 1.3.6.1.4.1.11610.435.10470.1.40.1.4
svPortTopologyPortRateDescription 1.3.6.1.4.1.11610.435.10470.1.40.1.6
svPortTopologyPortRateRxRate64 1.3.6.1.4.1.11610.435.10470.1.40.1.9
svPortTopologyPortRateMaxRate64 1.3.6.1.4.1.11610.435.10470.1.40.1.11
This notification is sent if the utilization for a particular port reaches or exceeds 90% of the maximum supported Rx rate. The
32-bit varbinds svPortTopologyPortRateRxRate and svPortTopologyPortRateMaxRate are deprecated in favour of these new
64-bit varbinds:
• svPortTopologyPortRateRxRate64
• svPortTopologyPortRateMaxRate64
Profile Description
Frequency 8 seconds
Severity Major
Condition SANDVINE-MIB::svPortTopologyPortRateRxUtilization >= 90%
3.24.2 High Network Interface Rx Rate Cleared

This notification is sent if an interface port, that previously sent out a rate high notification, is now receiving data at a rate that is
less than or equal to 80% of its capacity. It includes the current rate, max rate, utilization percentage, and description of the
associated interface port. Note that this notification is only sent for cluster interface ports.

MIB SANDVINE-MIB
Trap Name svSysIfPortRxRateNormalNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.12

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPortTopologyPortRateRxRate 1.3.6.1.4.1.11610.435.10470.1.40.1.1
05-00262 C07
PTS Alarms

svPortTopologyPortRateRxUtilization 1.3.6.1.4.1.11610.435.10470.1.40.1.4
svPortTopologyPortRateRxRate64 1.3.6.1.4.1.11610.435.10470.1.40.1.9
This alarm is cleared when the utilization for a particular port drops to at least 80% of the maximum supported Rx rate. The 32-bit
varbinds svPortTopologyPortRateRxRate and svPortTopologyPortRateMaxRate are deprecated in favour of these new 64-bit
varbinds:
• svPortTopologyPortRateRxRate64
Profile Description
Frequency 8 seconds
Severity Cleared
Condition SANDVINE-MIB::svPortTopologyPortRateRxUtilization <= 80%

If left to persist, the NPU(s) and associated switching fabric on the receiving element could become overloaded, resulting in
discarded traffic.
Use these CLI commands to check for potential errors and discards:
show interface counters interface-group [counts | discards | errors | pause | rmon]
1. Validate these steps:

a. If your cluster is configured in a ring or partial mesh then it is likely that the cluster ports are getting over utilized due
to inter element traffic (asymmetry). It is always recommended to deploy clusters as a full mesh, if possible.
b. The cluster links are configured for link aggregation. If the cluster links are not configured for link aggregation it is
recommended to do so (if possible) and verify the impact on cluster port utilization. To check cluster port utilization you
can run the show interface rate cluster CLI command on the controller.
c. Check if the Tee is enabled in policy and determine how much traffic is being teed. Also, it is useful to know where the
Tee Destinations are with respect to the cluster and which cluster links (if any) are used to facilitate transmission of
the tee-d traffic. If the Tee is enabled and you suspect that it is the culprit, try disabling it and checking changes in
cluster port utilization using the show interface rate cluster CLI command.
2. If the above items have been validated and the alarm still persists, it may be due to any of these reasons:
a. Another PTS may need to be added to the cluster.
b. This is potentially an issue with how the cluster is deployed.
c. There may be an excessive amount of asymmetric traffic in the network.
05-00262 C07
PTS Alarms
Alarm Model 25: High Network Interface Tx Rate
3.25 Alarm Model 25: High Network Interface Tx

Rate
This alarm is raised when an interface port is transmitting data at a rate that exceeds 90% of its capacity. It includes the current
rate, max rate, utilization percentage, and description of the associated interface port. If the data rate drops below 80% then a
clear notification is generated. Note that this notification is only sent for cluster interface ports.
Profile Description
Severities Major
Raise Notification svSysIfPortTxRateHighNotification
Clear Notification svSysIfPortTxRateNormalNotification
Triggers ifPortTxRateTrigger
Unique Instance Identifier svPortTopologyPortRateDescription
3.25.1 High Network Interface Tx Rate- Major

This notification is sent if the utilization for a particular port reaches or exceeds 90% of the maximum supported tx rate.
Profile Description
Frequency 8 seconds
Severity Major
Condition SANDVINE-MIB::svPortTopologyPortRateTxUtilization >= 90%
MIB Reference Trap Name

MIB SANDVINE-MIB
Trap Name svSysIfPortTxRateHighNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.13

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPortTopologyPortRateTxRate 1.3.6.1.4.1.11610.435.10470.1.40.1.2
svPortTopologyPortRateTxUtilization 1.3.6.1.4.1.11610.435.10470.1.40.1.5
svPortTopologyPortRateTxRate64 1.3.6.1.4.1.11610.435.10470.1.40.1.10
05-00262 C07
PTS Alarms
Alarm Model 25: High Network Interface Tx Rate
The 32-bit varbinds svPortTopologyPortRateTxRate and svPortTopologyPortRateMaxRate are deprecated in favour of these
new 64-bit varbinds:
• svPortTopologyPortRateTxRate64
3.25.2 High Network Interface Tx Rate Cleared

This notification is sent if an interface port, that previously sent out a rate high notification, is now transmitting data at a rate that
is less than or equal to 80% of its capacity. It includes the current rate, max rate, utilization percentage, and description of the
associated interface port.

MIB SANDVINE-MIB
Trap Name svSysIfPortTxRateNormalNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.14

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPortTopologyPortRateTxRate 1.3.6.1.4.1.11610.435.10470.1.40.1.2
svPortTopologyPortRateTxUtilization 1.3.6.1.4.1.11610.435.10470.1.40.1.5
svPortTopologyPortRateTxRate64 1.3.6.1.4.1.11610.435.10470.1.40.1.10
This alarm is cleared when the utilization for a particular port drops to at least 80% of the maximum supported Tx rate. The 32-bit
varbinds svPortTopologyPortRateTxRate and svPortTopologyPortRateMaxRate are deprecated in favour of these new 64-bit
varbinds:
• svPortTopologyPortRateTxRate64
Profile Description
Frequency 8 seconds
Severity Cleared
Condition SANDVINE-MIB::svPortTopologyPortRateTxUtilization <= 80%

If left to persist, the NPU(s) and associated switching fabric of the element on the receiving end of the cluster port could become
overloaded, resulting in discarded traffic.
05-00262 C07
PTS Alarms
Alarm Model 26: Unavailable Disk
These CLI commands should be executed to check for potential errors and discards on the element that we are transmitting to:
show interface counters interface-group [counts | discards | errors | pause | rmon]
1. Refer to your network diagram to determine who is on the receiving end of the cluster.
2. You should validate these steps:

a. If your cluster is configured in a ring or partial mesh then it is likely that the cluster ports are getting overutilized due to
inter-element traffic—asymmetry. It is always recommended to deploy clusters as a full mesh if possible.
b. The cluster links are configured for link aggregation. If the cluster links are not configured for link aggregation it is
recommended to do so (if possible) and verify the impact on cluster port utilization. To check cluster port utilization,
run the show interface rate cluster CLI command on both the sending and receiving elements.
c. Check if Tee is enabled in policy and determine how much traffic is being teed. Also, it is useful to know where the Tee
Destinations are with respect to the cluster and which cluster links (if any) are used to facilitate transmission of the
teed traffic. If the Tee is enabled and you suspect that it is the culprit, try disabling it and checking changes in cluster
port utilization using the show interface rate cluster CLI command.
3. If the above items have been validated and the alarm still persists then it may be due to any of these reasons:
a. Another PTS may need to be added to the cluster.
b. This is potentially an issue with how the cluster is deployed.
c. There may be an excessive amount of asymmetric traffic in the network.
3.26 Alarm Model 26: Unavailable Disk

This notification is sent if a disk is no longer available or no longer responsive (the disk status is not online). To reduce overhead
of checking the system disks, by default, the system cycles through checking disks every 360 seconds, with a built in delay
between each call to check of disk information, thus allowing up to 10 or more minutes (depending on the number of disks in the
system) for a failed disk to be discovered and the status to be updated.
Note:
Alarm Model 26 (Unavailable Disk) is not supported on the PTS Linux platform.
Profile Description
Severities Major
Raise Notification svEnvStorageDiskStatusErrorNotification
Clear Notification svEnvStorageDiskStatusNoErrorNotification
Triggers • diskStatusOfflineTrigger
• diskStatusOnlineTrigger
Unique Instance Identifier svStorageDiskTableSlot
Related CLI command

show system storage disk [ID]
05-00262 C07
PTS Alarms
3.26.1 Unavailable Disk

MIB SANDVINE-MIB
Trap Name svEnvStorageDiskStatusErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.13

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svStorageDiskTableStatus 1.3.6.1.4.1.11610.435.11249.1.12.1.24
3.26.1.1 Unavailable Disk

This notification is sent if the disk status is not online.
Profile Description
Severity Major
Condition SANDVINE-MIB::svStorageDiskTableStatus!= 1 (online)
3.26.2 Unavailable Disk Cleared

This notification is sent if a disk becomes available or responsive.

MIB SANDVINE-MIB
Trap Name svEnvStorageDiskStatusNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.14

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svStorageDiskTableStatus 1.3.6.1.4.1.11610.435.11249.1.12.1.24
05-00262 C07
PTS Alarms
3.26.2.1 Unavailable Disk Cleared

This alarm is cleared when the disk status is online. Run the show system storage disk [ID] CLI command to display
all disks on the system, including their description.
Profile Description
Severity Cleared
Condition SANDVINE-MIB::svStorageDiskTableStatus == 1 (online)

Different hardware platforms have different levels of redundancy in their disks, so the impact varies by platform.
3.26.3.1 SRP 3000-D

This device uses RAID-1 and RAID-6.
Disks 1 and 2 are part of a RAID-1 configuration with full redundancy, so there is no performance impact should one drive fail.
This logical drive contains the operating system of the system. If the second disk in this logical drive were to fail, the device would
fail and need to be reconfigured at Sandvine once new drives were added.
Disks 3 through 10 or 3 through 24 are part of a RAID-6 configuration. This means that the logical drive has two disks of redundancy.
This logical drive contains the database data for the SRP. The failure of up to two disks can be handled without affecting proper
functionality. After replacing the failed disk(s) the system must rebuild the RAID data and performance will be impacted while
this is in operation. A third simultaneous failed disk will result in irrecoverable data loss.
3.26.3.2 SRP 3000-D lite

Disks 1 and 2 (there are no disks in slots 3-24) are part of a RAID-1 configuration with full redundancy. The failure of a single
disk does not affect performance. If a second disk fails, the device fails and needs to be reconfigured at Sandvine and results in
data loss.
3.26.3.3 SRP3000-A, -B, or -C lite

For SRP 3000-A lite, SRP 3000-B lite, or SRP 3000-C lite, disks 1 and 14 (there are no disks in slots 2 - 13 or slot 15 if it exists)
are part of a RAID-1 configuration with full redundancy. The failure of a single disk does not affect performance. If a second disk
fails, the device fails it needs to be reconfigured at Sandvine and results in data loss.
3.26.3.4 SRP3000-B
This logical drive contains the operatin system of the system. If the second disk in this logical drive were to fail, the device would
Disks 2 through 13 and 15 are part of a RAID-5 configuration with a dedicated hot-spare. This means that the logical drive has
2 disks of redundancy. This logical drive contains the database data for the SRP. The failure of up to two disks can be handled
without affecting proper functionality. The first failed disk is replaced with the hot spare disk, and the RAID will rebuild using that
disk. This will result in reduced performance during the rebuild, but after it is completed the performance is optimal again. The
second failed disk will result in a degraded logical drive and performance is reduced until one of two failed disks has been replaced
and has completed rebuilding. The failure of a third disk in this drive will result in data loss.
05-00262 C07
PTS Alarms
3.26.3.5 PTS 24000

This logical drive contains the operating system of the system. If the second disk in this logical drive were to fail, the device would
3.26.3.6 PTS 32000 and 22000

These platforms have only one disk, so there is no redundancy. A failure of the only disk results in the device going down.
3.27 Alarm Model 27: Faulted Hardware

This notification is sent if a piece of hardware has been detected as faulty. If the hardware failure is intermittent, a minor alarm
occurs. If the hardware is failing consistently, a major alarm occurs. For either alarm severity, you may experience unexpected
behavior such as loss link or dropped packets. In that case, contact Sandvine Customer Support immediately, for assistance.
Note:
Alarm Model 27 (Faulted Hardware) is not supported on the PTS Linux platform.
Profile Description
Alarm Title Hardware Fault
Severities Minor, Major
Raise Notification svEnvHardwareFaultNotification
Clear Notification svEnvHardwareClrNotification
Triggers • HardwareFaultMinor
• HardwareFaultMajor
• HardwareFaultClear
Possible instances
There are many failures that may cause this alarm. Some of the most common are:
• Memory corruption on one of the network switches
• Unstable connection between silicon due to manufacturing defect
• Malfunctioning chip due to accident short circuit.

MIB SANDVINE-MIB
Trap Name svEnvHardwareFaultNotification
Trap OID .1.3.6.1.4.1.11610.6799.3.1.0.13

MIB SANDVINE-MIB
Trap Name svEnvHardwareFaultClrNotification
05-00262 C07
PTS Alarms

Trap OID .1.3.6.1.4.1.11610.6799.3.1.0.16

svClusterConfigName .1.3.6.1.4.1.11610.435.5213.1.2.1
sysName .1.3.6.1.2.1.1.5
svSeverity .1.3.6.1.4.1.11610.6799.1.10
svStorageDiskTableSlot .1.3.6.1.4.1.11610.435.11249.1.12.1.9
svStorageDiskTableDescription .1.3.6.1.4.1.11610.435.11249.1.12.1.6
svStorageDiskTableStatus .1.3.6.1.4.1.11610.435.11249.1.12.1.24
3.27.1 Hardware fault

A piece of hardware has been detected as marginal (minor) or faulty (major).
Profile Description
MIB SANDVINE-MIB
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.15
sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
Hardware fault: Minor error
Profile Description
Severity Minor
Condition SANDVINE-MIB:: svDiagnosticsFailureNumFailures = = 1
Description A piece of hardware has been detected as marginal (sporadic test failures).
Hardware fault: Major error
Profile Description
Severity Major
Condition SANDVINE-MIB:: svDiagnosticsFailureNumFailures > = 2
Description A piece of hardware has been detected as faulty (consistent failure).
05-00262 C07
PTS Alarms
Alarm Model 28: Discarded Subscriber State
3.27.2 Hardware no longer faulted

A piece of faulty hardware that was replaced and is no longer exhibiting failures. This notification indicates that the hardware is
not reporting faults.
Profile Description
MIB SANDVINE-MIB
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.16
sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
Hardware fault: Clear error

Profile Description
Severity Minor
Condition (marginal) SANDVINE-MIB::svDiagnosticsFailureNumFailures = = 0
Description A piece of faulty hardware that was replaced and is no longer exhibiting failures.

For either alarm severity, you may experience unexpected behavior such as loss link or dropped packets.
Read the failure comment and look for other alarms such as interface module errors.
If there is nothing obviously wrong with the unit, there is most likely a fault that needs to be addressed. Contact Sandvine
Customer Support or its authorized partner immediately.
3.28 Alarm Model 28: Discarded Subscriber State

This alarm is raised if either the PTS or the SDE receives an SPB request to clear all current subscriber mappings.
Profile Description
Severities Minor
Raise Notification svSubMappingFlushedNotification
Clear Notification svSubMappingFlushClearNotification
Triggers subMappingFlushed
Unique Instance identifier svSubscriberMapManagementSubscriberClearEvents
05-00262 C07
PTS Alarms
Alarm Model 28: Discarded Subscriber State
3.28.1 Subscriber Mappings Cleared - Notification

MIB Trap Name
MIB SANDVINE-MIB
Trap Name svSubMappingFlushedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.8.0.3

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svSubscriberMapManagementSubscriberClearEvents 1.3.6.1.4.1.11610.435.7742.1.3.1000.3
3.28.1.1 Subscriber Mappings Flushed

This notification is sent if the SPB sends a 'clear subscriber mappings' message to the PTS or SDE.
Profile Description
Frequency 8 seconds
Severity Minor
Condition DELTA (SANDVINE-MIB::svSubscriberMapManagementSubscriberClearEvents) > 1
3.28.2 Subscriber Mappings Cleared - Clear

Notification sent 30 minutes after most recent IP mapping flush.
It indicates that subscribers are mapped on SPB and PTS/SDE as normal.

MIB SANDVINE-MIB
Trap Name svSubMappingFlushClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.8.0.4

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svSubscriberMapManagementSubscriberClearEvents 1.3.6.1.4.1.11610.435.7742.1.3.1000.3
3.28.2.1 Clear Trap for Subscriber Mappings Flushed

This alarm is cleared when the SPB has not sent a “clear subscriber mappings” message to the PTS/SDE for 1800 seconds (30
minutes).
05-00262 C07
PTS Alarms
Alarm Model 29: Disabled Subscriber Lookups
Profile Description
Severity Cleared
Condition DELTA (SANDVINE-MIB::svSubscriberMapManagementSubscriberClearEvents) == 0
3.28.3 Subscriber Mappings on SPB and PTS/SDE Cleared - Minor

Alarm
This notification is sent if the SPB sends a “clear subscriber mappings” message to the PTS/SDE. This causes the counter
SANDVINE-MIB::svSubscriberMapManagementSubscriberClearEvents to increment by 1 and will clear all subscriber
mappings from the PTS/SDE.

Alarm Model 28 is typically the result of a mass calling event taking place on the SPB. Until subscribers are remapped, these
are the impacts of alarm 28:
• There is no subscriber-aware SandScript managing subscriber traffic.
• Subscriber-based reporting shows under counting.
• Subscriber attributes are not available to the PTS or SDE.
Check the SPB IP Mapper monitor logs to verify the alarm condition. Login to the SPB and check for error messages in
these files:
• /var/log/sonicmq.log
• /var/log/jboss-server.log
• /var/log/svlog
3.29 Alarm Model 29: Disabled Subscriber

Lookups
This alarm is raised when either the PTS or SDE receives a disable-lookups notification from the SPB. A mass calling event on
the SPB is typically the cause of Alarm Model 29.
Profile Description
Severities Minor
Raise Notification svSubLookupsDisabledNotification
Clear Notification svSubLookupsEnabledNotification
Triggers • subLookupsDisabled
• subLookupsEnabled
Unique Instance identifier N/A
05-00262 C07
PTS Alarms
Alarm Model 29: Disabled Subscriber Lookups
3.29.1 Disabled Subscriber Lookups

MIB SANDVINE-MIB
Trap Name svSubLookupsDisabledNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.8.0.5

svSeverity 1.3.6.1.4.1.11610.6799.1.10
3.29.1.1 Disabled Subscriber Lookups

This notification is sent when the SPB disables subscriber lookups on the PTS and the SDE.
Profile Description
Frequency 8 seconds
Severity Minor
Condition SANDVINE-MIB::svSubscriberMapControlPerformLookups == false
3.29.2 Disabled Subscriber Lookups Cleared

This notification is sent when the PTS or SDE receives an enable-lookups notification from the SPB.

MIB SANDVINE-MIB
Trap Name svSubLookupsEnabledNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.8.0.6

svSeverity 1.3.6.1.4.1.11610.6799.1.10
3.29.2.1 Clear Trap for Subscriber Lookups Disabled

This notification is sent when the SPB enables subscriber lookups on the PTS and the SDE.
Profile Description
Frequency 8 seconds
Severity Minor
Condition SANDVINE-MIB::svSubscriberMapControlPerformLookups == true
05-00262 C07
PTS Alarms
Alarm Model 30: Delayed Subscriber Mapping
3.29.3 Subscriber Lookups Disabled—Minor

This notification is sent when the SPB sends a cannot process lookups message to either the PTS or SDE. This causes the counter,
SANDVINE-MIB::svSubscriberMapManagementIpLookupsDisabledEvents, to increment by 1 and prevents the PTS from performing
any IP-based subscriber lookups.
The PTS/SDE resumes lookups when the SPB sends a lookup processing enabled message, which cause
SANDVINE-MIB::svSubscriberMapManagementIpLookupsEnabledEvents to increment, and lowers the alarm.

When this alarm occurs, until the time the SPB sends a lookup processing enabled message, unmapped IP addresses in subscriber
classes are not looked up from the SPB.
For these addresses, this can cause:
• Subscriber-aware SandScript is not managing subscriber traffic.
• Subscriber attributes are not available to the PTS or the SDE.
A Mass Calling Event on the SPB is typically the cause of this alarm.
Check the SPB IP Mapper Monitor logs, logon to the SPB and check the logs for error messages:
/var/log/sonicmq.log
/var/log/jboss-server.log
/var/log/svlog
3.30 Alarm Model 30: Delayed Subscriber Mapping

This alarm is raised when there are significant delays in IP mapping on the PTS or SDE.
Profile Description
Severities Minor
Raise Notification svSubMappingLateNotification
Clear Notification svSubMappingOnTimeNotification
Triggers subMappingLate
Unique Instance identifier svSubscriberMapStatsIpAddressesMappedLate
3.30.1 Delayed Subscriber Mapping

MIB SANDVINE-MIB
Trap Name svSubMappingLateNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.8.0.1
05-00262 C07
PTS Alarms

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svSubscriberMapConfigLateMappingTimeout 1.3.6.1.4.1.11610.435.7742.1.2.100
DISMAN-EXPRESSION-MIB::expValueCounter64Val 1.3.6.1.2.1.90.1.3.1.1.9."Sandvine.subMappingOnTimeDeltaExp.
0.0.0
DISMAN-EXPRESSION-MIB::expValueCounter64Val 1.3.6.1.2.1.90.1.3.1.1.9."Sandvine.subMappingLateDeltaExp.
0.0.0
3.30.1.1 Delayed Subscriber Mapping on the PTS/SDE

This notification is sent when more than 5% of all subscriber mappings occur late within an interval of 15 minutes (900 seconds).
This notification is sent if, over the past 15-minute interval, 5% or more of the IP addresses mapped to subscribers took longer
than 30 seconds to be mapped, after the arrival of the first data packet for that IP address.
Profile Description
Severity Minor
Condition (expValueCounter64Val."Sandvine". "subMappingLateDeltaExp".0.0.0 * 100) /
(expValueCounter64Val."Sandvine"."subMappingOnTimeDeltaExp".0.0.0 +
expValueCounter64Val."Sandvine"."subMappingLateDeltaExp".0.0.0) >= 5
3.30.2 Delayed Subscriber Mapping Cleared

This notification is sent if IP mapping on the PTS/SDE has been operating within reasonable delays within an interval of 900
seconds (15 minutes).

MIB SANDVINE-MIB
Trap Name svSubMappingOnTimeNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.8.0.2

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svSubscriberMapConfigLateMappingTimeout 1.3.6.1.4.1.11610.435.7742.1.2.100
DISMAN-EXPRESSION-MIB::e 1.3.6.1.2.1.90.1.3.1.1.9."Sandvine"."subMappingOnTimeDeltaExp".0.0.0
xpValueCounter64Val
DISMAN-EXPRESSION-MIB::e 1.3.6.1.2.1.90.1.3.1.1.9."Sandvine"."subMappingLateDeltaExp".0.0.0
xpValueCounter64Val
05-00262 C07
PTS Alarms
3.30.2.1 Clear Trap for Delayed Subscriber Mapping on PTS/SDE

This notification is sent when less than 1% of all subscriber mappings, within an interval of 900 seconds (15 minutes), occur late.
Profile Description
Severity Cleared
Condition (expValueCounter64Val."Sandvine"."subMappingLateDeltaExp".0.0.0 * 100) / (
expValueCounter64Val."Sandvine"."subMappingOnTimeDeltaExp".0.0.0 + expValueCounter64Val.
"Sandvine"."subMappingLateDeltaExp".0.0.0) <= 1

If this alarm occurs, these situations could occur for any late-mapped addresses before they are mapped:
• Subscriber traffic is not managed by any subscriber-aware SandScript.
• Subscriber attributes are not available to the PTS/SDE.
• Subscribers appear unmapped on the PTS/SDE for at least the first 30 seconds of their data traffic.
There are a number of conditions that could cause subscribers to be mapped for more than 30 seconds after their data traffic
starts. Possible causes include:
• RADIUS traffic may be delayed to the SPB. Verify that all RADIUS servers are up and are sending timely messages.
• CND is overloaded and unable to keep up with the rate of notifications from SPB. Or for the PTS, PTSD is overloaded and
unable to keep up with rate of notifications from CND.
a. Log in to the PTS/SDE and check the CPU usage. For SDE, run the show system resources 67 CLI command to
check the SVSDE process. For PTS, check the CND or PTSD.
b. Check that there are no CPU alarms.
c. Check /var/log/svlog for error messages regarding the JMS connection.
• The data interfaces may not have the correct functions configured. As a result a number of subscribers are not properly
mapped, and so when they get mapped, they are likely to have been on the system for longer than the delay mapping timeout.
• A large number of unmapped subscribers results in continuous lookups and delays for both unmapped and mapped subscribers.
a. Run the show service subscriber-management stats CLI command.
In the resulting output, a non-zero value in the column of "UnmappedResponses" indicates that subscribers are unmapped.
A large number indicates that the SPB is responding to many requests with "No mapping available".
b. Determine the subscribers that are missing records by inspecting the "NetworkGroupsPendingLookup" column. If the
same subnets of traffic are repeated in the output, it indicates that the PTS may be unable to retrieve subscriber records
for this subnet. For more information on subscriber mapping configuration, see the SPB Administration Guide .
• The SPB may be overloaded and unable to keep up with the rate of RADIUS messages. Log in to the SPB and check for
error messages in:
/var/log/sonicmq.log
05-00262 C07
PTS Alarms
Alarm Model 32: Disconnected Diameter Peer
/var/log/jboss-server.log
/var/log/svlog
3.31 Alarm Model 32: Disconnected Diameter Peer

This alarm is raised when the connection between a Diameter peer and client is lost.
The alarm is raised with these severities:
1. Major
a. Connection with a primary peer (without a secondary peer) is lost.
b. Connection with a primary peer (having a secondary peer) is lost and connection with the corresponding secondary peer
is down too.
2. Warning
a. Connection with a primary peer (having a secondary peer) is lost but the connection with the corresponding secondary
peer is up and running.
b. Connection with a secondary peer is lost, irrespective of the connection status of its corresponding primary peer.
Profile Description
• Warning
• Clear
Raise Notification svDiameterPeerDiscNotification

Clear Notification svDiameterPeerConnNotification
Unique Instance identifier svDiameterStatsClientPeerRemoteIdentity
3.31.1 Disconnected Diameter Peer

This notification is sent if the connection to a remote client Diameter peer is lost.

MIB SANDVINE-MIB
Trap Name svDiameterPeerDiscNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.1

svDiameterStatsClientPeerRemoteIdentity 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.7
svDiameterStatsClientPeerConnectionStatus 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.13
svDiameterStatsClientPeerWasDisconnected 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.12
05-00262 C07
PTS Alarms
Alarm Model 33: Failed Power On Self Test
3.31.2 Disconnected Diameter Peer Cleared

The notification is cleared once the connection with the remote client Diameter peer is restored.

MIB SANDVINE-MIB
Trap Name svDiameterPeerConnNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.2

svDiameterStatsClientPeerConnectionStatus 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.13
svDiameterStatsClientPeerWasDisconnected 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.12

If left to persist, packets destined to this peer are dropped.
1. Run these CLI commands to check for potential errors or discards:
show service diameter peer client
show service diameter messages detail
2. Ensure that the remote Diameter peer is operational and reachable.
3. Ensure that the hostname of the remote Diameter peer is correct in diam_peer_config.xml and that the hostname resolves
to a valid IP address.
4. Ensure that the local Diameter peer has not sent any invalid messages to the remote Diameter peer.
3.32 Alarm Model 33: Failed Power On Self Test

This alarm is raised when a power on self test failure has occurred. The element may exhibit unexpected behavior - contact
Sandvine Technical Support in this case.
There are many reasons why a power on self test could fail, including:
• A manufacturing defect is causes a chip not to initialize properly.
• Damage has been done to the system while moving or due to out-of-specification temperatures.
• There is a problem with the power supplies.
Note:
Alarm Model 33 (Failed Power On Self Test) is not supported on the PTS Linux platform.
Profile Description
Severity • Major
• Clear
05-00262 C07
PTS Alarms
Alarm Model 33: Failed Power On Self Test
Profile Description
Raise Notification svEnvPostFailureNotification
Clear Notification svEnvPostFailureClrNotification
Triggers • postFailed
• postCleared
Unique instance identifier svDiagnosticsStatsPostResult
3.32.1 Failed Power On Self Test—Major

The system detected a critical issue with a piece of hardware while powering on.

MIB SANDVINE-MIB
Trap Name svEnvPostFailureNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.8.0.2

svSeverity 1.3.6.1.4.1.11610.6799.1.10
sysName 1.3.6.1.2.1.1.5
Profile Description
Frequency 8 seconds
Severity Major
Condition SANDVINE-MIB::svDiagnosticsStatusPostResult == 3
3.32.2 Failed Power On Self Test—Clear

A previous hardware error has been corrected.

MIB SANDVINE-MIB
Trap Name svEnvPostFailureClrNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.18

svSeverity 1.3.6.1.4.1.11610.6799.1.10
sysName 1.3.6.1.2.1.1.5
05-00262 C07
PTS Alarms
Alarm Model 34: High Traffic Discrepancy

The element attempts to come up as normal, but there may be unexpected behavior due to the hardware fault. The internal
diagnostics has detected that a piece of hardware may not be performing correctly.
1. Check to see if there is noticeable physical damage to the system.
2. To see the result of the internal diagnostics, run: show system diagnostics
3. Ensure that the power cables are completely plugged in, and that the LEDs on all four power supplies are on turned on.
4. Look for other alarms that may point to specific failure such as interface module or blade errors.
5. For further assistance, contact Sandvine Customer Support or its authorized partner.
3.33 Alarm Model 34: High Traffic Discrepancy

This alarm is raised when the ingress to egress packet rate exceeds the configured ratio. An instance of this alarm is possible
for each direction of each configured bridge group. For example, if the PTS has one configured bridge group consisting of data
interfaces 3-1 and 3-2, it is possible to have these alarm instances:
• Inline Bridge Group Error: 3-1 to 3-2
• Inline Bridge Group Error: 3-2 to 3-1
Note:
Alarm Model 34 (High Traffic Discrepancy) is not supported on the PTS Linux platform.
Profile Description
• Clear
Raise Notification svInlineBridgeGroupErrorNotification
Clear Notification svInlineBridgeGroupClearNotification
Triggers • inlineBridgeGroupError
• inlineBridgeGroupClear
3.33.1 High Traffic Discrepancy—Major

An alarm with a severity of major is raised if the ingress to egress packet rate exceeds the configured ratio. This notification is
sent when:
• External networks fail.
• Extensive use of traffic management SandScript occurs.
• Bandwidth exceeds system specifications.
The notification is only sent when the bridge group is configured in the inline mode, and monitoring of the packet rates ratio is
administratively enabled, which, by default, is not enabled.
05-00262 C07
PTS Alarms
Alarm Model 34: High Traffic Discrepancy

MIB SANDVINE-MIB
Trap Name svInlineBridgeGroupErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.7

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svBridgeGroupCountTablePorts 1.3.6.1.4.1.11610.435.10470.1.31.200.1.3
svBridgeGroupCountTableInlineAlarmEvents 1.3.6.1.4.1.11610.435.10470.1.31.200.1.11
svBridgeGroupCountTableInlineAlarmTrigger 1.3.6.1.4.1.11610.435.10470.1.31.200.1.13
svBridgeGroupCountTableTriggeredRxDelta 1.3.6.1.4.1.11610.435.10470.1.31.200.1.14
svBridgeGroupCountTableTriggeredTxDelta 1.3.6.1.4.1.11610.435.10470.1.31.200.1.15
3.33.2 High Traffic Discrepancy—Clear

MIB SANDVINE-MIB
Trap Name svInlineBridgeGroupClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.8

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svBridgeGroupCountTablePorts 1.3.6.1.4.1.11610.435.10470.1.31.200.1.3
svBridgeGroupCountTableInlineAlarmEvents 1.3.6.1.4.1.11610.435.10470.1.31.200.1.11
svBridgeGroupCountTableInlineAlarmTrigger 1.3.6.1.4.1.11610.435.10470.1.31.200.1.13
svBridgeGroupCountTableTriggeredRxDelta 1.3.6.1.4.1.11610.435.10470.1.31.200.1.14
svBridgeGroupCountTableTriggeredTxDelta 1.3.6.1.4.1.11610.435.10470.1.31.200.1.15

It is likely that the discarded packets are creating a noticeable impact on the internet connections of some subscribers in the
network:
05-00262 C07
PTS Alarms
Alarm Model 35: Exhausted Resource
1. Check to see if the error counts on the switching fabric are abnormally high with the show interface counters
[fabric|data|module|cluster] CLI command and its parameter defined specific calls.
2. Ensure that all elements in a cluster or modules on a single PTS are running properly, and that traffic is distributed across
the deployment normally.
3. Look for other alarms that may point to the specific failure such as interface module or blade errors.
4. Contact Sandvine Technical Support for further guidance.
5. Once the root cause has been identified and addressed, manually clear the alarm using the clear alarms bridge-group
CLI command. Then the alarm history shows the entry: Clear Inline Bridge Group Error
3.33.3.1 Additional Information

You can monitor the status of the bridge group using the show interface bridge-group CLI command. Configuration is:
CLI command Description Default

set config interface bridge-group monitoring enabled Administratively enable/disable the threshold monitoring. false
set config interface bridge-group monitoring Ratio of the transmitted data to received data. If a bridge 0.90
alarm-threshold group's transmitted rate drops below this threshold for
the configured duration, the alarm triggers.
set config interface bridge-group monitoring Minimum ingress rate required before the ratio is 100000
min-rx-threshold measured. This prevents the alarm from triggering during
test lab situations.
set config interface bridge-group monitoring period Rate sampling interval (measured in seconds). 5
set config interface bridge-group monitoring Number of consecutive failure intervals before the alarm 3
failure-threshold is triggered. This allows the operator to adjust the
sensitivity of the alarm.
3.34 Alarm Model 35: Exhausted Resource

This alarm is raised when one of the system resources in hrStorageTable experiences allocation failures.
Note:
Conditions (PTS only) contributing to cause this alarm include:
• Existing SandScript policy could create rows in a policy table (more than once per policy evaluation), and never delete
them. This could potentially result in an ever-increasing utilization of policy rows before the number of available rows
is exhausted.
• Existing SandScript policy could create rows in a policy table (more than once per policy evaluation), and then delete
them. However, the rate (condition) at which rows are created, depending on the condition or network conditions, could
result in the insertion of rows at a faster rate than they are deleted. If this condition continues long enough, eventually
the number of available rows is also exhausted.
In case of a file system, you should remove some files to free up space. Over provisioning of a system, or improper tuning of
software, are typical causes of resource issues.
05-00262 C07
PTS Alarms
Profile Description
• Minor
Raise Notification svSystemResourceAllocationFailureNotification
Clear Notification svSystemResourceNoAllocationFailureNotification
Triggers hrStorageResourceAllocation<n>
Unique Instance Identifier • HOST-RESOURCES-MIB:hrStorageIndex
• SANDVINE-RESOURCES-MIB:svHrStorageIndex
3.34.1 Exhausted Resource

MIB SANDVINE-MIB
Trap Name svSystemResourceAllocationFailureNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.13

svSeverity 1.3.6.1.4.1.11610.6799.1.10
HOST-RESOURCES-MIB:hrStorageAllocationFailure 1.3.6.1.2.1.25.2.3.1.7
3.34.1.1 Exhausted Resource

This notification is sent to indicate that hrStorageAllocationFailures (64-bit counter) exceeds value 10 within an interval of 8
seconds.
Profile Description
Frequency 8 seconds
Severity Minor
Condition DELTA (HOST-RESOURCES-MIB::hrStorageAllocationFailures) > 10
05-00262 C07
PTS Alarms
3.34.2 Exhausted Resource Cleared

MIB • SANDVINE-MIB
• SANDVINE-RESOURCES-MIB
Trap Name svSystemResourceNoAllocationFailureNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.14

svSeverity 1.3.6.1.4.1.11610.6799.1.10
HOST-RESOURCES-MIB:hrStorageAllocationFailure 1.3.6.1.2.1.25.2.3.1.7
3.34.2.1 Exhausted Resource Cleared—Clear

This notification is sent when individual resource allocation failures have not increased in an interval of 1 hour
Profile Description
Frequency 1 hour
Severity Cleared
Condition DELTA (HOST-RESOURCES-MIB::hrStorageAllocationFailures) == 0
Possible Instances include:

Note:
For example:
ID Description Applicability
2 Real memory SPB 5.4 and all PTS releases.
3 Swap space All SPB and PTS releases.
4 Mbuf custers All SPB and PTS releases.
5* Packet memory All PTS releases.
6 Filesystem / All SPB and PTS releases.
7 Filesystem /d2 All SPB and PTS releases.
05-00262 C07
PTS Alarms
8 File descriptors All SPB and PTS releases.
9 Filesystem /d3 All SPB releases.
18 Kernel address space All SPB and PTS releases.
19 Kernel memory All SPB and PTS releases.
20 * PTS Flows All PTS releases.
21 * PTS Subscribers All PTS releases.
22 DNS Users All PTS releases.
23 PTS Subscriber stats counters All PTS releases starting with PTS 5.5.
24 NPU MacVlan table space All PTS releases starting with PTS 5.2 and the PTS 14000 only.
31 WDTM Detection Session All PTS releases starting with PTS 5.2.
32 WDTM Detection Session (on All PTS releases starting with PTS 5.2.
CND)
33 WDTM Attack Object All PTS releases starting with PTS 5.2.
34 * Attribute strings All PTS releases starting with PTS 5.4.
35 * PTS shaping memory All PTS releases starting with PTS 5.4.
36 * PTS level distribution instances All PTS releases starting with PTS 5.4 and all PTS platforms.
37 * PTS tee header entries All PTS releases starting with PTS 5.4.
38 * PTS or SDE measurement All PTS releases starting with PTS 5.2 and the SDE 6.2.
instances
39 PTS shaping packets All PTS releases starting with PTS 5.4.
40 * Ipusermap webservices queue PTS 5.40.05
41 * Ipusermap radius queue PTS 5.40.05
42 * PTS demographic stats hosts All PTS releases starting with PTS 5.5.
43 * PTS or SDE classifier instances All PTS releases starting with PTS 5.5 and the SDE 6.2.
44 * PTS or SDE SandScript table row All PTS releases starting with PTS 5.5 and the SDE 6.2.
memory
45 * TCP Reassembly Buffering All PTS releases starting with PTS 5.5.
46 * Stream Analysis Buffering All PTS releases starting with PTS 5.5.
47 NPU Diverted Source table space Packets between a new pair of MACs are not inspected.
48 NPU Layer 2 Rewrite table space Packets between a new pair of MACs are not inspected.
49 NPU Layer 3 Hairpin table space New layer 3 hairpin destinations are not configured.
50 * Total Memory Possible application failure/exit if usage continues to increase.
51 * PTS or SDE Map instances All PTS releases starting withPTS 5.51.08 and the SDE 6.2.
52 * PTS Streaming Flows All PTS releases starting withPTS 5.51.09.
53 * PTS Primed Flow Classification All PTS releases starting with PTS 5.40.08_4.
instances
55 * PTS IP Fragmentation Records All PTS releases starting with PTS 5.60.02.
54 * PTS Largest Flow Classification All PTS releases starting with PTS 5.40.08_4.
Container
55 * PTS IP Fragmentation Records All PTS releases starting with PTS 5.60.02.
05-00262 C07
PTS Alarms
56 * External MAC address table All PTS releases starting with PTS 5.51.13.
57 Spam Detector SMTP Host State All PTS releases starting with PTS 5.60.03.
58 WDTM detection user All PTS releases starting with PTS 5.60.08.
59 * Statistic Records All PTS releases starting with PTS 6.00.
61 Reassembly Buffers (Small) All PTS releases starting with PTS 6.00.
62 Reassembly Buffers (Medium) All PTS releases starting with PTS 6.00.
63 Reassembly Buffers (Large) All PTS releases starting with PTS 6.00.
64 * RTMP Streaming Flows All PTS releases starting with PTS 6.00
68 * HTTP Streaming Flows HTTP stream analyzer will not analyze some flows. Stream PAL fields for
those flows are null.
70 * PTS Policy Controller Server New unique by values passed to the policy controller longer create new control
memory systems. This results in a shaper rate of the configured maximum for this
unique by instance.
71 * PTS Policy Controller Client New unique by values passed to the policy controller on the current PTSD no
memory longer creates new control systems. If there is traffic for these unique by
instances on other PTSDs then there is little or no impact. If on the other hand,
all traffic for the given unique by instance is seen at this module, then this
results in a shaper rate of the configured maximum for this unique by instance.
72 BGPD subnets Some of the BGP subnet information may be dropped. Data used for traffic
reports may not be completely accurate.
73 BGPD RIB memory Some of the BGP subnet information may be dropped. Data used for traffic
reports may not be completely accurate.
74 BGP Client RIB memory Some of the BGP subnet information were dropped and this means that data
used for traffic reports is not completely accurate.
75 PTS policy table row memory Indicates that the SandScript defined policy tables require more memory than
the system currently lets them use. As a result, a row was not created in the
table. When a row is not created in a table, any values that should be stored
in it, and accessed in subsequent policy runs, are not available. Any business
logic deployed in SandScript that depends on the presence of a table row will
fail, and the SandScript is not applied as expected.
78 Dynamic Shunted Subnets Indicates that the database used to store subnets shunted for the IP Overload
Management features is nearly full. If the PTS cannot insert entries into this
database, additional abusive2 IP addresses that the PTS detects are not
shunted. This has the potential to impact inspection and the subscriber
experience.
79 Subscriber NAT Mappings Indicates that the system has reached the maximum supported number of
subscriber network-address-translation (NAT) mappings. As a result of this
condition, subscriber-aware policies cannot associate traffic to the transmitting
subscriber and, consequently, will under-count usage and otherwise treat
traffic as though its subscriber is unknown.
80 PTS Map Entries Reports the number of policy map entries that SandScript has loaded. When
the alarm is raised, it indicates that an attempt to reload a policy map has
failed because the number of map entries that the policy engine needs to load
the map is larger than the number of entries that the policy engine can use
without affecting other portions of the system. As a result, SandScript continues
to run with the contents of the map that were loaded prior to the attempt to
reload the map.
2 The PTS module (PTSM) samples packets and generates per-user stats. Users that cross the threshold for new flow rate, packet rate, or bit rate, are reported
as 'abusive'. When a drop occurs, the load balancer shunts a number of abusive IPs on the associated module
05-00262 C07
PTS Alarms
81 Central LB Table Rows Indicates that the table used to load-balance IPv4 addresses is nearly full. If
the PTS cannot find an entry in this table for a subscriber IP, it shunts packets
with that subscriber IP. Shunted packets are not inspected, meaning that the
PTS will not apply policy to them, nor will it count them beyond shunt statistics.
82 Subscriber Cache Tracks the number of subscribers allocated in the Subscriber Management
subsystem on the SDE.
84 PTS packet usage by all policy Tracks utilization of memory buffers available for queuing and delaying packets.
actions This is a subset of the total packet buffers in the system, but only a subset of
these are queued or delayed.
89 PTS detector memory Tracks the amount of memory that the Network Protection Detector Subsystem
uses on the PTS.
90 Mitigation Rules Tracks the number of mitigation rules issued to the Mitigation Rule Engine.
3.34.3 Exhausted Resource - Minor

This notification is sent if one of the system resources in the hrStorageTable has had allocation failures.
This typically happens because the capacity is exhausted. In case of a file system, remove unnecessary files to free up space.
Over provisioning of a system, or improper tuning of software, are the typically causes of other types or resource issues.
Alarm Model 7 is raised if a resource in the hrStorageTable has encountered allocation errors.
Run the show system resources command to view overall capacity for the system and the number of allocation errors.
However, in a multi-module system it is very likely that one module in particular is encountering the allocation errors.
Run the command to determine the exact module, run:
show system resources module [id]
Look for allocation errors for the resource in question on each module.
Note:
The capacity used for alarms is an aggregate sum across all modules, so an allocation error may occur on a single module
and raise the minor alarm even though no warning alarm was ever raised for the capacity for the resource.

The impact of allocation errors depends on the resource in question. The impact is similar to the list included for the warning
level alarm, with the likelihood of impact increased significantly once allocation errors occur.
Note:
For example:
2 Real memory Possible application failure/exit if usage continues to increase.
05-00262 C07
PTS Alarms
3 Swap space Possible application failure/exit if usage continues to increase.
4 Mbuf clusters Data packets may begin to drop if usage continues to increase. This does not apply to the
SDE.
5 Packet memory Packets may begin to drop if usage continues to increase. This does not apply to the SDE.
6 Filesystem / Log files, core files, etc., are lost if usage continues to increase.
7 Filesystem /d2 Log files, core files, etc., are lost if usage continues to increase.
8 File descriptors Applications may start to fail if usage continues to increase. This does not apply to the SDE.
9 Filesystem /d3 Report data will be lost if usage continues to increase.
10 Filesystem /d2
18 Kernel address space Possible system failure will result if usage continues to increase. This does not apply to the
SDE.
19 Kernel memory Possible system failure will result if usage continues to increase. This does not apply to the
SDE.
20 * PTS Flows Packet inspection will cease if usage continues to increase. This does not apply to the SDE.
21 * PTS Subscribers Packet inspection will cease if usage continues to increase. This does not apply to the SDE.
22 DNS Users Packet inspection will cease if usage continues to increase. This does not apply to the SDE.
23 PTS Subscriber stats User bandwidth detection can miss some abusers. This does not apply to the SDE.
counters
24 NPU MacVlan table Inspection of packets with new MAC or VLAN ID will cease if usage continues to increase.
space This does not apply to the SDE.
31 WDTM Detection Packet inspection will cease if usage continues to increase. This does not apply to the SDE.
Session
32 WDTM Detection Packet inspection will cease if usage continues to increase. This does not apply to the SDE.
Session (on CND)
33 WDTM Attack Object Packet inspection will cease if usage continues to increase. This does not apply to the SDE.
34 * Attribute strings String attributes are not set (have NULL values); SandScript may not perform as expected.
This does not apply to the SDE.
35 * PTS shaping memory Packet inspection will cease if usage continues to increase. This does not apply to the SDE.
36 * PTS level distribution Shaping and Session Management may not function correctly; the PTS could possibly shape
instances too much and/or limit too many flows (resulting in dropped packets). This does not apply to
the SDE.
37 * PTS tee header entries Teeing may not function correctly (destinations may not see all expected packets). This does
not apply to the SDE.
38 * PTS or SDE Measured statistics may be inc accurate or not collected altogether for certain instances.
measurement instances
39 PTS shaping packets Packets may drop if usage continues to increase. This does not apply to the SDE.
40 * Ipusermap webservices RADIUS and/or DHCP packets (sub-ip mapping) may drop and not reach SPB if usage
queue continues to increase. This does not apply to the SDE.
05-00262 C07
PTS Alarms
41 * Ipusermap RADIUS RADIUS and/or DHCP packets (sub-ip mapping) may drop and not reach SPB if usage
queue continues to increase. This does not apply to the SDE.
42 * PTS demographic stats Inaccurate host reports will appear in Network Demographics. This does not apply to the
hosts SDE.
43 * PTS or SDE classifier Classifiers will not be assigned to the correct value and measurements/limiters/shapers
instances unique by classifiers will not have all the correct instances.
44 * PTS or SDE SandScript SandScript logic that uses tables will not function as expected.
table row memory
45 * TCP Reassembly Analysis of TCP flows for the purposes of populating Flow. Stream fields in SandScript will
Buffering cease, leaving those fields unpopulated. This does not apply to the SDE.
46 * Stream Analysis Analysis of any analyzed flows for the purposes of populating Flow. Stream fields in
Buffering SandScript will cease, leaving those fields unpopulated. This does not apply to the SDE.
47 NPU Diverted Source Packet inspection between a new pair of MACs will cease. This does not apply to the SDE.
table space
48 NPU Layer 2 Rewrite Packet inspection between a new pair of MACs will cease. This does not apply to the SDE.
table space
49 NPU Layer 3 Hairpin New layer 3 hairpin destinations are not configured. This does not apply to the SDE.
table space
50 * Total memory
51 * PTS or SDE Map All SandScript defined maps have a 40Mb limit applied to total memory use. Although you
instances can override this limitation, dropped packets will result from setting it too high.
52 * PTS Streaming Flows The TCP stream analyzer will not analyze some flows. Stream SandScript fields for those
flows are null. This does not apply to the SDE.
53 * PTS Primed Flow New primes are rejected. New flows are misclassified and SandScript is not applied.
Classification instances
54 * PTS Largest Flow New primes for certain src/dest ips are rejected. New flows may be misclassified and
Classification Container SandScript is not applied.
55 * PTS IP Fragmentation If usage continues to increase, IP fragments are not re-assembled, and flows with fragmented
Records traffic are not inspected.
56 * External MAC address Some packets will bypass packet inspection, SandScript, and reporting.
table
57 * Spam Detector SMTP This does not apply to the SDE.
Host State
58 WDTM detection user WDTM SandScript does not affect additional user. This does not apply to the SDE.
59 * Statistic Records Statistic records are not published to the SPB.
61 * Reassembly Buffers ( Some IP fragmented flows are not inspected. This does not apply to the SDE.
Small)
Medium)
Large)
05-00262 C07
PTS Alarms
64 * RTMP Streaming Flows The RTMP stream analyzer will not analyze some flows. Stream SandScript fields for those
flows are null. This does not apply to the SDE.
68 * HTTP Streaming Flows The HTTP stream analyzer will not analyze some flows. Stream SandScript fields for those
flows are null.
72 BGPD subnets Some of the BGP subnet information may be dropped. Data used for traffic reports may not
be completely accurate.
73 BGPD RIB memory Some of the BGP subnet information may be dropped. Data used for traffic reports may not
be completely accurate.
74 BGP Client RIB memory Some of the BGP subnet information were dropped and this means that data used for traffic
reports is not completely accurate.
75 * PTS or SDE SandScript SandScript policy applications may have inconsistent behavior like incorrect measurement
table row memory increments.
82 Subscriber cache The subscriber subsystem is not able to add new subscribers.
83 Session storage The session subsystem is not able to add new sessions.
Suggested resolutions depend on the resource ID. Note the IDs previously referenced as used on both the PTS and Virtual PTS
platforms.:
ID Description Resolution
2 Real memory Check the configuration for over-provisioning.
3 Swap space Check that device is not over-provisioned. Also check to see if any application on the modules
in question has used an exceedingly large amount of memory, which could indicate a
misconfiguration, over-provisioning, or software error that has been exposed. Run the show
system processes CLI command to identify the memory usage for processes on each
module.
4 Mbuf clusters Check the configuration for over-provisioning
5 Packet memory Check the configuration for over-provisioning
6 Filesystem / Run the du command to search the filesystem for large files. Clear out those files that are no
longer needed.
7 Filesystem /d2 Run the du command to search the file-system for large files. Clear out those files that are no
longer needed.
8 File descriptors Use fstat to determine if any processes have an unusually large number of open files.
18 Kernel address space Check the configuration for over-provisioning.
19 Kernel memory Check the configuration for over-provisioning.
20 PTS Flows Check the configuration for over-provisioning.
21 PTS Subscribers Check the configuration for over-provisioning.
22 DNS Users Check the configuration for over-provisioning.
23 PTS Subscriber stats Check the configuration for over-provisioning.
counters
05-00262 C07
PTS Alarms
24 NPU MacVlan table Check the deployment model. Try to either:
space • Reduce the number of VLAN ID used in the network.
• Use the 2 port bridge-group deployment mode exclusively.
31 WDTM Detection Session Check the configuration for over-provisioning.

32 WDTM Detection Session Check the configuration for over-provisioning.
(on CND)
33 WDTM Attack Object Check the configuration for over-provisioning.
34 Attribute strings Consider simplifying SandScript to use fewer string attributes.
35 PTS shaping memory Check the configuration for over-provisioning.
36 PTS level distribution Do not use level distribution when shaping or limiting unique by something that has a large
instances number of instances cluster wide (i.e. subscribers). Consider load balancing by the thing you
are shaping or limiting unique by and disabling level distribution.
37 PTS tee header entries Figure out where there is an overlap of three or more tee actions and resolve in SandScript.
38 PTS or SDE Consider the size of the sets used in your SandScript's measurement unique-by specs. If the
measurement instances sets are large (for example, measurement unique by subscriber), consider removing some of
these measurements from SandScript and/or using measurements with fewer unique instances.
39 PTS shaping packets Check the configuration for over-provisioning.
40 Ipusermap webservices Verify the tee/ipusermap policy.
queue
41 Ipusermap RADIUS Verify the tee/ipusermap policy.
queue
42 PTS demographic stats Verify that network classes are properly configured. This is typical the result of including too
hosts many IP addresses in an 'internal' network class. You should also ensure that counting of
external hosts is disabled.
43 PTS or SDE classifier Consider the number of different values assigned to the classifiers in SandScript. For classifiers
instances that can take on a broad range of values (for example, the client IP address), find a way to
reduce the number of distinct values the classifier can take on.
44 PTS or SDE SandScript Consider the size of the sets used in your SandScript table unique-by specs, and how often
table row memory you are writing to a table row. Find a way to reduce the number of rows you need to persist to
a SandScript table.
45 TCP Reassembly Check the configuration for over-provisioning. Check the configuration for a scenario that could
Buffering prevent the routing of a large number of packets of every flow, through the PTS.
46 Stream Analysis Buffering Check the configuration for over-provisioning. Check the configuration for a scenario that could
prevent the routing of a large number of packets of every flow, through the PTS.
47 NPU Diverted Source Check the deployment model. Try to have traffic flowing between fewer distinct Layer 2
table space destinations.
48 NPU Layer 2 Rewrite Check the deployment model. Try to have traffic flowing between fewer distinct Layer 2
table space destinations.
49 NPU Layer 3 Hairpin Configure less layer 3 hairpin destinations.
table space
50 Total memory Check the configuration for over-provisioning.
05-00262 C07
PTS Alarms
51 PTS or SDE map Check the SandScript maps entries configured and remove entries from them to reduce the
instances memory usage to below 40 Mb.
52 PTS Streaming Flows Verify that the PTS is not overloaded.
53 PTS Primed Flow Check the configuration for over-provisioning.
Classification instances
54 PTS Largest Flow Check the configuration for over-provisioning.
Classification Container
55 PTS IP Fragmentation Check the configuration for over-provisioning.
Records
56 External MAC address • Switch to Layer 2 mode.
table
• Review external switch configuration to reduce number of Ethernet MAC addresses passing
through the PTS cluster.
• Add more PTS devices to the cluster.
57 Spam Detector SMTP Check the configuration for over-provisioning.

Host State
58 WDTM detection user Check the configuration for over-provisioning and adjust the WDTM SandScript as necessary.
59 Statistic Records Verify that the PTS is connected to the SPB, and that the SPB is properly configured to accept
messages from the PTS.
61 Reassembly Buffers ( Check the configuration for over-provisioning.
Small)
Medium)
Large)
64 RTMP Streaming Flows Check the configuration for over-provisioning.
68 HTTP Streaming Flows Check the configuration for over-provisioning.
72 BGPD subnets Increase the BGP subnet limit using the set config service bgp subnet-limit CLI
command. If the maximum limit is reached, then apply filters on the peer routers to filter the
BGP subnet information that is sent to the element.
73 BGPD RIB memory Increase the BGP subnet limit using the set config service bgp rib-memory limit
CLI command. If the maximum limit is reached, then apply filters on the peer routers to filter
the BGP subnet information that is sent to the element.
74 BGPD client RIB memory Increase the BGP subnet limit using the set config service bgp rib-memory limit
CLI command. If the maximum limit is reached, then consider applying filters on the peer routers
to filter the BGP subnet information that is sent to the element.
75 PTS policy table row SandScript policy applications may have inconsistent behavior like incorrect measurement
memory increments. Sandvine recommends that you investigate and modify system capacity parameters
to support your policy memory requirements.
05-00262 C07
PTS Alarms
Alarm Model 36: Faulted Form-factor Pluggable Module
82 Subscriber cache • Check the statistics and remove some subscribers so that the total number of active
subscribers reduces to 80% of the maximum subscribers configured.
• Configure the SDE to allow more subscribers.
• If the SDE is configured to the maximum, consider installing another SDE.
83 Session storage • Configure the SDE to allow more sessions.

• If the SDE is configured to the maximum, consider installing another SDE.
Additional PTS Information

These files define alarms, triggers, and events for Exhausted Resource Alarm Model 35:
/usr/local/sandvine/etc/alarms/lowResource.alarm.conf
/usr/local/sandvine/etc/events/events.hrStorage.conf
3.35 Alarm Model 36: Faulted Form-factor

Pluggable Module
This alarm is raised when a front panel slot is not capable of intersecting traffic due to an issue with the associated Form-factor
pluggable module. The notification contains the port name of the interface containing the module, the current administrative status
of that interface, and the operational status of that module.
Note:
Alarm Model 36 (Faulted Form-factor Pluggable Module) is not supported on the PTS Linux platform.
Profile Description
Raise Notification svSysIfModuleError
Clear Notification svSysIfModuleOk
Triggers • FpModuleStatusFaultTrigger
• FpModuleStatusClearTrigger
Unique Instance identifier svModulesFpStatusTablePortName
Note:
The Form-factor pluggable module is referred to as module, throughout this section.
3.35.1 Faulted Form-Factor Pluggable Module—Major

This notification is sent if there is a problem with the module.

MIB SANDVINE-MIB
05-00262 C07
PTS Alarms

Trap Name svSysIfModuleError
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.15

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svModulesFpStatusTableAdminStatus 1.3.6.1.4.1.11610.435.10470.1.50.1.1.3
svModulesFpStatusTablePortName 1.3.6.1.4.1.11610.435.10470.1.50.1.1.1
svModulesFpStatusTableFpOperStatus 1.3.6.1.4.1.11610.435.10470.1.50.1.1.9
3.35.1.1 Module Faulted Error—Major

This notification is sent if there is a hardware problem detected with the module.
Profile Description
Severity Major
Condition SANDVINE-MIB::svModulesFpStatusTableAdminStatus ==1(up) && SANDVINE-MIB::svModulesF
pStatusTableFpOperStatus == 1(up) (equal to 3 Faulted)
3.35.1.2 Module Not-Present Error—Major

This notification is sent if the module is removed while the AdminStatus is up. The alarm is not triggered if you remove the module
while the AdminStatus is down.
Profile Description
Severity Major
pStatusTableFpOperStatus ! = 1(up) (equal to 6 NotPresent)
3.35.1.3 Module Incompatible-Config Error—Major

This notification is sent when the module does not support the medium configured on the front panel slot.
Profile Description
Severity Major
Condition SANDVINE-MIB::svModulesFpStatusTableAdminStatus ==1(up) && SANDVINE-MIB::FpOperStat
us != 1(up) (equal to 5 IncompatibleMedium)
05-00262 C07
PTS Alarms
3.35.1.4 Module Unsupported-Power-Class Error—Major

This notification is sent whenever the PTS does not support the PowerClass that the module requires.
Profile Description
Severity Major
Condition SANDVINE-MIB::svModulesFpStatusTableAdminStatus ==1(up) && SANDVINE-MIB::FpOperStat
us != 1(up) (equal to 7 UnsupportedPowerClass)
3.35.1.5 Module Incompatible-Module Error—Major

This notification is sent when none of the mediums supported by the module is supported by the front panel slot.
Profile Description
Severity Major
Condition SANDVINE-MIB::svModulesFpStatusTableAdminStatr_mous ==1(up) && SANDVINE-MIB::
FpOperStatus != 1(up) (equal to 9 IncompatibleModule)
3.35.2 Faulted Form-Factor Pluggable Module—Clear

This notification is sent when a problem with the module is resolved.

MIB SANDVINE-MIB
Trap Name svSysIfModuleOk
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.16

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svModulesFpStatusTableAdminStatus 1.3.6.1.4.1.11610.435.10470.1.50.1.1.3
svModulesFpStatusTablePortName 1.3.6.1.4.1.11610.435.10470.1.50.1.1.1
svModulesFpStatusTableFpOperStatus 1.3.6.1.4.1.11610.435.10470.1.50.1.1.9
3.35.2.1 Module OK—Clear

This notification is sent whenever:
• The module has recovered from its bad state (unplugged or faulted).
• The interface was brought down administratively.
• The interface supports the configured medium.
05-00262 C07
PTS Alarms
Profile Description
Severity Clear
pStatusTableFpOperStatus == 1(up)) || SANDVINE-MIB::svModulesFpStatusTableAdminStatus
== 2(down)

This section provides the impact and resolution steps for Alarm Model 36.
Impact of Alarm 36
The external port exhibiting a failure is shut down with the possibility of a lost link or, possibly, a smaller number of drops. Due
to loss of link, Alarm Model 14 (Network Interface Down) can also occur with this alarm.
Suggested Resolution Steps for Alarm Model 36
1. Run the show interface modules CLI command to determine the operational status of the module.
The output of this command gives the statuses of the modules (ModuleStatus) on the front panel slot. See show
interface modules in the PTS CLI Reference Guide for additional information.
2. For a module reporting a ModuleStatus of faulted, perform these resolution steps:

• Verify that the module is fully inserted into the interface.
• Remove the module and inspect it for physical damage. If none is found, replace the module and check to see if this
clears the alarm.
Note:
The faulted module status is reported when the module cannot be initialized properly or there is a communication
failure with the module.
3. For a module reporting a ModuleStatus of unsupported-power-class, replace the module with one of lower power
requirements. Contact Sandvine Technical Support or its authorized partner, for assistance.
Note:
The unsupported-power-class status is reported when the module inserted exceeds the maximum power class
that the PTS front panel port supports. When the power class of the module exceeds the maximum supported power
class, the system forces the module into low power state. In this state, the data interface of the module is non-functional
but the management interface remains responsive.
4. For a module reporting a ModuleStatus of incompatible-config, run these CLI commands to determine whether the
module supports the medium configured on the external slot:
PTS> show interface medium

PTS> show interface modules
Note:
The incompatible-config status is reported when the medium type of the module does not match the medium
configuration set for the interface. See show interface modules in the PTS CLI Reference Guide for additional
information.
Example:
05-00262 C07
PTS Alarms
Alarm Model 37: Faulted Blade
This example shows how to determine the supported medium configurations and medium types on the external slot ports
of a PTS 32000 with BLD 32080.
Run the show interface medium 5-5 CLI command to view the supported medium configurations for SlotPort 5-5:
SlotPort : 5-5
Supported: none, 10gigabit-ethernet
Active : [10gigabit-ethernet]
Related : 3-11, 3-31
SubPorts : 5-5, 5-6, 5-7, 5-8
From the command ouput, the supported medium configurations for 5-5 are none or 10gigabit-ethernet.
Run the show interface modules 5-5 CLI command to view the supported medium types for SlotPort 5-5.
VENDOR INFORMATION
==================
VendorName : XYZVendorOUI : 00005f
VendorRevision: A
PartNumber : SQF0406L4LNGL
---------
-----
---
SupportedMedia : 40GBASE-LR4
From the command output, the supported medium type is 40GBASE-LR4, which implies that SlotPort 5-5 may not support
10GBASE medium types.
Compare this with the output for a different module (say 2-13) which supports 40 GigE and 10 GigE medium types.
For example,
PTS> show interface modules 2-13
VENDOR INFORMATION
==================
VendorName : ABC
VendorOUI : 447c7f
VendorRevision: 1B
------
----
CAPABILITIES INFORMATION
========================
-----
SupportedMedia : 40G-PSM4 Parallel SMF, 10GBASE-LR
5. For a module reporting a ModuleStatus of incompatible-module, replace the module with a supported module as
specified in the PTS Hardware Installation Guide.
6. If none of these steps clear the alarm, contact Sandvine Technical Support or its authorized partner, for additional information
on the port itself.
3.36 Alarm Model 37: Faulted Blade

The alarm indicates that PTS has detected a faulty blade. This alarm is raised to report a blade that cannot be used for data
intersection in its current operational state.
Note:
Alarm Model 37 (Faulted Blade) is not supported on the PTS Linux platform.
05-00262 C07
PTS Alarms
Profile Description
• Minor
• Clear
Raise Notification svEnvBladeFault

Minor Notification svEnvBladeFault
Clear Notification svEnvBladeNoErr
Triggers inactiveOrFaultedBlade
Unique Instance identifier svBladesBladeSlot
3.36.1 Faulted Blade—Major

This notification is sent when the blade is faulted and requires immediate attention. This notification indicates that the blade is
drawing too much current or a previously operational blade was removed during system operation.
Profile Description
Frequency 8 seconds
Severity Major
Condition SANDVINE-MIB::svBladesBladeOperStatus == 6 (faulted)

MIB SANDVINE-MIB
Trap Name svEnvBladeFault
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.19

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svBladesBladeSlot 1.3.6.1.4.1.11610.435.10470.1.60.100.1.2.1.1
svBladesBladeOperStatus 1.3.6.1.4.1.11610.435.10470.1. 60.100.1.5.1.1
When this notification is raised, to prevent damage to the blade and the PTS, shut down the power to the blade and disable all
of its functionality. However, the serial number and blade model should still be available through the show system blades
CLI command. The most likely cause of this condition is that there is a short circuit on the blade due to a manufacturing defect,
and it was shut down because it was drawing too much current.
05-00262 C07
PTS Alarms
3.36.2 Inactive Blade—Minor

The minor notification indicates that the blade is newly installed and requires a power cycle of the PTS to be enabled. This
notification also indicates that a blade was plugged in after the PTS was powered on.
The output of the show system blades CLI command should indicate that the blade is inactive, but the blade's serial number
and model are still available. No other blade features, including the network interfaces, are activated.
Profile Description
Frequency 8 seconds
Severity Minor
Condition SANDVINE-MIB::svBladesBladeOperStatus == 3 (inactiveBlade)

MIB SANDVINE-MIB
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.19

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
3.36.3 Faulted Blade—Clear

This notification is sent if the blade is no longer inactive. This notification indicates that either the fault status has been cleared
or the blade has been removed from the system.

MIB SANDVINE-MIB
Trap Name svEnvBladeNoErr
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.20

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
05-00262 C07
PTS Alarms

3.36.3.1 Blade is up—Clear

This notification is sent when a properly installed blade is powered up. For an inactive blade, this occurs after the PTS is rebooted.
Profile Description
Frequency 8 seconds
Severity Clear
Condition SANDVINE-MIB::svBladesBladeOperStatus == 0 (okBlade)
3.36.3.2 Blade is not installed—Clear

This notification is sent when a blade that was previously inactive is removed from the system.
Profile Description
Frequency 8 seconds
Severity Clear
Condition SANDVINE-MIB::svBladesBladeOperStatus == 2 (notInstalled)

The blade is not working.
3.36.4.1 Minor Alarm

A minor alarm indicates that this blade was added to a running system.
1. Reboot the PTS to allow the system to use the blade.
Note:
When installing some of the blade types, a power cycle may be required in the PTS. See Adding and Replacing Blades
in the PTS Hardware Installation Guide, for additional information.
When the system comes online, the alarm should no longer be present.
2. Verify that the blade is functioning. Run the show system blades CLI command.
3.36.4.2 Major Alarm

A major alarm indicates that the system has removed power from the blade to protect itself.
1. Run the show system blades CLI command to identify the faulted blade.
2. Run the shutdown CLI command to shut down the system.
3. Remove the malfunctioning blade.
05-00262 C07
PTS Alarms
Alarm Model 38: Diameter Error
4. Check for any obvious damage to the power connector.

• If no damage is detected, try to reinsert the blade, then power up the system. If the alarm persists, the blade must be
replaced.
• If damage is detected, contact Sandvine Support and replace the blade.
3.37 Alarm Model 38: Diameter Error

This alarm is raised when there is a general Diameter error. These errors can include:
• Outgoing rate too high.
• Early age threshold reached for incoming message.
• Incoming message dropped.
• Age threshold exceeded for incoming message.
• Outgoing message dropped.
• Incoming rate too high.
• Incoming rate reached threshold.
• Outgoing rate reached threshold.
There is no CLI command to display the Diameter errors on the element, although they do appear through SNMP:
> snmptable -v2c -cpublic localhost SANDVINE-MIB::svDiameterStatsDiameterAlarmsTable
SNMP table: SANDVINE-MIB::svDiameterStatsDiameterAlarmsTable
svDiameterStatsDiameterAlarmsName svDiameterStatsDiameterAlarmsCount
Early age threshold reached for incoming message 0
Incoming message dropped 0
Age threshold exceeded for incoming message 0
Outgoing message dropped 0
Outgoing rate too high 0
Incoming rate too high 0
Incoming rate reached threshold 0
Outgoing rate reached threshold 0
Profile Description
• Clear
Raise Notification svDiameterErrorNotification
Clear Notification svDiameterNoErrorNotification
Trigger diameterErrorTrigger
3.37.1 Unknown Diameter Session ID Error—Raise

This notification is sent for one of the Diameter error instances, if the counter has increased at all.

MIB SANDVINE-MIB
Trap Name svDiameterUnknownSessionNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.3
05-00262 C07
PTS Alarms
Alarm Model 38: Diameter Error

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsDiameterAlarmsName 1.3.6.1.4.1.11610.435.15450.1.3.115.100.1.2
svDiameterStatsDiameterAlarmsCount 1.3.6.1.4.1.11610.435.15450.1.3.115.100.1.3
3.37.2 Diameter Error—Clear

This notification is sent when the counter stops increasing for an hour or more.
Note:
It may take 1-2 hours for the alarm to clear.

MIB SANDVINE-MIB
Trap Name svDiameterNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.4

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10

The impact is different for each alarm instance.
Condition Name Possible Cause

Outgoing rate too high Dropped outgoing Diameter messages.
Incoming rate too high The incoming message receive rate is throttled resulting in dropped Diameter
messages.
Outgoing message dropped Dropped outgoing Diameter messages.
Incoming message dropped Dropped incoming Diameter messages.
Early age threshold reached for incoming Age of the incoming messages reached the configured early threshold. Possible
message cause is that the local Diameter peer is busy.
Age threshold exceeded for incoming Incoming messages are dropped.
message
05-00262 C07
PTS Alarms
Alarm Model 39: Diameter Server Outgoing Message Age Exceeded Maximum Threshold
Condition Name Possible Cause

Incoming rate reached threshold Dropped incoming Diameter messages.
Outgoing rate reached threshold Dropped outgoing Diameter messages.
The suggested resolutions for each instance of the alarm are:
Condition Name Resolution

Outgoing rate too high Adjust either outgoing Diameter message rate or configured limit for outgoing
message rate.
Incoming rate too high Adjust either incoming Diameter message rate or configured limit for incoming
message rate.
Outgoing message dropped An increase in the OutgoingDroppedCreationFailures is responsible for
Outgoing message dropped alarm.
Run the show service diameter messages detail CLI command.
Note:
Ensure the diameter max-message-size is configured with the recommended
value.
Incoming message dropped Run the show service diameter messages detail CLI command.
Early age threshold reached for incoming Reduce the load on the local Diameter node or adjust the configured value of early
message age threshold for incoming messages.
Age threshold exceeded for incoming Reduce the load on the local Diameter node or adjust the configured value of
message maximum age threshold for incoming messages.
Incoming rate reached threshold Try to adjust either incoming Diameter message rate or configured threshold limit
for incoming message rate.
Outgoing rate reached threshold Try to adjust either outgoing Diameter message rate or configured threshold limit
for outgoing message rate.
3.38 Alarm Model 39: Diameter Server Outgoing

Message Age Exceeded Maximum Threshold
This alarm is raised when the outgoing message age on a Diameter server exceeds the maximum threshold. It can occur on any
of the Diameter peers listed using the show service diameter peer server command.
Profile Description
• Clear
Raise Notification svDiameterServerMsgAgeNotification

Clear Notification svDiameterServerMsgAgeNoErrorNotification
05-00262 C07
PTS Alarms
Alarm Model 39: Diameter Server Outgoing Message Age Exceeded Maximum Threshold
3.38.1 Diameter Server Outgoing Message Age Exceeded Maximum

Threshold—Raise
This notification is sent when the age of an outgoing message reaches the maximum threshold.

MIB SANDVINE-MIB
Trap Name svDiameterServerMsgAgeNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.15

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsServerPeerLocalIdentity 1.3.6.1.4.1.11610.435.15450.1.3.109.101.1.2
svDiameterStatsServerPeerOutgoingExceededMaxAgeThres 1.3.6.1.4.1.11610.435.15450.1.3.109.101.1.29
hold
3.38.2 Diameter Server Outgoing Message Age Exceeded Maximum

Threshold—Clear
This notification is sent when no outgoing message reaches the maximum threshold within one minute.
Note:
It can take several minutes to clear this alarm.

MIB SANDVINE-MIB
Trap Name svDiameterServerMsgAgeNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.16

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsServerPeerOutgoingExceededMaxAgeThres 1.3.6.1.4.1.11610.435.15450.1.3.109.101.1.29
hold

Outgoing messages are dropped if this alarm condition continues to persist.
05-00262 C07
PTS Alarms
Alarm Model 40: Diameter Peer Failed Back Over
1. Run the show service diameter messages detail CLI command to check the Diameter message drops.
2. Determine if the local Diameter peer is overloaded.
3. Adjust the configured server's outgoing messages' maximum age threshold value.
3.39 Alarm Model 40: Diameter Peer Failed Back

Over
This alarm is raised when a Diameter peer fails over to the secondary peer. Run the show service diameter peer client
CLI command to identify the Diameter peers on which the alarm can occur.
Profile Description
• Clear
Raise Notification svDiameterPeerFailedOverNotification
Clear Notification svDiameterPeerFailedBackNotification
3.39.1 Diameter Peer Failed Back Over - Raise

This notification is sent when the Diameter peer fails over to the secondary peer.

MIB SANDVINE-MIB
Trap Name svDiameterPeerFailedOverNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.5

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsClientPeerFailedOver 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.14
3.39.2 Diameter Peer Failed Back Over—Clear

This notification is raised when the secondary peer fails back to primary peer.
05-00262 C07
PTS Alarms
Alarm Model 41: Diameter Server Connection with Client Peer Lost

MIB SANDVINE-MIB
Trap Name svDiameterPeerFailedBackNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.6

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsClientPeerFailedOver 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.14

If left to persist, messages destined to the primary peer are sent to its secondary Diameter peer.
1. Run these CLI commands to check for potential errors and discards:
show service diameter messages detail
show service diameter messages rate
2. Check:
a. That the remote primary Diameter peer is operational and reachable.
b. That the hostname of the remote primary Diameter peer is correct in diam_peer_config.xml.
c. Whether the Diameter local peer has sent any invalid message to the remote Diameter peer.
3.40 Alarm Model 41: Diameter Server Connection

with Client Peer Lost
This alarm is raised when a server loses a connection with a client peer. It can occur on any of the configured Diameter peers
that appear when you run the show service diameter peer server CLI command.
Profile Description
• Clear
Raise Notification svDiameterServerErrorNotification
Clear Notification svDiameterServerNoErrorNotification
05-00262 C07
PTS Alarms
Alarm Model 41: Diameter Server Connection with Client Peer Lost
3.40.1 Diameter Server Connection with Client Peer Lost—Raise

MIB SANDVINE-MIB
Trap Name svDiameterServerErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.7

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsServerPeerRemoteIdentity 1.3.6.1.4.1.11610.435.15450.1.3.109.101.1.27
svDiameterStatsServerPeerChildrenDestroyed 1.3.6.1.4.1.11610.435.15450.1.3.109.101.1.8
3.40.2 Diameter Server Connection with Client Peer Lost—Clear

This notification is sent when a server does not lose a connection with a client peer within an hour or more.
Note:
The actual time to clear may range between one and two hours.

MIB SANDVINE-MIB
Trap Name svDiameterServerNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.8

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsServerPeerRemoteIdentity 1.3.6.1.4.1.11610.435.15450.1.3.109.101.1.27
svDiameterStatsServerPeerChildrenDestroyed 1.3.6.1.4.1.11610.435.15450.1.3.109.101.1.8

If left to persist, messages destined to the remote Diameter client peer may be dropped.
1. Run the show service diameter peer server CLI command to review the Diameter peer server details.
2. Check if the:
a. Remote Diameter peer is operational and reachable.
05-00262 C07
PTS Alarms
Alarm Model 42: Diameter Client Outgoing Message Age Reached Early Threshold
b. Diameter local peer has sent any invalid message to the remote Diameter peer.
3.41 Alarm Model 42: Diameter Client Outgoing

Message Age Reached Early Threshold
This alarm is raised when the age of a clients outgoing message reaches the early threshold. Run the show service diameter
peer client CLI command to see the list of Diameter peers that this alarm can occur on.
Profile Description
Severities • Minor
• Clear
Raise Notification svDiameterClientEarlyAgeNotification
Clear Notification svDiameterClientEarlyAgeNoErrorNotification
3.41.1 Diameter Client Outgoing Message Age Reached Early

Threshold—Raise
This notification is sent when the age of a client's outgoing message reaches the early threshold.

MIB SANDVINE-MIB
Trap Name svDiameterClientEarlyAgeNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.9

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsClientPeerOutgoingExceededMaxAgeEarly 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.44
Threshold
3.41.2 Diameter Client Outgoing Message Age Reached Early

Threshold—Clear
This notification is sent when an outgoing message does not reach the early threshold within one minute.
05-00262 C07
PTS Alarms
Alarm Model 43: Diameter Client Outgoing Message Age Exceeded Maximum Threshold
Note:
The actual time to clear may range between one and two minutes.

MIB SANDVINE-MIB
Trap Name svDiameterClientEarlyAgeNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.10

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsClientPeerOutgoingExceededMaxAgeEarly 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.44
Threshold

Outgoing messages are dropped if this alarm is left to persist.
1. Run the show service diameter messages detail CLI command to view details.
2. Check whether:
a. The local Diameter peer is overloaded.
b. You need to adjust the configured outgoing message early age threshold value.
3.42 Alarm Model 43: Diameter Client Outgoing

Message Age Exceeded Maximum Threshold
This alarm is raised when the age of a client’s outgoing message reaches the maximum threshold.
This alarm can occur on any Diameter peer listed after running the show service diameter peer client CLI command.
Profile Description
• Clear
Raise Notification svDiameterClientMsgAgeNotification
Clear Notification svDiameterClientMsgAgeNoErrorNotification
05-00262 C07
PTS Alarms
Alarm Model 43: Diameter Client Outgoing Message Age Exceeded Maximum Threshold
3.42.1 Diameter Client Outgoing Message Age Exceeded Maximum

Threshold—Raise
MIB SANDVINE-MIB
Trap Name svDiameterClientMsgAgeNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.11

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsClientPeerOutgoingExceededMaxAgeThres 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.45
hold
3.42.2 Diameter Client Outgoing Message Age Exceeded Maximum

Threshold—Clear
This notification is sent when outgoing messages do not reach the maximum threshold within 1 minute.
Note:

MIB SANDVINE-MIB
Trap Name svDiameterClientMsgAgeNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.12

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsClientPeerOutgoingExceededMaxAgeThres 1.3.6.1.4.1.11610.435.15450.1.3.109.100.1.45
hold

Outgoing message are dropped if this alarm is left to persist.
1. Run the show service diameter messages detail CLI command to view details.
05-00262 C07
PTS Alarms
Alarm Model 44: Diameter Server Outgoing Message Age Reached Early Threshold
2. Check:
a. If the local Diameter peer is overloaded.
b. Adjust the configured client's outgoing messages maximum age threshold value.
3.43 Alarm Model 44: Diameter Server Outgoing

Message Age Reached Early Threshold
This alarm is raised when the age of a server's outgoing message reaches the early threshold. The Diameter server experiences
a lag in attempting to send messages to a client. This indicates that the client is experiencing issues or taking too long to process
messages.
Run the show service diameter peer server CLI command to identify that Diameter peers that this alarm occurs on.
Profile Description
• Clear
Raise Notification svDiameterServerEarlyAgeNotification
Clear Notification svDiameterServerEarlyAgeNoErrorNotification
3.43.1 Diameter Server Outgoing Message Age Reached Early

Threshold—Warning
This notification is sent when the age of a server's outgoing message reaches the early threshold.

MIB SANDVINE-MIB
Trap Name svDiameterServerEarlyAgeNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.13

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsServerPeerOutgoingExceededMaxAgeEarly 1.3.6.1.4.1.11610.435.15450.1.3.109.101.1.28
Threshold
05-00262 C07
PTS Alarms
Alarm Model 50: Unknown Diameter Session-ID
3.43.2 Diameter Server Outgoing Message Age Reached Early

Threshold - Clear
This notification is sent when none of the outgoing messages reach the early threshold within one minute.
Note:

MIB SANDVINE-MIB
Trap Name svDiameterServerEarlyAgeNoErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.14

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDiameterStatsServerPeerOutgoingExceededMaxAgeEarly 1.3.6.1.4.1.11610.435.15450.1.3.109.101.1.28
Threshold

Outgoing messages are dropped if this alarm is left to persist.
1. Run the show service diameter messages detail CLI command to check for potential errors and discards.
2. Check whether:
a. The local Diameter peer is overloaded.
b. You need to adjust the configured outgoing message early age threshold value.
3.44 Alarm Model 50: Unknown Diameter

Session-ID
This alarm is raised when there is an unsolicited request from the OCS in the Gy interface or from the PCRF in the Gx interface
to the PTS, with a Diameter session ID that is unknown to the PTS.
Profile Description
Severities Minor, Clear
Raise Notification svDiameterUnknownSessionNotification
05-00262 C07
PTS Alarms
Alarm Model 50: Unknown Diameter Session-ID
Profile Description
Clear Notification svDiameterNoUnknownSessionNotification
Trigger GxUnknownSessionsTrigger and GyUnknownSessionsTrigger
This alarm has these instances:

• Gy: when the varbind argument svMeasurementsIndex is 17899
• Gx: when the varbind argument svMeasurementsIndex is 17640.
3.44.1 Unknown Diameter Session ID Error- Minor

This notification is sent for one of the Diameter error instances if the counter has increased at all.
This notification indicates that an unsolicited request was sent from the OCS in the Gy interface, or PCRF in the Gx interface to
the PTS, with a session ID that is unknown to the receiving PTS. These request types are available in either interface:
• RAR—Re-Authorization Requests
• ASR—Abort Session Requests
Since unknown session IDs occur during regular operation, the alarm occurs only when more than 10,000 invalid IDs are detected
within a 10 minute interval. The alarm is cleared when fewer than 2,000 invalid IDs are detected within 10 minutes.
Invalid session IDs occur at these times:
• RAR/ASR—just before logout. These requests should not affect operations.
• After PTS module rebalancing. The new module re-initiates the session, so any updates the OCS/PCRF sent to the PTS are
sent to the new one when the new session is established.
If there is a message routing issue or a severe problem with the OCS/PCRF, it is expected that all unsolicited requests will have
invalid session IDs.

MIB SANDVINE-MIB
Trap Name svDiameterUnknownSessionNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.3

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10

If left to persist, unsolicited requests from the OCS/PCRF are not deployed on the PTS. Service continues but incorrect policy
could deploy to subscribers:
1. Verify the configuration of routing Diameter messages on the OCS/PCRF/Diameter Proxy/Network
05-00262 C07
PTS Alarms
Alarm Model 51: Diameter Interface Error
2. Correlate with alarms that can indicate information loss on the PTS. If so, take measures to verify re-initiation of sessions
over the Diameter interface with OCS/PCRF.
3.45 Alarm Model 51: Diameter Interface Error

This alarm is raised when an error condition is detected in the PCRF on the Gx interface or the OCS on the Gy interface.
Profile Description
Raise Notification svDiameterInterfaceErrorNotification
Clear Notification svDiameterNoInterfaceErrorNotification
Triggers GxInterfaceErrorTrigger, GyInterfaceErrorTrigger, GyEventChargingInterfaceErrorTrigger
Unique Instance Identifier • Gx: 18075
• Gy: 17900
• Gy Event Charging: 22710
Applicability Usage Management 3.00, Usage Management 4.20
This alarm has these instances:

• Gx: when the varbind argument svMeasurementsIndex is 18075
• Gy: when the varbind argument svMeasurementsIndex is 17900.
3.45.1 Raise and clear notifications

Raising

MIB SANDVINE-DIAMETER-IF-MIB
Trap Name svDiameterInterfaceErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.1.3
Clearing

Trap Name svDiameterNoInterfaceErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.1.4

05-00262 C07
PTS Alarms

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svMeasurementsIndex 1.3.6.1.4.1.11610.435.12757.1.10.1.100
svMeasurementsValue 1.3.6.1.4.1.11610.435.12757.1.10.1.3
Varbind values if the alarm is raised from the Policy Enforcement package:

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.4
svMeasurementsIndex 1.3.6.1.4.1.11610.435.12757.1.10.1.1.18075
svMeasurementsValue 1.3.6.1.4.1.11610.435.12757.1.10.1.3.18075
Varbind values if the alarm is raised from the Online Charging package:

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.4
3.45.2 Diameter Interface Error—Major

This notification is sent when an error condition is detected in the PCRF, on the Gx interface or the OCS on the Gy interface. It
is cleared when no problems occur for 10 minutes.
Gx: possible causes

• Mismatched session IDs between requests and answers.
• PCRF trying to set an unknown trigger.
• PCRF trying to set conflicting triggers.
• Sessions are deleted without terminate messages due to a severe protocol issue.
• Conflicting add/remove AVPs while installing rules.
• Conflicting rule activation and deactivation times.
• Missing rule names.
• Missing revalidation times.
• Sent the same rule name in both the Charging-Rule-Install and the Charging-Rule_Remove AVPs in CCA.
• Installed a rule where the deactivation time is less than the activation time in CCA-I/U.
• Sent the wrong trigger name in CCA-I/U.
• Sent the Charging Rule Install AVP without a rule name or a definition in CCA-I/U.
05-00262 C07
PTS Alarms
• Sent result code UNRECOVERABLE_ERRORS (For example: 3001,3003,3005, and so on) in the result code AVP in CCA-I/U.
• Sent the GX_TRIGGER_NO_EVENT_TRIGGERS with other triggers in CCA-I/U.
• Sent the revalidation timeout trigger without a revalidation time AVP in the CCA-I/U.
• Installed the session level key in CCA-I/U and then installed a send new session level key without disabling the previous one
in CCA-U.
• Sent a session level key with the wrong grant type value. This means that the Tx grant, Rx grant, and Total grant do not have
a null value.
• Sent a different GSU type without disabling the existing session level monitoring key in the CCA-U/RAR.
• Sent the rule level key in CCA-I/U and installed the session level key with the same name (rule level key name) in CCA-U.
• Configured two primary PCRF connection with the PTS, installed more than 8 monitoring keys along with a traffic classifier,
and sent traffic for all of them. This can also indicate that the PCRF sent a CCA message with an incorrect session ID.
• Disabled a session level key which does not exist through CCA-U.
• Sent more than 30 monitoring keys in CCA-I/U or more than 30 PCC rules in CCA-I/U.
• More than one session-level key install was received in a single Usage Monitoring Information, CCA, or RAR.
• Received a Usage Monitoring support disable with other grant AVPs in the Usage Monitoring Information of CCA or RAR.
• The Usage Monitoring Report Required was received but the Usage report trigger was not received for the session. The
Usage Monitoring Report required was received along with other grant AVPs.
• The Usage Monitoring Information was received in CCA and RAR but the monitoring key was absent in the Usage Monitoring
Information AVP.
• The new monitoring key was received but no grant was present in the Usage Monitoring Information.
• Usage monitoring report is required but no monitoring key is installed.
Gy: possible causes

• Mismatched session IDs between requests and answers.
• Mismatched RG/Service Ids between requests and answers.
• OCS is trying to set an unknown trigger.
• Sessions that are deleted without terminate messages due to a severe protocol issue.
• Quota grants that do not match the configuration of the service.
3.45.3 Impact and Suggested Resolutions, Alarm Model 51

If left to persist, the applications may not function.
This alarm indicates a severe problem in the interface between the PTS and OCS/PCRF:
1. Create traffic captures of Diameter traffic and analyze them.
2. Analyze the output of the CLI command show usage-management policy-enforcement error-events. If any of
the counters has a non-zero value, this may indicate the source of the error. To get more detailed information, such as the
time at which the error occurred or the subscriber IP, run the CLI command show usage-management
policy-enforcement error-events log.
05-00262 C07
PTS Alarms
Alarm Model 52: Diameter Missing Subscriber Information
3.46 Alarm Model 52: Diameter Missing Subscriber

Information
This alarm is raised when a session is not established, for a subscriber with PCRF for Gx or OCS for Gy, due to missing mandatory
IP session or subscriber information. Some subscriber information required to initiate a Diameter session is missing. This indicates
a configuration mismatch between the SPB, PTS, and RADIUS server.
Profile Description
• Clear
Raise Notification svDiameterMissingSubscriberInfoNotification

Clear Notification svDiameterNoMissingSubscriberInfoNotification
Triggers • GxMissingSubscriberInfoTrigger
• GyMissingSubscriberInfoTrigger
Unique Instance Identifier svMeasurementsIndex
3.46.1 Missing subscriber information—Minor

This notification is sent when a session is not established, for a subscriber with PCRF for Gx or OCS for Gy, due to missing
mandatory IP session or subscriber information.

Trap Name svDiameterMissingSubscriberInfoNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.1.5
Varbind values if the alarm is raised from the Policy Enforcement package:

svSeverity 1.3.6.1.4.1.11610.6799.1.10
Varbind values if the alarm is raised from the Online Charging package:

05-00262 C07
PTS Alarms
Alarm Model 53: Unknown Diameter Service

svSeverity 1.3.6.1.4.1.11610.6799.1.10
3.46.2 Missing subscriber information—Clear

This notification is sent when 10 minutes pass without detecting problems with subscriber information.

MIB SANDVINE-MIB
Trap Name svDiameterNoMissingSubscriberInfoNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.1.6

Sessions may not start if the source of the alarm is not addressed.
1. Create traffic captures of RADIUS (or any other mapping technology used in the deployment) traffic and analyze them.
2. Verify that these package parameters are configured with information that exists in those traffic captures:
• Gx: subscription_id_type, subscription_id_data, ip_can_type
• Gy: subscription_id_type, subscription_id_data
3.47 Alarm Model 53: Unknown Diameter Service

This alarm is raised when an unknown service is detected in the rating group, service ID or PCC rule name for PCRF in the Gx
interface or OCS in the Gy interface. Alarm Model 53 is also raised if Record Generator, or usage server, receives an unknown
Service ID in the Rf interface.
• Gx—PCRF tries to install or remove a Policy and Charging Control (PCC) rule, or a base rule, that was not pre-provisioned
on the PTS.
• GxGy—PCRF tries to install or remove a PCC rule containing a service (Rating Group and/or Service ID) that was not
pre-provisioned on the PTS.
• Gy—OCS sends services (Rating Group and/or Service ID) that are not pre-provisioned on the PTS.
Profile Description
• Clear
Raise Notification svDiameterUnknownServiceNotification
Clear Notification svDiameterNoUnknownServiceNotification
05-00262 C07
PTS Alarms
Profile Description
Triggers • GxUnknownRuleNameTrigger
• GyUnknownServiceTrigger
• GxGyUnknownServiceTrigger
Unique Instance Identifier • Gx: 17639
• Gy: 17904
• GxGy: 17637
Applicability • Usage Management 3.00 and 4.20+: Gx, Gy, GxGy, GyEventCharging
• Usage Management 4.40 and onward: Rf
Affected Platforms: PTS: GX, GY, and GxGy
3.47.1 Unknown Diameter Service - Major

Trap Name svDiameterUnknownServiceNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.1.7

Profile Description
Severity Major
Condition At least one invalid service is raised within 10 minutes.
Description This notification is received when there is any invalid service within a 10 minute period.
GxUnknownRuleNameTrigger: Major
Profile Description
Severity Major
Condition DELTA(svMeasurementsValue.17639) > 0
Description An Unknown PCC Rule Name was received.
GyUnknownServiceTrigger: Major
Profile Description
Severity Major
05-00262 C07
PTS Alarms
Profile Description
Description An Unknown service (Rating-Group and/or Service-Id) was received.
GxGyUnknownServiceTrigger: Major
Profile Description
Severity Major
Description An Unknown service (Rating-Group and/or Service-Id) was received.
3.47.2 Unknown Diameter Service - Clear

Trap Name svDiameterNoUnknownServiceNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.1.8

Profile Description
Severity Clear
Condition There is no invalid service within 10 minutes.
Description A clear notification is sent when there is no invalid service within 10minutes.
GxUnknownRuleNameTrigger: Clear
Profile Description
Severity Clear
Condition DELTA(svMeasurementsValue.17639) = 0
Description No unknown PCC Rule Name was received over the sampling period.
GyUnknownServiceTrigger: Clear
Profile Description
05-00262 C07
PTS Alarms
Profile Description
Severity Clear
Description No unknown service (Rating-Group and/or Service-Id) was received over the sampling period.
GxGyUnknownServiceTrigger: Clear
Profile Description
Severity Clear
Description No unknown service (Rating-Group and/or Service-Id) was received over the sampling period.

If the measurement index is for Gx, Gy, GxGy or GyEventCharging, verify that the OCS/PCRF and PTS service configurations
match.
If Measurement index is for RfSde or RfPts, verify that the PTS and SDE service configurations match.
These files define alarms, triggers, and events for GXGy Unknown Service Received:
/usr/local/sandvine/etc/alarms/diameter_interface.alarm.conf
/usr/local/sandvine/etc/events/events.diameter_interface.conf
/usr/local/share/snmp/mibs/SANDVINE-DIAMETER-IF-MIB.txt
Impact
Alarm Model 53 indicates that a configuration error exists between PTS and OCS/PCRF. If the alarms source is not addressed,
the application will not function properly. For example:
Configuration errors in... Can result in...

Gx Incorrect Traffic flow enforcement.
Gy Over/Under charging of customers.
Resolving Alarm Model 53

Modify the service configuration in both the PTS and SDE, to make them consistent for both platforms. See the Quota Manager
Product Guide for details of how to adjust the service configuration on the SDE.
Verifing Resolution
This alarm clears 600 seconds after the configuration error is resolved for each Rf instance.
Run CLI commands in both the PTS and SDE to verify configured services are matched.
05-00262 C07
PTS Alarms
Alarm Model 59: Unavailable BGP Master
3.48 Alarm Model 59: Unavailable BGP Master

This alarm is raised when BGP is enabled, but there is no active BGP master in a cluster. This can occur if no PTS elements
have peer routers configured, or if all master-eligible BGP daemons in a cluster fail.
Profile Description
Severities Major
Clear
Raise Notification svBgpdMasterFailErrorNotification
Clear Notification svBgpdMasterFailClearNotification
Triggers • bgpdNoMasterError
• bgpdMasterActive
3.48.1 Unavailable BGP Master - Major

This notification is sent if BGP is enabled, but there is no active BGP master in the cluster.
Note:
This alarm can flap when there is a single PTS with a local-id configured and one or more peer routers. When the element
cannot establish a connection with the peer router, this alarm might appear repeatedly. To prevent this, either remove or
reconfigure the peer router.

MIB SANDVINE-MIB
Trap Name svBgpdMasterFailErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.11.0.1

svServiceComponentAdminStatus 1.3.6.1.4.1.11610.435.11281.1.11.1.5.11326.7315
svSvbgpdStatsBgpdMasterStatus 1.3.6.1.4.1.11610.435.7272.1.3.10
Profile Description
Frequency Immediate
Severity Major
Condition svSvbgpdStatsBgpdMasterStatus >= 2
Where:
• svServiceComponentAdminStatus—Indicates the status of the component. Valid values are:
• up—Launches the component across the entire system.
• down—Stops the component across the entire system.
• svSvbgpdStatsBgpdMasterStatus—Indicates whether an active master BGP daemon is present. Valid values are:
• active(1)—Indicates that a master BGP daemon process is operating normally.
• down(2)—Indicates an error condition where no BGP daemon process is acting as the master.
• initial(3)—Indicates a system startup condition where no master BGP daemon process has yet been set as the master.
05-00262 C07
PTS Alarms
Alarm Model 59: Unavailable BGP Master
3.48.2 Unavailable BGP Master - Clear

This notification is sent if there was a BGP master failure, and a BGP master becomes active, or when SVBGPD is administratively
disabled.

MIB SANDVINE-MIB
Trap Name svBgpdMasterFailClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.11.0.2

svSvbgpdStatsBgpdMasterStatus 1.3.6.1.4.1.11610.435.7272.1.3.10
Profile Description
Frequency Immediate
Severity Clear
Condition svSvbgpdStatsBgpdMasterStatus < 2

If BGP is enabled, the element expects up-to-date subnet information from configured peer routers that are connected to the
element running the BGP master. If an active BGP master is not present, then the element cannot receive the subnet information.
This can result in incorrect packet processing.
Note:
A BGP daemon withdraws its master eligibility if it loses, or cannot establish, connection with the peer router.
Complete these steps to resolve the alarm:

1. Check the /var/log/svlog file for indications regarding why the BGP master failed.
2. Run the show service bgp peer CLI command and check these output fields to ensure that BGP is enabled:
• IPAddress—Confirm that at least one element has one or more peer routers configured.
• ConnectionState—Ensure that the ConnectionState output for the configured peer is ESTABLISHED.
3. Check the connection between the peer router and the element. If the BGP service is unable to establish a connection with
the peer router within 180 seconds, Alarm model 60 is raised. See Alarm Model 60: Disconnected BGP Peer on page 181
for instructions to resolve the alarm.
4. If required, run the restart service svbgpd CLI command to restart the SVBGPD service.
05-00262 C07
PTS Alarms
Alarm Model 60: Disconnected BGP Peer
3.49 Alarm Model 60: Disconnected BGP Peer

This alarm is raised when the BGP service is enabled and one or more configured peer router connections go down or are not
established in 180 seconds.
This alarms indicates one of these:
• The BGP service has lost connection with the peer router due to network connectivity issues.
• The peer router crashed or rebooted.
• The peer router is rejecting the connection based on the hold time that the connection initiator in the OPEN message sent.
Profile Description
• Minor
• Clear
Raise Notification svBgpdPeerFailErrorNotification
Clear Notification svBgpdPeerNoFailNotification
Triggers • bgpdPeerConnectFailError
• bgpdPeerConnectLostError
• bgpdPeerConnectClear
3.49.1 Disconnected BGP Peer - Minor

This notification indicates that the BGP service is enabled, but the connection to one or more configured peer routers is broken
or cannot be established. However, one or more peer routers are still connected.

MIB SANDVINE-MIB
Trap Name svBgpdPeerFailErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.11.0.3

svSvbgpdStatsBgpdPeerConnectivityStatus 1.3.6.1.4.1.11610.435.7272.1.3.11
Profile Description
Frequency Immediate
Severity Minor
Condition svSvbgpdStatsBgpdPeerConnectivityStatus == 2
Where:
• svServiceComponentAdminStatus—Indicates the status of the component. Valid values are:
05-00262 C07
PTS Alarms
• up—Launches the component across the entire system.

• down—Stops the component across the entire system.
• svSvbgpdStatsBgpdPeerConnectivityStatus—Indicates the overall connectivity status of the BGP service to BGP peer routers.
Valid values are:
• normal(1)—All peer routers are connected.
• degraded(2)—Some peer routers are not connected.
• lost(3)—No configured peer router is connected.
• initial(4)—The element is in a startup condition where peer router connection is being established.
3.49.2 Disconnected BGP Peer - Major

This notification indicates that the BGP service is enabled, but the connection to every configured peer router is broken or cannot
be established.

MIB SANDVINE-MIB
Trap Name svBgpdPeerFailErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.11.0.3

svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Frequency Immediate
Severity Major
Condition svSvbgpdStatsBgpdPeerConnectivityStatus >= 3
3.49.3 Disconnected BGP Peer - Clear

This notification is sent when all configured peer router connections are established for the BGP master, or when an element is
no longer the BGP master, and therefore, peer router connectivity does not apply.

MIB SANDVINE-MIB
Trap Name svBgpdPeerNoFailNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.11.0.4
05-00262 C07
PTS Alarms

svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Frequency Immediate
Severity Clear
Condition svSvbgpdStatsBgpdPeerConnectivityStatus <= 1

If BGP is enabled, the element expects up-to-date subnet information from configured peer routers connected to the element
running the BGP master. If the connection to a peer router is lost, then the subnet information becomes stale and, in time, becomes
inaccurate. This can result in incorrect packet handling through the PTS.
Note:
This alarm can flap when there is a single PTS with a local-id configured and one or more peer routers. When the element
cannot establish a connection with the peer router, this alarm might appear repeatedly. To prevent this, either remove or
reconfigure the peer router.
If a BGP master loses connectivity with its peer routers, it automatically resigns as master and the system attempts to elect
another eligible PTS running the BGP daemon as master. If successful, and if this new master establishes BGP connectivity with
its configured peer routers, then the alarm is cleared.
Complete these steps to resolve the alarm:
1. Run the show service bgp status CLI command to locate the element that is running the BGP master.
2. Run the show service bgp peer CLI command to view details about the configured BGP connections. A peer whose
ConnectionState output is active indicates that the peer is disconnected.
3. Ensure that the peer is powered on and can listen on the configured port.
If this does not clear the alarm, proceed to the next step.
4. [Minor alarm only] Complete these steps to remove the disconnected peer configurations:
a. Run the configure CLI command to enter configuration mode.
b. Run the delete config service bgp peer <ip-address> CLI command for each disconnected peer router
to delete its configuration.
c. Run the commit CLI command to apply the changes.
5. [Major alarm only] Disable BGP and configure it again.

Disabling BGP causes the system to use subnet information from the subnets.txt file. See the PTS Administration Guide
for instructions to disable and configure BGP.
05-00262 C07
PTS Alarms
Alarm Model 61: Analyzer parse errors—DEPRECATED
3.50 Alarm Model 61: Analyzer parse

errors—DEPRECATED
This alarm is raised if the analyzer parse error rate exceeds the threshold. Any of the protocol-specific analyzers can generate
this alarm:
• HTTP
• RTSP
• RTMP
This alarm is now deprecated.
Profile Description
• Clear
Raise Notification svAnalyzerParseErrorRateNotification

Clear Notification svAnalyzerNoParseErrorRateNotification
3.50.1 svAnalyzerParseErrorRateNotification—Minor notification

MIB SANDVINE-MIB
Trap Name svAnalyzerParseErrorRateNotification
Trap OID .1.3.6.1.4.1.11610.6799.3.7.0.9

svStreamsParseErrorAlarmTableName .1.3.6.1.4.1.11610.435.14855.1.100.1.1.2
expValueCounter64Val.Sandvine. analyzerTotalFlowsExp .1.3.6.1.2.1.90.1.3.1.1.9.Sandvine.analyzerTotalFlowsExp.0.0
expValueCounter64Val.Sandvine.analyzerParseErrorFlowsExp .1.3.6.1.2.1.90.1.3.1.1.9.Sandvine.analyzerParseErrorFlowsExp.
0.0
svStreamsParseErrorAlarmTableParseErrorPercentThreshold .1.3.6.1.4.1.11610.435.14855.1.100.1.1.5
svStreamsParseErrorAlarmTableParseErrorAbsoluteThreshold .1.3.6.1.4.1.11610.435.14855.1.100.1.1.6
3.50.1.1 Analyzer parse errors

This notification sent when the analyzer parse error rate exceeds its threshold.
Profile Description
Severity Minor
05-00262 C07
PTS Alarms
Alarm Model 61: Analyzer parse errors—DEPRECATED
Profile Description
Condition ($svStreamsParseErrorAlarmTableParseErrorAlarmEnabled == 1) && ($analyzerParseErrorFlows
Exp > $svStreamsParseErrorAlarmTableParseErrorAbsoluteThreshold) && ((($analyzerParseErrorF
lowsExp * 100)/($ analyzerTotalFlowsExp +1)) > $ svStreamsParseErrorAlarmTa
bleParseErrorPercentThreshold)
3.50.2 svAnalyzerNoParseErrorRateNotification—Clear notification

MIB SANDVINE-MIB
Trap Name svAnalyzerNoParseErrorRateNotification
Trap OID 1.3.6.1.4.11610.6799.37.0.10

svStreamsParseErrorAlarmTableName 1.3.6.1.4.1.11610.435.14855.1.100.1.1.2
expValueCounter64Val.Sandvine. analyzerTotalFlowsExp 1.3.6.1.2.1.90.1.3.1.1.9.Sandvine.analyzerTotalFlowsExp.0.0
expValueCounter64Val.Sandvine.analyzerParseErrorFlowsExp 1.3.6.1.2.1.90.1.3.1.1.9.Sandvine.analyzerParseErrorFlowsExp.
0.0
svStreamsParseErrorAlarmTableParseErrorPercentThreshold 1.3.6.1.4.1.11610.435.14855.1.100.1.1.5
svStreamsParseErrorAlarmTableParseErrorAbsoluteThreshold 1.3.6.1.4.1.11610.435.14855.1.100.1.1.6
3.50.2.1 No parse errors

Notification sent when the analyzer parse error rate has dropped below the threshold.
Profile Description
Severity Clear
Condition ($svStreamsParseErrorAlarmTableParseErrorAlarmEnabled ==0) or ($analyzerParseErrorFlows
Exp <= $svStreamsParseErrorAlarmTableParseErrorAbsoluteThreshold) or (((($analyzerParseErro
rFlowsExp)/($ analyzerTotalFlowsExp +1))*100) <= $ svStreamsParseErrorAlarmTa
bleParseErrorThreshold)

If this alarm occurs, there are many parse errors occurring in a particular analyzer.
If policy is using the fields produced by this analyzer, then a significant number of these fields may be NULL, instead of containing
the appropriate values. If these fields are used in policy, the policy may not be behaving as expected. Stalls may occur due to
asymmetric traffic, shunts, or packet drops.
1. For more information about the current state of the analyzers, run the show service streaming errors CLI command.
05-00262 C07
PTS Alarms
Alarm Model 62: Too Many Concurrent Analyzer Flows—DEPRECATED
2. To check if stalls counters are going up, run: show service streaming stats
3. If stalls counters are going up, the network may be seeing asymmetric traffic, which can cause the analyzer to drop the
stream.
4. If the stalls counters are not going up, review stats for the specific analyzer by running show service streaming
analyzer <analyzer-name>
5. To check for either process overloaded alarms or other drop-related alarms, run show alarms.
3.50.3.1 RTSP-specific impact & suggested resolutions

This error is most commonly seen with the RTSP analyzer. Due to RTSP's complex structure, sometimes valid flows are mis-parsed
by the PTS.
If policy is using RTSP fields, then a significant number of these fields may be NULL, rather than appropriate values. Further, it
is possible that RTSP data flows may not be recognized properly.
1. Capture the traffic that is causing the parse error by running:
--> pwd
/iso/org/dod/internet/private/enterprises/sandvine/devices/streaming/1/tcpAnalyzers/rtsp/debug
--> set dumpParseErrorStreams 10 --> ls
dumpParseErrorStreams [1] : 10
-->
This will dump the next 10 parse errors (per module) to be dumped to files in /d2/tmp/. The files will be named
instr_rtsp_ppu#_<timestamp>.cap
2. Examine the files to see if there are any obvious problems with the RTSP flows. If the packet looks like RTSP and no obvious
errors appear, contact Sandvine Support and provide the corresponding .txt file from the /d2/tmp directory.
3.51 Alarm Model 62: Too Many Concurrent

Analyzer Flows—DEPRECATED
This alarm is raised if the analyzer is currently parsing too many flows. Any of the protocol-specific analyzers can generate this
alarm:
• HTTP
• RTSP
• RTMP
This alarm is now deprecated.
Raising

MIB SANDVINE-MIB
Trap Name svAnalyzerConcurrentFlowsNotification
Trap OID 1.3.6.1.4.11610.6799.37.0.11
05-00262 C07
PTS Alarms
Alarm Model 63: Shunting Traffic Inspection
Clearing

MIB SANDVINE-MIB
Trap Name svAnalyzerNoConcurrentFlowsNotification
Trap OID 1.3.6.1.4.11610.6799.37.0.12

svStreamsConcurrentFlowsAlarmTableName 1.3.6.1.4.1.11610.435.14855.1.100.2.1.2
svStreamsConcurrentFlowsAlarmTableConcurrentFlows 1.3.6.1.4.1.11610.435.14855.1.100.2.1.3
expValueCounter64Val.Sandvine.analyzerParseErrorFlowsExp 1.3.6.1.2.1.90.1.3.1.1.9.Sandvine.analyzerParseErrorFlowsExp.
0.0
svStreamsConcurrentFlowsAlarmTableMaxConcurrentFlows 1.3.6.1.4.1.11610.435.14855.1.100.2.1.4
analyzerDropsConcFlowsExp 1.3.6.1.2.1.90.1.3.1.1.9.Sandvine.analyzerDropsConcFlowsExp.
0.0

This alarm is raised when there are too many flows currently being parsed by the analyzer.If policy is using fields produced by
that analyzer, then a number of these fields may be NULL, instead of containing the appropriate values. If these fields are used
in policy, the policy may not be behaving as expected:
1. For more information about the current state of the analyzers, run:show service streaming errors
2. To clear this alarm, reduce the number of flows that the analyzer is parsing. To do this either, reduce the amount of traffic
to the module or change your SandScript to not issue analyze on fewer flows.
3.52 Alarm Model 63: Shunting Traffic Inspection

This alarm is raised when one or more modules on a PTS element fail to stop bridging packets after a configured duration. This
can occur when a configuration reload is performed under stressful conditions.
Note:
Alarm Model 63 (Shunting Traffic Inspection) is not supported on the PTS Linux platform.
Profile Description
Raise Notification svSysBridgeModeTimeExceededNotification
Clear Notification svSysBridgeModeTimeOkNotification
Triggers • ptsdBridgeModeTimeExceeded
• ptsdBridgeModeTimeOk
05-00262 C07
PTS Alarms
Alarm Model 63: Shunting Traffic Inspection

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svPtsApplicationConfigBridgeModeTimeout 1.3.6.1.4.1.11610.435.8374.1.2.17
3.52.1 Shunting Traffic Inspection- Major

MIB SANDVINE-MIB
Trap Name svSysBridgeModeTimeExceededNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.15
3.52.2 Shunting Traffic Inspection - Clear

MIB SANDVINE-MIB
Trap Name svSysBridgeModeTimeOkNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.16

When a PTS is in the bridge mode, protocol identification is degraded. Consequently, new or existing flows may not have
SandScript applied. A bridge mode time-out value that is configured too low can cause this alarm to occur, and then clear
frequently, particularly if protocol identification is not degraded. You should consider adjusting the bridge mode time-out value.
1. Run the restart command to take the PTS out of the bridging mode. This lets you immediately address the problem.
2. To verify the issue is resolved, on the PTS element associated with the alarm:
a. Run the show alarms history [Id] CLI command. Verify that an entry similar to 107 Clear 13:47:17 61
PTSD has exited bridge mode is listed.
b. Run the show policy inspection traffic CLI command, and examine the Bridged Packets row. After a few
seconds, run this CLI command again and verify that the Bridged Packets value has not changed.
Use this CLI command to configure the PTSD bridging alarm. This determines the maximum length of time a PTS element
can bridge packets before an alarm occurs:
PTS# set config system reload bridge-mode alarm time-out
You can verify the existing configuration using this command:

PTS# show config system reload bridge-mode alarm time-out
05-00262 C07
PTS Alarms
Alarm Model 77: Misconfigured Network Interface
3.53 Alarm Model 77: Misconfigured Network

Interface
This alarm is raised when a high level of traffic is deemed to be backwards, potentially indicating that the ports are wired backwards.
It is raised if more than 50% of the flows analyzed in a 20 minute period are backwards. The alarm is cleared when the percentage
falls below 25%. Flows matching this criteria indicate backward flows:
• A subscriber-facing port with an internet IP, and
• An Internet-facing port with a subscriber IP.
The rate at which flows are analyzed for port role inconsistencies is variable, and defaults to every 1 millionth flow. This alarm
deprecates Alarm Model 22.
Profile Description
Severities Minor
Raise Notification svIfPortWiredBackwardsNotification
Clear Notification svIfPortWiredBackwardsClearedNotification
Triggers portWiredBackwards
Unique Instance Identifier svPortTopologyInfoPortAddrTracking.portIndex
Applicability PTS 5.51.14+
3.53.1 Misconfigured Network Interface- Minor

This notification is sent when traffic on this port appears backwards (both subscriber and internet networks appear backwards
when compared to the subnets.txt definition).

MIB SANDVINE-MIB
Trap Name svIfPortWiredBackwardsNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.17

svClusterConfigName 1.3.6.1.4.1.11610.435.5213.1.2.1.0
SNMPv2-MIB:sysName 1.3.6.1.2.1.1.5.0
svSeverity 1.3.6.1.4.1.11610.6799.1.10.0
svPortTopologyDataPortStatsDescription 1.3.6.1.4.1.11610.435.10470.1.3.200.1.4
svPortTopologyDataPortStatsSysSSN 1.3.6.1.4.1.11610.435.10470.1.3.200.1.1
svPortTopologyDataPortStatsSlot 1.3.6.1.4.1.11610.435.10470.1.3.200.1.2
svPortTopologyDataPortStatsPort 1.3.6.1.4.1.11610.435.10470.1.3.200.1.3
05-00262 C07
PTS Alarms
Alarm Model 77: Misconfigured Network Interface
Profile Description
Frequency 1800s
Severity minor
Condition delta(svPortTopologyDataPortStatsFlowsBackwards) >= 10000
3.53.2 Misconfigured Network Interface - Cleared

The traffic on this port appears to be correctly configured (subscriber and internet networks coincide with subnets.txt definitions).

MIB SANDVINE-MIB
Trap Name svIfPortWiredBackwardsClearedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.18

SNMPv2-MIB:sysName 1.3.6.1.2.1.1.5.0
svSeverity 1.3.6.1.4.1.11610.6799.1.10.0
svPortTopologyDataPortStatsDescription 1.3.6.1.4.1.11610.435.10470.1.3.200.1.4
svPortTopologyDataPortStatsSysSSN 1.3.6.1.4.1.11610.435.10470.1.3.200.1.1
svPortTopologyDataPortStatsSlot 1.3.6.1.4.1.11610.435.10470.1.3.200.1.2
svPortTopologyDataPortStatsPort 1.3.6.1.4.1.11610.435.10470.1.3.200.1.3
Profile Description
Frequency 1800s
Severity Clear
Condition delta(svPortTopologyDataPortStatsFlowsBackwards) < 100

If this alarm occurs, some policy do not operate correctly, because the class of traffic (subscriber or internet) is not determined
correctly. For example, policy actions applied in a specific direction may be applied in the opposite direction of the flow.
Any policy rules that rely on traffic class to be performed behaves incorrectly (and likely do exactly the opposite of what is intended
in the policy):
1. View the value sysSSN from the alarm. This value uniquely identifies each PTS element in a cluster.
2. To match the sysSSN value to a PTS, run the show system information CLI command on each PTS.
05-00262 C07
PTS Alarms
Alarm Model 79: Failed Reload
3. Once you have determined which PTS element is associated with the alarm, locate the physical port on the front of the PTS.
It should be clearly labeled in the form Module-Port (for example, 3-1). This device is deemed to be wired backwards. Likely
you will see alarms occur in parallel, indicating that the two ports probably need to be swapped--a bridge group has been
wired backwards and the cable connected to the subscriber side should be swapped with the cable connected to the internet
side.
4. If you are sure that the ports are wired correctly, the fault could be in the subnets.txt file.
Inspect the file (/usr/local/sandvine/etc/subnets.txt) and ensure that all local subnet ranges are correctly classed as
internal traffic, and that all other subnets fall under the external class. For more information on configuring the subnets.txt
file, see the SandScript Configuration Guide.
3.53.3.1 Port Wired Backwards Alarm Raised for Disabled Interface

When an interface on the PTS is disabled, its transmitter is also disabled. In a normal installation, this causes the remote link to
stop sending data packets and instead send Link Fault packets. If the remote link does not recognize that the PTS interface is
disabled, it may continue to send data packets, but the PTS will still not transmit packets out of the disabled interface.
If the PTS is used to gather statistical information in offline mode, the other networking equipment is not aware of the PTS
presence. The PTS receives packet data from the network connection, the PTS processes the data packets, but it does not
transmit them out the disabled interface.
3.54 Alarm Model 79: Failed Reload

This alarm is raised when a previous attempt to reload the Sandvine software suite has failed. This alarm indicates that Sandvine
software is running with either a previous configuration or the software is not configured at all.
Profile Description
Severity • Warning
• Minor
• Major
• Critical
Raise Notification svSysLastReloadFailedNotification

Clear Notification svSysLastReloadSucceededNotification
Triggers serviceReloadFailedTrigger
Unique Instance Identifier 1.3.6.1.4.1.11610.435.11281.1.20
Applicability This alarm applies to SDE 6.00 and later
3.54.1 svSysLastReloadFailedNotification: Failed Reload

This notification is sent when a service does not reload successfully and has reverted to the last-known stable configuration.
Note:
If the reload completes with a warning, the alarm text indicates Degraded Reload, together with an indication of the reason
for the warning.
05-00262 C07
PTS Alarms
Alarm Model 79: Failed Reload

MIB SANDVINE-MIB
Trap Name svSysLastReloadFailedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.17

svServiceLastReloadDetailsId 1.3.6.1.4.1.11610.435.11281.1.20.1.1
svServiceLastReloadDetailsDescription 1.3.6.1.4.1.11610.435.11281.1.20.1.2
svServiceLastReloadDetailsTrapEnabled 1.3.6.1.4.1.11610.435.11281.1.20.1.4
Profile Description
Severity Determined by the svServiceLastReloadDetailsErrorSeverity variable
Condition (lastReloadDetails.1.inError && lastReloadDetails.1.trapEnabled) == true
3.54.2 svSysLastReloadSucceededNotification: Failed Reload—Clear

The alarm is cleared separately for each aspect of the reload failure. Reloads are considered successful when all types of the
alarm clear.
If the alarm is raised before upgrading the software, the output of the show alarms history limit 0 CLI command after
the upgrade does not include the clear notification for the alarm.

MIB SANDVINE-MIB
Trap Name svSysLastReloadSucceededNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.18

svServiceLastReloadDetailsId 1.3.6.1.4.1.11610.435.11281.1.20.1.1
svServiceLastReloadDetailsDescription 1.3.6.1.4.1.11610.435.11281.1.20.1.2
svServiceLastReloadDetailsTrapEnabled 1.3.6.1.4.1.11610.435.11281.1.20.1.4
Profile Description
Severity Clear
Condition (lastReloadDetails.1.inError || lastReloadDetails.1.trapEnabled) == false
05-00262 C07
PTS Alarms
Alarm Model 82: Shunting Abusive IPs
3.54.3 Failed Reload—All Alarms

If a reload fails, the notification may appear as a warning. Run the show system services last-reload CLI command to
view which error conditions are tracked.
Varbind Name Description

svServiceLastReloadDetailsId This is the integer ID of the error code. This is occasionally used
as a input to the enable/disable configuration functions.
svServiceLastReloadDetailsDescription This provides a short description of the error that caused Alarm
Model 79 to occur.
svServiceLastReloadDetailsTrapEnabled This identifies whether the trap is currently enabled or disabled.
This is especially useful when inspecting the clear notification.
A 'false' value indicates that the error was not actually fixed,
but that Alarm Model 79 was disabled.

Since the system reverts to its previous configuration, any recent changes are not implemented.
1. Run show system services last-reload to see all the errors that have occurred since you ran the svreload
command.
2. Inspect /var/log/svlog for more information on a specific error.

Additionally, you can further examine these errors.
3. Run the svreload command after the issue is corrected.

Run the show system services last-reload CLI command to confirm that services have successfully reloaded; the
alarm should clear.
4. If the error condition is known, and you cannot correct it, you can disable the alarm for this error condition.
Use the set config system services last-reload <error-index> enabled <true|false> CLI command
to disable the numbered type of alarm model 79. For example, to disable alarms for error condition 9, run:
set config system services last-reload 9 enabled false
3.55 Alarm Model 82: Shunting Abusive IPs

This notification is sent if a traffic overload condition is detected and high-usage IPs identified. Traffic for one or more high-usage
IPs or subnets is temporarily shunted to prevent packet drops in the switching hardware and, in addition, the number of these
shunted IPs has exceeded a specified threshold.
Note:
Alarm Model 82 (Shunting Abusive IPs) is not supported on the PTS Linux platform.
05-00262 C07
PTS Alarms
Profile Description
• Clear
Raise Notification svLBHighUsageIPShuntedNotification

Clear Notification svLBHighUsageIPClearNotification
Triggers HighUsageIpsEventTrigger
HighUsageIpsClearEventTrigger
3.55.1 svLBHighUsageIPShuntedNotification: Shunting Abusive IPs

MIB SANDVINE-MIB
Trap Name svLBHighUsageIPShuntedNotification
Trap OID 1.3.6.1.4.1.11610.435.8377.1.2.500.9

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svIOMStatsHighIpManagementTempManagedSubnetsCount 1.3.6.1.4.1.11610.435.8377.1.3.500.4
svIOMConfigHighIpManagementManagedIpsAlarmThreshold 1.3.6.1.4.1.11610.435.8377.1.2.500.10
svIOMConfigHighIpManagementManagedIpsAlarmEnabled 1.3.6.1.4.1.11610.435.8377.1.2.500.9
3.55.1.1 Shunted high-usage IPs exceed limit

Internal packet switching resources have exceeded one or more limits, and some high-usage IPs on affected modules are
dynamically shunted to prevent packet drops. The number of these shunted IPs has exceeded a specified threshold. The
svIOMConfigHighIpManagementManagedIpsAlarmThreshold varbind identifies the threshold and the current number of
dynamically shunted IPs is given bysvIOMStatsHighIpManagementTempManagedSubnetsCount.
Profile Description
Frequency 8 seconds
Severity Minor
Condition svIOMConfigHighIpManagementManagedIpsAlarmEnabled == true &&
svIOMStatsHighIpManagementTempManagedSubnetsCount >= svIOMConfigHighIpManagemen
tManagedIpsAlarmThreshold && svIOMConfigHighIpManagementManagedIpsAlarmEnabled ==
false
05-00262 C07
PTS Alarms
3.55.2 svLBHighUsageIPClearNotification: Shunting Abusive IPs

Cleared
MIB SANDVINE-MIB
Trap Name svLBHighUsageIPClearNotification
Trap OID 1.3.6.1.4.1.11610.435.8377.1.2.500.9

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svIOMStatsHighIpManagementTempManagedSubnetsCount 1.3.6.1.4.1.11610.435.8377.1.3.500.4
svIOMConfigHighIpManagementManagedIpsAlarmThreshold 1.3.6.1.4.1.11610.435.8377.1.2.500.10
svIOMConfigHighIpManagementManagedIpsAlarmEnabled 1.3.6.1.4.1.11610.435.8377.1.2.500.9
3.55.2.1 Shunted high-usage IPs within limit

Internal packet switching resources have exceeded one or more limits,and high-usage IPs on affected modules have been
dynamically shunted to prevent packet drops. The number of these shunted IPs is at or below the specified threshold. The
threshold is given by svIOMConfigHighIpManagementManagedIpsAlarmThreshold and the current number of dynamically
shunted IPs is given by svIOMStatsHighIpManagementTempManagedSubnetsCount.
Profile Description
Frequency 8 seconds
Severity Clear
Condition svIOMConfigHighIpManagementManagedIpsAlarmEnabled == true && (
svIOMStatsHighIpManagementTempManagedSubnetsCount <
svIOMConfigHighIpManagementManagedIpsAlarmThreshold ||
svIOMConfigHighIpManagementManagedIpsAlarmEnabled == true)

When the PTS detects that it is overloaded with traffic, it identifies high-usage IPs and shunts their traffic. Dynamic shunting of
high-usage IPs is an automatic and temporary response to brief overloaded traffic conditions.
1. Use the show service ip-overload-management shunted-subnets CLI command to view a list all shunted
subnets.
2. To remove dynamically shunted IPs from the list:

• Run the clear service ip-overload-management subnet 4.0.0.0 CLI command, to temporarily remove a
specific IP address (for example 4.0.0.0) from the set of dynamically shunted subnets.
05-00262 C07
PTS Alarms
Alarm Model 87: Failed Health Check
• Run the clear service ip-overload-management subnet all CLI command, to temporarily remove all current
dynamically shunted IPs.
• Run the edit service ip-overload-management subnets never-shunt CLI command, to ensure that an IP
is never shunted, and add it to the never-shunted list.
3. To remove statically shunted IPs:

a. Use the edit service ip-overload-management subnets always-shunt CLI command to edit the list of
IPs that are always shunted.
b. When you have finished your changes, you must reload the file using the CLI command: reload
ip-overload-management-subnets
4. Run show config service ip-overload-management alarms CLI command, to view the configuration of IP-overload
management alarms. The show config service ip-overload-management alarms ips-dynamically-shunted
threshold variable indicates the number of dynamically shunted IPs above which an alarm notification is raised. If desired,
this threshold can be modified using set config service ip-overload-management alarms
ips-dynamically-shunted threshold CLI command.
3.56 Alarm Model 87: Failed Health Check

This alarm is raised when a server healthcheck fails.
Raise
Profile Description
Raise Notification svServerHealthCheckErrorNotification
Trigger svrHealthChkErrTriggered
OID 1.3.6.1.4.1.11610.6799.3.7.0.13
Unique Instance Identifier svHealthCheckServerHealthCheckInstanceDescription
1.3.6.1.4.1.11610.435.13535.1.101.11.1.7
Clear
Profile Description
Clear Notification svServerHealthCheckErrorClearNotification
Trigger svrHealthChkErrClrTriggered
OID 1.3.6.1.4.1.11610.6799.3.7.0.14
3.56.1 svServerHealthCheckErrorNotification: Failed Health Check

This notification is sent when a server healthcheck fails.

MIB SANDVINE-MIB
05-00262 C07
PTS Alarms

Trap Name svSvrHealthCheckErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.13

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svHealthCheckServerHealthCheckInstanceDescription 1.3.6.1.4.1.11610.435.13535.1.101.11.1.7
svHealthCheckServerHealthCheckInstanceName 1.3.6.1.4.1.11610.435.13535.1.101.11.1.1
svHealthCheckServerHealthCheckInstanceIp 1.3.6.1.4.1.11610.435.13535.1.101.11.1.2
svHealthCheckServerHealthCheckInstanceStatus 1.3.6.1.4.1.11610.435.13535.1.101.11.1.3
svHealthCheckServerHealthCheckInstanceChecks 1.3.6.1.4.1.11610.435.13535.1.101.11.1.4
svHealthCheckServerHealthCheckInstanceFailures 1.3.6.1.4.1.11610.435.13535.1.101.11.1.5
svHealthCheckServerHealthCheckInstanceTimeouts 1.3.6.1.4.1.11610.435.13535.1.101.11.1.6
Profile Description
Severity Minor
Condition svHealthCheckServerHealthCheckInstanceStatus = down
3.56.2 svServerHealthCheckErrorClearNotification: Failed Health

Check Cleared
This notification is sent when the server (destination) health check failure is resolved.

MIB SANDVINE-MIB
Trap Name svSvrHealthCheckErrorClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.14

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svHealthCheckServerHealthCheckInstanceDescription 1.3.6.1.4.1.11610.435.13535.1.101.11.1.7
svHealthCheckServerHealthCheckInstanceName 1.3.6.1.4.1.11610.435.13535.1.101.11.1.1
svHealthCheckServerHealthCheckInstanceIp 1.3.6.1.4.1.11610.435.13535.1.101.11.1.2
svHealthCheckServerHealthCheckInstanceStatus 1.3.6.1.4.1.11610.435.13535.1.101.11.1.3
05-00262 C07
PTS Alarms

svHealthCheckServerHealthCheckInstanceChecks 1.3.6.1.4.1.11610.435.13535.1.101.11.1.4
svHealthCheckServerHealthCheckInstanceFailures 1.3.6.1.4.1.11610.435.13535.1.101.11.1.5
svHealthCheckServerHealthCheckInstanceTimeouts 1.3.6.1.4.1.11610.435.13535.1.101.11.1.6
Profile Description
Severity Clear
Condition svHealthCheckServerHealthCheckInstanceStatus = up

This alarm indicates that a destination health check has failed. As a result, existing flows may experience packet loss until the
flow ends.
For new flows that are bound for the failed destination, tee/divert actions are not applied for 5 minutes. After 5 minutes, if there
are other healthy divert hosts within the group, the new flow is balanced to those other healthy tee/divert host within the group.
Otherwise, tee/divert actions are not applied until there are other healthy tee/divert hosts within the group.
1. For a “ping” healthcheck:
a. Run the show policy healthcheck CLI command to get more information about the healthcheck. In particular,
take note of the Ip field, which shows the divert hosts IP address, and the TimeoutMs fields.
b. Log on to the tee/divert host listed in the Ip field, and check its operational status.
c. Check the network connection between PTS and the tee/divert host. See the PTS Administration Guide for more
information.
2. For an “HTTP” health check:

a. Run the show policy healthcheck CLI command to get more information about the healthcheck. In particular,
take note of the Ip field which shows the tee/divert hosts IP address, and TimeoutMs, Port, Path, Request
version, and ResponseRegex.
b. Log on to the tee/divert host listed in the Ip field, and check its operational status.
c. Examine the tee/divert hosts HTTP server and ensure the configuration parameter matches with the specified parameter
as listed in the CLI command.
d. Check the network connection between PTS and the tee/divert host. See the PTS Administration Guide for more
information.
3.57 Alarm Model 88: Failed Health Check

This alarm is raised when the inline health check fails.
05-00262 C07
PTS Alarms
Raise
Profile Description
Raise Notification svInlineHealthCheckErrorNotification
Trigger inlineHealthChkErrTriggered
OID .1.3.6.1.4.1.11610.6799.3.7.0.15
Unique Instance Identifier svHealthCheckL2ClientHealthCheckInstanceDescription
1.3.6.1.4.1.11610.435.13535.1.101.15.1.7
Clear
Profile Description
Clear Notification svInlineHealthCheckErrorClearNotification
Trigger inlineHealthChkErrClrTriggered
OID .1.3.6.1.4.1.11610.6799.3.7.0.16
3.57.1 svInlineHealthCheckErrorNotification: Failed Health

Check—Minor
This notification is sent when an inline health check has failed.

MIB SANDVINE-MIB
Trap Name svInlineHealthCheckErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.15

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svHealthCheckL2ClientHealthCheckInstanceDescription 1.3.6.1.4.1.11610.435.13535.1.101.15.1.7
svHealthCheckL2ClientHealthCheckInstanceName 1.3.6.1.4.1.11610.435.13535.1.101.15.1.1
svHealthCheckL2ClientHealthCheckInstanceVlan 1.3.6.1.4.1.11610.435.13535.1.101.15.1.2
svHealthCheckL2ClientHealthCheckInstanceStatus 1.3.6.1.4.1.11610.435.13535.1.101.15.1.3
svHealthCheckL2ClientHealthCheckInstanceChecks 1.3.6.1.4.1.11610.435.13535.1.101.15.1.5
svHealthCheckL2ClientHealthCheckInstanceTimeouts 1.3.6.1.4.1.11610.435.13535.1.101.15.1.6
Profile Description
Severity Minor
Condition svHealthCheckL2ClientHealthCheckInstanceStatus = down
05-00262 C07
PTS Alarms
3.57.2 svInlineHealthCheckErrorClearNotification: Failed Health

Check—Clear
This notification is sent when an inline healthcheck that previously failed is now cleared.

MIB SANDVINE-MIB
Trap Name svInlineHealthCheckErrorClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.16

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svHealthCheckL2ClientHealthCheckInstanceDescription 1.3.6.1.4.1.11610.435.13535.1.101.15.1.1
svHealthCheckL2ClientHealthCheckInstanceName 1.3.6.1.4.1.11610.435.13535.1.101.15.1.7
svHealthCheckL2ClientHealthCheckInstanceVlan 1.3.6.1.4.1.11610.435.13535.1.101.15.1.2
svHealthCheckL2ClientHealthCheckInstanceStatus 1.3.6.1.4.1.11610.435.13535.1.101.15.1.3
svHealthCheckL2ClientHealthCheckInstanceChecks 1.3.6.1.4.1.11610.435.13535.1.101.15.1.5
svHealthCheckL2ClientHealthCheckInstanceTimeouts 1.3.6.1.4.1.11610.435.13535.1.101.15.1.6
Profile Description
Severity Clear
Condition svHealthCheckL2ClientHealthCheckInstanceStatus = up

A failed health check means that existing flow may experience packet loss until the flow ends.
For new flows that are bound for the failed destination, divert action is not applied for 5 minutes. After 5 minutes, if there are other
healthy divert sequences within the group, new flow is balanced to those other healthy divert sequence within the group. Otherwise,
divert action is not applied until there are other healthy divert sequence within the group:
1. To get more informaiton about the healthcheck, run show policy healthcheck CLI command.
In particular, take note of the “TTL”, and “SrcIp” and “DstIp (**)” fields which show the source and destination IP address
for the divert host.
2. Check network connection between PTS and divert host.

For more information, see the PTS Administration Guide.
3. Ensure the inline healthcheck packet is arriving and departing on each of the divert hosts within the sequence.
The source and destination IP address can be found in the CLI command show policy healthcheck.
05-00262 C07
PTS Alarms
Alarm Model 110: Subscriber Mapping timestamps are in the past
3.58 Alarm Model 110: Subscriber Mapping

timestamps are in the past
Subscriber Mapping messages are timestamped to indicate when they should take effect. If the system encounters messages
with a timestamp in the past, it indicates that the element has fallen behind in processing the messages, and usage information
is not applied to the correct subscribers. When this happens, Alarm Model 110 raises.
Profile Description
• Clear
Raise Notification svSubscriberMappingTimestampsInPastNotification

Clear Notification svSubscriberMappingTimestampsNotInPastNotification
Triggers SPTimestampsInPastTgr
Applicability Alarm model 110 is only applicable to the SDE, commencing
with Release 6.20 and the PTS, commencing with Release 7.
40.
3.58.1 Subscriber Mapping timestamps are in the past — Warning

This notification is sent when more than 5% of timestamp messages, in the most recent time interval, have late timestamps when
they are processed. The delta between timestamps of the system and the packet is set to 60 seconds as a default.

MIB SANDVINE-SUBSCRIBER-MAPPING-MIB
Trap Name svSubscriberMappingTimestampsInPastNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.23.1.1

svSubscriberMappingMappingSuccess 1.3.6.1.4.1.11610.435.12757.1.11.1.7.22006
svSubscriberMappingMappingFailure 1.3.6.1.4.1.11610.435.12757.1.11.1.7.22007
svSubscriberMappingUnMappingSuccess 1.3.6.1.4.1.11610.435.12757.1.11.1.7.22283
svSubscriberMappingUnMappingFailure 1.3.6.1.4.1.11610.435.12757.1.11.1.7.22284
svSubscriberMappingUpdateMappingFailure 1.3.6.1.4.1.11610.435.12757.1.11.1.7.22286
svSubscriberMappingUpdateMappingSuccess 1.3.6.1.4.1.11610.435.12757.1.11.1.7.22287
svSubscriberMappingSessionTimeStampInThepast 1.3.6.1.4.1.11610.435.12757.1.10.1.3. 22405
Profile Description
05-00262 C07
PTS Alarms
Profile Description
Severity Warning
Condition (svSubscriberMappingSessionTimeStampInThepast * 100) /
(svSubscriberMappingMappingSuccess +
svSubscriberMappingMappingFailure +
svSubscriberMappingUnMappingSuccess +
svSubscriberMappingUnMappingFailure +
svSubscriberMappingUpdateMappingFailure +
svSubscriberMappingUpdateMappingSuccess) > = 5
3.58.2 Subscriber Mapping timestamps are in the past — Clear

This notification is sent when more than 5% of timestamp messages, in the most recent time interval, have late timestamps when
they are processed. The delta between timestamps of the system and the packet is set to 60 seconds as a default.

Trap Name svSubscriberMappingTimestampsNotInPastNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.23.1.2

svSubscriberMappingSessionTimeStampInTheFuture 1.3.6.1.4.1.11610.435.12757.1.11.1.3.22127
Profile Description
Frequency 15 minutes
Severity Clear
Condition svSubscriberMappingSessionTimeStampInThePast * 100) /
svSubscriberMappingUpdateMappingSuccess)
<= 1
05-00262 C07
PTS Alarms

Varbind Description
svSubscriberMappingSessionTimeStampInThepast This represents a counter that increases when a received
session timestamp is in the past.
svSubscriberMappingMappingSuccess This represents a counter that increases when mapping is
successful.
svSubscriberMappingMappingFailure This represents a counter that increases when mapping fails.
svSubscriberMappingUnMappingSuccess This represents a counter that increases when unmapping is
successful.
svSubscriberMappingUnMappingFailure This represents a counter that increases when unmapping fails.
svSubscriberMappingUpdateMappingFailure This represents a counter that increases when update mapping
fails.
svSubscriberMappingUpdateMappingSuccess This represents a counter that increases when update mapping
is successful.
Impact
Subscriber Mapping messages are processed before the time they become applicable, or the traffic flow will not be attributed to
the correct subscriber. Having the timestamp in the past means that either processing has fallen behind, or one of the sources
of the messages has an incorrect clock setting. Diameter SD messages sent to the TDF contain a timestamp which indicates
when they were created. The element must process these messages in a timely manner and stale timestamps could indicate
queueing or clock synchronization issues. Future timestamps are a definite indication of a clock synchronization problem. Since
stale timestamps imply that the desired actions are not processed in time, this alarm suggests an investigation.
Billing and traffic enforcement actions are affected if processing is delayed.
Suggested Resolution
First Investigate the clock synchronization and correct it; if that is not the cause, then investigate the system load required. Check
the:
• Subscriber Mapping session_timestamp configuration parameter.
Warning:
This SandScript example is taken from the policy.conf file and highlights the session_timestamp parameter value
from the RADIUS AVP called Event-Timestamp.
DIAMETER "true" \
trigger "Mapping" \
condition "All(Diameter.Sd.TSR.SubscriptionValue is not null, Diameter.Sd.TSR.ResultCode
= 2001)" \
session_id "Diameter.Sd.TSR.SessionID" \
session_ipv4_prefix "Diameter.Sd.TSR.IPv4" \
session_ipv4_prefix_length "32" \
session_ipv4_site_number "0" \
session_ipv6_prefix_length "Diameter.Sd.TSR.IPv6PrefixLength" \
05-00262 C07
PTS Alarms
Alarm Model 111: Subscriber Mapping timestamps are in the future
session_timestamp "NowMs" \
subscriber_name "Diameter.Sd.TSR.SubscriptionMSISDN" \
This SandScript example shows how the timestamp is extracted from the packet and, if it is not present, to use NowMs.
You can also run the show service ntp CLI command on the element.In the case where the times are correct, run
the show system resources CLI command to verify that the system is not overloaded or if any queues are over-full.
• Run the service ntpd status command to check the NTP service status and check the server configurations. For
example:
server 0.asia.pool.ntp.org
• NTP configuration of components including the SDE, DHCP server, PTS, GGSN, RADIUS, and SPB.

timestamps are in the future
This alarm model is raised when session timestamps are in the future.
3.59.1 Alarm Model 111: Subscriber Mapping timestamps are in the

future
Alarm model 111 is raised when session timestamps are in the future. It compares the element time against the originating
server's time, which is embedded in the packet when the message is issued. An acceptable difference between clocks is ± 5
seconds. If it is greater then that, either the elements clock is out of synch or the originating server clock is not synchronized with
the network time server.
Profile Description
• Clear
Raise Notification svSubscriberMappingTimestampsInFutureNotification

Clear Notification svSubscriberMappingTimestampsNotInFutureNotification
Triggers SPTimestampsInFutureTgr
Applicability This alarm applies to:
• SDE 6.20 and later.
• PTS 7.40 and later.
3.59.2 Subscriber Mapping timestamps are in the Future — Warning

This notification is sent when the timestamp of a mapping action is later than the current PTS computer time by a deviation greater
than the timestamp deviation threshold.
05-00262 C07
PTS Alarms

Trap Name svSubscriberMappingTimestampsInFutureNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.23.1.3

Profile Description
Severity Warning
Condition (svSubscriberMappingSessionTimeStampInTheFuture * 100)
/
svSubscriberMappingUpdateMappingSuccess) >= 5
3.59.3 Subscriber Mapping timestamps are in the Future — Clear

This notification is sent when a Subscriber Mapping session timestamp is current, meaning that it is no longer in the future. The
alarm is cleared when the difference between the elements timestamp and the received message is within tolerance.

Trap Name svSubscriberMappingTimestampsNotInFutureNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.23.1.4

05-00262 C07
PTS Alarms

Profile Description
Severity Clear
Condition (svSubscriberMappingSessionTimeStampInTheFuture * 100)
/
svSubscriberMappingUpdateMappingSuccess) <= 1

Varbind Description
svSubscriberMappingSessionTimeStampInThepast This represents a counter that increases when the session
timestamp is in the past.
svSubscriberMappingMappingSuccess This represents a counter that increases when mapping is
successful.
svSubscriberMappingMappingFailure This represents a counter that increases when mapping fails.
svSubscriberMappingUnMappingSuccess This represents a counter that increases when unmapping is
successful.
svSubscriberMappingUnMappingFailure This represents a counter that increases when unmapping fails.
svSubscriberMappingUpdateMappingFailure This represents a counter that increases when update mapping
fails.
svSubscriberMappingUpdateMappingSuccess This represents a counter that increases when update mapping
is successful.
Impact
Subscriber tracing is not exact and can impact your billing and traffic management decisions.
Check the:
05-00262 C07
PTS Alarms
Alarm Model 114: Subscriber Mapping Overloaded
• session_timestamp—Subscriber Mapping configuration parameter.

• Run the service ntpd status command to check the NTP service status and check the server configurations. For
example:
• NTP configuration of components including the SDE, DHCP server, PTS, GGSN, RADIUS, and SPB.
3.59.5 Debugging Mapping Failure on the PTS

If mapping failures appear after receiving the TDF Session-Request from the PCRF to map subscribers, it might indicate a problem
upstream of the SandScript policy. This means that the PTS provisioning subsystem detected the problem. The problem occurs
for one of these reasons:
• The provisioning subsystem is overloaded and cannot accept more transactions.
• The SPB connection was down and the SDE/PTS was unable to send the transaction to the SPB, despite multiple attempts.
• The SPB received the transaction but the transaction failed for some reason.
Run these CLI commands to gather more information about the problem:
• Run the show alarms CLI command. This indicates a connectivity issue or invalid SandScript configuration.
• Run the show service subscriber-provisioning suite of CLI commands. These commands provide more details
about why the transactions failed.
• Run the show service spb connections <DomainName> role subscrriberCLI command. This command shows
a low-level view of the Java Message Service (JMS) abstraction layer (the layer of the SDE/PTS that is closest to the SPB).
# Unmapping success event logging
PolicyGroup expr(Event.SpUnmappingSuccessEvent) all
{
rg_LogEvent(SessionIp: Coalesce(Event.SpUnmappingSuccessEvent.sessionIPv6Address_0,
Event.SpUnmappingSuccessEvent.sessionIPv4Address_0), \
EventType: SM_EVENT_TYPE_UNMAPPING_SUCCESS, \
EventId: SM_EVENT_ID_UNMAPPING_SUCCESS, \
EventStatus: 0, \
StartTime: Now, \
EndTime: Now , \
EventAttribute1: Event.SpUnmappingSuccessEvent.SubscriberName, \
EventAttribute2: string(Event.SpUnmappingSuccessEvent.sessionIPv6Address_0), \
EventAttribute3: string(Event.SpUnmappingSuccessEvent.sessionIPv4Address_0), \
EventAttribute4: Event.SpUnmappingSuccessEvent.SessionId, \
EventAttribute5: string(Event.SpUnmappingSuccessEvent.sessionQualifierSiteNumber_0), \
EventAttribute6: Event.SpUnmappingSuccessEvent.OpaqueData_1, \
EventAttribute10:Event.SpUnmappingSuccessEvent.OpaqueData_5, \
)

Overloaded
This alarm is raised when the elements provisioning subsystem is overloaded.
05-00262 C07
PTS Alarms
The provisioning subsystem allows the element to modify subscribers, subscriber attributes, sessions, and session attributes on
the SPB.
The CLI commands show service subscriber-provisioning performance and show service
subscriber-provisioning stats provide more information about system specifics that could trigger this alarm.
Profile Description
Title Subscriber Mapping Provisioning Overloaded
Severity • Major
• Clear
Raise Notification svProvisionOverloadedNotification

Clear Notification svProvisionOverloadedNotification
Triggers ProvisionOverloadTrigger
Applicability This alarm applies to PTS 6.20 and later
3.60.1 ProvisionOverloadMajEvt: Provision Subsystem is Dropping

Events
This notification is sent whenever the provisioning system drops events for an extended period (one hour or more).

MIB SANDVINE-PROVISION-MIB
Trap Name svInvalidProvisionParamsNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.0.11

svProvisionSummaryDroppedResults 1.3.6.1.4.1.11610.435.19994.1.3.100.8
svProvisionLoginPresenceLoginDropped 1.3.6.1.4.1.11610.435.19994.1.3.200.53
svProvisionLoginCompleteDroppedStorageOverflow 1.3.6.1.4.1.11610.435.19994.1.3.200.81
svProvisionLogoutPresenceLogoutDropped 1.3.6.1.4.1.11610.435.19994.1.3.300.71
svProvisionLogoutCompleteDroppedStorageOverflow 1.3.6.1.4.1.11610.435.19994.1.3.300.91
svProvisionCacheMissMappingCacheMissDropped 1.3.6.1.4.1.11610.435.19994.1.3.500.5
svProvisionReconcileDroppedQueueToPolicyOverflow 1.3.6.1.4.1.11610.435.19994.1.3.400.21
svProvisionLoginSessionsNotTrackedDueToStorageOverflow 1.3.6.1.4.1.11610.435.19994.1.3.200.51
svProvisionLoginIpsNotTrackedDueToStorageOverflow 1.3.6.1.4.1.11610.435.19994.1.3.200.70
svProvisionReconcilePresenceReconcileFailed 1.3.6.1.4.1.11610.435.19994.1.3.400.5
svProvisionLoginPresenceLoginFailedQueueTransactionsFull 1.3.6.1.4.1.11610.435.19994.1.3.200.22
svProvisionLogoutPresenceLogoutFailedQueueTransactionsFull 1.3.6.1.4.1.11610.435.19994.1.3.300.32
05-00262 C07
PTS Alarms

svProvisionSubscriberAttrByNameGetSubAttrByNameDropped 1.3.6.1.4.1.11610.435.19994.1.3.704.9
svProvisionSubscriberAttrByNameGetSubAttrByNameFaile 1.3.6.1.4.1.11610.435.19994.1.3.704.7
dQueueTransactionsFull
svProvisionDeleteSubscriberDeleteSubByNameDropped 1.3.6.1.4.1.11610.435.19994.1.3.705.9
svProvisionDeleteSubscriberDeleteSubByNameFailedQueueTransactionsFull 1.3.6.1.4.1.11610.435.19994.1.3.705.7
Profile Description
Severity Major
Condition Delta (svProvisionSummaryDroppedResults +
svProvisionLoginPresenceLoginDropped +
svProvisionLoginCompleteDroppedStorageOverflow +
svProvisionLogoutPresenceLogoutDropped +
svProvisionLogoutCompleteDroppedStorageOverflow +
svProvisionCacheMissMappingCacheMissDropped +
svProvisionReconcileDroppedQueueToPolicyOverflow +
svProvisionLoginSessionsNotTrackedDueToStorageOverflow +
svProvisionLoginIpsNotTrackedDueToStorageOverflow +
svProvisionReconcilePresenceReconcileFailed +
svProvisionLoginPresenceLoginFailedQueueTransactionsFull +
svProvisionLogoutPresenceLogoutFailedQueueTransactionsFull +
svProvisionSubscriberAttrByNameGetSubAttrByNameDropped +
svProvisionSubscriberAttrByNameGetSubAttrByNameFailedQueueTransactionsFull +
svProvisionDeleteSubscriberDeleteSubByNameDropped +
svProvisionDeleteSubscriberDeleteSubByNameFailedQueueTransactionsFull) > 0
3.60.2 ProvisionOverloadClearEvt: Provision Subsystem is Not

Overloaded
This notification is sent when the provisioning subsystem is no longer overloaded.

Trap Name svProvisionNotOverloadedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.0.2

svProvisionSummaryDroppedResults 1.3.6.1.4.1.11610.435.19994.1.3.100.8
svProvisionLoginPresenceLoginDropped 1.3.6.1.4.1.11610.435.19994.1.3.200.53
svProvisionLoginCompleteDroppedStorageOverflow 1.3.6.1.4.1.11610.435.19994.1.3.200.81
svProvisionLogoutPresenceLogoutDropped 1.3.6.1.4.1.11610.435.19994.1.3.300.71
05-00262 C07
PTS Alarms

svProvisionLogoutCompleteDroppedStorageOverflow 1.3.6.1.4.1.11610.435.19994.1.3.300.91
svProvisionCacheMissMappingCacheMissDropped 1.3.6.1.4.1.11610.435.19994.1.3.500.5
svProvisionReconcileDroppedQueueToPolicyOverflow 1.3.6.1.4.1.11610.435.19994.1.3.400.21
svProvisionLoginSessionsNotTrackedDueToStorageOverflow 1.3.6.1.4.1.11610.435.19994.1.3.200.51
svProvisionLoginIpsNotTrackedDueToStorageOverflow 1.3.6.1.4.1.11610.435.19994.1.3.200.70
svProvisionReconcilePresenceReconcileFailed 1.3.6.1.4.1.11610.435.19994.1.3.400.5
svProvisionLoginPresenceLoginFailedQueueTransactionsFull 1.3.6.1.4.1.11610.435.19994.1.3.200.22
svProvisionLogoutPresenceLogoutFailedQueueTransactionsFull 1.3.6.1.4.1.11610.435.19994.1.3.300.32
svProvisionSubscriberAttrByNameGetSubAttrByNameDropped 1.3.6.1.4.1.11610.435.19994.1.3.704.9
svProvisionSubscriberAttrByNameGetSubAttrByNameFaile 1.3.6.1.4.1.11610.435.19994.1.3.704.7
dQueueTransactionsFull
svProvisionDeleteSubscriberDeleteSubByNameDropped 1.3.6.1.4.1.11610.435.19994.1.3.705.9
svProvisionDeleteSubscriberDeleteSubByNameFailedQueueTransactionsFull 1.3.6.1.4.1.11610.435.19994.1.3.705.7
Profile Description
Severity Clear
Condition Delta (svProvisionSummaryDroppedResults +
svProvisionLoginPresenceLoginDropped +
svProvisionLoginCompleteDroppedStorageOverflow +
svProvisionLogoutPresenceLogoutDropped +
svProvisionLogoutCompleteDroppedStorageOverflow +
svProvisionCacheMissMappingCacheMissDropped +
svProvisionReconcileDroppedQueueToPolicyOverflow +
svProvisionLoginSessionsNotTrackedDueToStorageOverflow +
svProvisionLoginIpsNotTrackedDueToStorageOverflow +
svProvisionReconcilePresenceReconcileFailed +
svProvisionLoginPresenceLoginFailedQueueTransactionsFull +
svProvisionLogoutPresenceLogoutFailedQueueTransactionsFull +
svProvisionSubscriberAttrByNameGetSubAttrByNameDropped +
svProvisionSubscriberAttrByNameGetSubAttrByNameFailedQueueTransactionsFull
+
svProvisionDeleteSubscriberDeleteSubByNameDropped +
svProvisionDeleteSubscriberDeleteSubByNameFailedQueueTransactionsFull) = 0

The element sends login/logout requests to the SPB and the SPB returns an acknowledgement to the element. Traffic is queued
at various stages and Alarm Model 114 is raised when the traffic queues are overloaded.
05-00262 C07
PTS Alarms
Varbind Description
svProvisionSummaryDroppedResults The number of login/logout transaction results received from
the SPB and dropped before processing because the queue
to the provisioning subsystem was full.
svProvisionLoginPresenceLoginDropped The number of login requests dropped before they were
sent to the SPB because the queue from Policy Engine to
the provisioning subsystem was overloaded.
svProvisionLoginCompleteDroppedStorageOverflow The number of login transaction results received from the
SPB and dropped before processing because the queue to
Policy Engine was full.
svProvisionLogoutPresenceLogoutDropped The number of logout requests dropped before they were
sent to the SPB because the queue from Policy Engine to
the provisioning subsystem was overloaded.
svProvisionLogoutCompleteDroppedStorageOverflow The number of logout transaction results received from the
SPB and dropped before processing, because the queue
to Policy Engine was full.
svProvisionCacheMissMappingCacheMissDropped The number of cache miss notifications dropped before the
provisioning subsystem could process them.
svProvisionReconcileDroppedQueueToPolicyOverflow The number of reconcile events dropped because the queue
to Policy Engine was full.
svProvisionLoginSessionsNotTrackedDueToStorageOverflow The number of subscriber sessions that were not tracked
for TTL expiration because the maximum number of tracked
sessions was reached.
svProvisionLoginIpsNotTrackedDueToStorageOverflow The number of subscriber IP addresses that were not
tracked, for TTL expiration, because the maximum number
of tracked addresses was reached.
svProvisionReconcilePresenceReconcileFailed The number of reconcile events not raised to Policy Engine
because a queue internal to the provisioning subsystem
overflowed.
svProvisionLoginPresenceLoginFailedQueueTransactionsFull The number of login transactions not sent to the database
because the queue of pending transactions was already
full.
svProvisionLogoutPresenceLogoutFailedQueueTransactionsFull The number of logout transactions not sent to the database
because the queue of pending transactions was already
full.
svProvisionSubscriberAttrByNameGetSubAttrByNameDropped The number of subscriber profile (get subscriber attributes
by name) operations that were dropped before they could
be processed by the provisioning subsystem.
svProvisionSubscriberAttrByNameGetSubAttrByNameFailed The number of subscriber profile (get subscriber attributes
QueueTransactionsFull by name) operations that were not sent to the database
because the queue of pending transaction to the database
was already full.
svProvisionDeleteSubscriberDeleteSubByNameDropped The number of delete subscriber by name operations that
were dropped before they could be processed by the
provisioning subsystem.
05-00262 C07
PTS Alarms
Varbind Description
svProvisionDeleteSubscriberDeleteSubByNameFailed The number of delete subscriber by name operations that
QueueTransactionsFull were not sent to the database because the queue of pending
transaction to the database was already full.
3.60.3.1 Impact
The provisioning subsystem ensures that the SPB knows which subscribers are mapped to which IP addresses. When SandScript
wants to map (or unmap) a subscriber to an address, the provisioning subsystem proxies that request to the Subscriber Management
System (SMS) on the SRP database. When the database responds, the result is sent back to SandScript.
The subsystem maintains a cache of the mappings for the session, each paired with a time-to-live (TTL). When a mapping TTL
expires, a reconcile event is raised. You can use this event as an action in the SandScript and perform another action. The
database sends an unsolicited notification to the element indicating that it has an IP address and cannot identify the corresponding
subscriber. This is known as a cache miss event.
This alarm indicates that messages on the provisioning interface from the element to the SPB are being dropped. This can result
in operations such as the creation of new sessions or the loss of subscriber attribute modifications.
3.60.3.2 Suggested Resolution

This alarm is typically the result of a miss matched configuration or bursts in the stream of mapping data. Follow these steps to
diagnose:
1. Run the show config service subscriber-provisioning CLI command to verify that the element is properly
provisioned and has adequate capacity for the expected peak load.
PTS> show config service subscriber-provisioning
max-provision-ip: 10
stalled-mapping
interval : 900
percentage: 95
threshold : 10000
stat-mgr-timeout : 3600000
logout-to-policy-queue-size : 100000
login-to-policy-queue-size : 100000
deleted-records-queue-size : 100000
batching-interval : 10
results-queue-size : 100000
policy-to-subsystem-queue-size : 50000
outstanding-transaction : 1000000
enable-tracking : true
backoff-max-limit : 35000
batching-timeout : 10
latency-histogram-lookback : 900
stats-sampling-interval : 1000
request-retries : 3
batch-size : 2000
latency-threshold-for-99th-percentile: 60000
latency-threshold-for-95th-percentile: 30000
backoff-upper-limit : 600000
backoff-multiplier : 4
backoff-min-limit : 30000
2. Run the show service subscriber-provisioning stats CLI command to verify the queue size, login count, logout
count, update count and runtime information.
PTS> show service subscriber-provisioning stats
SUBSCRIBER PROVISIONING STATUS

==============================
TotalLogins : 0
TotalLogouts: 0
TotalUpdates: 0
05-00262 C07
PTS Alarms
INVALID PARAMETERS
==================
Parameter Total Delta

---------- ----- -----
Name 0 0
IP 0 0
Flag 0 0
TimeStamp 0 0
SiteNumber 0 0
NAT MAPPING
===========
TotalLogins : 0
TotalLogouts: 0
INVALID PARAMETERS
==================

----------------- ----- -----
PrivateIP 0 0
PrivatePrefix 0 0
PrivateSiteNumber 0 0
PublicIP 0 0
LowPort 0 0
HighPort 0 0
Timestamp 0 0
SUBSCRIBER PROFILE
==================
TotalRequests: 0
NameInvalid : 0
SUBSCRIBER DELETE
=================
TotalRequests: 0
NameInvalid : 0
GENERAL
=======

-------------- ----- -----
DroppedResults 0 0
AppToProvisionPendingRequests : 0
CurrentSumOfMappingPerInterval: 0
IsStalledMapping : 0
LastSumOfMappingPerInterval : 0
PendingDeletedRecords : 0
PendingRequests : 0
PendingResultsFromStatMgr : 0
3. If the provisioning subsystem configuration was changed, run the show config service subscriber-provisioning
CLI command to verify that there are no issues; for example, if one of the maximum data structures was inadvertently set
too low for your deployment.
You will, for example, see this alarm if you expect one million active concurrent subscribers, but have run:
set config service subscriber-provisioning current-sessions 500000
Note:
This step is not valid on the PTS.
4. The svPresenceLoginPresenceLoginDropped and svPresenceLogoutPresenceLogoutDropped indicate that

the incoming rate of messages on the provisioning interface is too high. This can indicate misconfiguration of either SandScript,
the provisioning subsystem or, less frequently, an extremely large sustained burst of incoming mapping traffic. Run the set
05-00262 C07
PTS Alarms
Alarm Model 115: Invalid Subscriber Provisioning Parameters
config service subscriber-provisioning policy-to-subsystem-queue-size CLI command to increase

the maximum (500,000) queue size.
5. When svProvisionSummaryDroppedResults increases, the database is sending responses to requests faster than
the provisioning subsystem can handle them. Run the set config service subscriber-provisioning
results-queue-size CLI command to increase the maximum (500,000) queue size.
6. When svProvisionCacheMissMappingCacheMissDropped increases, the database is sending cache miss requests

faster than the provisioning subsystem can handle them. Verify that the SPB and the element are provisioned for the correct
subscriber counts and transaction rates. Run the set config service subscriber-provisioning
cache-miss-queue-size CLI command and increase the maximum queue size.
Note:
7. When svProvisionReconcileDroppedQueueToPolicyOverflow,
svProvisionLoginCompleteDroppedStorageOverflow, or
svProvisionLogoutCompleteDroppedStorageOverflow have increased, SandScript is unable to handle the rate of
incoming events from the provisioning subsystem. Run these CLI commands, with new queue-size values that are suitable
for your deployment, to decrease the debug log output and reduce the SandScript engine load:
• set config service subscriber-provisioning login-to-policy-queue-size
• set config service subscriber-provisioning logout-to-policy-queue-size
8. When svProvisionLoginPresenceLoginFailedQueueTransactionsFull and/or

svProvisionLogoutPresenceLogoutFailedQueueTransactionsFull have increased, the SPB did not respond
to requests from the element quickly enough. Verify that the links between the PTS and the SPB, and between the SDE
and PTS, do not have high latency or packet loss rates. Verify that the SPB is not flow controlling notifications. If the SPB
is overloaded as a result of executing another action, it may have fewer CPU cycles to service the PTS requests to map
subscribers. Run the set config service subscriber-provisioning outstanding-transaction CLI command
to ensure that the SPB is not overloaded with other tasks.
9. When svProvisionLoginSessionsNotTrackedDueToStorageOverflow or
svProvisionLoginIpsNotTrackedDueToStorageOverflow have increased, there are more concurrent subscriber
sessions (or addresses per session) than expected. Run either the set config service subscriber-provisioning
current-sessions or set config service subscriber-provisioning current-tracked-ips CLI commands
to increase the maximums values.
Note:
The maximum value for both commands is 20 million.
Note:
3.61 Alarm Model 115: Invalid Subscriber

Provisioning Parameters
This alarm is raised when invalid parameters like bad subscriber name, bad IP (both IPv4 and IPv6), wrong presence flag, and
timestamp is used to provision subscribers. As a result, data on the two nodes may not be synchronized.
05-00262 C07
PTS Alarms
Profile Description
• Major
• Clear
Raise Notification ProvisionInvalidSubParamEvt

Clear Notification ProvisionValidSubParamEvt
Triggers • ProvisionInvalidSubParamTgr
• ProvisionValidSubParamTgr
3.61.1 Invalid Subscriber Provisioning Parameters - Raise

Trap Name svInvalidProvisionParamsNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.11

svProvisionSummaryPresenceNameParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.10
svProvisionSummaryPresenceIPParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.13
svProvisionSummaryPresenceFlagParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.14
svProvisionSummaryPresenceTimestampParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.16
svProvisionSummaryTotalLogins 1.3.6.1.4.1.11610.435.19994.1.3.100.1
svProvisionSummaryTotalLogouts 1.3.6.1.4.1.11610.435.19994.1.3.100.2
Profile Description
Severity Major
Condition (svProvisionSummaryPresenceNameParamInvalid + svProvisionSummaryPresenceIPParamInvalid
+ svProvisionSummaryPresenceFlagParamInvalid + svProvisionSummaryPresence
TimestampParamInvalid) / (svProvisionSummaryTotalLogins + svProvisionSummaryTotalLogouts)
> 5%
Profile Description
Severity Minor
Condition Condition svProvisionSummaryPresenceNameParamInvalid + svProvisionSummaryPresence
IPParamInvalid + svProvisionSummaryPresenceFlagParamInvalid + svProvisionSummaryPresence
TimestampParamInvalid / (svProvisionSummaryTotalLogins + svProvisionSummaryTotalLogouts)
> 2%
05-00262 C07
PTS Alarms
3.61.2 Invalid Subscriber Provisioning Parameters - Clear

Trap Name svValidProvisionParamsNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.12

svProvisionSummaryPresenceNameParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.10
svProvisionSummaryPresenceIPParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.13
svProvisionSummaryPresenceFlagParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.14
svProvisionSummaryPresenceTimestampParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.16
Profile Description
Severity Major
Condition svProvisionSummaryPresenceNameParamInvalid + svProvisionSummaryPresenceIPParamInvalid
+ svProvisionSummaryPresenceFlagParamInvalid + svProvisionSummaryPresence
TimestampParamInvalid / (svProvisionSummaryTotalLogins + svProvisionSummaryTotalLogouts)
< 1%

If it is not possible to log subscribers in or out, the PTS and SDE cannot execute subscriber-aware SandScript properly. It may
not be possible to correctly accumulate by subscriber or subscriber attributes and can result in invalid enforcement and charging
subscribers incorrectly.
A minor alarm may indicate transient network issues or packet corruption. A major alarm indicates a configuration problem from
the Subscriber Mapping application, the elements provisioning policy, or an external entity that sends traffic used for subscriber
mapping, such as SSGN, GGSN, CMTS, AAA server, or DHCP server.
1. Check the varbinds to see which parameter or parameters are missing or invalid.

svProvisionSummaryPresenceNameParamInvalid The name or subscriber ID parameter is missing or has a
null value. Modify the subscriber mapping SandScript to
extract the name from RADIUS messages and use the same
name during provisioning.
svProvisionSummaryPresenceIPParamInvalid Invalid IP arguments when trying to provision a subscriber.
Possible reasons are:
• The IP address (session_ipv4_prefix or
session_ipv6_prefix) is invalid (0.0.0.0).
• The IP prefix or the prefix length is missing.
05-00262 C07
PTS Alarms

• Prefix is negative or greater than maximum (32 for IPv4
and 128 for IPv6).
• Both IPv4 and IPv6 pair is null.
svProvisionSummaryPresenceFlagParamInvalid The presence flag arguments when trying to provision a

subscriber are either missing or have values other than
LOGIN or LOGOUT.
svProvisionSummaryPresenceTimestampParamInvalid The session timestamp is missing or the value is negative.
svProvisionSummaryPresenceSiteNumberParamInvalid The site number is null or greater than 32 bit.
svProvisionSummaryPresenceSessionAttrInUnmapAction A session attribute was specified in an unmapping action (
which is not allowed).
2. If the Subscriber Mapping application is installed, check the package configuration for missing or invalid parameters:
package subscriber_mapping \
debug_flag "true" \
single_ip_assignment "true" \
logging_level "SP_LOGGING_LEVEL_INFO" \
DIAMETER "true" \
trigger "Mapping" \
condition "All(Diameter.Sd.TSR.SubscriptionValue is not null, Diameter.Sd.TSR.ResultCode =
2001)" \
session_id "Diameter.Sd.TSR.SessionID" \
session_ipv4_prefix_length "32" \
session_ipv4_site_number "GetDiameterSiteNumber()" \
session_ipv6_prefix_length "Diameter.Sd.TSR.IPv6PrefixLength" \
session_timestamp "NowMs" \
subscriber_name "Diameter.Sd.TSR.SubscriptionMSISDN"
Check the subscriber_name, session_ipv4_prefix and session_ipv4_prefix_length parameters to see

whether you can set the parameters to null.
3. If the Subscriber Mapping application is not installed, verify that the provisioning policy is set correctly:
- vi /usr/local/sandvine/etc/policy.conf
Provision.Session.ProvisionSubscriber( \
'SubscriberID': sub_name, \
'IPv4[0].Address': StringToIp(sub_ipv4_1), \
'IPv4[0].Prefix':32, \
'IPv6[0].Address': StringToIp("2001:1::4"), \
'IPv6[0].Prefix':32, \
'Presence': Provision.PRESENCE_LOGIN, \
4. Verify that the interface (RADIUS, DIAMETER, DHCP, GTP-C, and so on) that triggers the provisioning process is exposing
the correct values used for provisioning.
5. Configure the originator of the traffic (RADIUS, DHCP, GTP-C, and so on) to send the correct parameters to be used for
future subscriber mapping.
05-00262 C07
PTS Alarms
Alarm Model 116: Discarded Subscriber Provisioning Update
3.62 Alarm Model 116: Discarded Subscriber

Provisioning Update
This alarm is raised when the ratios of DeleteNameFailed/TotalDeletes and GetNameFailed/TotalGets exceeds the
threshold value. As a result, data synchronization may not exist on the PTS and the SPB.
Profile Description
• Warning
• Major
• Clear
Raise Notification svSpbErrorNotification

Clear Notification svNoSpbErrorNotification
Triggers • ProvisionSpbErrorDetectedTgr
• ProvisionSpbErrorResolvedEvt
3.62.1 Discarded Subscriber Provisioning Update - Raise

Trap Name svProvisioningSpbErrorResolvedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.7

svProvisionLoginSPBfailures 1.3.6.1.4.1.11610.435.19994.1.3.200.100
svProvisionLogoutSPBfailures 1.3.6.1.4.1.11610.435.19994.1.3.300.100
svProvisionLoginSPBfailuresLoginFailureName 1.3.6.1.4.1.11610.435.19994.1.3.200.100.1.1
svProvisionLoginSPBfailuresLoginFailureCount 1.3.6.1.4.1.11610.435.19994.1.3.200.100.1.2
svProvisionLogoutSPBfailuresLogoutFailureName 1.3.6.1.4.1.11610.435.19994.1.3.300.100.1.1
svProvisionLogoutSPBfailuresLogoutFailureCount 1.3.6.1.4.1.11610.435.19994.1.3.300.100.1.2
svProvisionMalformedResults 1.3.6.1.4.1.11610.435.19994.1.3.100.26
svProvisionSummaryNatTotalLogins 1.3.6.1.4.1.11610.435.19994.1.3.100.32
svProvisionSummaryNatTotalLogouts 1.3.6.1.4.1.11610.435.19994.1.3.100.32
svProvisionDeleteSubscriberDeleteSubByNameFailed 1.3.6.1.4.1.11610.435.19994.1.3.100.50
svProvisionSubscriberAttrByNameGetSubAttrByNameFailed 1.3.6.1.4.1.11610.435.19994.1.3.100.50
svProvisionSummaryTotalDeletes 1.3.6.1.4.1.11610.435.19994.1.3.100.51
05-00262 C07
PTS Alarms

svProvisionSummaryGetSubAttrByNameRequests 1.3.6.1.4.1.11610.435.19994.1.3.100
Profile Description
Severity Major
Condition (one of svProvisionLoginSPBfailures)/(svProvisionSummaryTotalLogins +
svProvisionSummaryNatTotalLogins) + svProvisionMalformedResults/(svProvisionSummaryTot
alLogins + svProvisionSummaryNatTotalLogins + svProvisionSummaryTotalLogouts +
svProvisionSummaryNatTotalLogouts) + (one of svProvisionLogoutSPBfailures)/(
svProvisionSummaryTotalLogouts + svProvisionSummaryNatTotalLogouts) >= 3%"
Profile Description
Severity Minor
svProvisionSummaryTotalLogouts + svProvisionSummaryNatTotalLogouts) >= 2%
AND
(one of svProvisionLoginSPBfailures)/(svProvisionSummaryTotalLogins +
svProvisionSummaryTotalLogouts + svProvisionSummaryNatTotalLogouts) < 3%
Profile Description
Severity Warning
svProvisionSummaryTotalLogouts + svProvisionSummaryNatTotalLogouts) >= 1%
AND
(one of svProvisionLoginSPBfailures)/(svProvisionSummaryTotalLogins +
svProvisionSummaryTotalLogouts + svProvisionSummaryNatTotalLogouts) < 2%
3.62.2 Discarded Subscriber Provisioning Update - Clear

Trap Name svProvisioningSpbErrorResolvedNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.8
05-00262 C07
PTS Alarms

svProvisionLoginSPBfailures 1.3.6.1.4.1.11610.435.19994.1.3.200.100
svProvisionLogoutSPBfailures 1.3.6.1.4.1.11610.435.19994.1.3.300.100
svProvisionMalformedResults 1.3.6.1.4.1.11610.435.19994.1.3.100.26
svProvisionSummaryNatTotalLogins 1.3.6.1.4.1.11610.435.19994.1.3.100.32
svProvisionSummaryNatTotalLogouts 1.3.6.1.4.1.11610.435.19994.1.3.100.32
svProvisionDeleteSubscriberDeleteSubByNameFailed 1.3.6.1.4.1.11610.435.19994.1.3.100.50
svProvisionSubscriberAttrByNameGetSubAttrByNameFailed 1.3.6.1.4.1.11610.435.19994.1.3.100.50
svProvisionSummaryGetSubAttrByNameRequests 1.3.6.1.4.1.11610.435.19994.1.3.100
Profile Description
Severity Major
svProvisionSummaryTotalLogouts + svProvisionSummaryNatTotalLogouts) < 2/3%

If it is not possible to log subscribers in or out, the PTS and the SDE cannot execute subscriber-aware policies properly. It may
not be possible to correctly calculate by subscriber or subscriber attributes. It may result in invalid enforcement and charging
subscriber incorrectly.
• If the alarm is at warning level, the subscribers are mapped successfully, but problems can still exist. Check the show
service subscriber-provisioning stats logout|logout CLI command for more information:
a. If the SubscriberCreate counter caused the alarm, it indicates that unmapped subscribers are not known to the SPB.
If this is a new deployment, this may not indicate a problem. However, if the problem persists, it can indicated that SPB
is missing login requests. Verify this against the provisioning counter, the subscriber mapping application (if relevant),
and the interface that should trigger the mapping.
b. If InvalidAttribute counters are causing the problem, it indicates that the attribute definitions on the element and
SPB are not consistent.
On the SDE—Run the service sde reload command, from the SDE shell, to reload the SDE.
On the PTS—Run the svreload command, to reload the PTS.
c. Check that the attribute definitions in the /usr/local/sandvine/etc/policy.conf file on the SDE match the attributes
defined in the SPB database:
05-00262 C07
PTS Alarms
• psql sv_stat pgsql
• sv_stat=# select * from subscriber_attr_defn
• A major or minor alarm can indicate a configuration or network problem, or an SPB issue. Check the show service
subscriber-provisioning stats logout|logout CLI command to identify the problem:
a. If Offline counters are causing the alarm, it indicates that the SPB is overloaded, down, or has run into base state too
often. Verify that the SPB is running. Check /var/log/svlog for this message that shows the SPB is still running:
(URI: `<SPB IP>`)
b. If the log message does not appear, configure the SPB connection properly. See the SDE User Guide for additional
information.
c. Verify that the request retrying parameters on the element are configured correctly. Use a timeout sufficient to let the
SPB recover from temporary problems.
• show config service subscriber-provisioning backoff-max-limit— The value must exceed more
than 30000ms.
• show config service subscriber-provisioning backoff-upper-limit—The value must exceed more
than 30000ms.
• show config service subscriber-provisioning backoff-multiplier—The value must exceed more
than 30000ms.
• show config service subscriber-provisioning backoff-min-limit—The value must exceed than
30000ms.
d. Ensure that the batching parameters are configured properly so as not to create large bursts on the SPB. You may need
to tune the SPB to reduce the load. Run these CLI commands:
• show config service subscriber-provisioning batching-interval
• show config service subscriber-provisioning batch-size
e. If Invalid counters are causing the problem, it indicates that the subscriber realm used in the message is not defined
on the SPB, or the SPB is missing the definition of a default subscriber realm.
f. If Rejected counters are causing the alarm, it indicates that the SPB does not support the subscriber provision interface.
Verify that the SPB is release 6.00 or later.
Run the show system version CLI command on the SPB.
g. If Unclassified counters are causing the alarm, it indicates that the SPB encountered an unexpected error.
h. If LinkDown counters are causing the alarm, it indicates there is a persistent communication problem with the SPB:
• Check network configuration and connectivity.
• Check the status of the sonicMQ message broker on the SPB.
• Check /var/log/svlog for this message that shows the SPB is still running:
(URI: `<SPB IP>`)
If the log message does not appear, configure the SPB connection properly. See the SDE User Guide for additional
information.
05-00262 C07
PTS Alarms
Alarm Model 117: Delayed Mapping
3.63 Alarm Model 117: Delayed Mapping

This alarm is raised when latency in mapping or unmapping subscribers exceeds the default threshold of 30 seconds. Run the
show config servicesubscriber-provisioning to verify the default thresholds for
latency-threshold-for-99th-percentile and latency-threshold-for-95th-percentile.
Profile Description
Severity: • Major
• Minor
• Warning
• Clear
Raise Notification: • ProvisionDelayedMappingMajorEvt

• ProvisionDelayedMappingMinorEvt
• ProvisionDelayedMappingWarnEvt
Clear Notification: ProvisionDelayedMappingClearEvt

Triggers: • ProvisionDelayedMappingMajorTgr
• ProvisionDelayedMappingWarnTgr
• ProvisionDelayedMappingMinorTgr
• ProvisionDelayedMappingClearTgr
Applicability: This alarm applies to SDE 6.20 and later
3.63.1 High Subscriber Provisioning Latency

This notification is sent when subscriber provisioning latency is too high. The default thresholds are 2500 ms for the 99th percentile
and 1000 ms for the 95th percentile. This means that alarm model 117 is raised if the latency for more than 5 percent exceeds
1000 ms. However, these values are configurable, for the 99th percentile and the 95th percentile accordingly, using:
set config service subscriber-provisioning latency-threshold-for-95th-percentile <value> or
set config service subscriber-provisioning latency-threshold-for-99th-percentile <value> CLI
commands.

Trap Name svProvisionDelayedMappingNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.9

svProvisionPerformanceReqProc95Percentiles 1.3.6.1.4.1.11610.435.19994.1.3.600.19
svProvisionConfigBad95thPercentileThreshold 1.3.6.1.4.1.11610.435.19994.1.2.10
05-00262 C07
PTS Alarms

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Severity Major
Condition svProvisionPerformanceReqProc95Percentiles >=
svProvisionConfigBad95thPercentileThreshold ||
svProvisionPerformanceReqProc99Percentiles >=
svProvisionConfigBad99PercentileThreshold
3.63.2 Medium Subscriber Provisioning Latency

This notification is sent when some subscriber provisioning latencies are nearing unacceptable durations. For the 99th percentile,
this is 70 percent of the threshold that is defined for the major alarm. It is 75 percent of the threshold for the 95th percentile.
Run the show config service subscriber-provisioning CLI command to verify the default thresholds.

Trap OID 1.3.6.1.4.1.11610.6799.3.26.9

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Severity Minor
Condition svProvisionPerformanceReqProc95Percentiles <
svProvisionConfigBad95thPercentileThreshold AND
05-00262 C07
PTS Alarms
Profile Description
svProvisionPerformanceReqProc99Percentiles <
svProvisionConfigBad99PercentileThreshold
AND
svProvisionPerformanceReqProc95Percentiles >= (7/
10)*svProvisionConfigBad95thPercentileThreshold OR
svProvisionPerformanceReqProc99Percentiles >= (75/
100)*svProvisionConfigBad99PercentileThreshold
3.63.3 Moderate Subscriber Provisioning Latency

This notification is sent when subscriber provisioning latencies indicate potential for unacceptably long durations. Refer to the
conditions field in the Profile table for more information.

Trap OID 1.3.6.1.4.1.11610.6799.3.26.9

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Severity Warning
Condition svProvisionPerformanceReqProc95Percentiles < (7/10) *
svProvisionConfigBad95thPercentileThreshold AND
svProvisionPerformanceReqProc99Percentiles < (75/100) *
svProvisionConfigBad99thPercentileThreshold
AND
svProvisionConfigBad95thPercentileThreshold/2 OR
svProvisionConfigBad99thPercentileThreshold/2
05-00262 C07
PTS Alarms
3.63.4 Optimal Subscriber Provisioning Latency

This notification is sent when subscriber provisioning latencies have returned to an acceptable low duration.

Trap Name svProvisionNotDelayedMappingClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.0.10

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Severity Clear
Condition svProvisionPerformanceReqProc95Percentiles <
svProvisionConfigBad95thPercentileThreshold/2 and
svProvisionPerformanceReqProc99Percentiles <
svProvisionConfigBad99PercentileThreshold/2

This alarm indicates problems in subscriber mapping latency. It monitors the 95th and 99th percentile latencies as an indication
of systemic problems. Refer to the conditions field in the Profile table for information on actual thresholds.
3.63.5.1 Impact
If the changes in the subscriber rates do not get implemented throughout the system, the system incorrectly executes the
subscriber-related policies on the PTS and SDE. This incorrect execution can result in inaccurate subscriber statistics, charging
information, and enforcement actions.
This alarm measures transaction latency between the element and the SPB. Alarm severity increases as latencies grow larger;
low latencies are better and higher latencies are worse.
95th Percentile Latency Severity

Less than 250ms No Alarm
250 to 350ms Warning
05-00262 C07
PTS Alarms
95th Percentile Latency Severity

350ms to 500ms Minor
500ms+ Major
The 95th percentile is tracked separately for subscriber login and logout transactions using
svProvisionPerformanceLoginReqProc95Percentiles and svProvisionPerformanceLogoutReqProc95Percentiles. Latencies at
the 99th percentile level track these transactions through svProvisionPerformanceLoginReqProc99Percentiles and logout using
svProvisionPerformanceLogoutReqProc99Percentiles.
Varbind Description
svProvisionPerformanceLoginReqProc95Percentiles The 95th percentile of the login latency, from the time an event
is detected on the element until the SPB confirms that the
mapping database was updated.
svProvisionPerformanceLogoutReqProc95Percentiles The 95th percentile of the logout latency, from the time an event
is detected on the SDE until the SPB confirms that the mapping
database was updated.
svProvisionPerformanceLoginReqProc99Percentiles The 99th percentile of the login latency, from the time an event
svProvisionPerformanceLogoutReqProc99Percentiles The 99th percentile of the logout latency, from the time an event
3.63.5.2 Resolution
1. Ping the SPB to check network conditions and latency.
The optimal round-trip ping latency is 250 microseconds or less. Higher latencies will contribute this alarm, similar to packet
loss rates greater than 0 percent. If the SDE is in a geographically different location from the SPB, or if a latency-inducing
stateful router is installed between them, latency can reach a point where this alarm is raised.
2. Run these CLI commands on the SPB to check the SPB status:
Note:
It can take several minutes for these commands to execute.
• show service subscriber-management dashboard
• show service subscriber-provisioning stats
3. Run the ping command from the SDE and measure the latency. Acceptable ping latency is RTTs < 200 microseconds
99.999 percent of the time, with 0 percent packet loss.
4. Perform a general SPB health check if ping latency is out of tolerance and address any active alarms.
5. Run the show service subscriber-management dashboard, show service subscriber-provisioning

stats, and show service subscriber-management stats CLI commands on the SPB and analyze the results.
6. Run the show service subscriber-provisioning stats, show service subscriber-provisioning stats
login/logout/update, and show service subscriber-provisioning performance CLI commands on the
element and analyze the results, which should show no failures or errors.
You should specifically look for failures due to SPB errors (included in the results of the show service
subscriber-provisioning stats login/logout/update command). Note the failures due to SPB errors entry
in the output. Failures due to SPB errors indicate a misconfiguration of the SPB or that the SPB is not functioning properly.
05-00262 C07
PTS Alarms
Alarm Model 125: Subscriber Mappings have Stalled or Halted
The output from the show service subscriber-provisioning performance command identifies latency (in
milliseconds). Based on percentile, acceptable latencies are:
Percentile Acceptable latency

50 300 ms
75 500 ms
95 1000 ms
99 2000 ms
3.64 Alarm Model 125: Subscriber Mappings have

Stalled or Halted
This alarm is raised when the rate of mapping requests received in the provisioning subsystem decreases at an abnormally rapid
pace.
Profile Description
• Clear
Raise Notification svSubscriberMappingsStalledNotification

Clear Notification svSubscriberMappingsStalledClearNotification
Triggers ProvisionStalledMappingTrigger
Applicability This alarm applies to:
• SDE—6.20 and later.
• PTS—7.40 or later.
3.64.1 Number of Mapping Requests is Stalling

This notification is sent when there is a sudden decrease in the rate of subscriber mappings, which indicates a potential problem
in the system.

Trap Name svSubscriberMappingsStalledNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.0.3

svProvisionSummaryIsStalledMapping 1.3.6.1.4.1.11610.435.19994.1.3.100.23
05-00262 C07
PTS Alarms
Alarm Model 125: Subscriber Mappings have Stalled or Halted

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Severity Warning
Condition svProvisionSummaryIsStalledMapping > 0
3.64.2 Number of Mapping Requests is Not Stalling - Clear

This notification is sent when new mappings in the provisioning subsystem are no longer stalled.

Trap Name svSubscriberMappingsStalledClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.0.4

svProvisionSummaryIsStalledMapping 1.3.6.1.4.1.11610.435.19994.1.3.100.23
sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
Profile Description
Severity Clear
Condition svProvisionSummaryIsStalledMapping == 0

The svProvisionSummaryIsStalledMapping varbind is set to 1 when the rate of mapping requests received in the provisioning
subsystem decreases at an abnormally rapid pace. When the decrease crosses a configurable percentage (configurable in the
CLI), between two intervals, and the number of mappings during the last interval is greater than a configurable threshold, the
svProvisionSummaryIsStalledMapping flag is set to one. This is designed to detect a sudden decrease in the mapping rate.
The threshold is configurable, to prevent false alarms, and includes these special values:
05-00262 C07
PTS Alarms
Alarm Model 129: Disconnected Tee Destination
• 100—With this value, the alarm only occurs when the decrease in mapping requests reaches zero.
• 0—The alarm is never raised when the value is configured as zero.
Run the show config service subscriber-provisioning CLI command to display all of the values currently configured
in the system. This will identify the systems current state.
Run the set config service subscriber-provisioning stalled-mapping interval <num of sec> CLI
command to configure the time interval at which the provisioning system checks whether the number of mapping requests is
stalling. The default interval is 900 seconds.
The alarm is raised when a percentage reduction in login transactions is detected from one interval to the next. Run the set
config service subscriber-provisioning stalled-mapping percentage <x percent> CLI command to change
the percentage from the 95 percent default value.
This alarm is raised only if the number of mappings that occurred during the previous interval was greater than this threshold.
Run the set config service subscriber-provisioning stalled-mapping threshold <value> CLI command
to change the threshold from its default value of 10000.
Impact
In some instances, mapping requests might get dropped as part of normal operation and does not indicate an SDE problem.
Run the show service subscriber-mapping stats CLI command as a general diagnostic step. This helps in identifying
the current status of traffic, as it applies to the Subscriber Mapping application.
3.65 Alarm Model 129: Disconnected Tee

Destination
This alarm is raised when the tee destination is down.
Profile Description
• Clear
Raise Notification svTeeDestinationDownNotification

Clear Notification svTeeDestinationUpNotification
Triggers • teeDestDownTriggered
• teeDestDownClrTriggered
Unique Instance Identifier svDestinationsTeeDestinationName
3.65.1 svTeeDestinationDownNotification: Disconnected Tee

Destination—Minor
This notification is sent when the Tee destination is down. The name of the tee destination which is down is found in the
svDestinationsTeeDestinationName varbind.
05-00262 C07
PTS Alarms
Alarm Model 129: Disconnected Tee Destination

MIB SANDVINE-MIB
Trap Name svTeeDestinationDownNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.17

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDestinationsTeeDestinationName 1.3.6.1.4.1.11610.435.13433.1.10.1.2
svDestinationsTeeDestinationIpAddr 1.3.6.1.4.1.11610.435.13433.1.10.1.5
svDestinationsTeeDestinationEtherAddr 1.3.6.1.4.1.11610.435.13433.1.10.1.6
svDestinationsTeeDestinationStatus 1.3.6.1.4.1.11610.435.13433.1.10.1.7
Profile Description
Severity Minor
Condition svDestinationsTeeDestinationStatus == statusDown
3.65.2 svTeeDestinationUpNotification: Disconnected Tee

Destination—Clear
This notification is sent when the Tee destination is back up again. The name of the up tee destination is found in the
svDestinationsTeeDestinationName varbind.

MIB SANDVINE-MIB
Trap Name svTeeDestinationUpNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.18

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDestinationsTeeDestinationName 1.3.6.1.4.1.11610.435.13433.1.10.1.2
svDestinationsTeeDestinationIpAddr 1.3.6.1.4.1.11610.435.13433.1.10.1.5
05-00262 C07
PTS Alarms
Alarm Model 130: Disconnected Divert Destination

svDestinationsTeeDestinationEtherAddr 1.3.6.1.4.1.11610.435.13433.1.10.1.6
svDestinationsTeeDestinationStatus 1.3.6.1.4.1.11610.435.13433.1.10.1.7
Profile Description
Severity Clear
Condition svDestinationsTeeDestinationStatus == statusUp

Teeing redirects a copy of the traffic flow to a file or to another device for further processing.
Details of tee configuration can be found in the SandScript Configuration Guide.
If a tee destination is down, traffic cannot be teed to the specified destination. If the tee destination is SPB or SDE, mapping of
IP addresses to corresponding subscribers fails. Depending on the charging model, this can cause loss of revenue from the
subscriber.
Possible causes for a tee destination to be down are:
• Network connection problems between PTS and the tee destination.
• The tee destination is not operating correctly. Perhaps because its interface is down, the destination is not powered on, and
so on.
• The tee destination is not accepting ping from the PTS.
1. To obtain additional information, such as the number of bytes teed, run the show policy destination <tee
destination name> CLI command.
2. If there are healthchecks defined for the tee destination, ensure the healthcheck is up.
3. Check that the tee destination is operating properly.
4. Check the wiring and router connections between the PTS and tee destination. A successful connection can be confirmed
by pinging the destination IP address from the PTS controller.
3.66 Alarm Model 130: Disconnected Divert

Destination
This alarm is raised when a divert destination is not operating.
Profile Description
• Clear
05-00262 C07
PTS Alarms
Profile Description
Raise Notification svDivertDestinationDownNotification
Clear Notification svDivertDestinationUpNotification
Triggers: • divertDestDownTriggered
• divertDestDownClrTriggered
Unique Instance Identifier svDestinationsDivertDestinationName
3.66.1 svDivertDestinationDownNotification: Disconnected Divert

Destination—Minor
This notification is sent when the Divert destination is down. The name of the inoperable divert destination is found in the
svDestinationsDivertDestinationName varbind.

MIB SANDVINE-MIB
Trap Name svDivertDestinationDownNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.19

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDestinationsDivertDestinationName 1.3.6.1.4.1.11610.435.13433.1.12.1.2
svDestinationsDivertDestinationStatus 1.3.6.1.4.1.11610.435.13433.1.12.1.8
svDestinationsDivertDestinationAdminStatus 1.3.6.1.4.1.11610.435.13433.1.12.1.17
svDestinationsDivertDestinationErrors 1.3.6.1.4.1.11610.435.13433.1.12.1.101
svDestinationsDivertDestinationIsChildOfSequence 1.3.6.1.4.1.11610.435.13433.1.12.1.16
Profile Description
Severity Minor
Condition svDestinationsDivertDestinationStatus == statusDown && svDestinationsDivertDestin
ationIsChildOfSequence == false
05-00262 C07
PTS Alarms
3.66.2 svDivertDestinationUpNotification: Disconnected Divert

Destination—Clear
This notification is sent when the Divert destination is up. The name of the up divert destination is found in the varbind
svDestinationsDivertDestinationName.

MIB SANDVINE-MIB
Trap Name svDivertDestinationUpNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.22

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDestinationsDivertDestinationName 1.3.6.1.4.1.11610.435.13433.1.12.1.2
svDestinationsDivertDestinationStatus 1.3.6.1.4.1.11610.435.13433.1.12.1.8
svDestinationsDivertDestinationAdminStatus 1.3.6.1.4.1.11610.435.13433.1.12.1.17
svDestinationsDivertDestinationErrors 1.3.6.1.4.1.11610.435.13433.1.12.1.101
svDestinationsDivertDestinationIsChildOfSequence 1.3.6.1.4.1.11610.435.13433.1.12.1.16
Profile Description
Severity Clear
Condition svDestinationsDivertDestinationStatus == statusUp

Divert redirects selected traffic to a device on the PTS service network instead of forwarding it as is normally done.
Details of divert configuration can be found in the SandScript Configuration Guide.
A divert destination that is down causes diverted flows to experience packet loss until the flow ends.
Possible causes for a divert destination to be down are:
• Network connection problems between the PTS and the divert destination.
• The divert destination is not operating correctly.
• Check that its interface is up.
• Verify that the destination is powered on.
• The divert destination is not configured correctly.
05-00262 C07
PTS Alarms
Alarm Model 131: Disconnected Divert Sequence Destination
• Check the MTU settings and the HTTP healthcheck configuration.

• Verify that the HTTP server is responding to requests.
For new flows that use the failed destination, a divert action is not applied for five minutes; instead the flows go through to their
network destination after all other SandScript is applied. After five minutes, if there are other healthy divert destinations within
the divert destination group, new flows are balanced to other healthy divert destinations within the group. New flows are diverted
if the divert destination host comes back up during that interval. No flows are diverted except when the flow is new. Otherwise,
the divert action is not applied until there is another healthy divert destination within the group.
To resolve this issue:
1. Identify the <divert destination name> from the alarm varbind called svDestinationsDivertDestinationName.
2. Run the show policy destination <divert destination name> CLI command to gather information, such as
the IP of the divert destination.
3. Run the show policy healthcheck CLI command to ensure any healthcheck defined for divert destinations is operational.
4. Log on to the divert destination and verify that the divert destination is operating properly.
5. Check the wiring and router connections between PTS and divert destination.
6. Check that the MTU of the divert destination matches the MTU of the data path.
7. Ensure the divert destination (for TCP flow) is responding to the TCP handshake from the PTS.
3.67 Alarm Model 131: Disconnected Divert

Sequence Destination
This alarm is raised when the divert sequence destination is down. A divert sequence destination is a member of a divert sequence.
It is a dedicated networked device which is designed to filter or reply to a specific kind of traffic, as specified in policy.
Profile Description
• Clear
Raise Notification svDivertSeqDestinationDownNotification

Clear Notification svDivertSeqDestinationUpNotification
Triggers • divertSeqDestDownTriggered
• divertSeqDestDownClrTriggered
Unique Instance Identifier svDestinationsDivertSequenceDestinationName
05-00262 C07
PTS Alarms
3.67.1 svDivertSeqDestinationDownNotification : Disconnected

Divert Sequence Destination
This notification is sent when the Divert sequence destination is down. The name of the down divert sequence destination can
be found in the varbind svDestinationsDivertSequenceDestinationName.

MIB SANDVINE-MIB
Trap Name svDivertSeqDestinationDownNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.21

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDestinationsDivertSequenceDestinationName 1.3.6.1.4.1.11610.435.13433.1.16.1.2
svDestinationsDivertSequenceDestinationStatus 1.3.6.1.4.1.11610.435.13433.1.16.1.8
svDestinationsDivertSequenceDestinationAdminStatus 1.3.6.1.4.1.11610.435.13433.1.16.1.24
svDestinationsDivertSequenceDestinationChildDestinations 1.3.6.1.4.1.11610.435.13433.1.16.1.16
svDestinationsDivertSequenceDestinationErrors 1.3.6.1.4.1.11610.435.13433.1.16.1.18
Profile Description
Severity Minor
Condition svDestinationsDivertSequenceDestinationStatus == statusDown
3.67.2 svDivertDestinationSeqUpNotification:Disconnected Divert

Sequence Destination—Clear
This notification is sent when the Divert sequence destination is up. The name of the up divert sequence destination is found in
the varbind svDestinationsDivertSequenceDestinationName.

MIB SANDVINE-MIB
Trap Name svDivertSeqDestinationClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.7.0.22
05-00262 C07
PTS Alarms

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svDestinationsDivertSequenceDestinationName 1.3.6.1.4.1.11610.435.13433.1.16.1.2
svDestinationsDivertSequenceDestinationStatus 1.3.6.1.4.1.11610.435.13433.1.16.1.8
svDestinationsDivertSequenceDestinationAdminStatus 1.3.6.1.4.1.11610.435.13433.1.16.1.24
svDestinationsDivertSequenceDestinationChildDestinations 1.3.6.1.4.1.11610.435.13433.1.16.1.16
svDestinationsDivertSequenceDestinationErrors 1.3.6.1.4.1.11610.435.13433.1.16.1.18
Profile Description
Severity Clear
Condition svDestinationsDivertSequenceDestinationStatus == statusUp

A divert sequence is a way to allow selected traffic to be redirected to multiple devices on the PTS service network instead of
being forwarded on the data-intersect network.
Details of divert sequence configuration can be found in the SandScript Configuration Guide.
A divert sequence destination that is down causes an existing diverted flow to experience packet loss until the flow ends. Possible
reasons for a divert sequence destination to be down are:
• Network connection problems between PTS and the divert destination sequence.
• A member of the divert sequence destination is not operating correctly. Check that its interface is up, the destination is powered
on, and so on.
• The divert sequence destination is not configured correctly. Check its MTU settings, VLAN configurations, and so on.
For new flows that are bound for the failed destination, the divert action is not applied for five minutes. After five minutes, if there
are other healthy divert destinations within the group, new flows are balanced to a healthy divert destination within the group.
Otherwise, divert action is not applied until there is at least one other healthy divert destination within the group.
1. To obtain additional information, such as the VLAN or the name of the child destination, run the show policy destination
<divert sequence destination name> CLI command.
2. If there are healthchecks defined for the divert sequence destination, ensure that the associated healthcheck is up by running
show policy healthcheck CLI command.
3. Log on to the child divert destination to verify if the divert destination is operating properly.
4. Check the wiring and router connections between PTS and divert destination.
5. Ensure the MTU of the divert destination matches the MTU of the data path.
05-00262 C07
PTS Alarms
Alarm Model 132: Worn Solid State Drive
6. For TCP flow, ensure the divert destination is responding to the TCP handshake from the PTS.
3.68 Alarm Model 132: Worn Solid State Drive

This alarm is raised when the system's solid state drive (SSD) is nearing end-of-life or is aging abnormally quickly. The alarm is
sent in time to give you time to prevent rapid aging and avert drive failure.
Note:
Alarm Model 132 (Worn Solid State Drive) is not supported on the PTS Linux platform.
Profile Description
• Warning
• Clear
Raise Notification svEnvStorageSSDLifespanNotification

Clear Notification svEnvStorageSSDLifespanClearNotification
Triggers • SSDWearWarnTrigger
• SSDWearMinorTrigger
• SSDWearClearTrigger
Unique Instance Identifier svStorageDiskTableIndex

Applicability PTS 6.1 and higher
3.68.1 svEnvStorageSSDLifespanNotification:Worn Solid State Drive

This notification is sent when the system's SSD has aged to 50% of its lifespan. The minor notification is sent if the system's SSD
has aged to 80% of its lifespan.

MIB SANDVINE-MIB
Trap Name svEnvStorageSSDLifespanNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.21

svStorageDiskTablePercentageLifetimeUsed 1.3.6.1.4.1.11610.435.11249.1.12.1.25
svStorageDiskTablePowerOnHours 1.3.6.1.4.1.11610.435.11249.1.12.1.26
05-00262 C07
PTS Alarms
3.68.1.1 SSD nearing end-of-life—Warning

This notification is sent when the SSD is approaching the end of its lifespan.
Profile Description
Severity Warning
Condition svStorageDiskTablePercentageLifeTimeUsed >= svStorageConfigSSDWearWarnThreshold
&& svStorageDiskTablePercentageLifeTimeUsed < svStorageConfigSSDWearMinorThreshold
3.68.1.2 SSD nearing end-of-life—Minor

This notification is sent when the SSD is near the end of its lifespan and is ready for replacement.
Profile Description
Severity Minor
Condition svStorageDiskTablePercentageLifeTimeUsed >= svStorageConfigSSDWearMinorThreshold
3.68.2 svEnvStorageSSDLifespanClearNotification: Worn Solid State

Drive Cleared
This notification is sent when the system's SSD lifespan is acceptable.

MIB SANDVINE-MIB
Trap Name svEnvStorageSSDLifespanClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.1.0.22

svName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svStorageDiskTablePercentageLifetimeUsed 1.3.6.1.4.1.11610.435.11249.1.12.1.25
svStorageDiskTablePowerOnHours 1.3.6.1.4.1.11610.435.11249.1.12.1.26
3.68.2.1 SSD lifespan good—Clear

This notification is sent when the system's SSD remaining lifespan is acceptable.
05-00262 C07
PTS Alarms
Profile Description
Severity Clear
Condition svStorageDiskTablePercentageLifeTimeUsed < svStorageConfigSSDWearWarnThreshold

This alarm does not indicate a service-affecting condition, however the SSD is expected to suffer increasing penalties to write
performance until it fails. Complete these procedures to diagnose, resolve, or mitigate the condition that is affecting the SSD’s
lifespan. If the alarm severity is minor, after using these steps, replace the drive at your earliest convenience.
Examine the drive, in particular look at the number of power on hours. If it is more than 16000 hours (approximately two years),
the issue is likely age-related and you should replace the disk. Before doing so, refer to:
1. Gather Drive Information on page 239
2. Determine if the Disk is Overused on page 239
3.68.3.1 Gather Drive Information

Prior to replacing the drive:
1. Note of the description of the worn-out drive
2. Run the show system storage disk CLI command, then note the drive ID.
3. Run the show system storage disk <id> CLI command, then note the information in the deviceName and
powerOnHours fields.
3.68.3.2 Determine if the Disk is Overused

To determine whether the disk is overused:
1. Run the command: iostat –d <device> 6 10 CLI command, from the system shell, but replace <device> with the
deviceName noted in Impact and Suggested Resolution, Alarm Model 132 on page 239—with the leading “/dev/” removed.
For instance, if deviceName were” /dev/ad0”, you would enter ad0 as the <device>.
This displays I/O statistics for the worn-out drive every 6 seconds for 1 minute. If the MB/s column is frequently over 20,
then the wear may be due to aggressive writes to the disk. Otherwise, the alarm is probably the result of disk age.
2. Run the top –mio command, from the system shell, and note which processes are near the top of the list and have a high
number (over 100) in the “WRITE” column. This lets you determine which process is over-using the disk. Press q, when
done, to return to a shell.
3. Complete these steps if ptsd or nfsd is at fault:

a. Run the show policy destination CLI command and note any entries under “FILE DESTINATIONS”.
b. Determine whether the BytesTeed column is suspiciously high (depending on how long the policy has run, upwards
of terabytes), wait approximately one minute, and then run the show policy destination CLI command again.
Note the change in the BytesTeed column and, if it has increased by more than a gigabyte, this is likely the source
of the wear.
05-00262 C07
PTS Alarms
Alarm Model 133: Misconfigured Cluster Name
c. Evaluate the importance of this data, and determine whether to adjust the sandScript to avoid wearing out the disk or
to continue using it and risk replacing the disk frequently.
4. Complete these steps if syslogd is at fault:

a. From the system shell, run the ls –l /var/log command, then note the file size values (in the fifth column).
b. Wait for a minute, then re-run the ls –l /var/log command. If any of the numbers have changed substantially (by
nearly billions), then this is likely the source of the wear. Examine the offending files and determine what is causing
the excessive writes to the log. If the logging is intentional, evaluate its importance and determine whether or not to
continue logging.
5. If the process at fault is another Sandvine process (sfcd, scdpd, cnd, msd, serviceLauncher, or lcd), something may be
wrong with the configuration. Contact Sandvine support.
6. If non-Sandvine process is at fault, determine whether or not its excessive disk writing is intentional. If so evaluate its
importance and determine whether or not to allow it to continue. If not, stop the process if it is safe to do so. If you are unsure,
contact Sandvine support.
3.69 Alarm Model 133: Misconfigured Cluster

Name
This alarm is raised when the cluster name is invalid.
Profile Description
• Clear
Raise Notification svClusterInvalidNameErrorNotification

Clear Notification svClusterInvalidNameClearNotification
Triggers clusterNameSetToDefault, clusterNameNotSetToDefault
3.69.1 svClusterInvalidNameErrorNotification:Misconfigured Cluster

Name—Major
Sandvine configures a default cluster name in elements before shipping them; change the default name to suit your deployment.
To prevent the default cluster name from polluting the SPB database and cluster entries in reports, no statistics are sent until
you change the cluster name. Detection of the default cluster name triggers this alarm.

MIB SANDVINE-MIB
05-00262 C07
PTS Alarms
Alarm Model 133: Misconfigured Cluster Name

Trap Name svClusterInvalidNameErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.5.0.3

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svClusterStatsSuppressingMessages 1.3.6.1.4.1.11610.435.5213.1.3.2
Profile Description
Frequency Immediate
Severity Major
Condition defaultClusterName == 1
3.69.2 svClusterInvalidNameClearNotification:Misconfigured Cluster

Name—Clear
This notification is sent when the cluster name is no longer set to the factory default and messages are sent.

MIB SANDVINE-MIB
Trap Name svClusterDefaultNameClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.5.0.4

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svClusterStatsSuppressingMessages 1.3.6.1.4.1.11610.435.5213.1.3.2
Profile Description
Frequency Immediate
Severity Clear
Condition defaultClusterName == 0
05-00262 C07
PTS Alarms
Alarm Model 136: Misconfigured Load Balancer

When this alarm is active, the element is in an impaired state.
This alarm is raised when the element is not properly initialized and configured. As a result, to prevent the default cluster name
from polluting the SPB database, certain functions of the element are suppressed. If this condition is not cleared, subscriber
traffic statistics are not saved in the database; Control Center does not perform some configuration on the element until its cluster
name is properly initialized.
The cluster name is used to group network elements by name, and appears on Network Demographics reports and Control
Center. To clear this element condition, you must assign a new name to the cluster:
1. Discover the existing cluster names using Control Center or consult your system administrator.
You must use a unique cluster name that does not conflict with any pre-existing cluster names.
2. Run these CLI commands to change the cluster name:

• configure
• set config cluster name <name>
• commit
A valid cluster name must start with an alphabetic character and contain only alphanumeric characters, '_', '\', or '-', and
must not exceed 64 characters. It is recommended that you set your cluster name to something different for different products.
For example, if you have a cluster of PTSes, an SPB, and some SDEs, you must have one cluster name for the PTSes, a
different cluster name for the SPB, and another name for the SDEs.
3.70 Alarm Model 136: Misconfigured Load

Balancer
This alarm is raised when the load balancer has detected that the element's configuration does not match the master load
balancer.
Note:
Alarm Model 136 (Misconfigured Load Balancer) is not supported on the PTS Linux platform.
Profile Description
• Clear
Raise Notification svLBConfigErrorNotification

Clear Notification svLBConfigClearNotification
Triggers LBCConfigMismatchErrorTrigger, LBCConfigMismatchClearTrigger
05-00262 C07
PTS Alarms
3.70.1 svLBCConfigErrorNotification: Misconfigured Load

Balancer—Major
This notification is sent if an element has a load balancing configuration that does not match the configuration on the master load
balancer.

MIB SANDVINE-MIB
Trap Name svLBCConfigErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.17

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svLBCConfigLbcConfigSerial 1.3.6.1.4.1.11610.435.8377.1.400.1.2
svLBCConfigLbcConfigCompatible 1.3.6.1.4.1.11610.435.8377.1.400.1.11
svLBCConfigLbcConfigMismatch 1.3.6.1.4.1.11610.435.8377.1.400.1.12
Profile Description
Frequency 8 seconds
Severity Major
Condition LBCConfigMismatchErrorTrigger == 1
3.70.2 svLBCConfigClearNotification: Misconfigured Load Balancer

Cleared
This notification is sent when the alarm is active and the element's configuration matches the master load balancer.

MIB SANDVINE-MIB
Trap Name svLBCConfigClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.6.0.18

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
05-00262 C07
PTS Alarms

svLBCConfigLbcConfigSerial 1.3.6.1.4.1.11610.435.8377.1.400.1.2
svLBCConfigLbcConfigCompatible 1.3.6.1.4.1.11610.435.8377.1.400.1.11
svLBCConfigLbcConfigMismatch 1.3.6.1.4.1.11610.435.8377.1.400.1.12
Profile Description
Frequency 8 seconds
Severity Clear
Condition LBCConfigMismatchErrorTrigger != 1

This alarm indicates that the load balancer configuration is not identical on each PTS cluster element. Running different load
balancer configurations result in an unbalanced traffic distribution. This reduces cluster efficiency and may result in performance
bottlenecks.
1. Identify the element that raised the alarm.
For example, you can use the show alarms CLI command to view the alarm:
PTS> show alarms
AlarmId Severity EventTime Model Description
------- -------- ------------------- ----- ------------------------------
46 [major] 2012-09-12 15:37:10 136 LoadBalancer detected a configuration mismatch:SDVN8888888
2. Run the show service load-balancer cluster compatibility CLI command to identify the configuration elements
that have a cluster scope.
Serial Compatible LoadBalancingMode Layer2Mode HashMode IPv4Window IPv6Window TrafficClassShaping

AlgorithmType
------------- ---------- ----------------- ---------- -------- ---------- ---------- -------------------
----------------------
SDVN86017547* [true] static [mapping] svmpls 21-32 53-64 [false]
[weighted-round-robin]
SDVN86010722 [false] static [mapping] svmpls 21-32 53-64 [true]
[weighted-round-robin]
Refer to Configurations in Adding a PTS Element to a Cluster in the PTS Administration Guide and show service
load-balancer cluster compatibility in the PTS CLI Reference Guide for more information.
3. Verify the configuration on the element using these CLI commands:

show config service load-balancer mode
show config service load-balancer <ipv4|ipv6> hashing-window
show config service load-balancer hashing-width
4. If the configuration on the element differs from the configuration on the master, in CLI configuration mode, correct the element
using these CLI commands:
set config service load-balancer mode
set config service load-balancer <ipv4|ipv6> hashing-window
set config service load-balancer hashing-width
5. Run the commit CLI command to commit your changes. This will restart the SFCD.
05-00262 C07
PTS Alarms
Alarm Model 146: Incompatible Blade
6. Run the configure CLI command to change to the PTS configuration mode.
7. If the elements are load-balanced by using policy mode, inspect the policy.conf file on the element for load_balance
by and verify the bundle distribution definitions configured on each element are identical.
8. If the elements are load-balanced by using policy mode, ensure that the policy.conf file has no errors and it loads
correctly, using the reload validate command.
3.71 Alarm Model 146: Incompatible Blade
This alarm is raised during bootup if the current bladed configuration of the PTS is incapable of inspecting traffic. In this situation,
the PTS is also not capable of shunting, however, external and internal bypass remain functional.
Note:
Alarm Model 146 (Incompatible Blade) is not supported on the PTS Linux platform.
Profile Description
Severities Critical
Raise Notification svSystemInvalidBladeConfigurationErrorNotification
Clear Notification N/A
Triggers InvalidBladeConfigurationTrigger
3.71.1 Incompatible Blade- Critical

This alarm indicates one of these situations exists:
• There are no blades installed on the PTS.
• The installed blades are incompatible.
• There are two BLD 24080 blades installed and the hardware revision of the main-board does not support this configuration.

MIB SANDVINE-MIB
Trap Name svSystemInvalidBladeConfigurationErrorNotification
Trap OID 1.3.6.1.4.1.11610.435.6799.3.4.0.19

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.435.1.10
svHalStatsBladeConfigurationValid 1.3.6.1.4.1.11610.13982.435.1.3.100.1
05-00262 C07
PTS Alarms
Alarm Model 146: Incompatible Blade

svHalStatsBladeConfigurationErrorDescription 1.3.6.1.4.1.11610.13982.435.1.3.100.2
Profile Description
Frequency Immediate
Severity Critical
Condition No blades or incompatible blades are installed.

If this alarm is raised, the PTS cannot inspect traffic.
You cannot use the BLD 24080 in combination with BLD 24010 or BLD 24020; any other combination of blades is supported.
The blade type and the compatible PTS platforms are:
Blade Model Compatible PTS Platform

BLD 24080 PTS 24000
BLD 24020 PTS 24000
BLD 24010 PTS 24000, PTS 22000
BLD 24052 PTS 24000, PTS 22000
BLD 24050 PTS 24000, PTS 22000
BLD 24042 PTS 24000, PTS 22000
BLD 24040 PTS 24000, PTS 22000
BLD 24032 PTS 24000, PTS 22000
BLD 24030 PTS 24000, PTS 22000
BLD 22006 PTS 22000
BLD 32080 PTS 32000
BLD 32042 PTS 32000
1. Run the show alarms CLI command.

The description for Alarm Model 146 describes which components are incompatible. For example, Blade 1 and motherboard,
or Blade 1 and Blade 2.
2. Run the show system hardware CLI command.

This command lists the installed components. Look for the components listed in the description of Alarm Model 146.
3. Remove or replace one of the incompatible components.

Some possible situations are:
• If a PTS 24000 with no NPUs has no blades installed, you must power the system down and install a supported blade,
such as BLD 24080, BLD 24020, or BLD 24010.
• If a PTS 24000 has two blades installed, they may be incompatible. Power the system down, remove one or both of the
blades, and then install compatible blades.
05-00262 C07
PTS Alarms
Alarm Model 154: Invalid Subscriber Operation Name
• The PTS 22000 is incompatible with BLD 24080 and BLD 24020. Power the system down, remove the incompatible
blade, and then install a compatible blade.
• If it is none of these cases, a hardware failure may exist. Contact Sandvine Customer Support or and authorized partner
for assistance.
3.71.2.1 Verifying the Device State

1. Power on the PTS.
2. Run the show system services CLI command.
3. Wait for all services to come online, this may take up to 15 minutes.
4. Verify that the SFCD service is online.
5. Run the show alarms CLI command and verify if Alarm Model 146 was not raised.
3.72 Alarm Model 154: Invalid Subscriber

Operation Name
This alarm is raised when an invalid subscriber name is used in the provisioning operation.
Profile Description
• Minor
• Clear
Raise Notification ProvisionSubscriberInvalidNameMajEvt

ProvisionSubscriberInvalidNameMinEvt
Clear Notification ProvisionSubscriberInvalidNameClearEvt
Trigger ProvisionInvalidSubOpNameTrigger
Applicability This alarm applies to SDE 6.40 and later
3.72.1 Invalid Subscriber Operation Name - Major

This notification is sent when an invalid subscriber name, a string provided by the Policy Engine to the provisioning subsystem
is NULL, is used in the provisioning operation.

Trap Name svInvalidSubscriberOperationNameNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.0.15
05-00262 C07
PTS Alarms
Alarm Model 154: Invalid Subscriber Operation Name

svProvisionSummaryDeleteNameParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.52
svProvisionSummarySubAttrNameParamInvalid 1.3.6.1.4.1.11610.435.19994.1.3.100.50
svProvisionSummaryGetSubAttrByNameRequests 1.3.6.1.4.1.11610.435.19994.1.3.100.49
Profile Description
Frequency 3600 seconds.
Severity Major
Condition (svProvisionSummarySubAttrNameParamInvalid + svProvisionSummaryDeleteNameParamInvalid)
/ (svProvisionSummaryTotalDeletes + svProvisionSummaryGetSubAttrByNameRequests) > 5%
3.72.2 Invalid Subscriber Operation Name - Minor

This notification is sent when an invalid subscriber name, a string provided by the Policy Engine to the provisioning subsystem
is NULL, is used in the provisioning operation. This is raised when the percentage of requests that contains invalid parameters
is greater than 5% of the total requests sent to SPB, it results in notification with major severity. If it is greater than 2% of the total
requests sent to SPB, then notification is sent with minor severity.

Trap Name svInvalidSubscriberOperationNameNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.0.15

Profile Description
Frequency 3600 seconds.
Severity Minor
/ (svProvisionSummaryTotalDeletes + svProvisionSummaryGetSubAttrByNameRequests) > 2%
3.72.3 Invalid Subscriber Operation Name - Clear

This notification is sent when a valid subscriber name is used in the subscriber operation.
This notification is sent when the alarm threshold is not triggered anymore and is within acceptable configured tolerance.
05-00262 C07
PTS Alarms
Alarm Model 157: Unavailable Accounting Server

Trap Name svValidSubscriberOperationNameNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.26.0.16

Profile Description
Severity Clear
/ (svProvisionSummaryTotalDeletes + svProvisionSummaryGetSubAttrByNameRequests) < 1%

An invalid name used for a subscriber operation raises this alarm. The invalid name entered is either null or an invalid character.
Varbind Description
svProvisionSummaryDeleteNameParamInvalid Number of times a subscriber delete operation failed due to
an invalid name.
svProvisionSummarySubAttrNameParamInvalid Number of times a subscriber get operation failed due to an
invalid name.
svProvisionSummaryTotalDeletes Total number of delete operations.
svProvisionSummaryGetSubAttrByNameRequests Total number of get (subscriber profile) operations.
When the alarm is triggered at a minor level, it indicates a network problem or indicates that some packets are lost. If this is the
case, the alarm clears after the network problem is resolved.
When the alarm is triggered at a major level, it indicates a configuration problem, either by the PTS provisioning subsystem or
an external entity sending traffic for get and delete operations with subscriber by name.
3.73 Alarm Model 157: Unavailable Accounting

Server
This alarm is raised when communication with a remote server, for example TACACS+ accounting server, is interrupted for a
sufficient amount of time to cause the queue that holds accounting records to become full.
05-00262 C07
PTS Alarms
Profile Description
• Minor
• Clear
Raise Notification svSystemAccountingQueueErrorNotification

Clear Notification svSystemAccountingQueueClearNotification
Triggers systemAccountingQueue
Unique Instance identifier svUserMgmtAcctProtocolName
3.73.1 svSystemAccountingQueueErrorNotification—Raise
This notification is sent when the queue that holds accounting records becomes 80% full, and a minor alarm is raised when it
becomes completely full.

MIB SANDVINE-MIB
Trap Name svSystemAccountingQueueErrorNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.21

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svUserMgmtAcctProtocolName 1.3.6.1.4.1.11610.435.26681.1.100.10.1.2
svUserMgmtAcctProtocolQueued 1.3.6.1.4.1.11610.435.26681.1.100.10.1.4
svUserMgmtAcctProtocolQueuePercentFull 1.3.6.1.4.1.11610.435.26681.1.100.10.1.5
svUserMgmtAcctProtocolSent 1.3.6.1.4.1.11610.435.26681.1.100.10.1.6
svUserMgmtAcctProtocolErrors 1.3.6.1.4.1.11610.435.26681.1.100.10.1.7
svUserMgmtAcctProtocolDropped 1.3.6.1.4.1.11610.435.26681.1.100.10.1.8
svUserMgmtAcctConfigMaxQueued 1.3.6.1.4.1.11610.435.26681.1.100.2.1
3.73.2 svSystemAccountingQueueClearNotification—Clear
This notification is sent when the queue that holds accounting records drops below 90% and the warning is cleared when the
queue drops below 70%.

MIB SANDVINE-MIB
Trap Name svSystemAccountingQueueClearNotification
05-00262 C07
PTS Alarms

Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.22

sysName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
svUserMgmtAcctProtocolName 1.3.6.1.4.1.11610.435.26681.1.100.10.1.2
svUserMgmtAcctProtocolQueued 1.3.6.1.4.1.11610.435.26681.1.100.10.1.4
svUserMgmtAcctProtocolQueuePercentFull 1.3.6.1.4.1.11610.435.26681.1.100.10.1.5
svUserMgmtAcctProtocolSent 1.3.6.1.4.1.11610.435.26681.1.100.10.1.6
svUserMgmtAcctProtocolErrors 1.3.6.1.4.1.11610.435.26681.1.100.10.1.7
svUserMgmtAcctProtocolDropped 1.3.6.1.4.1.11610.435.26681.1.100.10.1.8
svUserMgmtAcctConfigMaxQueued 1.3.6.1.4.1.11610.435.26681.1.100.2.1

The warning indicates that unless communication between the element and the remote accounting server is re-established, the
queue may become full at which point accounting records are dropped.
The minor alarm indicates that the queue is full and that accounting records have been (or will be) dropped. In this case, the
remote accounting server may be missing some records.
If the system is dropping remote accounting records, these records will be missing from the remote accounting servers.
Note:
All records are always logged to the local accounting files.
3.73.3.1 Resolution
Ensure that the system is running with the correct configuration, that there is network connectivity between the element and the
remote accounting server, and that the accounting server is online. Within a few seconds of connectivity and communication
being established, the accounting records in the queue are successfully transmitted to the server and the alarms get cleared.
Run the set config system accounting tacacs+ enabled false CLI command to clear the alarms.
This alarm is raised due to one of these issues:
• The configuration for remote accounting is incorrectly specified. Follow these steps to resolve this :
1. Run the show system accounting CLI command to view the configuration.
2. Verify that the server hostname/IP address, port and shared secret (if applicable) are correct.
• There is no network connectivity between the element and the remote accounting server. Run the pingcommand to ping the
hostname/IP address of the failing accounting server to confirm connectivity.
• The remote accounting server is not responding. Ensure that the accounting server is running and check its logs to see if
there are any errors.
05-00262 C07
PTS Alarms
Alarm Model 167: Delayed Distribution Event
3.73.3.2 Verifying Resolution

The output of the show system accounting command displays the queues for all accounting protocols that are empty (or
nearly empty) and each time a CLI or shell command is executed, the Sent counter increments but the Error counter does not.
To verify that the alarm is cleared, run the show alarms CLI command.
3.74 Alarm Model 167: Delayed Distribution Event

Under heavy load, Level Distribution may not distribute rates within the request time interval. This alarm raises when more than
5% of all instances see distribution intervals larger than the configured interval length.
Profile Description
• Minor
• Clear
Raise Notification svDelayedShapingDistributionNotification
Clear Notification svDelayedShapingDistributionClearNotification
Triggers • urgentIntervalExceededTrigger
• normalIntervalExceededTrigger
• allIntervalsOkayTrigger
3.74.1 svDelayedShapingDistributionNotification—Major
MIB SANDVINE-MIB
Trap Name svDelayedShapingDistributionNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.34.0.1

sysName 1.3.6.1.2.1.1.5.0
svSeverity 1.3.6.1.4.1.11610.6799.1.10.0
3.74.2 svDelayedShapingDistributionNotification—Minor
MIB SANDVINE-MIB
Trap Name svDelayedShapingDistributionNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.34.0.1
05-00262 C07
PTS Alarms
Alarm Model 168: High Login Failures

sysName 1.3.6.1.2.1.1.5.0
svSeverity 1.3.6.1.4.1.11610.6799.1.10.0
3.74.3 svDelayedShapingDistributionNotification—Clear
MIB SANDVINE-MIB
Trap Name
Trap OID 1.3.6.1.4.1.11610.6799.3.34.0.2

Distributed shaping will not be as responsive at handling variations in traffic patterns and may result in under- or over-shaping.
Additionally, the controller load may increase, causing delayed stats publishing, or subscriber mapping.
To resolve this alarm, you must configure the level-distribution queue intervals in the CLI.
For example, to configure each queue's interval as one second longer than the default value, run:
set config level-distribution urgent-queue interval 2000
set config level-distribution urgent-queue interval 4000
commit
Once the new interval configuration is applied, view the current status of each queue via the show service
level-distribution command.
If there are no more delayed intervals, the alarm should clear itself within 15 minutes.
3.75 Alarm Model 168: High Login Failures

This alarm indicates a high rate of failed login attempts. An excessive number of login failures could indicate that someone is
trying to break into the system.
Profile Description
• Clear
Raise Notification svHighLoginFailuresNotification

Clear Notification svHighLoginFailuresClearNotification
Triggers highLoginFailureTrigger
highLoginFailureClearTrigger
05-00262 C07
PTS Alarms
Alarm Model 168: High Login Failures
Profile Description
Applicability
3.75.1 High Login Failures- Minor

The PTS sends this notification whenever the number of failed login attempts during the most recent monitoring period, reaches
the configured threshold.

MIB SANDVINE-MIB
Trap Name SANDVINE-MIB :: svHighLoginFailuresNotification
Trap OID 1.3.6.1.4.1.11610.3.6799.35.0.1

svLoginManagementStatsLoginFailures 1.3.6.1.4.1.11610.435.29639.1.3.1
svLoginManagementConfigLoginFailuresThreshold 1.3.6.1.4.1.11610.435.29639.1.2.1
Profile Description
Severity Minor
Condition Delta of svLoginManagementStatsLoginFailures after 60 minutes >
svLoginManagementConfigLoginFailuresThreshold
Description The number of login failure attempts increased the threshold limit in the past one hour.
Note:
The default value for svLoginManagementConfigLoginFailuresThreshold is 3600.
3.75.2 High Login Failures- Clear

The PTS sends this notification whenever the number of failed login attempts during the most recent monitoring period, falls
below the configured threshold.

MIB SANDVINE-MIB
Trap Name SANDVINE-MIB :: svHighLoginFailuresClearNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.35.0.2

svLoginManagementStatsLoginFailures 1.3.6.1.4.1.11610.435.29639.1.3.1
svLoginManagementConfigLoginFailuresThreshold 1.3.6.1.4.1.11610.435.29639.1.2.1
05-00262 C07
PTS Alarms
Alarm Model 175: License Service Unavailable
Profile Description
Severity Clear
Condition Delta of svLoginManagementStatsLoginFailures after 60 minutes <
svLoginManagementConfigLoginFailuresThreshold
Description The number of login failure attempts is less than the threshold limit in the past one hour.

The high number of login failure notifications result in these issues:
• The /var/log/notification.log file floods with failure attempts only. The notification.log updates on a log
rotation basis. When it reaches the maximum possible number of files, it rolls over to the initial file. In this way, high login
failure notifications override many other critical notifications.
• The show alarms history command mostly shows Login Failures and gives less visibility to other critical alarms.
Perform these steps to resolve the alarm:
1. Enable a firewall to block the IP addresses sending too many login failure attempts.
Note:
The /var/log/auth.log file contains the login failure details.
2. Tune the threshold value when the threshold for the number of login failures is less or very high. Use the CLI command set
config system authentication notify-login-failures threshold <1-10000> to tune the threshold value.
3. Enable notifications per login failure, and view the notifications.

a. Use the CLI command set config system authentication notify-login-failures enable
<true|false>, and set the value to true to enable notifications per login failure. Set the value to false, to disable
notifications per login failure. The default value is false.
b. Use the CLI command show config system authentication notify-login-failures enable, to view
the notifications per login failure.
4. Make sure that your password is strong to prevent unauthorized access to the system.
3.76 Alarm Model 175: License Service

Unavailable
This alarm is raised when the element detects an issue with license services. Currently held licenses may be invalid or lost when
using a license server and floating licenses.
05-00262 C07
PTS Alarms
Alarm Model 175: License Service Unavailable
Profile Description
• Clear
Raise Notification svSysLicenseServiceNotification
Clear Notification svSysLicenseServiceClearNotification
Triggers licenseServerDisconnectTrigger and licenseServerClearTrigger
3.76.1 License Service Unavailable–Major

This notification is sent when the element loses connection with the license server or the license clients lose connection with the
license manager daemon (LMD).

MIB SANDVINE-MIB
Trap Name svSysLicenseServiceNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.23

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svLicenseServerConnection 1.3.6.1.4.1.11610.435.7534.1.13.1
svLicenseManagerDaemonConnection 1.3.6.1.4.1.11610.435.7534.1.14.1
3.76.2 License Service Unavailable–Clear

This notification is sent when the license service is available.

MIB SANDVINE-MIB
Trap Name svSysLicenseServiceNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.4.0.23

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svLicenseServerConnection 1.3.6.1.4.1.11610.435.7534.1.13.1
svLicenseManagerDaemonConnection 1.3.6.1.4.1.11610.435.7534.1.14.1
05-00262 C07
PTS Alarms
Alarm Model 187: SandScript Alarm

When this notification is raised, there is a risk of not finding the required licenses when the element is reloaded. It is recommended
that you ensure that no reloads occur until this alarm is resolved.
If this alarm is raised, then one of two conditions has occurred:
• The element has lost communication with the licensing server and the element was using network licenses.
• The applications have lost communication with the LMD.
Perform these steps to resolve the alarm:
1. Check if the LMD on the element is running, if you are not using a license server and network licenses or the license server
is up and reachable from the element.
2. Run the show system services CLI command to verify that the LMD process is online. Run the start service lmd
CLI command to start the LMD process if it is not online. If you cannot start the process or if it does not come online, contact
Sandvine Customer Support or its authorized partner for further assistance.
3. Run the show config service license-server CLI command to view the license server(s) that are configured.
4. Run the show system licenses CLI command to verify if the element is using any network licenses. If the type output
for any license is [network], it indicates that the element is using a network license received from a configured license
server.
5. Ensure that the license server is not down. Check the log for any messages stating that you have lost communication with
the license server.
3.77 Alarm Model 187: SandScript Alarm

Alarm Model 187 is raised whenever a SandScript application triggers the alarm using customized criteria. As a best practice,
each SandScript application that triggers a custom alarm should identify the symptoms and resolution steps for the conditions
that are raised.
Tip:
When defining a SandScript alarm, specify the symptom and resolution in the description field.
Profile Description
Severities • Critical
• Major
• Minor
• Warning
• Clear
Raise Notification svSandScriptAlarmsFailureNotification
Clear Notification svSandScriptAlarmClearNotification
Triggers • sandScriptAlarmsTrigger137F
• sandScriptAlarmsTrigger26E
• sandScriptAlarmsTrigger4C
• sandScriptAlarmsTrigger5D
• sandScriptAlarmsTrigger8
• sandScriptAlarmsTrigger9
05-00262 C07
PTS Alarms
Alarm Model 187: SandScript Alarm
Profile Description
• sandScriptAlarmsTriggerA
• sandScriptAlarmsTriggerB
Unique Instance Identifier A unique ID as defined in the alarm SandScript.
Applicability This alarm applies to both SDE 7.50 or later, and PTS 7.40 or later.
3.77.1 SandScript Alarm Severity

Each SandScript application that triggers a custom alarm must identify the symptoms and resolution steps for the conditions that
were raised. As a best practice, while defining the alarm SandScript, specify the symptoms and resolution in the description field.

MIB SANDVINE-MIB
Trap Name • svSandScriptAlarmsFailureNotification
• svSandScriptAlarmClearNotification
Trap OID • 1.3.6.1.4.1.11610.6799.3.43.0.1
• 1.3.6.1.4.1.11610.6799.3.43.0.2

svPolicyAlarmsName 1.3.6.1.4.1.11610.435.15973.1.10.1.2
svPolicyAlarmsInstance 1.3.6.1.4.1.11610.435.15973.1.10.1.1
svPolicyAlarmsDescription 1.3.6.1.4.1.11610.435.15973.1.10.1.3
svPolicyAlarmsPeriod 1.3.6.1.4.1.11610.435.15973.1.10.1.6
svPolicyAlarmsWarningClear 1.3.6.1.4.1.11610.435.15973.1.10.1.8
svPolicyAlarmsWarningRaise 1.3.6.1.4.1.11610.435.15973.1.10.1.9
svPolicyAlarmsMinorClear 1.3.6.1.4.1.11610.435.15973.1.10.1.11
svPolicyAlarmsMinorRaise 1.3.6.1.4.1.11610.435.15973.1.10.1.12
svPolicyAlarmsMajorClear 1.3.6.1.4.1.11610.435.15973.1.10.1.14
svPolicyAlarmsMajorRaise 1.3.6.1.4.1.11610.435.15973.1.10.1.15
svPolicyAlarmsCriticalClear 1.3.6.1.4.1.11610.435.15973.1.10.1.17
svPolicyAlarmsCriticalRaise 1.3.6.1.4.1.11610.435.15973.1.10.1.18
svPolicyAlarmsCurrentValue 1.3.6.1.4.1.11610.435.15973.1.10.1.19
svPolicyAlarmsExpressionValue 1.3.6.1.4.1.11610.435.15973.1.10.1.20
svPolicyAlarmsPreviousExpressionValue 1.3.6.1.4.1.11610.435.15973.1.10.1.21
Profile Description
Frequency (for all severities) As defined in the alarm SandScript.
Severity The supported severity for the alarm as defined in the alarm SandScript.
Condition (for all severities) As defined in the alarm SandScript.
05-00262 C07
PTS Alarms
Alarm Model 191: Overloaded Diameter Aggregator
Where:
• svPolicyAlarmsName—The name of the SandScript alarm.
• svPolicyAlarmsInstance—A unique integer identifier of the SandScript alarm.
• svPolicyAlarmsDescription—A textual description of the error event, that describes the symptoms of the alarm.
• svPolicyAlarmsPeriod—The interval over which the alarm is raised and cleared.
• svPolicyAlarms<severity>Clear—The threshold for clearing the alarm for a specific severity.
• svPolicyAlarms<severity>Raise—The threshold for raising the alarm for a specific severity.
• svPolicyAlarmsCurrentValue—The current value of the alarm.
• svPolicyAlarmsExpressionValue—The expression value that is monitored for raising and clearing the alarm with a specific
severity.
• svPolicyAlarmsPreviousExpressionValue—The previous expression value of the alarm.
Note:
The values of these varbinds are dependent on what is defined in the alarm SandScript.

The impact and resolution of Alarm Model 187 is dependent on the SandScript application that triggers the alarm. As a best
practice, policy creators should specify these details in the description field when they define the alarm SandScript.
Contact Sandvine Customer Support, or it's authorized partner, if you cannot resolve this alarm.
3.78 Alarm Model 191: Overloaded Diameter

Aggregator
This alarm is raised when the master load balancer is unable to keep up with the incoming Sd Diameter Messages and the queue
serving the request to the master load balancer reaches its threshold.
Profile Description
• Clear
Raise Notification svOverLoadedDCANotification
Clear Notification svOverLoadedDCAClearNotification
Triggers • overLoadedDCANotification
• overLoadedDCAClearNotification
3.78.1 Overloaded Diameter Aggregator–Major

This notification is sent when the buffer between SdProxy and load balancer crosses the threshold mark indicating that the load
balancer is unable to keep up with the incoming Sd Diameter Messages.

MIB SANDVINE-MIB
05-00262 C07
PTS Alarms

Trap Name svOverLoadedDCANotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.17

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svAggregatorStatsSdHandler 1.3.6.1.4.1.11610.435. 30752.1.3.200.19
ProcessedSdMsgsSize
svAggregatorConfigSdHandle 1.3.6.1.4.1.11610.435.30752. 1.2.200.4
rProcessedSdMsgsThreshold
3.78.2 Overloaded Diameter Aggregator–Clear

This notification is sent when the buffer level goes below the threshold mark indicating that the load balancer is ready again to
process the Sd Diameter Messages.

MIB SANDVINE-MIB
Trap Name svOverLoadedDCANotification
Trap OID 1.3.6.1.4.1.11610.6799.3.9.0.18

svSeverity 1.3.6.1.4.1.11610.6799.1.10
svAggregatorStatsSdHandler 1.3.6.1.4.1.11610.435. 30752.1.3.200.19
ProcessedSdMsgsSize
svAggregatorConfigSdHandle 1.3.6.1.4.1.11610.435.30752. 1.2.200.4
rProcessedSdMsgsThreshold

This alarm is raised when the master load balancer is unable to keep up with the incoming Sd Diameter Messages and the queue
serving the request to the master load balancer reaches its threshold. If this issue persists then the Sd messages related to
session login, session logout like TSR and RAR (with IP allocate/deallocate) starts getting dropped at diameter-aggregator.
To resolve this issue:
• Run the show service loadbalancer stats CLI command to check whether the master load balancer is processing
the login and logout notifications.
• Check for the incoming message rate at the PTS is within 70000-75000 messages per second.
05-00262 C07
PTS Alarms
05-00262 C07
Miscellaneous Traps
4
Miscellaneous Traps
• "Miscellaneous Traps" on page 263
05-00262 C07
Miscellaneous Traps
Miscellaneous Traps
4.1 Miscellaneous Traps

PTS has a few notifications that are sent from the system but which aren't associated to any alarm models. These traps appear
only when you run the show alarms history CLI command, and include:
• coldStart Trap on page 263
• warmStart Trap on page 263
• Administratively Enabled Interface on page 264
• Administratively Disabled Interface on page 265
• SNMP Agent Started on page 265
• SNMP Agent Shutting Down on page 266
4.1.1 coldStart Trap

A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its
configuration may have been altered.
Sample Output
This sample output is displayed when you run PTS>show alarms history limit 100 CLI command:
EVENT DATE: 2015-08-14
======================
TrapLogId Severity EventTime Model Description

--------- --------- --------- ----- --------------------------------------------
1 [warning] 05:02:30 Cold Start
2 [clear] 05:11:09 Enabled Network Interface: cluster 2-14
3 [clear] 05:11:09 Enabled Network Interface: data 2-13
5 [major] 05:11:32 14 Network Interface Down: data 2-13
7 [major] 05:11:48 14 Network Interface Down: cluster 2-14
8 [clear] 05:11:48 14 Network Interface Down Cleared: data 2-12
10 [clear] 05:11:56 14 Network Interface Down Cleared: cluster 2-14
11 [major] 05:12:38 18 Disconnected SPB
12 [clear] 05:12:42 18 Disconnected SPB Cleared
PTS> show alarms history 1
======================
TrapLogId : 1
Severity : [warning]
EventTime : 01:54:46
Model :
Notification : coldStart
Value :
NotificationID : SNMPv2-MIB::coldStart
DISMAN-EVENT-MIB::sysUpTimeInstance: 686
SNMPv2-MIB::snmpTrapOID : SNMPv2-MIB::coldStart
4.1.2 warmStart Trap

A warmStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself such that its
configuration is unaltered.
05-00262 C07
Miscellaneous Traps
Miscellaneous Traps
Sample Output
This sample output is displayed when you run PTS> show alarms history CLI command:
======================
TrapLogId Severity EventTime Model Description

--------- --------- --------- ----- ---------------------------------------------------------------------
2 [clear] 05:11:09 Enabled Network Interface: cluster 2-14
7 [major] 05:11:48 14 Network Interface Down: cluster 2-14
10 [clear] 05:11:56 14 Network Interface Down Cleared: cluster 2-14
11 [major] 05:12:38 18 Disconnected SPB
12 [clear] 05:12:42 18 Disconnected SPB Cleared
13 [clear] 02:12:53 14 Network interface up: data 1-6
14 [clear] 02:13:01 14 Network interface up: cluster 1-7
15 [clear] 02:14:36 18 Disconnected SPB: Statistics database
16 [minor] 02:17:09 129 Disconnected Tee Destination: ipusermap
17 [major] 02:17:12 32 Disconnected Diameter Peer: <hostname>.abc.sandvine.com
18 [clear] 02:17:29 32 Disconnected Diameter Peer: <hostname>.abc.sandvine.com
19 [clear] 02:17:39 129 Tee destination up: ipusermap
20 [minor] 02:19:49 29 Disabled Subscriber Lookups disabled
21 [minor] 02:19:55 28 Discarded Subscriber State cleared
22 [clear] 02:19:57 29 Disabled Subscriber Lookups enabled
23 [clear] 02:49:55 28 Discarded Subscriber State functional
24 [warning] 03:08:26 Warm Start
25 [major] 03:08:36 9 Processing module down: Module 0
PTS> show alarms history 24

======================
TrapLogId : 24
Severity : [warning]
EventTime : 03:08:26
Model :
Notification : warmStart
Value :
NotificationID : SNMPv2-MIB::warmStart
DISMAN-EVENT-MIB::sysUpTimeInstance: 394
SNMPv2-MIB::snmpTrapOID : SNMPv2-MIB::warmStart
4.1.3 Administratively Enabled Interface

This notification indicates that the ifAdminStatus of an interface has gone from Down to Up. The value of the svSeverity varbind
will be 1 [clear].

MIB IF-MIB
Trap Name svLinkAdminUpNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.26

svName 1.3.6.1.2.1.1.5
05-00262 C07
Miscellaneous Traps
Miscellaneous Traps

svSeverity 1.3.6.1.4.1.11610.6799.1.10
ifIndex 1.3.6.1.2.1.2.2.1.1
ifAdminStatus 1.3.6.1.2.1.2.2.1.7
ifOperStatus 1.3.6.1.2.1.2.2.1.8
ifDescr 1.3.6.1.2.1.2.2.1.2
Profile Description
Frequency 0 seconds (Immediately)
Condition (IF-MIB::ifAdminStatus == 2(up))
4.1.4 Administratively Disabled Interface

This notification indicates that the ifAdminStatus of an interface has gone from Up to Down. The value of the svSeverity varbind
will be 6 [warning].

MIB IF-MIB
Trap Name svLinkAdminDownNotification
Trap OID 1.3.6.1.4.1.11610.6799.3.2.0.25

svName 1.3.6.1.2.1.1.5
svSeverity 1.3.6.1.4.1.11610.6799.1.10
ifIndex 1.3.6.1.2.1.2.2.1.1
ifAdminStatus 1.3.6.1.2.1.2.2.1.7
ifOperStatus 1.3.6.1.2.1.2.2.1.8
ifDescr 1.3.6.1.2.1.2.2.1.2
Profile Description
Frequency 0 seconds (Immediately)
Condition (IF-MIB::ifAdminStatus == 2(down))
4.1.5 SNMP Agent Started

This notification appears when the CDPD is set up to receive traps from other net-snmp sub-agents.

MIB NET-SNMP-AGENT-MIB
05-00262 C07
Miscellaneous Traps
Miscellaneous Traps

Trap Name nsNotifyStart
Trap OID 1.3.6.1.4.1.8072.4.0.1
4.1.6 SNMP Agent Shutting Down

This notification appears when the CDPD is set up to receive traps from other net-snmp sub-agents.

MIB NET-SNMP-AGENT-MIB
Trap Name nsNotifyShutdown
Trap OID 1.3.6.1.4.1.8072.4.0.2
05-00262 C07
Miscellaneous Traps
Miscellaneous Traps
05-00262 C07

PTS Alarms Reference Guide R7.40 C07

Uploaded by

Copyright:

Available Formats

PTS Alarms Reference Guide R7.40 C07

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PTS Alarms Reference Guide R7.40 C07

Uploaded by

Copyright:

Available Formats

What is the document about?

What is the document about?

What information is contained in the document?

What information is contained in the document?

Sandvine Policy Traffic Switch Alarms

Reference Guide, Release 7.40

2 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

Document Part Number

Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 3

4 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

3.6.2 Faulted Power Supply - Notification.............................................................................................................40

Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 5

3.14.1 Discarded Packets - Notifications...............................................................................................................82

6 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

3.21.3 Impact and Suggested Resolution, Alarm Model 21................................................................................105

Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 7

3.29.4 Impact and Suggested Resolution, Alarm Model 29................................................................................131

8 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

3.39 Alarm Model 40: Diameter Peer Failed Back Over.........................................................................................162

Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 9

3.49 Alarm Model 60: Disconnected BGP Peer......................................................................................................181

10 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

3.58.3 Impact and Suggested Resolution, Alarm Model 110..............................................................................203

Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 11

3.67.2 svDivertDestinationSeqUpNotification:Disconnected Divert Sequence Destination—Clear....................235

12 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

3.77 Alarm Model 187: SandScript Alarm...............................................................................................................257

Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 13

14 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

1.1.1 Sandvine Notifications

1.1.1.1 Bad Logical Drive

Warning The drive is rebuilding.

Major The drive is degraded.

Critical The drive is either failed or offline.

Trap Name svRaidMonLogicalDriveBadStateNotification

Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 15

1.1.1.2 Good Logical Drive

Trap Name svRaidMonLogicalDriveGoodStateNotification

1.1.1.3 Faulted Physical Drive

Warning Drive is ready.

Minor Drive is rebuilding.

Major Drive is failed.

MIB reference SANDVINE-RAIDMON-MIB and SNMPv2-MIB

Trap Name svRaidMonPhysicalDeviceFaultedNotification

16 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

1.1.1.4 Physical Drive Not Faulted

MIB reference SANDVINE- RAIDMON-MIB and SNMPv2-MIB

Trap Name svRaidMonPhysicalDeviceNotFaultedNotification

Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 17

18 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

2.1 General Resources

2.1.1 Memory Resources

2.1.2 PTS Per Module General Resources

Inspection Performance Monitoring

Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40 19

2.2 Inspection Performance Monitoring

2.2.1 CPU Resource

2.2.2 Memory Resource

20 Sandvine Policy Traffic Switch Alarms Reference Guide, Release 7.40

2.2.3 Inspection Engine