Siemens RUGGEDCOM MX5000RE, Справочное руководство

Страница: 36 / 148

Chapter 3
NETCONF Sessions
RUGGEDCOM NETCONF
Reference Guide
24 Saying Hello
•
{user}
A user name on the device assigned the administrative user role.
•
{ipAddress}
The IP address or hostname of the device.
•
-p 830
Specifies port 830. The default NETCONF port is port 830.
•
-s netconf
Specifies the NETCONF subsystem. You must always specify the NETCONF subsystem when initiating a
NETCONF session.
You can configure the IP addresses and ports on which RUGGEDCOM ROX II listens for NETCONF. For more
information, refer to Section 3.1, “Configuring/Monitoring NETCONF in RUGGEDCOM NETCONF” .
When prompted, provide the user password.
When you connect to the device, the device responds with a
<hello>
message, listing its NETCONF capabilities.
For more information on the
<hello>
message and on how to respond to it, refer to Section 3.3, “Saying Hello” .
Section 3.3
Saying Hello
When you open a NETCONF session, the device responds with a <hello> message. The <capabilities>
elements in the message list the NETCONF commands, functions, and namespaces supported on the device. The
<hello> message also includes a <session-id> element, containing a numeric identifier for the new session.
Before you can issue NETCONF requests, you must respond to the
<hello>
message. The minimal response is to
reply with a
<hello>
message listing just the netconf:base capability from the client. You can also reply with
the client's actual capabilities, or reply by returning the device's capabilities back to the device. In all examples in
this guide, we respond to the
<hello>
message with the minimal response.
NOTE
Your reply to the
<hello>
message must not contain a
<session-id>
. Including a
<session-id>
in your response results in a bad element error and the device closes the session.
If you choose to return the device's
<hello>
message as the response, make sure that only one version of each
capability is present in your response. RUGGEDCOM ROX II advertises two versions of the following capabilities:
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:netconf:base:1.1</capability>
<capability>urn:ietf:params:netconf:capability:confirmed-commit:1.0</capability>
<capability>urn:ietf:params:netconf:capability:confirmed-commit:1.1</capability>
<capability>urn:ietf:params:netconf:capability:validate:1.0</capability>
<capability>urn:ietf:params:netconf:capability:validate:1.1</capability>
You must return either version 1.0 or version 1.1 of each capability. Do not return both versions of each capability.
CONTENTS
• Section 3.3.1, “RUGGEDCOM ROX II NETCONF <hello> Message”