• Managing a few routers through the CLI works, but configuring 200 devices manually does not scale.

    Admin connecting over SSH to each of 200+ routers and switches one by one, the manual approach NETCONF replaces

    Figure 1 – Configuring 200 devices manually does not scale

    CLI Text vs. Structured XML

    Every CLI command returns unstructured text formatted for human eyes.
    Extracting an IP address from show ip interface brief requires fragile text parsing that breaks whenever an IOS update shifts spacing or adds a column.

    CLI approach returning unstructured text versus NETCONF approach returning structured XML mapped to YANG model

    Figure 2 – CLI vs

    On the left, the CLI outputs raw text that your script must split line by line.
    On the right, returns structured XML mapped directly to a data model.

    Answer the question below

    What format does NETCONF use to return data to your scripts?

    NETCONF Architecture

    (Network Configuration Protocol, RFC 6241) was built specifically for programmatic configuration management:

    Data models use to define the structure of device settings.

    Encoding uses XML so scripts can read and write values without text parsing.

    Transport uses SSH to provide an encrypted, authenticated channel.

    Before NETCONF

    Before , was the main protocol for network management, but it was designed for monitoring rather than pushing configuration changes.

    Approach

    Designed for

    Data format

    Configuration support

    CLI

    Human operators

    Unstructured text

    Full, but manual

    Monitoring and polling

    MIB/OID (structured but rigid)

    Limited and complex

    Programmatic management

    XML (structured, flexible)

    Full read and write

    Table 1 – CLI vs vs

    Answer the question below

    What data modeling language does NETCONF rely on to define the structure of configuration data?