Persistent indexing of SNMP Tables

Certain Oracle Communications Session Border Controller proprietary MIB tables support persistent indexing across reboots. The purpose is to maintain the value of that object so that after a reboot or configuration reload, the value that identifies an object remains the same.

Please be aware of the following three limitations:

ObjectID Wrapping

The maximum value of an object that is persistently indexed is 4294967295. In the unlikely event that the Net-Net SBC exhausts all index values, it will wrap beginning with the first, lowest, unused index number.

Consecutive Table Entries

For any two consecutive table entries, the indices from ObjectID are not guaranteed to be consecutive. The value of an ObjectID reflects the order when the object is created.

Persistent Exception

Using the backup-config and the restore-backup-config commands do not impact the index persistency. But, if a configuration file created on one Net-Net SBC is loaded on another Net-Net SBC, the element IDs were assigned by the first Net-Net SBC are likely to be different that the IDs used on the second Net-Net SBC.

If, after a backup is created, an element is deleted from the configuration and then later created again, the element's ID will probably change. Then, if the operator restores an older backup, a change in the MIB ID of the object will result.

MIB Table	in MIB file	Persistent Index
apSigRealmStatsTable 1.3.6.1.4.1.9148.3.2.1.2.4	ap-smgmt.mib	apSigRealmStatsRealmIndex
apCombinedSessionAgentStatsTable 1.3.6.1.4.1.9148.3.2.1.2.1	ap-smgmt.mib	apCombinedStatsSessionAgentIndex
apSipSessionAgentStatsTable 1.3.6.1.4.1.9148.3.2.1.2.2	ap-smgmt.mib	apSipSAStatsSessionAgentIndex
apH323SessionAgentStatsTable 1.3.6.1.4.1.9148.3.2.1.2.3	ap-smgmt.mib	apH323SAStatsSessionAgentIndex