Monitoring configuration updates

When a change is made to a bond or aggregator setting in the management application, a configuration update command is pushed to the bonder and aggregator over the management VPN. You can monitor the status of these messages on the bond or aggregator details page under Updates.

When a message has been delivered, it moves from the Pending Updates section to the Completed Updates section. The Updates section on the bond details page shows updates sent to both the bonder and the bond’s aggregator, while the Updates section on the aggregator details page shows only updates for that particular aggregator.

If a message cannot be delivered, an error message is shown and the update is retried until it succeeds. Messages are applied to the node in the order they are submitted, so an undeliverable message for a bonder or aggregator will delay the delivery of all later messages to that bonder or agg. You can submit configuration changes even while other messages are undeliverable and they will be sent when connectivity to the node is restored.

Configuration changes submitted after a bonder has been imaged but before it has been set up at the customer’s site are retried at a long interval. It could take several minutes after the bonder comes online to get the changes. To update the bonder’s configuration manually, run nodeconfig after starting the bonder for the first time, and then restart bonding.