User`s guide

production jobs when the data will not be used again.
There is one caution: if you have a failure (for instance, a power outage) during the reduce step and any
age limits at detail level are zero and any age limits at non-detail levels are non-zero, make sure that you
re-submit the reduce step before you go on; otherwise, the next day’s production job will remove the detail
data before the data have an opportunity to be summarized in the non-detail levels.
ii. Check the Age Limits at reduction levels.
By default, the PDB keeps reduction-level data as follows
Day 45 days
Week 15 weeks
Month 18 months
Year 5 years
but the age limits in your tables may be different.
If you want your reports on these levels to be able to cover a different number of days, weeks, months, or
years, or if you want to keep fewer data in order to save disk space and shorten processing time, overwrite
the current value with a new value.
f. Consider whether to keep data for string variables whose default value is kept status in No.
The following variables/metrics fall in this category: IFSPEC (ifSpecific), SYSCONT (sysContact), SYSLOC
(sysLocation), SYSNAME (sysName), and SYSOBID (sysObjectID).
The process step takes longer when string variables are kept in the detail level of the PDB. HPOV/NVAIX does
not automatically collect the values of the string variables so their Kept status is set to No by default. If you
change the Kept status to Yes, an additional snmp get request per variable is required to gather this data during
the process step.
Gathering this data can slow down the process step, especially if there are network problems that delay the snmp
get requests. However, the information in these fields is often useful in reports; for example, an interfaces report
on a router is more meaningful if the interface is identified as "Ethernet/0" rather than just "4".
If you are thinking of keeping values for string variables, in the task after this one you can time processing with
the Kept status set to various combinations of Yes and No to check how much extra time is required to gather the
data. Based on that, you can decide whether the time to gather the data is acceptable to you.
3. Your test PDB is the active PDB, and you have write access to it.
4. If you want to monitor line utilization for full-duplex lines, you know the host name and instance number of each
full-duplex interface, if any, on your network.
For example, you would know something like this: the number 2 interface on dimes.unx.sas.com and the number 4
interface on swimmer.unx.sas.com are full-duplex, and these are the only full duplex interfaces.
Actions
1. If you plan to customize the PDB, delete data from the PDB.
You can customize with data in the PDB, but deleting the data makes the customization and testing much faster and
easier. Deleting the data also results in a consistent set of data at the end of this task.
a. Display the list of tables.