NETCONF
7450 ESS System Mangement Guide Page 351
Config system security ssh server-cipher-list protocol-version 1 cipher 200-205
Config system security ssh server-cipher-list protocol-version 2 cipher 190-235
Config log filter 1001
Config log filter 1001 entry 10
Config log log-id 99 & 100
Some SPC objects can't be deleted (Non-Deletable SPC Objects):
• There is no 'no' form in CLI
• The Non-Deletable SPC Objects are not visible in a <get-config> response when they
are:
∅ Set to their default values (including all child leaves & objects)
∅ Removed or deleted
• The Non-Deletable SPC Objects are visible in a <get-config> response if a child leaf
or object is changed away from the default value; for example, setting the card-type.
• The list of Non-Deletable SPC Objects as of 13.0.R1 is as follows:
Config system security user-template {tacplus_default|radius_default}
Config log event-control …
Config filter log 101
Config qos … various default policies can’t be deleted
Config qos queue-group-templates … these can’t be deleted
Config card <x>
Config router network-domains network-domain “default”
Config oam-pm bin-group 1
Config call-trace trace-profile “default”
There are some Non-Deletable SPC Objects that are visible in a <get-config> request even if
they are set to default values:
Config system security cpu-protection policy 254 and 255
Config router interface “system"
Config service customer 1
Establishing a NETCONF Session
The following example shows a client on a Linux PC initiating a connection to an SR OS
NETCONF server. The SSH session must be invoked using an SSH subsystem (as
recommended in RFC 6242):
ssh -s my_username@192.168.0.92 -p 830 netconf
The following example shows an exchange of hello messages which include advertisement of
capabilities.
From the SR OS server:
<?xml version="1.0" encoding="UTF-8"?>
To Next Page
Loading...
