Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Understanding Build Mode in Service View of Edge Services Director

 

In Build mode, you can create services, policies, and filters for devices that are managed by Edge Services Director. The service templates and attributes for services, policies, and filters help you classify and control the manner in which packets must be handled by the various services.

Configuring a policy has a major impact on the flow of routing information or packets within and through the router. For example, you can configure a routing policy that does not allow routes associated with a particular customer to be placed in the routing table. As a result of this routing policy, the customer routes are not used to forward data packets to various destinations and the routes are not advertised by the routing protocol to neighbors.

You can also import objects, which are components or parameters used for creation of services, from the Service Delivery Gateways (SDGs) that are present in the Edge Services Director database or from external XML files.

This topic contains the following sections that describe the different workspaces or utilities that you can access from Build mode:

Service Designer

The service planning functionality enables you to use the Service Designer page to create service templates, which can be used on multiple devices. The Service Designer page lists all service components used to create service templates. According to the business needs, you can configure generic properties in a template and enable the editing of deployment-specific parameters. The operator can then easily and quickly configure the service on a large number of devices. You can use the Service Designer page to define and manage stateful firewall (SFW), carrier-grade NAT (CGNAT), application delivery controller (ADC), and traffic load balancing (TLB) services.

Note

Edge Services Director currently supports only brownfield deployments and not greenfield deployments. A greenfield deployment refers to the Junos OS base configurations and bootstrapping, core device settings such as routing instances, interfaces and IP addresses, and routing protocols to be available for configuration using the network management application. A brownfield deployment refers to the basic and mandatory device settings already being configured on the devices before they are imported or discovered for additional modifications, such as configuration of services, using the network management application.

As a designer, you can also modify service parameters and definitions by using the View Service page that you can open from the Service Gateways -- Unmanaged devices page in the Build mode without using service templates for updating services details. All the service components are listed on the Service Designer page so that the designer can use choose components and create the new service template.

Services Inventory

The Services Inventory page lists the services configured in the Edge Services Director database and provides basic information about the configured services, such as adaptive delivery controller (ADC), stateful firewall (SFW), server load balancing (SLB), and carrier grade NAT (CGNAT). The Services Inventory page is available in Build mode and under Service view.

Object Builder

Objects are constituents or building blocks that are used to create service definitions and policy or filter templates. You can use the Object Builder page to retrieve and transfer the objects or components that have been previously created on the SDGs or devices. The objects might reside on the managed SDGs or SDG groups if the objects were defined using the appropriate configuration statements and parameters in the Junos CLI interface of the respective SDGs. This mechanism of importing object settings enables you to easily, quickly, and optimally use the object definitions when you create service and policy templates.