RUGGEDCOM NETCONF
Reference Guide
NETCONF Sessions
This section describes how to do the following:
• connect to the NETCONF service on a device via Secure Shell (SSH). You must do this each time you connect to
the device to start a NETCONF session.
• respond to the device's <hello> message. You must do this each time you start a NETCONF session.
• close the session gracefully with the <close-session> command. Closing the session with the <close-
session> command is recommended, but is optional.
• kill the session with the <kill-session> command. Closing the session with the <kill-session>
command is optional.
CONTENTS
•
Section 3.1, "Configuring/Monitoring NETCONF in RUGGEDCOM NETCONF"
•
Section 3.2, "Connecting to the NETCONF Service"
•
Section 3.3, "Saying Hello"
•
Section 3.4, "Closing the Session"
•
Section 3.5, "Killing a Session"
Section 3.1
Configuring/Monitoring NETCONF in RUGGEDCOM
NETCONF
Before sending NETCONF XML messages to any RUGGEDCOM NETCONF device, make sure NETCONF sessions are
enabled and configured. For more information, refer to either the RUGGEDCOM ROX II Web Interface or CLI User
Guides for the device.
The RUGGEDCOM ROX II User Guides also detail how to look up important statistics, such as the number of bad
hellos, the total number of dropped sessions, etc.
Section 3.2
Connecting to the NETCONF Service
RUGGEDCOM ROX II supports the use of Secure Shell (SSH) to connect to the NETCONF service on the device. To
connect to the NETCONF service, specify an IP address, port, and subsystem:
$ ssh {user}@{ipAddress} -p 830 -s netconf
Configuring/Monitoring NETCONF in RUGGEDCOM
NETCONF
Chapter 3
NETCONF Sessions
23