Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Understanding Build Mode in Gateway View of Edge Services Director

 

In Gateway view of Build mode, you create the network managed by Junos Space Edge Services Director by bringing devices under the administration of the network management application and retrieving the device settings to save in the Edge Services Director database. It provides you with the ability to use device discovery to bring devices under Edge Services Director management, to customize your view of the devices, to configure devices, and to perform some common device management tasks.

This topic describes:

Discovering Devices

Device discovery finds your network devices and brings them under Edge Services Director management. You provide Edge Services Director with identifying information about the devices you want Edge Services Director to manage—an IP address or hostname, an IP address range, an IP subnetwork, or a CSV file that contains this information. Edge Services Director uses the information to probe the devices by using either ping or SNMP get requests. If a device probe is successful, Edge Services Director then attempts to make an SSH connection to the device using the login credentials you supply. If the connection is successful and the device is a supported device, Edge Services Director adds the device to its database of managed devices. Edge Services Director uses Juniper Network’s Device Management Interface (DMI), which is an extension to the NETCONF network configuration protocol, to connect to and configure its managed devices.

You can also discover devices using the device discovery feature provided by the Junos Space Network Management Platform. Devices you discover using Junos Space device discovery are brought under Edge Services Director management if they are supported by Edge Services Director.

Besides bringing your devices under Edge Services Director management, device discovery:

  • Reads the device configuration and saves it in the Junos Space configuration database. Edge Services Director uses this record of the device configuration to determine what configuration commands it needs to send to a device when you deploy the configuration on the device. For this reason, it is important for the Junos Space configuration record to match, or be in sync with, the device configuration.

  • Imports the device configuration into the Gateway view of Build mode configuration. For more information about importing device configurations, see Importing Device Configurations.

Configuring Devices

In Gateway view of Build mode, you can define the configuration of network devices in your Physical network. To support rapid, large-scale deployment of devices, you can define much of your Gateway view of Build mode configuration in a set of profiles.

Note

This section does not apply to virtual devices that Edge Services Director manages.

Deploying Device Configurations

After you build your device configurations in Gateway view of Build mode, you need to deploy the configurations on the devices. None of the configurations you create in Gateway view of Build mode affect your devices until the configurations are actually deployed on the devices.

To deploy the configuration on devices, use Deploy mode. When you change a device’s configuration in Gateway view of Build mode, the device becomes available in Deploy mode for configuration deployment.

For more information about deploying configuration changes, see Understanding Deploy Mode in Edge Services Director.

Importing Device Configurations

As part of device discovery, Edge Services Director analyzes the configuration of a newly discovered device and automatically imports the configuration into the Gateway view of Build mode configuration for that device.

As it imports the device configuration, Edge Services Director automatically creates discovery profiles to match the configuration. It first determines whether any existing profiles match the configuration, and if so, assigns those profiles to the device. It then creates and assigns new profiles as needed. For example, if an access switch has some ports that match the configuration of an existing Port profile, Edge Services Director assigns the existing Port profile to those ports. For the other ports, Edge Services Director creates as many Port profiles as needed to match the port configurations and assigns them to the ports.

You can manage the profiles that Edge Services Director creates as part of device discovery in the same way that you manage user-created profiles—that is, you can modify, delete, or assign them to other devices.

Out-of-Band Configuration Changes

Out-of-band configuration changes are configuration changes made to a device outside of Edge Services Director. Examples include changes made by:

  • Using the device CLI.

  • Using the device Web-based management interface (the J-Web interface or Web View).

  • Using the Junos Space Network Management Platform configuration editor.

  • Using RingMaster software.

  • Restoring or replacing device configuration files.

When an out-of-band change is made, the device configuration no longer matches the Gateway view of Build mode configuration, and the device configuration state changes to out of sync. You cannot deploy configuration on a device that is out of sync. The Edge Services Director resolves out-of-band configuration changes and synchronizes the Gateway view of Build mode configuration with the device configuration by using the resynchronization of devices functionality.

Tip

Before you make configuration changes in Gateway view of Build mode, make sure that devices that will be affected are in sync. Resynchronizing the device configuration can result in losing pending Gateway view of Build mode configuration changes for that device.

Viewing the Devices Inventory

This inventory page lists all the SDG hardware and inventory of the chassis components. A graphical representation is provided of the types of services, connection status of the SDGs or devices, and the configuration status of managed SDGs. A pie chart is displayed to signify these details. Also, you can view full-blown information on the chassis, line cards, and associated hardware components of an SDG and the interface attributes. All of the SDGs that are created are displayed in a tree structure on the left pane of the Inventory page.

Note

From Service view in Build mode, you can select View Inventory from the tasks pane also view comprehensive, consolidated information on each of the services, such as load balancing or CGNAT, from the Inventory page by clicking the plus (+) sign that appears adjacent to each service on the page.

Service Delivery Gateway Groups

Service delivery gateways (SDGs) are discovered by SDG discovery workflow. The discovered SDGs are shown in the SDG inventory page. The discovered SDGs can be a part of a high availability (HA) pair or standalone SDGs. In case of SDG HA pairs, all the actions from SDG management are at the SDG HA pair level; you cannot an action on only the master SDG alone or the standby SDG. SDGs can be grouped as zones or domains. The SDG groups contain one or more SDGs. Each SDG can be part of just one group. User can create, edit, or delete SDG Groups.

KPI Templates

Templates contain the KPI parameters that evaluate the health of a SDG device. A system-created default KPI template is available. This system-created KPI template cannot be edited or deleted. However, an SDG administrator can clone a new template based on this default template. An administrator-created KPI template can be edited or deleted. During the SDG discovery process, one of the KPI template copy is associated to each and every SDG. The KPI parameters from the KPI template are part of the SDG settings and are used to compute the statuses and condition of services of SDGs as green, orange or red.

Related Documentation