[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Multiple "Running" configurations
Phil,
I think we should support both single running config and multiple
running config. Your scenario of scheduled backup for a single running
config is correct but note that in some cases, especially during
diagnose phase, operator may need to upload or download a separate
running config for a particular chassis or board without touching the
rest of the configuration. For example, to upgrade a single chassis or
board.
-faye
-----Original Message-----
From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On
Behalf Of Phil Shafer
Sent: Monday, September 15, 2003 9:38 AM
To: Allen, Keith
Cc: netconf@ops.ietf.org
Subject: Re: Multiple "Running" configurations
"Allen, Keith" writes:
>The protocol as it is currently envisioned identifies
>operations on this configuration with a special "<running>" XML tag.
The
>problem brought up by David (correct me if I mischaracterize this,
David)
>was that some devices might have multiple running configurations
(running on
>separate cards, for example), and he would like to see the protocol
support
>operations on devices of this type.
One of the operator requirements was to be able to fetch the entire
configuration from a device in a single, simple operation. This
seems like a reasonable request, since it allows the operators to
completely archive the entire device configuration hourly/nightly/etc.
The running configuration is the full configuration of the device.
If there are multiple sub-systems, the netconf daemon should proxy
all the pieces into a cohesive whole.
If my archive application has to know sufficient in-depth knowledge
about the layout of your box to be able to pull pieces of configuration
off embedded hardware, we've failed.
Thanks,
Phil
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>