To configure and run an OmniSwitch OAM traceroute test CLI script
WARNING Network Damage |
Scripts that are not correctly created or applied can cause serious damage to the network.
Nokia recommends that system administrators clearly define user responsibilities for CLI script usage, and ensure that scripts are verified and validated before they are executed on devices in a live network.
Steps
The following procedure describes how to configure and run an OmniSwitch traceroute using the script created using To create an OmniSwitch ping or traceroute OAM diagnostic test using a CLI script .
1 |
Ensure that the mediation policy for each OmniSwitch target is configured with the correct user name and password for CLI communication. See To configure device mediation . |
2 |
Choose Tools→Scripts from the NFM-P main menu. The Scripts list form opens. |
3 |
Choose CLI Script (script) from the object drop-down menu. |
4 |
Configure the filter criteria. A list of scripts appears at the bottom of the Scripts form. |
5 |
Double-click on the OmniSwitch traceroute script that you created using To create an OmniSwitch ping or traceroute OAM diagnostic test using a CLI script . The CLI Script (Edit) form opens. |
6 |
Click on the Targets tab. |
7 |
Click on Add. The Target Configuration form opens. |
8 |
Click Add in the target list to add an OmniSwitch to the list. The Select Network Elements form opens with a list of OmniSwitch NEs. |
9 |
Choose one or more OmniSwitch NEs and click OK. The Select Network Elements form closes, and the OmniSwitch NEs appear in the target list panel of the Target Configuration form. |
10 |
Configure the test parameters.
|
11 |
To run the script on the specified targets, choose one or more entries from the list. |
12 |
Click Execute. The test results appear. |
13 |
Perform one of the following to view the results of the scripts:
|
14 |
Click OK or Cancel to close the CLI Script (Edit) form. |
15 |
Close the form. End of steps |