<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.netyce.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://wiki.netyce.com/feed.php">
        <title>Technical documentation - menu:build</title>
        <description></description>
        <link>https://wiki.netyce.com/</link>
        <image rdf:resource="https://wiki.netyce.com/lib/exe/fetch.php?media=wiki:logo.png" />
       <dc:date>2026-04-30T21:15:15+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://wiki.netyce.com/doku.php?id=menu:build:domains&amp;rev=1720009872&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.netyce.com/doku.php?id=menu:build:mpls_vpns&amp;rev=1720009872&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.netyce.com/doku.php?id=menu:build:osversions&amp;rev=1720009872&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.netyce.com/doku.php?id=menu:build:regions&amp;rev=1727705821&amp;do=diff"/>
                <rdf:li rdf:resource="https://wiki.netyce.com/doku.php?id=menu:build:sitemigrations&amp;rev=1720009872&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://wiki.netyce.com/lib/exe/fetch.php?media=wiki:logo.png">
        <title>Technical documentation</title>
        <link>https://wiki.netyce.com/</link>
        <url>https://wiki.netyce.com/lib/exe/fetch.php?media=wiki:logo.png</url>
    </image>
    <item rdf:about="https://wiki.netyce.com/doku.php?id=menu:build:domains&amp;rev=1720009872&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-07-03T12:31:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>domains</title>
        <link>https://wiki.netyce.com/doku.php?id=menu:build:domains&amp;rev=1720009872&amp;do=diff</link>
        <description>Domains

A Domain in netYCE sets common communication parameters for devices administered by the same team.
Let's say your network has an admin teams for North America and EMEA. Devices in these two admin Domains
have different configurations for AAA server in NA and EMEA. NA admins cannot access EMEA devices and vice versa.
Accounts used by netYCE to access devices have different credentials in both Domains.</description>
    </item>
    <item rdf:about="https://wiki.netyce.com/doku.php?id=menu:build:mpls_vpns&amp;rev=1720009872&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-07-03T12:31:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mpls_vpns</title>
        <link>https://wiki.netyce.com/doku.php?id=menu:build:mpls_vpns&amp;rev=1720009872&amp;do=diff</link>
        <description>MPLS vpns

Within the MPLS VPN form, it is possible to define MPLS VPN's. Instead of fixed values, it's possible to use parameterized values. 

Although the term MPLS is used, this form and the information stored can also be used as a VRF lite configuration.



VRF id

The</description>
    </item>
    <item rdf:about="https://wiki.netyce.com/doku.php?id=menu:build:osversions&amp;rev=1720009872&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-07-03T12:31:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>osversions</title>
        <link>https://wiki.netyce.com/doku.php?id=menu:build:osversions&amp;rev=1720009872&amp;do=diff</link>
        <description>OS-Repository

Overview



The os repo form allows you to manage the OS images that are used for OS upgrades. The os files are stored in the /var/opt/yce/public/os files, categorized by vendor type, which can then be used in OS upgrade scenario commands. 

Within a vendor type, os files are categorized by device type. Nodes with the same device type all use the same files for their os upgrades, which prevents you from uploading modeling the same files for every single node.</description>
    </item>
    <item rdf:about="https://wiki.netyce.com/doku.php?id=menu:build:regions&amp;rev=1727705821&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-09-30T14:17:01+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>regions</title>
        <link>https://wiki.netyce.com/doku.php?id=menu:build:regions&amp;rev=1727705821&amp;do=diff</link>
        <description>Regions

The regions form lets you manage your regions within defined client types to configure parameters specific for the region (for example a province, or a management region). The parameters can be defined in the Parameters form within the Design fase, under the Regions section.</description>
    </item>
    <item rdf:about="https://wiki.netyce.com/doku.php?id=menu:build:sitemigrations&amp;rev=1720009872&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-07-03T12:31:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>sitemigrations</title>
        <link>https://wiki.netyce.com/doku.php?id=menu:build:sitemigrations&amp;rev=1720009872&amp;do=diff</link>
        <description>Site migrations

Overview

The site migrations form exists in order to help you to migrate a site from one client to the other. It is designed to handle the nodes, services and supernets when doing so. 

A site migration is a migration from one site to another site. If you want to migrate every site in a client, this means that you will need a site migration for every site in the migrating client.</description>
    </item>
</rdf:RDF>
