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 T1/E1 TDM (pseudowire) services in a BTI810 network. Service activation is performed by first creating a regular Ethernet service and then creating a pseudowire service that uses that Ethernet service.

    Figure 1 shows the component model for a BTI810 switch with a T1/E1 card residing in slot 1 and an OC3/STM1 card residing in slot 2.

    Figure 1: BTI800 Series Component Model

    BTI800 Series Component Model

    Each card consists of a set of TDM and logical pseudowire interfaces. The pseudowire interfaces are logically connected to the UNI, and are distinguishable from each other through different CVLANs. Each card is automatically associated with its own UNI, with the UNI in logical slot 2 port 1 (2/1) associated with the card in physical slot 1, and the UNI in logical slot 3 port 1 (3/1) associated with the card in physical slot 2. These associations are hardcoded and cannot be changed.

    The incoming bitstream on the TDM interface is processed on the card, encapsulated inside an Ethernet frame (with a destination MAC address of the remote TDM card), and passed to the local UNI. From there, the TDM traffic is transported across the network as regular Ethernet traffic.

    Note: When configuring the underlying Ethernet service, you should take into consideration the delay variation requirements for a TDM circuit.

    Although a TDM service is point-to-point, the Ethernet service (or EVC) that transports the TDM traffic can be EVPLINE or EVPLAN. If EVPLINE is used, then each TDM service uses its own point-to-point EVC. If EVPLAN is used, then more than one TDM service can share the same EVC. In the previous figure, all TDM services on the switch share a single EVC. Note that each TDM service is still point-to-point. The network routes the Ethernet frames based on the destination MAC address and CVLAN membership, so only the intended destination will receive the traffic.

    Tip: For convenience, you can share a single EVC across multiple TDM services. In this way, you do not need to create an Ethernet service for each TDM service.

    Activating a Pseudowire Service

    Use this procedure to configure and activate a pseudowire service on a BTI800 Series network.

    Prerequisites:

    • All the necessary Ethernet NNIs have been configured in the network. If this network includes BTI7000 Series NEs, then all the necessary packetVX cards and virtual switches have been configured.
    • The Ethernet service connecting the two TDM endpoints has been configured.
    • The TDM endpoint interfaces have been configured.
    • ERPS has been configured, as applicable. This prevents routing loops when multiple paths exist through the network.
    1. Click the Service Activation button on the toolbar and choose Pseudowire from the drop-down menu.

      If you have one Ethernet domain only, the Activate Pseudowire Service window appears, as shown. Proceed to 3.

      Figure 2: Activate Pseudowire Service (CESOP)

      Activate Pseudowire Service (CESOP)

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

    2. From the Select Domain drop-down menu, select a domain in which to create the service. Click OK.

      Although you are creating a pseudowire service, you still need to select the Ethernet domain in which you are running the service because you will need to associate the pseudowire service to an Ethernet service later.

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

      Table 1: Fields in the Service Attributes Pane

      Field

      Description

      Required field?

      Service Name

      User-defined name that identifies the service. Must be unique to all pseudowire services in the domain.

      Yes

      ECID

      Emulated circuit identifier. Must be unique to all pseudowire services in the domain.

      The auto-populated value can be overridden.

      Yes

      Customer

      User-defined. See Adding a Customer.

      Optional

      Service Type

      The service type can be SATOP or CESOP. By default, the service type is SATOP. When you select CESOP, additional fields are available for configuration.

      Yes

    4. Configure the Interface A endpoint.
      1. In the Service Details pane, use the pulldown menu to select the Network Element for the Interface A endpoint.

        The pulldown menu is populated with all BTI800 Series nodes that have TDM cards inserted.

      2. Select the Slot and Interface from the pulldown menus.

        The pulldown menus are populated with all possible selections. Only the interfaces (or timeslots) not already in use can be selected. Interfaces or timeslots that are part of an existing service are greyed out.

        Note: Only ports that have been configured on the device as framed and enabled are selectable for a CESOP service.

        Note: Entries with an (M) designation can be configured as clock masters. Entries without that designation can only be configured as slaves (or use internal clocking).

      3. Select the Clock Reference.
      4. For CESOP, specify the Channels that make up the service.

        You can specify a single channel (e.g. 5), a range of contiguous channels (e.g. 5-20), non-contiguous channels (e.g. 5,9), or a mix (e.g. 3,5-20). For T1, the available channels are 1 to 24. For E1, the available channels are 1 to 31. A channel cannot belong to more than one service.

        Note: If the Clock Reference is set to Adaptive Master, then you must select one, two, four, or eight channels.

        Note: Channelized services can only be configured for T1/E1 cards.

      5. Configure the TDM and physical interface settings (optional).

        Click on the Settings tab and set the TDM and physical interface (T1/E1 card only) attributes by clicking in the appropriate box.

        Table 2: TDM Attributes

        Attribute

        Description

        Range

        Default

        Customer VLAN Priority

        This specifies the priority to assign to the service.

        0 to 7

        6

        PDV (Jitter Buffer)

        This specifies the size of the jitter buffer in microseconds.

        2000 to 32000

        5000

        Payload Size

        This specifies the payload size of the packetized bitstream in bytes. Both endpoints must have the same payload size.

        SATOP: 192, 384, 576, 768, 960

        CESOP: Depends on the number of channels. See Table 4.

        SATOP: 192

        CESOP: None.

        Table 3: Physical Interface Attributes (T1/E1 Card Only)

        Attribute

        Description

        Range

        Default

        Line Build Out

        This specifies the line build out (in feet) for the interface.

        0 to 133, 134 to 266, 267 to 399, 400 to 533, 534 to 655 feet

        0 to 133

        Line Code

        This specifies the line coding for the interface.

        AMI or B8ZS (T1) or HDB3 (E1)

        B8ZS (T1)

        HDB3 (E1)

        Table 4: CESOP Payload Sizes

        Number of channels

        Allowed payload sizes

        1

        64

        2

        64,96,128,160,192,224,256

        3

        96,120,144,168,192,216

        4

        64,96,128,160,192,224,256

        5

        40,80,120,160,200,240,280,320

        6

        48,96,144,192,240,288,336

        7

        56,112,168,224,280,336

        8

        64,128,192,256,320

        9

        72,144,216,288

        10

        80,160,240,320

        11

        88,176,264,352

        12

        96,192,288

        13

        104,208,312

        14

        112,224,336

        15

        120,240

        16

        128,256

        17

        136,272

        18

        144,288

        19

        152,403

        20

        160,320

        21

        168,336

        22

        176,352

        23

        184

        24

        192

        25

        200

        26

        208

        27

        216

        28

        224

        29

        232

        30

        240

        31

        248

    5. Repeat 4 for Interface Z.

      Note: Unlike the BTI800 Series CLI, you do not need to enter the destination MAC address. PSM automatically determines the MAC address at both ends of the service.

    6. Select the Ethernet Service to use from the pulldown menu.

      Only the Ethernet services that include the UNIs at both ends are shown.

    7. Specify the CVLAN to use for the service. This is the CVLAN that exists between the pseudowire endpoint and the Ethernet UNI.

      The same CVLAN is used at both endpoints. The value itself is not important but it must be unique at each UNI.

    8. Click Activate. The service is activated.

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

    Modified: 2017-11-07