Re: netconf and working "on the box"

[Phil Shafer <phil@juniper.net>]

"Faye Ly" writes:
>1. The protocol may have to take redundant or secondary path to the
>network element into consideration so that when the primary route to the
>NE is lost, the secondary kicks in.

The NM application can have a prioritized list of access methods
defined for each device. For example, the highest priority path
could be NETCONF/BEEP (or NETCONF/SSH) to an inband interface
address, with a fallback to the same protocol over management
ethernet, and a lowest priority entry for running netconf over
the serial console via a terminal server. The fallback would
not be transparent, since each access method would require a
new connection, but the reachability and the ability to operate
in failure conditions is the key.

The application can also allow the user to explicitly choose
an access method, so that your PDA can be told to access the
box directly in front of you via a direct serial connection.

Thanks,
 Phil

--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>