This NED is equipped with a number of runtime configuration options "NED settings" allowing for customization by the end user. All options are configurable using the NSO API for NED settings. Most NED settings can be configured globally, per device profile or per device instance in the following locations:
global /ncs:devices/global-settings/ned-settings/huawei-vrp/ profile /ncs:devices/ncs:profiles/profile:/ned-settings/huawei-vrp/ device /ncs:/device/devices/device:/ned-settings/huawei-vrp/
Profiles setting overrides global-settings and device settings override profile settings, hence the narrowest scope of the setting is used by the device.
If user changes a ned-setting, then user must reconnect to the device, i.e. disconnect and connect in order for the new setting to take effect.
From the NSO CLI the device instance NED settings for this NED are available under:
huwaei-vrp device specific NED settings.
Connection configuration.
Settings used while interacting with a device.
Add regular expressions for warnings/errors which the ned should ignore when applying the configuration on a device.
Extend available commands to send.
Extend available patterns to expect.
Extend available actions to perform.
Extend state machine with answers/questions to handle.
Settings for controlling logs generated.
Configure NED to access device via a proxy.
Configure NED to access device via a second proxy.
Transaction specific settings.
Settings used when reading from device.
This ned-setting list can be used to inject config when syncing from device, hence parsing display current-configuration. The injected config is inserted at the top or after each DOTALL regexp match. Note that in order for the new inject setting to take effect, you must not only disconnect and disconnect (as usual when re-reading ned-settings) but also perform a sync-from in order to populate NCS/NSO CDB with newly configured injection config.
The replace-config list ned-setting can be used to replace or filter out config line(s) upon reading from device, i.e. both in a sync-from and a config-hash transaction id.
Settings used when writing to device.
This ned-setting list can be used to inject commands (e.g. config lines) when writing to the device (i.e. upon commit). This can be used, for example, to undo undesired dynamic config automatically set by the device. An example of some inject-command entries used to undo peer enable in bgp ipv4-family unicast mode:
devices device ne40e-1 ned-settings huawei-vrp write inject-command bgp1 config "\n peer ([0-9.]+) as-number \d+" command " ipv4-family unicast\n no peer $1 enable\n exit" after-each
devices device ne40e-1 ned-settings huawei-vrp write inject-command bgp2 config "\n group (\S+) (internal|external)" command " ipv4-family unicast\n no peer $1 enable\n exit" after-each
devices device ne40e-1 ned-settings huawei-vrp write inject-command bgp3 config "\n peer ([0-9.]+) group \S+" command " ipv4-family unicast\n no peer $1 enable\n exit" after-each
Note the $1 used to inject the first catch group. Up to 9 groups may be used.
This ned-setting can be used to add dynamic dependency rules to the NED before being permanently fixed in the NED. This can be useful if a dependency bug is found and you do not want to upgrade the NED or are in a hurry for the fix.
Configure auto (dynamic behaviour).
Configure NED settings related to live-status.