151
The common namespace is incompatible with module-specific namespaces. To set up a NETCONF
session, the device and the client must use the same type of namespaces. By default, the common
namespace is used. If the client does not support the common namespace, use this feature to
configure the device to use module-specific namespaces.
Configuration restrictions and guidelines
For this feature to take effect, you must reestablish the NETCONF session.
Configuration procedure
To configure NETCONF to use module-specific namespaces:
Step
Command
Remark
1.
Enter system view.
system-view
N/A
2.
Configure NETCONF to use
module-specific
namespaces.
netconf capability
specific-namespace
By default, the common
namespace is used.
Establishing a NETCONF session
After a NETCONF session is established, the device automatically sends its capabilities to the client.
You must send the capabilities of the client to the device before you can perform any other
NETCONF operations.
You can use the
aaa session-limit
command to set the maximum number of NETCONF sessions
that the device can support. If the upper limit is reached, new NETCONF users cannot access the
device. For information about this command, see
Security Configuration Guide
.
Before performing a NETCONF operation, make sure no other users are configuring or managing
the device. If multiple users simultaneously configure or manage the device, the result might be
different from what you expect.
Setting the NETCONF session idle timeout time
If no packets are exchanged between the device and a user within the NETCONF session idle
timeout time, the device tears down the session.
To set the NETCONF session idle timeout time:
Task
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Set the NETCONF
session idle timeout
time.
netconf
{
soap
|
agent
}
idle-timeout
minute
By default, the NETCONF session idle
timeout time is as follows:
•
10 minutes for NETCONF over
SOAP over HTTP sessions and
NETCONF over SOAP over
HTTPS sessions.
•
0 minutes for SSH sessions,
Telnet sessions, and NETCONF
over SSH sessions.