Cisco Cisco Packet Data Interworking Function (PDIF)
Support Data Collector
▀ Managing Record Collection
▄ ASR 5500 System Administration Guide, StarOS Release 17
330
Managing Record Collection
The SDRs are stored together in a self-relative set. This self-relative set is called a Support Record Collection. Each
individual SDR is identified with a record-id. The record-id of the most recent SDR is always 0 (zero). The next older
SDR is record-id 1, and so on, for the number of records in the stored collection. For example, if there are five SDRs,
they are identified as SDR-0 through SDR-4.
individual SDR is identified with a record-id. The record-id of the most recent SDR is always 0 (zero). The next older
SDR is record-id 1, and so on, for the number of records in the stored collection. For example, if there are five SDRs,
they are identified as SDR-0 through SDR-4.
Figure 28. Support Data Collection Hierarchy
When a new SDR is created, the numbers all increment by one and the newest SDR is given the value of 0. If the total
number of records exceeds a configured maximum, then the oldest SDR is deleted.
number of records exceeds a configured maximum, then the oldest SDR is deleted.
Using the example above, when the maximum SDR count of 5 is reached, the SDRs continue to be SDR-0 through
SDR-4, with the file timestamps indicating that the files are changing over time.
SDR-4, with the file timestamps indicating that the files are changing over time.
The time interval between collections may vary by several minutes in relation to the specified sleep-duration. This is
because the interval specifies the idle time between scheduled collection runs. Since the actual overhead of the
because the interval specifies the idle time between scheduled collection runs. Since the actual overhead of the