The user may request a distributed validation by using the validate-router-all keyword. This operation is much slower than local validation because the conductor must wait for all routers to report their results and some may be unreachable or timeout.
If the user wishes, the conductor has the ability to distribute the configuration to all managed routers for each of them to validate it and report the results of their validation before the commit takes place (assuming a successful validation). When run from an SSR conductor, the conductor only validates the configuration itself locally before committing the configuration and then distributing it to all managed routers.
It is used once a series of configuration changes have been made, and an administrator wishes to "activate" those configuration changes. The commit command causes the SSR router to validate the candidate configuration, and then replace the running configuration with the candidate configuration (assuming it passes the validation step). Usage #Ĭommit Copy Keyword Arguments # nameĭistribute config to each managed router for validation and wait for results before committing Version History # ReleaseĬlear routes associated with one or all BGP neighbors. The PCLI will auto-complete typed entries for improved accuracy. The command has multiple filters, allowing administrators to specify which specific entry to remove. The clear arp command is typically used during troubleshooting, to remove ARP (Address Resolution Protocol) entries from an SSR router or node's ARP cache. Shows the contents of the ARP table on the specified node. The VLAN on which to clear the ARP cache (must be specified after 'device-interface') The IP address for which to clear an ARP entry (must be specified after 'device-interface') The device interface on which to clear the ARP cache (default: all)
Installing Using the Pre-5.0 Interactive ISO.Conductor High Availability for Cloud Deployments.Getting Started with the 128T Networking Platform.