Package mediation
The XML API OSS interface uses the mediation package to configure the following policies:
- NFM-P-to-node deployment policy: When you save a configuration using the
NFM-P, the configurations are stored and sent to the node according to the
deployment policy. The deployment policy specifies how often the NFM-P sends
configurations to the node. The deployment policy parameters include:
- frequency of the deployment
- number of retries by the NFM-P to make the deployment
- Backup Policy: When NFM-P backs up/ restores node configurations,
the files transferred from/to the node are:
- bof file (bof.cfg),
- primary-config specified in the bof
- index file (primary-config) with a .ndx extension.
These files are saved in NFM-P database on a backup operation and can be dumped to a selected location
on the file system using export operation. The backup policy parameters include:
- whether backups are enabled.
- whether to perform a reboot after the database is restored to the router.
- whether to schedule backups based on a time interval, or based on the number of
configurations on the router.
- Software Upgrade Policy: When NFM-P performs a node software upgrade, the NFM-P transfers the node
software image saved in NFM-P database to the node. The software upgrade policy parameters include:
- whether to activate the image, after it has been transferred to the router.
- whether to perform a reboot after the image has been transferred and activated on the router.
- whether this is an In-service software upgrade activate the image.ra
- upgrade file locations on the node.
Because the NFM-P opens an FTP session with the router for backup, restore and software upgrade,
the FTP User Name and FTP User Password (configured in the mediationPolicy) must match a user account on the
router, where FTP access is enabled for that user.