Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Service Activation

    PSM supports the Metro Ethernet Forum (MEF) paradigm for activating Layer 2 Ethernet services in the network. As part of service activation, you define the service and you select the endpoints (and in some cases, the internal NNIs) that make up the service.

    Note: Unless otherwise specified, all references to UNI include UNI LAG, all references to NNI include NNI LAG, and all references to ENNI include ENNI LAG.

    An endpoint can be one of the following:

    • An Ethernet UNI, which is an Ethernet user-to-network interface.
    • An Ethernet ENNI, which is an external Ethernet network-to-network interface.
    • An Ethernet NNI, which can be an internal or external Ethernet network-to-network interface. An external NNI is an endpoint, but an internal NNI is not. If PSM detects (via LLDP discovery) that the NNI is connected to Juniper Networks equipment, PSM considers that the NNI is internal. Otherwise, PSM considers the NNI is external, and treats it as an endpoint. An NNI that is determined to be external is similar to an ENNI. To avoid confusion, it is best to use ENNIs for external NNIs where possible. For those network elements that do not support ENNI functionality, PSM continues to support the ability to treat the regular NNI as an external endpoint where applicable.

    Note: ENNI is supported on BTI7000 Series network elements starting in Release 13.2 only. ENNI is not supported on any other network elements.

    Before using PSM for service activation, you need to configure the packetVX cards on the appropriate network elements, and create the virtual switches that represent those cards. You should also create the necessary internal NNIs, but you do not need to create the endpoints as you have the option of creating endpoints in PSM when you activate the service. You can create internal NNIs in PSM as well, but if you create the internal NNIs beforehand, PSM will be able to query the network and use the discovered LLDP topology to automatically select the appropriate internal NNIs as you add endpoints to the service. The ability to automatically select the internal NNIs is called the Auto-Provision NNIs feature.

    Note: For the Auto-Provision NNIs feature to work properly, you must create all internal NNIs and bring up their links beforehand. In this situation, all NNIs that you create as part of service activation are external endpoint NNIs.

    Creating a UNI, NNI, or ENNI refers to the initial configuration needed to transform an unprovisioned port to a UNI, NNI, or ENNI port.

    Selecting a UNI, NNI, or ENNI refers to choosing that UNI, NNI, or ENNI port to be part of the service. When you select a UNI, NNI, or ENNI and you activate the service, PSM performs the necessary configuration to include that port in the service.

    Note: In PSM, if you use the Provision As ... feature, you can create and select a UNI, NNI, or ENNI in a single step.

    Not all internal NNIs need to be selected manually. If the network is running GVRP, then the network can select the internal NNIs automatically after the service is activated. In other situations, PSM can automatically select and configure the internal NNIs that are needed for the service. This is shown in the following table:

    Network Composition

    NNI Selection

    The domain contains only BTI7000 Series network elements.

    You do not need to manually select the internal NNIs. The BTI7000 Series network elements use GVRP to select and configure the required internal NNIs. For more information on GVRP, see GVRP - GARP VLAN Registration Protocol.

    The domain contains one or more BTI700 Series network elements or one or more BTI800 Series network elements.

    If all network elements in the domain are running the following minimum levels of software:

    • BTI7000 Series - Release 10.3 or later
    • BTI700 Series - Release 1.5 or later
    • BTI718E - Any release
    • BTI800 Series - Release 1.1 or later

    then you can use the Auto-Provision NNIs feature to instruct PSM to automatically select the required internal NNIs.

    Note: PSM uses topology information gathered from LLDP to select the required NNIs. Only those NNIs that cannot be configured using GVRP are selected.

    Otherwise, you must manually select some or all of the internal NNIs that make up the service. For more information on which internal NNIs you need to select, see Mixed networks - BTI7000 Series with BTI700 Series or BTI800 Series elements.

    Service Types

    Note: Unless otherwise specified, all references to UNI include UNI LAG, all references to NNI include NNI LAG, and all references to ENNI include ENNI LAG.

    The service types supported are listed in the table below. The Service Type selected in the Service Attributes panel determines how UNIs can be used, and should be based on the UNIs you have or expect to have in the service. The service type cannot be changed once the service is activated. If the service does not and will not include any UNIs, then you can set the service type to any value.

    Table 1: Service Types

    Service type

    Description

    EPLINE

    (Ethernet Private Line)

    Used to replace TDM private lines.

    A port-based service with a point-to-point EVC (Ethernet Virtual Connection) between dedicated UNIs (that is, only a single EVC per UNI).

    User can select a maximum of two endpoints.

    EVPLINE

    (Ethernet Virtual Private Line)

    Used to replace Frame Relay or ATM services.

    A multiplexed service with a point-to-point EVC between service-multiplexed endpoints (that is, multiple EVCs per endpoint).

    User can select a maximum of two endpoints.

    Allows a single physical connection to the attached equipment with multiple virtual connections.

    EPLAN

    (Ethernet Private LAN)

    Used to support transparent LAN services and multipoint Layer 2 VPNs.

    A port-based service with a multipoint-to-multipoint EVC across dedicated endpoints (that is, only a single EVC per endpoint).

    User can select more than two UNIs.

    EVPLAN

    (Ethernet Virtual Private LAN)

    Used to support transparent LAN services and multipoint Layer 2 VPNs.

    A multiplexed service with a multipoint-to-multipoint EVC across service-multiplexed endpoints (that is, multiple EVCs per endpoint).

    User can select more than two endpoints.

    EPTREE

    (Ethernet Private TREE)

    Used to support a multipoint service consisting of leaf endpoints and root endpoints. Leaf endpoints and root endpoints can send and receive packets from (other) root endpoints, but leaf endpoints cannot send and receive packets from other leaf endpoints.

    A port-based service with a rooted-multipoint EVC across dedicated endpoints (that is, only a single EVC per endpoint).

    User can select more than two endpoints.

    This service type is only supported on BTI7000 Series network elements.

    EVPTREE

    (Ethernet Virtual Private TREE)

    Used to support a multipoint service consisting of leaf endpoints and root endpoints. Leaf endpoints and root endpoints can send and receive packets from (other) root endpoints, but leaf endpoints cannot send and receive packets from other leaf endpoints.

    A port-based service at the leaf nodes and a multiplexed service at the root node, using a rooted-multipoint EVC across endpoints (that is, only a single EVC at the leaf endpoint, and multiple EVCs at the root endpoint).

    User can select more than two endpoints.

    This service type is only supported on BTI7000 Series network elements.

    See the BTI7000 Series packetVX Solutions Guide for more details on Ethernet services and Ethernet VCs.

    Auto-provisioning NNIs

    Note: Unless otherwise specified, all references to UNI include UNI LAG, all references to NNI include NNI LAG, and all references to ENNI include ENNI LAG.

    PSM has the capability of selecting the necessary internal NNIs to add to the service. Internal NNIs are the NNIs that connect the service endpoints together.

    You should only choose this option if all network elements in the domain are running the following minimum levels of software:

    • BTI7000 Series - Release 10.3 or later
    • BTI700 Series - Release 1.5 or later
    • BTI718E - Any release
    • BTI800 Series - Release 1.1 or later

    Additionally, all the required internal NNIs must already exist and their links brought up, and LLDP enabled.

    When this option is selected, PSM uses topology information gathered from LLDP to select and configure those required internal NNIs that do not have GVRP enabled. If PSM determines that GVRP is enabled on a particular NNI, it will let GVRP configure that NNI.

    PSM selects internal NNIs differently depending on whether the required NNI is part of an ERPS ring or not. If the NNI is part of an ERPS ring, then PSM has sufficient information to determine whether the NNI should be selected or not. If the NNI is not part of an ERPS ring, then PSM uses a more liberal set of selection criteria and may select more internal NNIs than is necessary. In such a case, you can manually delete the unnecessary NNIs from the service.

    As an alternative, you can force PSM to select a single path through non-ERPS nodes when Auto-Provision NNIs is enabled. See the proNX Service Manager Installation and Administration Guide for details.

    Activating an Ethernet Service

    Use this procedure to configure and activate an Ethernet service.

    Pre-requisites:

    • All the necessary packetVX cards and virtual switches have been configured.
    • ERPS rings (or MSTP) have been configured, as applicable. This prevents routing loops when multiple paths exist through the network.

    Note: Unless otherwise specified, all references to UNI include UNI LAG, all references to NNI include NNI LAG, and all references to ENNI include ENNI LAG.

    Additionally:

    If you want to ...

    Pre-requisite

    Notes

    Select all UNIs, NNIs, and ENNIs manually during service activation.

    There is no additional pre-requisite.

    When you activate a service, you manually select (and/or create) all the UNIs, NNIs, and ENNIs that make up that service.

    Note: After you activate, GVRP, if enabled, may cause other NNIs to be selected as well, but this is performed outside of PSM.

    Select endpoints manually and let the network select internal NNIs using GVRP.

    Enable GVRP on BTI7000 Series network elements where possible.

    In a network that only contains BTI7000 Series network elements, GVRP can be used to propagate VLAN membership information to all the NNIs, making it unnecessary to select and configure each internal NNI individually from PSM. Just select the endpoints and let GVRP configure the required internal NNIs (outside of PSM). PSM automatically discovers and displays the internal NNIs as soon as you select the service endpoints.

    If the internal NNIs are down or not yet created, GVRP will not be able to configure the required internal NNIs. You can activate the service but the service will be disconnected. Once the internal NNIs have been created and/or their links brought up, the path through the network will be established as VLAN membership information propagates to all the internal NNIs through GVRP.

    In a mixed network that contains BTI7000 Series, BTI700 Series, and/or BTI800 Series network elements, you may need to manually select internal NNIs because not all of these devices support GVRP. See Activating services over combinations of BTI7000 Series packetVX and BTI700 Series or BTI800 Series networks

    Select endpoints manually and let the network select internal NNIs using GVRP, and let PSM select internal NNIs using the Auto-Provision NNIs option.

    Ensure all network elements in the domain are at the following minimum levels of software:

    • BTI7000 Series - Release 10.3 or later
    • BTI700 Series - Release 1.5 or later
    • BTI718E - Any release
    • BTI800 Series - Release 1.1 or later

    Enable LLDP on all network elements in the domain.

    Create all the required internal NNI ports and bring their links up.

    Enable GVRP on BTI7000 Series network elements.

    This lets GVRP configure the required internal NNIs where possible. If GVRP is not enabled or not supported, then PSM uses topological information gathered by the NEs through LLDP, and automatically selects the necessary internal NNIs. PSM only selects those internal NNIs that cannot be configured using GVRP.

    The general service activation workflow is as follows:

    1. Create the Ethernet service and set the service-wide attributes.
    2. Select ports to be added to the service.
    3. Set the port-based attributes (optional).
    4. Set the advanced switch-based and the advanced port-based attributes (optional).
    5. Activate the service.

    Note: ENNI is supported on BTI7000 Series network elements starting in Release 13.2 only. ENNI is not supported on any other network elements.

    1. Create the Ethernet service and set the service-wide attributes.
      1. Click the Service Activation button on the toolbar and choose Ethernet from the drop-down menu.

      2. If you have multiple domains, a Service Activation pop-up dialog box is displayed, as shown.

        From the Select Domain drop-down menu, select a domain in which to create the service. Each domain has its own S-VLAN ID namespace, allowing you to re-use S-VLAN IDs across domains. Click OK.

      3. The Activate Ethernet Service window appears, as shown.

        In the Service Attributes pane of the Activate Ethernet Service window, enter the required information as listed in the following table.

        Table 2: Fields in the Service Attributes Pane

        Field

        Description

        Required field?

        Service Name

        User-defined name that identifies the service. Must be unique to the domain.

        Yes

        SVLAN

        Auto-populated with the next available value. Must be unique to the domain. A value of -1 is shown if there are no SVLAN identifiers available.

        The auto-populated value can be overridden.

        Yes

        Max Frame Size

        The maximum frame size (in bytes) for the Ethernet service. Applicable to UNI ports on BTI7000 Series NEs only.

        Default: 1522

        For BTI7000 Series NEs, this value is used at each UNI port in the service, and supersedes (but must not be greater than) the "Max Frame Size" setting configured on those ports. If this value is greater than the "Max Frame Size" configured on any port in the service, an error message appears.

        For BTI700 Series and BTI800 Series NEs, this value is ignored. The "Max Frame Size" configured on each port is used instead.

        Yes

        Service Type

        See Service types.

        Default: EPLINE

        Note: The BTI700 Series network element does not make a distinction between E(V)PLINE and E(V)PLAN service types. Consequently, PSM may display a service type of an existing BTI700 Series service as E(V)PLAN regardless of how it was originally configured.

        Note: EPTREE and EVPTREE services are supported on BTI7000 Series NEs only.

        Yes

        Customer

        User-defined. See Adding a Customer.

        Optional

        Auto-Provision NNIs

        Specify whether you want PSM to select internal NNIs automatically. This check box is selected by default. See Auto-provisioning NNIs.

        If you do not select this option, you will need to manually select the required internal NNIs in a mixed network. For more information on mixed networks, see Mixed networks - BTI7000 Series with BTI700 Series or BTI800 Series elements.

        Optional

    2. Select ports to be added to the service.

      These ports can be endpoints and/or internal NNIs. You must always select the endpoints.

      Depending on configuration, you may need to select internal NNIs. The rules for internal NNI selection are as follows:

      • You must not select internal NNIs if Auto-Provision NNIs is enabled.
      • You must select internal NNIs if Auto-Provision NNIs is disabled and GVRP is disabled on the NNI ports being selected. GVRP is configured on the NNI port using the proNX 900 or the CLI directly.
      • If Auto-Provision NNIs is disabled and GVRP is enabled on the NNI ports being selected, you may select internal NNIs but there is generally no added benefit to doing so. GVRP will select the appropriate internal NNIs for you.

      Note: When you select an NNI port, you do not make a distinction between an endpoint NNI and an internal NNI. PSM makes that determination automatically based on topology. If PSM detects (via LLDP discovery) that the NNI is connected to Juniper Networks equipment, PSM considers that the NNI is internal. Otherwise, PSM considers the NNI is external (endpoint).

      1. In the Service tab of the UNI/NNI/ENNI Ports panel, click on the icon.

        The following dialog appears.

        This dialog lets you specify UNI/NNI/ENNI ports to include in the service. These ports are MEF interface ports on network elements within the selected domain. Selecting an NE from the list auto-populates the switch members and ports that are available for the Service Type chosen in the Service Attributes pane.

      2. Select a network element, card and port. The port can be UNI or UNI LAG, NNI or NNI LAG, ENNI or ENNI LAG, or Unprovisioned. You can multi-select ports by using the <ctrl> or <shift> keys, but you cannot multi-select a mix of provisioned and unprovisioned ports. You will need to add these separately.

        Note: If you did not select Auto-Provision NNIs, you may have to add a number of internal NNIs to the service in order for traffic to be carried through the network. See Routing Considerations in Mixed Networks.

        If you select an unprovisioned port in the Ports field, the Provision As field is activated, allowing you to provision it as a UNI or UNI LAG, NNI or NNI LAG, ENNI or ENNI LAG.

        If you use the Provision As option to create a UNI LAG, an NNI LAG, or an ENNI LAG, then all ports you multi-select will be added to the LAG.

        Note: If you use the Provision As field to create a new NNI port on a BTI700 Series network element, you cannot use the proNX 900 to reconfigure any of the settings on that port. If you want to be able to use the proNX 900 to reconfigure the settings on that port, you must create the NNI port using the proNX 900 instead of using the Provision As option.

      3. Click Add UNI or Add UNI LAG, Add NNI or Add NNI LAG, or Add ENNI or Add ENNI LAG depending on the type of port chosen.

        PSM adds the port and any auto-selected internal NNI ports required. Additionally, if the port that you are adding is a multi-chassis LAG member, PSM automatically adds all members of that multi-chassis LAG to the service. See Example: Activating an Ethernet service on a multi-chassis LAG for a service activation example involving a mutli-chassis LAG.

      4. After you have finished adding ports, click on the Service tab to view the added ports.

        Note: PSM displays a warning message if it cannot find all the internal NNIs necessary for the service. This can occur if an internal NNI port is down, for example. In this situation, you can still activate the service but the service may not work.

      5. To view the added ports, click on the Details tab.

        The Details window displays the added ports, showing the containing NE, switch, and LAG (if applicable). PSM displays the ports you manually specified, and the internal NNI ports that PSM has selected through the Auto-Provision NNIs feature.

      6. To filter your view, click the All, Endpoints, or NNI tabs to view all ports, view only UNI and ENNI ports, or view only NNI ports (both internal and endpoint) respectively.
      7. To edit the list of ports, proceed as follows:
        • To remove a port from the service, right-click the port or LAG entry and select Remove Port, or select the port or LAG entry and click .
          • If you remove an auto-selected NNI port from the list, a Revert NNIs option appears. This option allows you to add the NNI back to the list.

            Note: Reverting only adds back the auto-provisioned NNIs to this list. Any change you previously made to the NNI port, such as changing the service profiles, remain in effect and are not reverted.

          • If you remove a UNI or ENNI port, all internal NNI ports that have been auto-selected due to that UNI or ENNI port are also removed.
        • To add members to a LAG, right-click the LAG entry and select Add LAG Member(s).
        • To remove a member from a LAG, right-click the LAG member and select Remove LAG Member.
        • To add more ports, repeat 2.

        Note: By adding or removing internal NNIs, you have full control over what NNIs (auto-selected or otherwise) are included in the service. In some situations, it may be necessary for you to manually delete internal NNIs in this manner. For more information, see Auto-provisioning NNIs.

        Note: Any internal NNIs that will be added due to GVRP are not shown, as this is performed outside of PSM.

    3. Set the port-based attributes (optional).
      1. Click on the Details tab.
      2. Set the port-based attributes by clicking in the appropriate box.

        Table 3: Port-based Attributes

        Attribute

        Description

        Range

        Default

        VLAN Mappings

        For a UNI port, this specifies the customer VLAN ID(s) that map to the service, and only applies to virtual services:

        • For the Virtual Single service type, specify a single VLAN ID.
        • For the Virtual Multiple service type, specify one or more VLAN IDs as a comma-separated list (e.g. 2000, 2200) or a range (e.g. 2000-2100) or both.
        • For the Virtual Untagged service type, PSM populates this field with the C-PVID that has been set for the port.

        Note: If CVLAN Translation is enabled, only one customer VLAN ID mapping can be specified.

        For an ENNI port, this specifies the external VLAN ID that maps to the service. Only one VLAN ID can be specified. This field is mandatory.

        This field is not applicable to NNI ports.

        UNI: 1 to 4094

        ENNI: 2 to 4094

        None

        Ingress Service Profile

        This is the service or bandwidth policy to apply at the ingress. Select the available policies using the drop-down list or click on the ellipsis to see more details. See Managing profile templates for more information on how to create profiles.

        Note: Service policies are not supported on the BTI805, BTI821, and BTI822.

        Not applicable

        None

        Egress Service Profile

        This is the service or bandwidth policy to apply at the egress. Select the available policies using the drop-down list or click on the ellipsis to see more details. See Managing profile templates for more information on how to create profiles.

        Note: Service policies are not supported on the BTI805, BTI821, and BTI822.

        Note: This field is not supported on NNI ports on BTI800 Series network elements.

        Not applicable

        None

        TPID

        This shows the outer TPID used at the NNI or ENNI for a stacked Ethernet frame. This field cannot be changed.

        This field is not applicable to UNI ports.

        Not applicable

        0x88a8

        Max Frame

        This is the maximum frame size (in bytes) for the port.

        For UNI ports on BTI7000 Series NEs, this value is not used. The "Max Frame Size" defined for the service is used instead. However, the service "Max Frame Size" must still be less than or equal to this value.

        For UNI ports on BTI700 Series and BTI800 Series NEs, this value is used instead of the service "Max Frame Size".

        For NNI ports, this value is always used.

        If the "Max Frame Size" is already set for this port on the NE, and if the value is not within the valid range, PSM will set the "Max Frame Size" on the port to the default value.

        UNI: 1522 to 9600

        NNI, ENNI: 1526 to 9600

        UNI: 1522

        NNI, ENNI: 9600

        Media Rate

        This specifies the Ethernet mode and media rate.

        Auto

        Full 10 Mb/s

        Half 10 Mb/s

        Full 100 Mb/s

        Half 100 Mb/s

        Full 1000 Mb/s

        Half 1000 Mb/s

        Auto

        EPTREE and EVPTREE services (BTI7000 Series only)

        Forwarding

        This indicates whether the UNI or ENNI port is a root node or a leaf node. There can be multiple root and leaf nodes. If all nodes are root nodes, the resulting service is a LAN.

        This field is not applicable for NNI ports.

        Normal (root) or Leaf

        Normal

    4. Set the advanced switch and port attributes.

      Note: Not all attributes are supported on every device.

      1. To configure advanced switch attributes, click the ellipsis in the Advanced Settings column for the switch entry.

        Configure the switch attributes according to the following table.

        Table 4: Advanced Switch Attributes

        Attributes

        Range of Values

        Applicable to:

          

        Description

        BTI700

        BTI800

        BTI7000

        Service Settings (switch)

        CVLAN Translation

        On or Off

        BTI712

        BTI718

        BTI718E

        Yes

        Yes

        Allows the customer VLAN ID to be remapped for all ports on the switch with virtual services.

        This attribute has the opposite meaning of the MEF CE-VLAN ID Preservation attribute.

        SLA Measurement Profile

        Provisioned profiles

        No

        No

        Yes

        Applies to UNI ports. This attribute can only be set after the service has been activated and MEPs have been created.

        Control Frame Profile

        Provisioned profiles

        No

        Yes

        No

        Sets the L2CP EVC profile.

        Read/write for BTI805, BTI821, BTI822.

        Read-only for BTI810.

        When you are finished configuring the advanced switch settings, click OK.

      2. To configure advanced port attributes for a regular (non-LAG) port, click the ellipsis in the Advanced Settings column for the port entry.

        Table 5: Advanced Port Attributes

        Attributes

        Range of Values

        Applicable to:

          

        Description

        BTI700

        BTI800

        BTI7000

        Service

        E-FPSD

        On or Off

        No

        Yes

        Yes

        Applies to optical UNI ports for EPLINE services.

        For BTI800 Series equipment, this attribute can only be set after the service has been activated and MEPs have been created.

        TPID Action

        None, Aware, Blind

        No

        No

        Yes

        Applies to UNI ports for EPLINE and EPLAN services.

        Service Map Profile

        Provisioned templates and service map profiles

        BTI712

        BTI718

        No

        Yes

        List of provisioned templates and service map profiles. Applies to UNI ports with virtual services.

        Service Map Sequence

        1-100, default 50

        BTI712

        BTI718

        No

        Yes

        The sequence number of the service map. A service map with a lower sequence is evaluated first. Applies to UNI ports with virtual services.

        Layer 1

        Wavelength

        Copper SFP, 850nm to 1560.61nm

        No

        No

        Yes

        The wavelength of the transceiver in nm, or a copper SFP or port. This attribute can only be changed if you are creating the port as part of this service activation. If the port already exists, and you are including it as part of this service activation, you cannot change its value.

        Circuit ID

        1 to 32 alphanumeric characters

        No

        No

        Yes

        The circuit identifier of the port.

        Description

        String

        No

        Yes

        Yes

        User-defined description for the circuit ID.

        Layer 2

        Service Type

        Private

        Virtual Single

        Virtual Multiple

        Virtual Untagged

        BTI718E

        Yes

        Yes

        The UNI service type:

        • Private - service multiplexing is off, bundling is on, all-to-one bundling is on
        • Virtual Single - service multiplexing is on, bundling is off, all-to-one bundling is off
        • Virtual Multiple - service multiplexing is on, bundling is on, all-to-one bundling is off
        • Virtual Untagged - a special setting to support the situation where the local UNI is untagged and the remote UNI is tagged

        Note: This is not the same attribute as the Ethernet service type in Service types.

        C-PVID

        1 to 4094, default is unselected

        BTI718E

        Yes

        Yes

        Specifies the customer's default VLAN ID. This attribute is required on UNI ports running a virtual untagged service, but is optional for other service types.

        Control Frame Profile

        Provisioned profiles

        No

        Yes

        Yes

        Sets the L2CP UNI profile. See the documentation for the respective devices for details. Applies to UNI ports.

        Read/write for BTI805, BTI821, BTI822, and BTI7000 equipment.

        Read-only for BTI810.

        MSTP Enabled

        On or Off

        No

        No

        Yes

        Select to enable MSTP. Applies to UNI ports.

        CCM Enabled

        On or Off

        No

        No

        Yes

        Select to enable CCMs. Applies to UNI ports.

        SVLAN Translation

        On or Off, default is Off.

        If On, specify the external SVLAN ID from 2 to 4094.

        No

        No

        Yes

        Specify the external SVLAN ID. This SVLAN ID is mapped to the internal SVLAN ID from Table 2. Applies to NNI ports only.

        Note: To specify the external VLAN mapping for ENNI ports, see Table 3

        This attribute can only be configured when you first add the NNI to the service. You cannot change the configuration after the NNI has been added to the service. To change the configuration after the NNI has been added, you must first remove the NNI and then add it back to the service.

        This mapping is 1:1. You cannot specify an external SVLAN ID that is mapped to another service on this same port.

        If SVLAN Translation is enabled, untagged frames will be discarded on ingress.

        SVLAN translation cannot co-exist with GVRP and MSTP. If SVLAN translation is enabled on an NNI that has GVRP and/or MSTP also enabled, PSM will automatically disable GVRP and/or MSTP. When the last SVLAN translation is removed from the NNI, PSM will automatically enable GVRP and/or MSTP if either or both were originally enabled.

        When you are finished configuring the advanced port settings, click OK.

      3. To configure port-based attributes for a LAG port, click the ellipsis in the Advanced Settings column for the LAG port entry.

        Table 6: Advanced LAG Port Attributes

        Attributes

        Range of Values

        Applicable to:

          

        Description

        BTI700

        BTI800

        BTI7000

        Service

        Same asTable 5.

        Layer 2

        Same as Table 5.

        LAG

        Distribution Method

        Source MAC

        Destination MAC

        Source and Destination MAC

        Source IP

        Destination IP

        Source and Destination IP

        Source Port

        Destination Port

        Yes

        Yes

        Yes

        The LAG distribution method.

        LACP Mode

        BTI7000:

        Active, Passive, On

        BTI718E:

        LACP, Static

        BTI718E

        No

        Yes

        The LACP mode. This sets the LACP mode for all members of the LAG. A setting of Active (LACP) means that the port will initiate LACP negotiation. A setting of Passive means that the port will not initiate LACP negotation but will respond to it. A setting of On (Static) means that the port will neither initiate nor respond to LACP negotiation.

        Max Links

        1-8

        Yes

        No

        Yes

        The maximum number of links permitted in the LAG.

        Min Links

        1-8

        BTI718E

        No

        No

        The minimum number of links that must be up before the LAG is considered up.

        When you are finished configuring the advanced LAG port settings, click OK.

      4. To configure port-based attributes for a LAG member, click the ellipsis in the Advanced Settings column for the LAG member entry.

        Table 7: Advanced LAG Member Attributes

        Attributes

        Range of Values

        Applicable to:

          

        Description

        BTI700

        BTI800

        BTI7000

        Layer 1

        Same as Table 5.

        LAG Member

        LACP Port Priority

        0-65535

        Yes

        No

        Yes

        The LACP port priority.

        LACP Wait Time

        0-10 seconds

        No

        No

        Yes

        The LACP wait time.

        LACP Mode

        Active, Passive, On

        No

        No

        Yes

        The LACP mode. This sets the LACP mode for individual members of the LAG.

        LACP Timeout

        Long, Short

        No

        No

        Yes

        The LACP timeout period.

        When you are finished configuring the advanced LAG member settings, click OK.

    5. Click Activate. The service is activated.

      For information about error messages, see Service Activation Error Messages.

      Note: You must wait for the activation tasks to complete before performing any other operation on the NEs affected by this activation.

    Example: Activating an EVPLINE Service

    This is an example of how to use PSM to activate two different types of EVPLINE services. The first service, between NEWYORK and MIAMI, requires CVLAN translation and no bundling. The second service, between NEWYORK and DALLAS, requires connectivity between a tagged and an untagged interface, also with no bundling. This is shown in Figure 1 along with the desired service policies.

    Figure 1: Example: EVPLINE Services

    Example: EVPLINE Services

    Note: Before configuring the service, ensure that the PVX cards, virtual switches, and the NNIs have all been created on the appropriate network elements. For information on how to do this, refer to the BTI7000 SeriespacketVX Solutions Guide.

    This example is divided into two parts, setting up the EVPLINE service between NEWYORK and MIAMI with CVLAN translation, and setting up the service between NEWYORK and DALLAS with the virtual untagged option.

    Part 1: Setting Up the EVPLINE Service with CVLAN Translation

    The service between NEWYORK (10.1.212.1:1-1-13-10) and MIAMI (10.10.20.99:1-1-5-10) requires CVLAN translation and no bundling. CVLAN ID 201 is mapped to the service at the NEWYORK UNI and CVLAN ID 101 is mapped to the service at the MIAMI UNI. The UNI ports are initially unprovisioned in this example.

    1. On the PSM Client, click the Service Activation button on the toolbar, as shown.

      Choose Ethernet from the pulldown menu.

      The Activate Service panel is displayed.

    2. Enter the service attributes and click on the plus sign to start adding interfaces.

    3. Add the NEWYORK UNI to the service by highlighting the "Unprovisioned 1:1:13:GIGE:10" port and selecting Provision As:UNI.

      Note: The switches and ports only appear in this menu if they have been properly configured on the NE. See the BTI7000 Series packetVX Solutions Guide for information on how to add and configure a switch.

      When you are done, click Add UNI.

    4. Add the MIAMI UNI to the service by highlighting the "Unprovisioned 1:1:5:GIGE:10" port and selecting Provision As:UNI.

      When you are done, click Add UNI.

      The result is the following topology.

      Note: The NNIs do not need to be explicitly added if the network elements are running GVRP. When working with network elements that do not support GVRP such as the BTI700 Series or BTI800 Series devices, you will need to add the appropriate NNIs to the service or use the Auto-Provision NNIs feature.

    5. Select the Details tab in the UNI/NNI Ports pane to enter more detailed information for each UNI.

    6. Set the CVLAN mappings by clicking in the box and entering the desired CVLAN values for each UNI. In this example, the MIAMI UNI maps CVLAN ID 101 to the service, and the NEWYORK UNI maps CVLAN ID 201 to the service.

    7. Click on the pulldown menu or the ellipsis in the Ingress Service Profile column for the MIAMI UNI.

    8. Select the desired ingress service profile by highlighting it and clicking OK. When a profile is highlighted, the profile details are displayed in the Selected Profile pane. In this example, the desired policy has already been defined.

    9. Repeat for the NEWYORK UNI.

    10. Open the Advanced Settings menu for the MIAMI UNI by clicking on the ellipsis.

    11. Select the service type from the pulldown menu and click OK.

      In this example, the Service Type is Virtual Single, meaning that service multiplexing is on, bundling is off and all-to-1 bundling is off. Leave the C-PVID unchecked.

    12. Open the Advanced Settings menu for the MIAMI switch by clicking on the ellipsis.

    13. Select CVLAN Translation and click OK. This attribute has the opposite meaning of the Metro Ethernet Forum CE-VLAN ID Preservation attribute. In other words, CVLAN Translation = yes is equivalent to CE-VLAN ID Preservation = no.

    14. Repeat steps 10 through 13 for the NEWYORK UNI.
    15. Click Activate.

      It is good practice to check whether the activate completes successfully. Open the Tasks panel to check.

      For information about error messages, see Service Activation Error Messages

    Part 2: Setting Up the EVPLINE Service with the Virtual Untagged Option

    The service between NEWYORK (10.1.212.1:1-1-13-10) and DALLAS (10.1.213.1:1-1-5-10) requires connectivity between a tagged and an untagged interface. CVLAN ID 202 is mapped to the service at the NEWYORK UNI, while the DALLAS UNI is an untagged interface. In this example, the NEWYORK UNI port has already been provisioned but the DALLAS UNI port is unprovisioned.

    1. On the PSM Client, click the Service Activation button on the toolbar, as shown.

      Choose Ethernet from the pulldown menu.

      The Activate Service window is displayed.

    2. Enter the service attributes and click on the plus sign to start adding interfaces.

    3. Add the NEWYORK UNI to the service by highlighting the "UNI 1:1:13:GIGE:10" port.

      Note: The switches and ports only appear in this menu if they have been properly configured on the NE. See the BTI7000 Series packetVX Solutions Guide for information on how to add and configure a switch.

      When you are done, click Add UNI.

    4. Add the DALLAS UNI to the service by highlighting the "Unprovisioned 1:1:5:GIGE:10" port and selecting Provision As:UNI.

      When you are done, click Add UNI.

      The result is the following topology.

      Note: The NNIs do not need to be explicitly added if the network elements are running GVRP. When working with network elements that do not support GVRP such as the BTI700 Series or BTI800 Series devices, you will need to add the appropriate NNIs to the service or use the Auto-Provision NNIs feature.

    5. Select the Details tab in the UNI/NNI Ports pane to enter more detailed information for each UNI.

    6. Set the CVLAN mappings by clicking in the box and entering the desired CVLAN values for each UNI. In this example, the NEWYORK UNI maps CVLAN ID 202 to the service while the DALLAS UNI has no mapping.

    7. Click on the pulldown menu or the ellipsis in the Ingress Service Profile column for the DALLAS UNI. Select the desired bandwidth profile. In this example, the desired bandwidth profile has already been defined.

    8. Repeat for the NEWYORK UNI.

    9. Open the Advanced Settings menu for the DALLAS UNI by clicking on the ellipsis.

    10. Select the service type from the pulldown menu and click OK.

      The Service Type should be Virtual Untagged, with C-PVID set to the value used at the remote endpoint, in this case, 202. Ingress traffic at the DALLAS site will be automatically tagged with this value, while egress traffic will automatically have this tag stripped.

    11. Open the Advanced Settings menu for the DALLAS switch by clicking on the ellipsis.

    12. Ensure CVLAN Translation is unchecked and click OK. This attribute has the opposite meaning of the Metro Ethernet Forum CE-VLAN ID Preservation attribute. In this example, the DALLAS site only expects untagged traffic, so this parameter is not applicable.

    13. Modify the Advanced Settings attributes for the NEWYORK UNI. Ensure the Service Type is set to Virtual Single, C-PVID is unchecked, and CVLAN Translation is unchecked, meaning that CE-VLAN ID preservation is on, service multiplexing is on, bundling is off, and all-to-1 bundling is off.
    14. Click Activate.

      It is good practice to check whether the activate completes successfully. Open the Tasks panel to check.

      For information about error messages, see Service Activation Error Messages

    Example: Activating an Ethernet Service on a Multi-chassis LAG

    This is an example of how to activate an Ethernet service on a multi-chassis LAG UNI. A multi-chassis LAG UNI has member links that terminate on two different network elements. If one link or network element fails, the service continues to operate over the other link. Service activation for a multi-chassis LAG UNI is very similar to service activation on a regular UNI.

    This example focuses on details that are specifc to multi-chassis LAG service activation.

    1. Select Tools >Service Activation >Ethernet.

      The Activate Ethernet Service panel is displayed.

      Note: If multiple domains exist, you will need to select the domain first.

    2. Enter the service attributes and click on the plus symbol to start adding UNI ports.
      1. Select a multi-chassis LAG port and click Add UNI LAG.

        You can select any member of the multi-chassis LAG as the UNI endpoint. When you select a multi-chassis LAG member, PSM automatically adds all members of that same multi-chassis LAG to the service.

        You can distinguish between different multi-chassis LAGs by the MLAG index. For example, to select MLAG 1, simply select a member belonging to MLAG 1.

      2. Add the other UNI endpoint as you normally do.

        For example:

        The result is the following topology.

    3. Select the Details tab to enter more detailed information for each UNI.

      Only parameters for the active multi-chassis LAG member can be configured. PSM automatically copies the parameters from the active member to the non-active members. You cannot change the parameters for the non-active members directly. In the figure below, the active multi-chassis LAG member is on SA-821-80, and the standby multi-chassis LAG member is on SA-822-83.

    4. Click Activate.

      The PSM server sends the activation request to the network element. You can monitor the status of the request through the View >Server >Tasks window. The changes are shown in PSM a short while after the task completes successfully.

    For information about error messages, see Service Activation Error Messages

    Example: Activating EVPLAN and EVPLINE Services Using Service Maps for Flow Redirection

    This is an example of how to use PSM to activate two different types of services for three endpoints. The first is a typical multipoint-to-multipoint EVPLAN service for regular data connectivity and the second is a set of separate EVPLINE point-to-point services for voice connections. This models a corporate network where regular intranet traffic between sites use the EVPLAN service, while the lower latency, more stringent quality-of-service site-to-site voice traffic uses a special EVPLINE service. The assumption is that the network provider has set up low latency pathways for the EVPLINE traffic, perhaps with little or no CIR oversubscription on any of the network segments that comprise the path.

    Note: Although the interfaces are untagged, the services are still considered virtual since more than one service is provided at each UNI. Therefore the services are EVPLINE and EVPLAN rather than EPLINE and EPLAN.

    Figure 2 shows the desired network configuration along with the bandwidth policies.

    Figure 2: Example: EVPLINE and EVPLAN Services

    Example: EVPLINE and EVPLAN Services

    Note: Before configuring the service, ensure that the PVX cards, virtual switches, and the NNIs have all been created on the appropriate network elements. For information on how to do this, refer to the BTI7000 Series packetVX Solutions Guide.

    This example is divided into three parts: setting up the service maps, setting up the EVPLINE services, and setting up the EVPLAN service. The service maps are used to classify voice traffic for the EVPLINE services. Data traffic for the EVPLAN service do not require classification. Instead, CVLAN ID mapping and C-PVIDs are used to map data traffic to the EVPLAN service.

    To keep this example short, some details covered in previous examples are omitted.

    Part 1: Setting Up the Service Maps

    A service map must be created at each site to classify ingress packets for the voice service. In this example, voice traffic needs to be diverted to the EVPLINE service while all other traffic remains on the EVPLAN service. This is performed using a combination of class maps and service maps. A class map is a specific filter used to classify traffic, such as matching a destination port number. A service map is a collection of class maps, or in other words, a collection of filters. A match is declared in the service map if the ingress packet matches any of the filters specified in the collection of class maps.

    Note: The terminology used by PSM differs slightly from that used by the CLI. Specifically, the CLI expands the notion of service policy to include service maps, while PSM treats the service map as distinct from service policy. The general configuration approach, however, remains the same.

    In this example, all ingress SIP, RTP, and RTCP packets are considered to be voice traffic. The approach is therefore to create class maps to identify each of these protocols, and then group these class maps together into a service map that maps these packets to the EVPLINE service. The remaining traffic will be mapped to the EVPLAN service using CVLAN mapping.

    1. Open the Profiles panel.

    2. Create class map profiles to identify SIP, RTP, and RTCP traffic destined for NEWYORK.

      Note: The port numbers used below are for illustration purposes only. Actual port numbers may differ and may likely include a range.

      1. Right-click and select Create Class Map Profile.

      2. In the Selected Profile pane, enter the criteria for determining SIP traffic destined for the NEWYORK site. This is UDP traffic heading to the 10.1.212.x subnet with a destination port of 5060. Click Apply.

      3. Repeat to create a class map for RTP traffic destined for the NEWYORK site. This is UDP traffic heading to the 10.1.212.x subnet with a destination port of 5004. Click Apply.

      4. Repeat to create a class map for RTCP traffic destined for the NEWYORK site. This is UDP traffic heading to the 10.1.212.x subnet with a destination port of 5005. Click Apply.

      This results in three class maps, classifying SIP, RTP, and RTCP traffic destined for NEWYORK.

    3. Repeat to create class maps for SIP, RTP, and RTCP traffic destined the MIAMI site.

    4. Repeat to create class maps for SIP, RTP, and RTCP traffic destined for the DALLAS site.

    5. Group the class maps by creating a service map profile to identify voice traffic destined for the NEWYORK site.
      1. Right-click and select Create Service Map Profile.

      2. In the Selected Profile pane, add the three TO_NEWYORK_xxx class maps created in the previous step. Click Apply.

      The result is a service map that identifies voice traffic destined for NEWYORK.

    6. Repeat to create the service map for voice traffic destined for the MIAMI site.

    7. Repeat to create the service map for voice traffic destined for the DALLAS site.

    The required service maps have now been created.

    Part 2: Setting Up the EVPLINE Services

    All three EVPLINE services are identical.

    1. Create the NEWYORK to MIAMI EVPLINE service.
      1. On the PSM Client, click the Service Activation button on the toolbar and choose Ethernet.
      2. If you have defined multiple Ethernet domains, a dialog appears allowing you to select the Ethernet domain in which you want to create this service. Use the pulldown menu to select the desired domain and click OK.

      3. Enter the service attributes and click on the plus sign to start adding interfaces.

      4. Add the NEWYORK UNI on "1:1:13:GIGE:10" and the MIAMI UNI on "1:1:5:GIGE:10".

        Note: The switches and ports only appear in the Add UNI menu if they have been properly configured on the NE. See the BTI7000 Series packetVX Solutions Guide for information on how to add and configure a switch.

        Note: The NNIs do not need to be explicitly added if the network elements are running GVRP. When working with network elements that do not support GVRP such as the BTI700 Series or BTI800 Series devices, you will need to add the appropriate NNIs to the service or use the Auto-Provision NNIs feature.

      5. Click the Details tab in the UNI/NNI Ports pane to enter more detailed information for each UNI.

        There is no need to specify any CVLAN mappings since the interfaces are untagged.

      6. Select the ingress service profile for both sites by clicking on the pulldown menu or the ellipsis.

      7. Open the Advanced Settings menu for the MIAMI UNI by clicking on the ellipsis.

      8. Select the service map from the pulldown menu and click OK.

        The Service Type is not applicable. Ensure the C-PVID is unchecked. The Service Map sequence is also not applicable.

      9. Open the Advanced Settings menu for the MIAMI switch by clicking on the ellipsis.

      10. Ensure CVLAN Translation is unchecked and click OK.

      11. Repeat substeps f through i for the NEWYORK UNI but select the TO_MIAMI_VOICE service map.

      12. Click Activate.

        It is good practice to check whether the activate completes successfully. Open the Tasks panel to check that the task has finished.

        For information about error messages, see Service Activation Error Messages

    2. Repeat for the NEWYORK to DALLAS EVPLINE service, with the following differences:
      • Service Name - NEWYORK_DALLAS_1051
      • SVLAN - 1051
      • UNI ports - NEWYORK UNI on "1:1:13:GIGE:10" and DALLAS UNI on "1:1:5:GIGE:10"
      • Service Map - TO_DALLAS_VOICE service map at the NEWYORK UNI and TO_NEWYORK_VOICE service map at the DALLAS UNI.
    3. Repeat for the DALLAS to MIAMI EVPLINE service, with the following differences:
      • Service Name - DALLAS_MIAMI_1053
      • SVLAN - 1053
      • UNI ports - DALLAS UNI on "1:1:5:GIGE:10" and MIAMI UNI on "1:1:5:GIGE:10"
      • Service Map - TO_DALLAS_VOICE service map at the MIAMI UNI and TO_MIAMI_VOICE service map at the DALLAS UNI.

    Setting Up the EVPLAN Service

    1. On the PSM Client, click the Service Activation button on the toolbar and choose Ethernet.
    2. If you have defined multiple Ethernet domains, a dialog appears allowing you to select the Ethernet domain in which you want to create this service. Use the pulldown menu to select the desired domain and click OK.

    3. Enter the service attributes and click on the plus sign to start adding interfaces.

    4. Add the NEWYORK UNI on "1:1:13:GIGE:10", the MIAMI UNI on "1:1:5:GIGE:10", and the DALLAS UNI on "1:1:5:GIGE:10".

      Note: The switches and ports only appear in the Add UNI menu if they have been properly configured on the NE. See the BTI7000 Series packetVX Solutions Guide for information on how to add and configure a switch.

      Note: The NNIs do not need to be explicitly added if the network elements are running GVRP. When working with network elements that do not support GVRP such as the BTI700 Series or BTI800 Series devices, you will need to add the appropriate NNIs to the service or use the Auto-Provision NNIs feature.

    5. Click the Details tab in the UNI/NNI Ports pane to enter more detailed information for each UNI.

    6. Configure the Advanced settings for each UNI.
      1. Open the Advanced Settings menu for the each UNI by clicking on the ellipsis.

      2. Set the C-PVID to an arbitrary value and click OK. For simplicity, set the C-PVID to the same value for all three UNIs.

        By setting the C-PVID value, all untagged traffic arriving at the UNI will be treated as if it contained a CVLAN ID equal to the C-PVID value. This value can then be used in the CVLAN mapping table. The Service Type is not applicable. The Service Map sequence is also not applicable.

    7. Configure the Advanced Settings attributes for each switch.
      1. Open the Advanced Settings menu for each switch by clicking on the ellipsis.

      2. Ensure CVLAN Translation is unchecked and click OK.

    8. Set the CVLAN mapping for each UNI, using the C-PVID value configured earlier.

    9. Select the ingress service profile by clicking on the pulldown menu or the ellipsis.

    10. Click Activate.

      It is good practice to check whether the activate completes successfully. Open the Tasks panel to check that the task has finished.

      For information about error messages, see Service Activation Error Messages

    Modified: 2016-12-11