10. Setting Up NetScout Manager Plus for FrameSaver Devices9128-A2-GB20-80 September 2002 10-13Creating History FilesUp to 14 additional user history tables can be created in the FrameSaver unit foreach interface. An interface is a specific DLCI or the entire frame relay interface. Atable must be created for each DLCI or frame relay link to be monitored. Additionaluser history tables are created using the command-line prompt in NetScoutManager Plus to load a file that contains the OIDs (Object IDs) to be monitoredinto the unit.OpenLane provides several useful examples, including three files containing acomplete set of OIDs appropriate to the interface to be monitored: one for a DLCI,one for a frame relay link, and one containing system-type OIDs. Any of these filescan be used as a template when creating customized history files specific to theFrameSaver unit.These files have a pdn*.udh (user-defined history) format and are found in theOpenLane/netscout/userHistory directory. The userHistory files should bemoved to $NSHOME/usr so they can be used.A separate *.udh file must be created and loaded for each DLCI or link that will bemonitored before a customized user history table can be loaded. Use a text editorto create these *.udh files by: Copying one of the interface-specific files (DLCI or link) and editing it usingone of the examples provided as a guide. Copying one of the examples provided and editing the extensions to fit theFrameSaver unit.CAUTION:Two user history table files are already configured and installed in theunit, UserHistory1 and UserHistory2. These files must not be modified.These two tables are used to keep SLV data for reports.It is always a good idea to rediscover agents and their DLCIs before starting to besure your agent and DLCI lists are current. To rediscover agents and their DLCIs,select the Learn button on the NetScout Manager Plus main window (theFrameRelay and Admin radio buttons still selected).
