Cisco Active Network Abstraction Network Service Activation 1.2 User Guide, 3.7.2 - Activating Network Services [Cisco Active Network Abstraction]

Table Of Contents

Activating Network Services

E-LAN Activations

E-LAN VPLS Hub

E-LAN VPLS Hub Service Inputs

Create the E-LAN VPLS Hub Service

E-LAN VPLS Neighbor

E-LAN VPLS Neighbor Inputs

Create an E-LAN VPLS Neighbor Service

E-LAN H-VPLS Hub Neighbor

E-LAN H-VPLS Hub Neighbor Inputs

Create an E-LAN H-VPLS Hub Neighbor Service

E-LAN H-VPLS Spoke

E-LAN H-VPLS Spoke Inputs

Create an E-LAN H-VPLS Spoke

E-Line Service Activations

E-Line Point-to-Point Service

E-Line Point-to-Point Service Inputs

Create an E-Line Point-to-Point Service

E-Line Local Connect Service

E-Line Local Connect Service Inputs

Create an E-Line Local Connect Service

Activate Access

Activate Access on UNI and NNI Interfaces Inputs

Activate Access on UNI and NNI Interfaces

Layer 3 VPN

Layer 3 VPN Inputs

Create a Layer 3 VPN

MToP Service Activations

MToP ATM Pseudowire

MToP ATM Pseudowire Service Inputs

Create a MToP ATM Pseudowire Service

MToP TDM Clock Pseudowire

MToP TDM Clock Pseudowire Inputs

Create a MToP TDM Clocking Pseudowire

MToP TDM Pseudowire

MToP TDM Pseudowire Inputs

Create a MToP TDM Pseudowire

MToP Clocking Synchronization

MToP Clock Synchronization Inputs

Create a MToP Clock Synchronization

HSI Service Activations

HSI Point to Multipoint Inputs

Create an HSI Point to Multipoint Activation

Ethernet Flow Point

Multipoint EFP Inputs

Create an Ethernet Flow Point

Policy Activations

Layer 2 Access Control List

Layer 2 ACL Inputs

Create a Layer 2 ACL

QoS Policy

QoS Policy Inputs

Create a QoS Policy

Add MAC Secure Addresses

Add MAC Secure Addresses Inputs

Add MAC Secure Addresses

Activating Network Services

This chapter describes how Cisco ANA NSA allows you to activate Carrier Ethernet services and create policies using wizards launched from the Cisco ANA NetworkVision Activation menu. The topics tell you how to activate the services and policies, and how to manage the service activation jobs after you submit them. Topics include:

•E-LAN Activations

•E-Line Service Activations

•Activate Access

•Layer 3 VPN

•MToP Service Activations

•HSI Service Activations

•Ethernet Flow Point

•Policy Activations

Note Activation descriptions and procedures described in these topics are based on the wizards and workflows provided with the Cisco ANA NSA 1.2 package. To perform activations in Cisco ANA NSA, you must have privileges equal to or higher than Operator level.

Cisco ANA NSA wizards and workflows can be customized. If the packaged wizards and workflows are customized, the descriptions and procedures contained in these topics might not apply. To perform custiomizations in Cisco ANA NSA, you must have privileges equal to or higher than Administrator level. For information about customizing Cisco ANA NSA wizards and workflows, see the Cisco Active Network Abstraction Network Service Activation 1.2 Customization Guide.

Note Cisco ANA NSA does not support service modifications. Provisioning another service on a resource already used by another service could result in modification of the first service if errors occur in the second service and it is rolled back. This does not occur in all cases and is typical only in complex scenarios.

Note Data entered in Cisco ANA NSA wizard screens are only saved when you click Next. Data entered in a wizard screen will be lost if you return to a previous screen without clicking Next first.

Note Time stamping must be disabled on devices where you plan to run Cisco ANA NSA service activations. By default, time stamping is disabled on IOS devices, and enabled for Cisco IOS XR devices.

After you select a service and provide the initial input parameters for the activation of the selected service, we recommend that you complete performing the selected service.

Note If you enter the initial input parameters for a service activation and navigate from the input screen to another window, you will lose the information you entered.

E-LAN Activations

The following sections provide descriptions, inputs, and procedures for completing the Cisco ANA NSA E-LAN service activations:

•E-LAN VPLS Hub

•E-LAN VPLS Neighbor

•E-LAN H-VPLS Hub Neighbor

•E-LAN H-VPLS Spoke

Note If E-LAN wizards and workflows have been customized, descriptions, and procedures contained in these topics might not apply.

E-LAN VPLS Hub

You can create an E-LAN VPLS hub using Flex-UNI access points (see Figure 3-1). This service activation allows you to configure each of the following:

•Ethernet flow point (EFP)

•VLAN matching commands

•VLAN ID push, pop, and translate commands

•Bridge domain

•Virtual forwarding instance (VFI) creation

•Connection between the VFI and the bridge domain

The E-LAN VPLS hub service can be provisioned on the following devices:

•Cisco ASR 9000 Series

•Cisco 7600 Series

Note Verify that time stamping is disabled on devices where you plan to run the E-LAN VPLS hub service activation.

E-LAN VPLS hub wizard sequence:

•Create the VFI and apply a no shutdown command to it. For Cisco 7600 Series, optionally enable IGMP snooping on the VFI.

•Create a neighbor pseudowire with or without split horizon. Inline MPLS encapsulation is used for Cisco 7600 pseudowires. Inline MPLS encapsulation is optional for Cisco ASR 9000 Series Routers.

•Create a bridge domain for Cisco 7600 Series Switches/Routers, Create a bridge group and bridge domain for Cisco ASR 9000 series routers, Apply the no shutdown command on the bridge domain.

•Create one EFP on a UNI for each hub device. See the Ethernet Flow Point.

Note For an VPLS technology overview, see VPLS and H-VPLS, page 2-3.

Figure 3-1 Activation of an E-LAN VPLS Hub

E-LAN VPLS Hub Service Inputs

Table 3-1 lists the inputs you need to activate E-LAN VPLS hubs. An X in the Required column indicates the attribute is required. However, whether an attribute is available for provisioning depends on the provisioning of other attributes. In addition, not all devices support all attributes. If a device does not support an attribute, it is not available for provisioning. See the device user documentation to determine the attributes supported by a specific Cisco device platform and Cisco IOS release.

Table 3-1 E-LAN VPLS Hub Activation Inputs

User Input

Required

Description

First Add Multiple E-LAN Hubs Screen

Device

X

The device you want to provision as an E-LAN VPLS hub.

Platform

The platform of the device selected in the Device field.

Local Peering IP

X

The local peering IP address.

UNI ID

X

The UNI identifier.

Customer ID

X

(Cisco 7600 only) The customer identifier.

EFP ID

X

The Ethernet flow point identifier.

Outer VLAN ID

The outer VLAN ID in QinQ implementations. The outer ID is assigned to S-VLANs. Valid outer VLAN ID entries include:

•" "(blank) or "any" to indicate any ID value is acceptable.

•A single VLAN ID (nnn).

•A list of VLAN IDs (nnn, nnn, nnn).

•A range of VLAN IDs (nnn-nnn).

•A combination of single, list, and range IDs, for example, (nnn, nnn, nnn-nnn).

Where nnn = valid VLAN ID.

If an inner VLAN ID is entered, some restrictions apply. See the Inner VLAN ID field for information.

Inner VLAN ID

The inner VLAN ID in QinQ implementations. The inner ID is assigned to CE-VLANs. Valid inner VLAN ID entries are the same as the outer VLAN IDs. You can enter "any", a single VLAN ID, a list of VLAN IDs, a range of VLAN IDs, or combination of single, list, and range VLAN IDs.

Inner VLAN ID restrictions include:

•Requires an outer VLAN ID.

•Is not valid with multiple outer VLAN IDs.

•Multiple inner VLAN IDs are only supported with a single outer VLAN ID.

VLAN ID Preservation

X

The VLAN ID process applied to VLAN IDs:

•None—No VLAN ID processing is applied.

•Pop—The VLAN ID is removed.

•Push—The VLAN ID is imposed on to the incoming frames.

•Translate—The VLAN ID is translated.

Pop Action

X

When VLAN ID Preservation is set to Pop, the pop action:

•None—No pop action is applied.

•1—Remove the outer VLAN ID.

•2—Remove both outer and inner VLAN IDs.

Push Outer VLAN ID

When VLAN ID Preservation is set to Push, specifies the outer (customer) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Push Inner VLAN ID

When VLAN ID Preservation is set to Push, specifies the inner (provider) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Translate Action

X

When VLAN ID Preservation is set to Translate, the translate action:

•None

•1-1

•1-2 (Cisco ASR 9000 series router only)

•2-1 (Cisco ASR 9000 series router only)

•2-2 (Cisco ASR 9000 series router only)

For option descriptions, see Table 3-2.

Translate Outer VLAN ID

X

When VLAN ID Preservation is set to Translate, specifies the outer (customer) VLAN IDs that will be translated.

Translate Inner VLAN ID

X

When VLAN ID Preservation is set to Translate, specifies the inner (provider) VLAN IDs that will be translated.

Bridge Group Name

X

(Cisco ASR 9000 series router only) The bridge group name.

Bridge Domain Name

X

(Cisco ASR 9000 series router only) The bridge group domain name.

VFI Name

X

The virtual forwarding instance name.

S-VLAN ID

X

(Cisco 7600 only) The service provider VLAN identifier.

PW Class Name

The pseudowire class name.

VC ID

X

The virtual circuit identifier. (Numeric only.)

Enable Split Horizon EFP

X

Indicates whether to enable split horizon at the EFP: True or False. Split horizon prevents a router from advertising a route back out the interface from which the route was learned.

Enable Split Horizon PW

X

Indicates whether to enable split horizon on the pseudowire: True or False.

Enable IGMP Snoop

X

(Cisco 7600 only) Internet Group Management Protocol; if enabled (True), provides the ability to send Layer 2 multicast frames from CPE to remote peer CPE.

Second Add Multiple E-LAN Hubs Screen

MAC Access List Name

(Cisco 7600 only) The MAC Access Control List (ACL) name.

Enable MAC Security

X

(Cisco 7600 only) Indicates whether or not the MAC security feature is enabled: True or False. If enabled, you can complete the Maximum Secure Addresses, Secure Aging Time, and Secure Violation Mode attributes to limit and control the EFP MAC addresses. Additionally, you can use the MAC Security Policy wizard to define specific MAC addresses to which the MAC security policies apply. For information, see Add MAC Secure Addresses.

Maximum Secure Addresses

If Enable MAC Security is set to True, sets the maximum number of addresses that can be stored in the EFP MAC address table.

Secure Aging Time

If Enable MAC Security is set to True, allows you to set the aging time of the addresses in the MAC address table to <n> minutes. By default, this affects only dynamically learned addresses.

Secure Violation Mode

If Enable MAC Security is set to True, allows you to define the MAC address violation behavior:

•None (Shutdown, default):

–The ingress frame is dropped.

–The service instance on which the offending frame arrived is shut down.

–The violation count is incremental, and the violating address is recorded for later CLI display.

–The event and the response are logged to the syslog.

•Restrict:

–The ingress frame is dropped.

–The violation count is incremental, and the violating address is recorded for display.

–The event and the response are logged to the syslog.

•Protect—The ingress frame is dropped.

Attach Bandwidth Profile

X

Indicates whether a bandwidth profile should be attached: True or False.

Direction

X

If Attach Bandwidth Profile is set to True, indicates the direction the policy should be applied:

•Ingress—The QoS policy is applied to ingress frames.

•Egress—The QoS policy is applied to egress frames.

•Both—The QoS policy is applied to both ingress and egress frames.

Ingress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Ingress or Both, indicates the bandwidth profile that should be applied to ingress frames.

Egress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Egress or Both, indicates the bandwidth profile that should be applied to egress frames.

Ingress Shared Bandwidth Profile Name

(Cisco ASR 9000 series router only.) If Attach Bandwidth Profile is set to True and Direction is set to Ingress or Both, indicates the shared bandwidth profile that should be applied to ingress frames.

Egress Shared Bandwidth Profile Name

(Cisco ASR 9000 only.) If Attach Bandwidth Profile is set to True and Direction is set to Egress or Both, indicates the shared bandwidth profile that should be applied to egress frames.

A summary of VLAN translation inputs are shown in Table 3-2.

Table 3-2 VLAN Translation Summary Table

Type

Match Outer ID

Match Inner ID

Translate Outer ID

Translate Inner ID

1:1

True

N/A

X

1:2

True

N/A

X

X

2:1

True

True

X

2:2

True

True

X

X

Create the E-LAN VPLS Hub Service

To create the E-LAN VPLS hub service:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the E-LAN VPLS hub service.

Step 2 From the Activation menu, choose Activation.

Step 3 Do one of the following:

•To provision a new activation, expand the Service > E-LAN trees, choose Create E-LAN VPLS Hub Service, and click Next.

•To provision a new activation using a completed one as a starting point, click Clone Activation, choose an E-LAN VPLS hub service activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Add Multiple E-LAN Hubs screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Create E-LAN VPLS Hub Add Multiple E-LAN Hubs screen, click Add or Edit (if you started the activation with an existing one and want to edit the existing attributes).

If you clicked Add, the following fields are populated:

•Device—Populated with the map view device based on the earliest alphabetic or numeric name or IP address.

•Platform—The platform of the device in the Device field.

Step 5 In the Device field, select a device from the drop-down list.

The Platform attribute is populated with the device platform, and the UNI ID is populated with the UNI identifiers provisioned on the device.

Step 6 Complete the remaining attributes, as they are available and required for your specific implementation. See Table 3-1 for descriptions.

•Local Peering IP

•UNI ID

•Customer ID

•EFP ID

•Outer VLAN ID

•Inner VLAN ID

•VLAN ID Preservation

•Pop Action

•Push Outer VLAN ID

•Push Inner VLAN ID

•Translate Inner VLAN ID

•Translate Outer VLAN ID

•Bridge Group Name

•Bridge Domain Name

•VFI Name

•S-VLAN ID

•PW Class Name

•VC ID

•Activate Bridge Domain

•Enable Split Horizon EFP

•Enable Split Horizon PW

•Enable IGMP Snoop

Step 7 Click Next, then complete the next group of VPLS hub attributes:

•MAC Access List Name.

•Enable MAC Security

•Maximum Secure Addresses

•Secure Aging Time

•Secure Violation Mode

•Attach Bandwidth Profile

•Direction

•Ingress Bandwidth Profile Name

•Egress Bandwidth Profile Name

•Ingress Shared Bandwidth Profile Name

•Egress Shared Bandwidth Profile Name

Step 8 Click Next.

Step 9 In the User Input Tab, review the E-LAN hub information by clicking Prev to review the device information, then click Finish to add the device to the list of E-LAN VPLS hubs that will be created.

The Add Multiple E-LAN VPLS Hubs screen appears with the device listed.

Step 10 If you want to add an additional E-LAN VPLS hub, complete Steps 4 through 9.

Repeat until all VPLS E-LAN hubs are added, then proceed with the next step.

Step 11 Click Next in the Add Multiple E-LAN Hubs screen.

Step 12 In the User Input Tab, review the E-LAN hub information by clicking Prev to review the devices that will be added.

Step 13 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 14 Click Finish to create the E-LAN VPLS hubs.

The activation is performed on the VPLS hubs indicated. The Run Activation screen communicates the status of the activation.

Step 15 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note After completing the E-LAN VPLS hub activation, you must create the EFPs. See Create an Ethernet Flow Point

Note For Cisco 7600 Series, the activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

E-LAN VPLS Neighbor

This wizard creates additional hubs to join an existing VPLS hub membership (see Figure 3-2). This service activation allows you to configure each of the following:

•EFP (Service instance)

•VLAN matching commands

•VLAN ID translation commands pop, no push, and translate

•Bridge domain

•VFI creation

•Connection between the VFI and the BD

The E-LAN VPLS hub service can be provisioned on the following devices:

•Cisco 7600 Series

•Cisco ASR 9000 Series Router

Note Verify that time stamping is disabled on devices where you plan to run the E-LAN VPLS neighbor activation.

E-LAN VPLS Neighbor wizard sequence:

•Add a neighbor to the existing hub with and without pseudowire split horizon.

Note For an VPLS technology overview, see VPLS and H-VPLS, page 2-3.

Figure 3-2 Activation of an E-LAN VPLS Neighbor

E-LAN VPLS Neighbor Inputs

Table 3-3 lists the inputs you need for activation of E-LAN VPLS neighbor. An X in the Required column indicates the attribute is required.

Table 3-3 E-LAN VPLS Neighbor Activation Inputs

User Input

Required

Description

Add E-LAN VPLS Neighbors Screen

Device

X

The device where the E-LAN begins.

Platform

X

The device platform.

VC ID

X

The device virtual circuit identifier. (Numeric only.)

Customer ID

X

(Cisco 7600 only) The customer identifier.

VFI Name

X

(Cisco ASR 9000 Series Routers only) The virtual forwarding instance name.

Bridge Group Name

X

(Cisco ASR 9000 Series Routers only) The bridge group name.

Bridge Domain Name

X

(Cisco ASR 9000 Series Routers only) The bridge domain name.

PW Class Name

X

(Cisco ASR 9000 Series Routers only) The pseudowire class name.

Add E-LAN VPLS Neighbors - IP Address Screen

Peer Device IP

X

The IP address of the peer device.

Enable Split Horizon PW

X

The IP address of the peer device.

Create an E-LAN VPLS Neighbor Service

To create the E-LAN VPLS neighbor service:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the E-LAN VPLS neighbor.

Step 2 From the Activation menu, choose Activation.

Step 3 Do one of the following:

•To provision a new activation, expand the Service > E-LAN trees, choose Create VPLS Neighbor and click Next.

•To provision a new activation using a completed activation as a starting point, click Clone Activation, choose an E-LAN VPLS neighbor activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Add Multiple E-LAN VPLS Neighbors - IP Address screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Add Multiple E-LAN VPLS Neighbors screen, do one of the following:

•To add a neighbor, click Add.

•To edit information you entered for an existing neighbor, select it and click Edit.

•To delete an existing neighbor, select it and click Delete.

If you clicked Add or Edit, the Add Multiple E-LAN VPLS Neighbors window appears with the hub attributes.

Step 5 In the Device field, choose a device from the drop-down list.

The Platform field is automatically populated based on the model of the device you selected.

Step 6 Complete the following VPLS neighbor attributes.

See Table 3-3 for descriptions. The attributes that appear depend on the device you selected in the Device field.

•VC ID

•Customer ID

•VFI Name

•Bridge Group Name

•Bridge Domain Name

•PW Class Name

Step 7 Click Next.

The Add E-LAN VPLS Neighbors - IP Address screen appears.

Step 8 Click Add.

Step 9 In the second Add e-LAN VPLS Neighbors - IP Address screen, complete the following attributes. See Table 3-3 for descriptions.

•Peer Device IP

•Enable Split Horizon PW

Step 10 Click Next.

Step 11 In the User Input Tab, review the E-LAN VPLS neighbor information by clicking Prev to review the device information, then click Finish to add the device to the list of E-LAN VPLS neighbors that will be created.

The Add Multiple E-LAN VPLS Neighbors screen appears with the first device listed.

Step 12 If you want to add an additional VPLS neighbor, complete Steps 4 through 11.

Repeat until all devices are added. After you have added all the devices, proceed with the next step.

Step 13 Click Next in the Add Multiple E-LAN VPLS Neighbors screen.

Step 14 In the User Input Tab, review the E-LAN VPLS neighbors information by clicking Prev to review the devices that will be added.

Step 15 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 16 Click Finish to create the E-LAN VPLS neighbors.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 17 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note For Cisco 7600 Series, the activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

E-LAN H-VPLS Hub Neighbor

You can create an E-LAN H-VPLS hub neighbor. This service activation allows you to configure each of the following:

•EFP (Service instance)

•VLAN matching commands

•VLAN ID translation commands pop, no push, and translate

•Bridge domain (BD)

•VFI creation

•Connection between the VFI and the BD

The E-LAN H-VPLS hub neighbor service can be provisioned on the Cisco 7600 Series routers.

Note Verify that time stamping is disabled on devices where you plan to run the E-LAN H-VPLS hub neighbor activation.

E-LAN H-VPLS hub neighbor wizard sequence:

•Create a spoke neighbor in the existing VFI with no split horizon. This VFI is usually created on the distribution node.

Note For an overview of H-VPLS technology, see VPLS and H-VPLS, page 2-3.

E-LAN H-VPLS Hub Neighbor Inputs

Table 3-4 lists the inputs you need for activation of E-LAN H-VPLS hub neighbor. An X in the Required column indicates the attribute is required.

Table 3-4 E-LAN H-VPLS Hub Activation Inputs

User Input

Required

Description

Add Multiple E-LAN H-VPLS Hub Neighbors Screen

Device

X

The device where the E-LAN begins.

Customer ID

X

The customer identifier.

HUB VC ID

X

The hub device virtual circuit identifier. (Numeric only.)

Neighbor VC ID

X

The neighbor device virtual circuit identifier. (Numeric only.)

Peer Device IP

X

Peer device IP address

Create an E-LAN H-VPLS Hub Neighbor Service

To create the E-LAN H-VPLS hub neighbor service:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the E-LAN H-VPLS hub neighbor service.

Step 2 From the Activation menu, choose Activation.

Step 3 Do one of the following:

•To provision a new activation, expand the Service > E-LAN trees, choose Create H-VPLS Hub Neighbor and click Next.

•To provision a new activation using a completed activation as a starting point, click Clone Activation, choose an E-LAN H-VPLS hub neighbor activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Add Multiple E-LAN H-VPLS Hub Neighbor screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Add Multiple E-LAN H-VPLS Hub Neighbors screen, do one of the following:

•To add a hub neighbor, click Add.

•To edit an existing hub neighbor, select it and click Edit.

•To delete an existing hub neighbor, select it and click Delete.

If you clicked Add or Edit, the Add Multiple E-LAN H-VPLS Hub Neighbors screen appears with the hub attributes.

Step 5 Complete the following E-LAN H-VPLS hub attributes. See Table 3-4 for descriptions.

•Device

•Customer ID

•Hub VC ID

•Neighbor VC ID

•Peer Device IP

Step 6 Click Next.

Step 7 In the User Input Tab, review the E-LAN H-VPLS hub information by clicking Prev to review the device information, then click Finish to add the device to the list of E-LAN H-VPLS hubs that will be created.

The Add Multiple E-LAN H-VPLS Hubs screen appears with the first device listed.

Step 8 If you want to add an additional E-LAN H-VPLS hubs, complete Steps 4 through 7.

Repeat until all devices are added. After you have added all the devices, proceed with the next step.

Step 9 Click Next in the Add Multiple E-LAN H-VPLS Hubs screen.

Step 10 In the User Input Tab, review the E-LAN H-VPLS hub information by clicking Prev to review the devices that will be added.

Step 11 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 12 Click Finish to create the E-LAN H-VPLS hubs.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 13 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note The activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

E-LAN H-VPLS Spoke

The E-LAN H-VPLS Spoke wizard adds a spoke connected to a H-VPLS network through EoMPLS tunnel. This wizard allows you to configure each of the following:

•EFP (Service instance)

•xConnect on the EFP or SVI on the spoke node

•Neighbor command on the VFI of the hub node

The E-LAN H-VPLS spoke service can be provisioned on the Cisco 7600 Series routers.

Note Verify that time stamping is disabled on devices where you plan to run the E-LAN H-VPLS spoke activation.

E-LAN H-VPLS Spoke wizard sequence:

•Create a spoke that is associated with a spoke neighbor in the VFI. This spoke is usually created on the aggregation node.

•Create an EFP on the UNI. See the Ethernet Flow Point

•If multipoint, create a bridge domain. (If single point, no bridge domain is created.) For multipoint, the multipoint EFP wizard (see Create an Ethernet Flow Point) can be used to create additional EFPs to join the same bridge domain.

Note For an H-VPLS technology overview, see VPLS and H-VPLS, page 2-3.

E-LAN H-VPLS Spoke Inputs

Table 3-5 lists the inputs you need for activation of E-LAN H-VPLS spoke. An X in the Required column indicates the attribute is required.

Table 3-5 E-LAN H-VPLS Spoke Activation Inputs

User Input

Required

Description

First Add Multiple E-LAN H-VPLS Spokes Screen

Device

X

The device where the E-LAN begins.

Platform

(Read only) This is automatically populated based on the selection in the Device field.

UNI ID

X

The user network interface identifier.

EFP ID

X

The Ethernet flow point identification

Outer VLAN ID

The outer VLAN ID in QinQ implementations. The outer ID is assigned to S-VLANs. Valid outer VLAN ID entries include:

•" " (blank) or "any" to indicate any ID value is acceptable.

•A single VLAN ID (nnn).

•A list of VLAN IDs (nnn, nnn, nnn).

•A range of VLAN IDs (nnn-nnn).

•A combination of single, list, and range IDs, for example, (nnn, nnn, nnn-nnn).

Where nnn = valid VLAN ID.

If an inner VLAN ID is entered, some restrictions apply. See the Inner VLAN ID field for information.

Inner VLAN ID

The inner VLAN ID in QinQ implementations. The inner ID is assigned to CE-VLANs. Valid inner VLAN ID entries are the same as the outer VLAN IDs. You can enter "any", a single VLAN ID, a list of VLAN IDs, a range of VLAN IDs, or combination of single, list, and range VLAN IDs.

Inner VLAN ID restrictions include:

•Requires an outer VLAN ID.

•Is not valid with multiple outer VLAN IDs.

•Multiple inner VLAN IDs are only supported with a single outer VLAN ID.

VLAN ID Preservation

X

The VLAN ID process applied to VLAN IDs:

•None—No VLAN ID processing is applied.

•Pop—The VLAN ID is removed.

•Push—The VLAN ID is imposed on to the incoming frames.

•Translate—The VLAN ID is translated.

Pop Action

X

When VLAN ID Preservation is set to Pop, the pop action:

•None—No pop action is applied.

•1—Remove the outer VLAN ID.

•2—Remove both outer and inner VLAN IDs.

Push Outer VLAN ID

Imposes (pushes) an outer VLAN ID onto the incoming frames that fulfill the match criteria.

Push Inner VLAN ID

Imposes (pushes) an inner VLAN ID onto the incoming frames that fulfill the match criteria.

Translate Outer VLAN ID

Outer VLAN ID translation attribute.

VC ID

X

The VC identifier. (Numeric only.)

Peer Device IP

X

The peer device IP address

X-Connect Location

The cross connect location: Service Instance or VLAN.

S-VLAN ID

If X-Connector Location is VLAN, the service provider VLAN identifier.

Enable Split Horizon

X

If X-Connector Location is VLAN, indicates whether to enable split horizon: True or False. Split horizon prevents a router from advertising a route back out the interface from which the route was learned.

Enable IGMP Snoop

X

If X-Connector Location is VLAN, the Internet Group Management Protocol; if enabled (True), provides the ability to send Layer 2 multicast frames from CPE to remote peer CPE.

Second Add Multiple E-LAN H-VPLS Spokes Screen

MAC Access List Name

The Access Control List name.

Enable MAC Security

X

Indicates whether or not the MAC security feature is enabled: True or False. If enabled, you can complete the Maximum Secure Addresses, Secure Aging Time, and Secure Violation Mode attributes to limit and control the VPLS spoke MAC address. Additionally, you can use the MAC Security Policy wizard to define specific MAC addresses to which the MAC security policies apply. For information, see Add MAC Secure Addresses.

Maximum Secure Addresses

If Enable MAC Security is set to True, sets the maximum number of addresses that can be stored in the VPLS spoke MAC address table.

Secure Aging Time

If Enable MAC Security is set to True, allows you to set the aging time of the addresses in the MAC address table to <n> minutes. By default, this affects only dynamically learned addresses.

Secure Violation Mode

If Enable MAC Security is set to True, allows you to define the MAC address violation behavior:

•None (Shutdown, default):

–The ingress frame is dropped.

–The service instance on which the offending frame arrived is shut down.

–The violation count is increased, and the violating address is recorded for later CLI display.

–The event and the response are logged to the syslog.

•Restrict:

–The ingress frame is dropped.

–The violation count is increased, and the violating address is recorded for display.

–The event and the response are logged to the syslog.

•Protect—The ingress frame is dropped.

Attach Bandwidth Profile

X

Indicates whether a bandwidth profile should be attached: True or False.

Direction

X

If Attach Bandwidth Profile is set to True, indicates the direction the policy should be applied:

•Ingress—The bandwidth profile is applied to ingress frames.

•Egress—The bandwidth profile is applied to egress frames.

•Both—The bandwidth profile is applied to both ingress and egress frames.

Ingress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Ingress or Both, indicates the bandwidth profile that should be applied to ingress frames.

Egress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Egress or Both, indicates the bandwidth profile that should be applied to egress frames.

Create an E-LAN H-VPLS Spoke

To create the E-LAN H-VPLS spoke:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the E-LAN VPLS spoke service.

Step 2 From the Activation menu, choose Activation.

Step 3 Do one of the following:

•To provision a new activation, expand the Service > E-LAN trees, choose Create H-VPLS Spoke and click Next.

•To provision a new activation using a completed activation as a starting point, click Clone Activation, choose an E-LAN H-VPLS spoke activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Add Multiple E-LAN H-VPLS Spokes screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Add Multiple E-LAN H-VPLS Spokes screen, do one of the following:

•To add a spoke, click Add.

•To edit an existing spoke, select it and click Edit.

•To delete an existing spoke, select it and click Delete.

If you clicked Add or Edit, the Add Multiple E-LAN H-VPLS Spokes screen appears with the spoke attributes.

Step 5 In the Device field, choose a device from the drop-down list.

Step 6 In the first Add Multiple E-LAN H-VPLS Spokes screen, enter the following attributes.

Not all attributes will appear, depending on your attribute selections. See Table 3-5 for descriptions.

•Device

•UNI ID

•EFP ID

•Outer VLAN ID

•Inner VLAN ID

•VLAN ID Preservation

•Push Outer VLAN ID

•Push Inner VLAN ID

•Translate VLAN ID

•VC ID

•Peer Device IP

•X-Connect Location

•S-VLAN ID

•Enable Split Horizon

•Enable IGMP Snoop

Step 7 Click Next.

Step 8 In the second Add Multiple E-LAN H-VPLS Spokes screen, enter the following attributes.

Not all attributes will appear, depending on your attribute selections. See Table 3-5 for descriptions.

•MAC Access List Name

•Enable MAC Security

•Maximum Secure Addresses

•Secure Aging Time

•Secure Violation Mode

•Attach Bandwidth Profile

•Direction

•Ingress Bandwidth Profile Name

•Egress Bandwidth Profile Name

Step 9 Click Next.

Step 10 In the User Input Tab, review the E-LAN H-VPLS spoke information by clicking Prev to review the device information, then click Finish to add the device to the list of E-LAN spokes that will be created.

The Add Multiple E-LAN Spokes screen appears with the first device listed.

Step 11 If you want to add an additional E-LAN spoke, complete Steps 4 through 10.

Repeat until all spokes are added. After you have added all the devices, proceed with the next step.

Step 12 Click Next in the Add Multiple E-LAN Spokes screen.

Step 13 In the User Input Tab, review the E-LAN spoke information by clicking Prev to review the devices that will be added.

Step 14 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 15 Click Finish to create the E-LAN spokes.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 16 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note The activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

E-Line Service Activations

E-Line service activations include:

•E-Line Point-to-Point Service

•E-Line Local Connect Service

E-Line Point-to-Point Service

You can create an E-Line point-to-point service (see Figure 3-3). This activation allows you to configure the following:

•Ethernet flow point (EFP).

•VLAN matching commands.

•VLAN ID push, pop, and translate commands.

•xConnect under EFP (service instance).

Note The service activation will roll back the activation commands if errors occur.

The E-Line point-to-point service can be provisioned on the following devices:

•Cisco ASR 9000 Series Routers

•Cisco 7600 Series

Note Verify that time stamping is disabled on devices where you plan to run the E-Line point-to-point service activation.

E-Line point-to-point activation wizard sequence:

•Create an EFP on the UNI with all-in-one, 1:N, or 1:1 matching.

•Allow VLAN ID manipulation options none, push, pop or translate:

–Push—Outer VLAN ID or inner VLAN and outer VLAN ID.

–Pop—Outer VLAN ID or both inner and outer VLAN ID.

–Translate—1-1 only for Cisco 7600; 1-1, 1-2, 2-1, 2-2 for Cisco ASR 9000 Series Router.

•Activate side A and B UNIs with no shutdown by default.

•Create a single pseudowire from point A to point Z. For Cisco ASR 9000s, the pseudowire class can be optionally created.

•Optionally attach a MAC ACL

•Optionally attach QoS policies with these options:

–Ingress, egress, or both ingress and egress.

–For Cisco ASR 9000, support shared policy attachment.

Note For an E-Line point-to-point technology overview, see E-Line Service, page 2-2.

Figure 3-3 Activation of a E-Line Point-to-Point Service

E-Line Point-to-Point Service Inputs

Table 3-6 lists the E-Line point-to-point service attributes as you will provision them in the E-Line Point to Point wizard. An X in the 7600 and ASR 9000 columns indicate whether the attribute is provisioned on a Cisco 7600 or Cisco ASR 9000 routers. An X in the Required column indicates the attribute is required.

Table 3-6 E-Line Point-to-Point Activation Service Inputs

Field Name

Cisco 7600

Cisco ASR 9000

Required

Description

First A Side and Z Side Screens

Device

X

X

X

The A-side (point where the E-Line begins) and Z-side (point where the E-Line ends) devices must be available in the Cisco ANA map.

Platform

X

X

X

Automatically populated

UNI ID

X

X

X

The A-side and Z-side user network interface (UNI)

EFP ID

X

X

X

The Ethernet flow point identification

Outer VLAN ID

X

X

The outer VLAN ID in QinQ implementations. The outer ID is assigned to S-VLANs. Valid outer VLAN ID entries include:

•" (blank)" or "any" to indicate any ID value is acceptable.

•A single VLAN ID (nnn).

•A list of VLAN IDs (nnn, nnn, nnn).

•A range of VLAN IDs (nnn-nnn).

•A combination of single, list, and range IDs, for example, (nnn, nnn, nnn-nnn).

Where nnn = valid VLAN ID.

If an inner VLAN ID is entered, some restrictions apply. See the Inner VLAN ID field for information.

Inner VLAN ID

X

X

The inner VLAN ID in QinQ implementations. The inner ID is assigned to CE-VLANs. Valid inner VLAN ID entries are the same as the outer VLAN IDs. You can enter "any", a single VLAN ID, a list of VLAN IDs, a range of VLAN IDs, or combination of single, list, and range VLAN IDs.

Inner VLAN ID restrictions include:

•Requires an outer VLAN ID.

•Is not valid with multiple outer VLAN IDs.

•Multiple inner VLAN IDs are only supported with a single outer VLAN ID.

VLAN ID Preservation

X

X

X

Sets the VLAN ID preservation.

•None—No VLAN operation is performed.

•Pop—The VLAN ID is removed.

•Push—The VLAN ID is pushed to the next interface.

•Translate—The VLAN ID is translated to a new ID.

Pop Action

X

X

X

When VLAN ID Preservation is set to Pop, the pop action:

•None—No pop action is applied.

•1—Remove the outer VLAN ID.

•2—Remove both outer and inner VLAN IDs.

Push Outer VLAN ID

X

X

When VLAN ID Preservation is set to Push, specifies the outer (customer) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Push Inner VLAN ID

X

X

When VLAN ID Preservation is set to Push, specifies the inner (service provider) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Translate Action

X

X

When VLAN ID Preservation is set to Translate, the Translate Action:

•None

•1-1

•1-2

•2-1

•2-2

For option descriptions, see Table 3-2.

Translate Outer VLAN ID

X

X

When VLAN ID Preservation is set to Translate, specifies the outer (customer) VLAN IDs that will be translated.

Translate Inner VLAN ID

X

When VLAN ID Preservation is set to Translate, specifies the inner (provider) VLAN IDs that will be translated.

VC ID

X

X

X

The virtual circuit identifier. (Numeric only.)

Pseudowire Class Name

X

X

The pseudowire tunnel class name.

Xconnect Group Name

X

X

The xconnect group name.

Xconnect Name

X

The xconnect name.

Second A Side and Z Side Screens

MAC Access List Name

X

X

If a Layer 2Access Control List is applied, the ACL name. The ACL should be created before completing this wizard. See Layer 2 Access Control List.

Attach Bandwidth Profile

X

X

X

Indicates whether a bandwidth profile should be attached: True or False. The bandwidth profile should be created before completing this wizard. See QoS Policy.

Direction

X

X

X

If Attach Bandwidth Profile is set to True, indicates the direction the policy should be applied:

•Ingress—The QoS policy is applied to ingress frames.

•Egress—The QoS policy is applied to egress frames.

•Both—The QoS policy is applied to both ingress and egress frames.

Ingress Bandwidth Profile Name

X

X

X

If Attach Bandwidth Profile is set to True and Direction is set to Ingress or Both, indicates the bandwidth profile that should be applied to ingress frames.

Egress Bandwidth Profile Name

X

X

X

If Attach Bandwidth Profile is set to True and Direction is set to Egress or Both, indicates the bandwidth profile that should be applied to egress frames.

Ingress Shared Bandwidth Profile Name

X

(Cisco ASR 9000 Series Router only.) If Attach Bandwidth Profile is set to True and Direction is set to Ingress or Both, indicates the shared bandwidth profile that should be applied to ingress frames.

Egress Shared Bandwidth Profile Name

X

(Cisco ASR 9000 only.) If Attach Bandwidth Profile is set to True and Direction is set to Egress or Both, indicates the shared bandwidth profile that should be applied to egress frames.

Peer Information Screen

A Peer IP Address

X

X

X

The A side peer IP address.

Z Peer IP Address

X

X

X

The Z side peer IP address.

Create an E-Line Point-to-Point Service

To create an E-Line point-to-point service:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the E-Line point-to-point service.

Step 2 From the Activation menu, choose Activation.

The Activation window appears with the activation tree.

Step 3 Do one of the following:

•To provision a new activation, expand the Service > E-Line trees, choose Create E-Line Point-to-Point Service, and click Next.

•To provision a new activation using a completed activation as a starting point, click Clone Activation, choose an E-Line point-to-point activation in the Service Activation List window, and click OK.

The completed activation data values appear in the A Side screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Create E-Line Point-to-Point Service A Side screen, complete (or edit) the following attributes. See Table 3-6 for input descriptions.

Input

Cisco 7600

Cisco ASR 9000

Device

X

X

Interface

X

X

EFP ID

X

X

Outer VLAN ID

X

X

Inner VLAN ID

X

X

VLAN ID Preservation

X

X

Pop Action

X

X

Push Outer VLAN ID

X

X

Push Inner VLAN ID

X

X

Translate Action

X

X

Translate Inner VLAN ID

X

Translate Outer VLAN ID

X

VC ID

X

X

Pseudowire Class Name

X

Xconnect Group Name

X

Xconnect Name

X

Step 5 Click Next.

Step 6 In the second A Side screen, complete (or edit) the remaining A Side attributes:

Input

Cisco 7600

Cisco ASR 9000

MAC Access List Name

X

X

Attach Bandwidth Profile

X

X

Direction

X

X

Ingress Bandwidth Profile Name

X

X

Egress Bandwidth Profile Name

X

X

Ingress Shared Bandwidth Profile Name

X

Egress Shared Bandwidth Profile Name

X

Step 7 Click Next.

Step 8 In the first Z Side screen, complete (or edit) the attributes for the E-Line end point.

These are the same attributes as the A side in Step 4.

Step 9 Click Next.

Step 10 In the second Z Side screen, complete (or edit) the remaining Z Side attributes.

These are the same attributes as the A side in Step 6.

Step 11 If you are provisioning the point-to-point service on a Cisco 7600 Router, complete the following steps. If not, continue with Step 12.

a. In the Peer Information screen, complete the following:

–A Peer IP Address

–Z Peer IP Address

b. Click Next.

Step 12 In theUser Input Tab, review the E-Line information by clicking Prev to review the A side, Z side, and peer IP information.

Step 13 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 14 Click Finish.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 15 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note For Cisco 7600 Series, the activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

E-Line Local Connect Service

You can create an E-Line local connect service where the two UNI endpoints of an E-Line service reside on the same aggregation network element (see Figure 3-4). You can provision the E-Line point-to-point service on:

•Cisco 7600 Series Switches/Routers

•Cisco ASR 9000 Series Routers.

Note Verify that time stamping is disabled on devices where you plan to run the E-Line local connect service activation.

E-Line local connect activation wizard sequence:

•Create an EFP on the UNI with all-in-one, 1:N, or 1:1 matching.

•Allow VLAN ID manipulation options none, push, pop or translate:

–Push—Outer VLAN ID or inner VLAN and outer VLAN ID.

–Pop—Outer VLAN ID or both inner and outer VLAN ID.

–Translate—1-1 only for Cisco 7600; 1-1, 1-2, 2-1, 2-2 for Cisco ASR 9000 Series Routers.

•Activate side A and B UNIs with no shutdown by default.

•Optionally attach a MAC ACL

•Optionally attach QoS policies with these options:

–Ingress, egress, or both ingress and egress.

–For Cisco ASR 9000 Series Routers, support shared policy attachment.

Note For an E-Line point-to-point technology overview, see E-Line Service, page 2-2.

Figure 3-4 Activation of a E-Line Local Connect Service

E-Line Local Connect Service Inputs

Table 3-7 lists the inputs you must have to complete the E-Line local connect service. An X in the Required column indicates the parameter is required.

Table 3-7 E-Line Local Connect Service Activation Inputs

Field Name

Required

Description

Local Connect Common Screen

Device

X

The A-side (point where the E-Line begins) and Z-side (point where the E-Line ends) devices must be available in the Cisco ANA map.

Platform

X

Automatically populated.

Service Order ID

X

(Cisco 7600 only) The service order identifier.

Xconnect Group Name

X

Cisco ASR 9000 only) The Xconnect group name.

Xconnect Name

X

Cisco ASR 9000 only) The Xconnect name.

First A Side and Z Side Screens

UNI ID

X

The A-side and Z-side UNI identifiers must be known.

EFP ID

X

The Ethernet flow point identifier.

Outer VLAN ID

The outer VLAN ID in QinQ implementations. The outer ID is assigned to S-VLANs. Valid outer VLAN ID entries include:

•"(blank)" or "any" to indicate any ID value is acceptable.

•A single VLAN ID (nnn).

•A list of VLAN IDs (nnn, nnn, nnn).

•A range of VLAN IDs (nnn-nnn).

•A combination of single, list, and range IDs, for example, (nnn, nnn, nnn-nnn).

Where nnn = valid VLAN ID.

If an inner VLAN ID is entered, some restrictions apply. See the Inner VLAN ID field for information.

Inner VLAN ID

The inner VLAN ID in QinQ implementations. The inner ID is assigned to CE-VLANs. Valid inner VLAN ID entries are the same as the outer VLAN IDs. You can enter " ", "any", a single VLAN ID, a list of VLAN IDs, a range of VLAN IDs, or combination of single, list, and range VLAN IDs.

Inner VLAN ID restrictions include:

•Requires an outer VLAN ID.

•Is not valid with multiple outer VLAN IDs.

•Multiple inner VLAN IDs are only supported with a single outer VLAN ID.

VLAN ID Preservation

Sets the VLAN ID Preservation.

•None—No VLAN operation is performed.

•Pop—The VLAN ID is removed.

•Push—The VLAN ID is pushed to the next interface.

•Translate—The VLAN ID is translated to a new ID.

Pop Action

X

When VLAN ID Preservation is set to Pop, the pop action:

•None—No pop action is applied.

•1—Remove the outer VLAN ID.

•2—Remove both outer and inner VLAN IDs.

Push Outer VLAN ID

When VLAN ID Preservation is set to Push, specifies the outer (customer) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Push Inner VLAN ID

When VLAN ID Preservation is set to Push, specifies the inner (provider) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Translate Outer VLAN ID

When VLAN ID Preservation is set to Translate, specifies the outer (customer) VLAN IDs that will be translated.

Second A Side and Z Side Screens

MAC Access List Name

If a Layer 2Access Control List is applied, the ACL name. The ACL should be created before completing this wizard. See Layer 2 Access Control List.

Attach Bandwidth Profile

X

Indicates whether a QoS policy should be attached: True or False. The QoS policy should be created before completing this wizard. See QoS Policy.

Direction

X

If Attach Bandwidth Profile is set to True, indicates the direction the policy should be applied:

•Ingress—The QoS policy is applied to ingress frames.

•Egress—The QoS policy is applied to egress frames.

•Both—The QoS policy is applied to both ingress and egress frames.

Ingress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Ingress or Both, indicates the bandwidth profile that should be applied to ingress frames.

Egress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Egress or Both, indicates the bandwidth profile that should be applied to egress frames.

To verify that the service activation executed successfully, or to troubleshoot any aspect of its execution, see Viewing Service Activation Results, page 4-1.

Create an E-Line Local Connect Service

To create the E-Line local connect service:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the E-Line point-to-point service.

Step 2 From the Activation menu, choose Activation Wizard.

Step 3 Do one of the following:

•To provision a new activation, expand the Service > E-Line trees, choose Create E-Line Local Connect Service, and click Next.

•To provision a new activation using a completed one as a starting point, click Clone Activation, choose an E-Line local connect activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Local Connect Common screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Local Connect Common screen, complete (or edit) the following. See Table 3-7 for descriptions.

Input

Cisco 7600

Cisco ASR 9000

Device

X

X

Service Order ID

X

X

Xconnect Group Name

X

X

Xconnect Name

X

X

Step 5 Click Next.

Step 6 In the first A Side screen, complete (or edit) the following:

Input

Cisco 7600

Cisco ASR 9000

UNI ID

X

X

EFP ID

X

X

Outer VLAN ID

X

X

Inner VLAN ID

X

X

VLAN ID Preservation

X

X

Pop Action

X

X

Push Outer VLAN ID

X

X

Push Inner VLAN ID

X

X

Translate Inner VLAN ID

X

X

Step 7 Click Next.

Step 8 In the Second A Side screen complete (or edit) the following:

Input

Cisco 7600

Cisco ASR 9000

MAC Access List Name

X

Attach Bandwidth Profile

X

X

Direction

X

X

Ingress Bandwidth Profile Name

X

X

Egress Bandwidth Profile Name

X

X

Ingress Shared Bandwidth Profile Name

X

Egress Shared Bandwidth Profile Name

X

Step 9 Click Next.

Step 10 In the first Z Side screen, complete the E-Line attributes.

These are the same attributes as Step 6.

Step 11 Click Next.

Step 12 In the Second Z Side screen complete (or edit) the remaining Z side attributes.

These are the same attributes as Step 8.

Step 13 Click Next.

Step 14 In the User Input Tab, review the E-Line local connect information by clicking Prev to review the A side, Z side, and common attributes.

Step 15 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 16 Click Finish.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 17 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note For Cisco 7600 Series, the activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

Activate Access

The Activate Access wizard configures IEEE 802.1q tunneling on access devices, including user network interfaces (UNIs) and network-to-network interfaces (NNIs). Using 802.1Q tunneling (QinQ), service providers can use a single VLAN to support customers who have multiple VLANs. Customer VLAN IDs (C-VLANs) are preserved, and traffic from different customers is segregated within the service provider network, even when they appear to be in the same VLAN. 802.1Q tunneling expands a VLAN space by using a VLAN-in-VLAN hierarchy and retagging the tagged packets. A port configured to support 802.1Q tunneling is called a tunnel port. When you configure tunneling, you assign a tunnel port to a VLAN ID that is dedicated to tunneling.

Note QinQ applies only to UNIs on Cisco 3400E Series switches.

The Create Access wizard can be performed on the following devices:

•Cisco ME 3400 Series Switches

•Cisco 3750 Series Switches

•Cisco 4500 Series Switches

Note Verify that time stamping is disabled on devices where you plan to run the activate access wizard.

Activate Access wizard sequence:

•UNI side:

–UNI side (Cisco 4500/3750/3400 devices)—Create switch port as access mode with one VLAN.

–UNI side (Cisco ME 3400 E switches—Users have options to configure selective QinQ. The switch port is set to trunk mode. Multiple VLANs can be set. If selected QinQ is not configured, switch port is set to access mode with one VLAN.

•NNS side:

–Create a trunk port with one or more VLANs.

–Optionally configure the switch port. If configure switch port is set to true, the existing VLANs, if any, are overridden. If configure switch port is set to false, a new set of VLANs are added to the trunk port. Because no switch port setting exists, adding new VLANs to an existing switch port might fail.

Activate Access on UNI and NNI Interfaces Inputs

Table 3-8 lists the inputs you need to activate a UNI or NNI on the access device. An X in the Required column indicates the parameter is required.

Table 3-8 UNI Interface Access Activation Inputs

User Input

Required

Description

Activate Access on UNI Interfaces Screen

UNI Device

X

The device with UNI interface you want to activate.

UNI Interface

X

The UNI interface.

UNI Interface Mode

X

The UNI interface mode you want to use-Trunk, Access.

Configure Switch Port

X

Configures the switch port, True or False. When you select True, the existing VLAN is removed from the UNI interface and a new VLAN is configured.When you select False, no new VLAN is configured in the switch port.

Caution If Configure Switch Port is set to True, all previously configured UNIs on the port are destroyed.

UNI SVLAN ID

X

The UNI SVLAN identifier (numeric only).

Add Selected QinQ

X

(Cisco ME 3400E only) Indicates whether QinQ will be provisioned, Yes or No.

CE VLAN Tag

X

The CE VLAN tag.

Default Mapping

X

(Cisco ME 3400E only) Indicates whether or not default mapping will be used, True or False.

Activate Access on NNI Interfaces Screen

NNI Device

X

The device with the NNI interface you want to activate.

NNI Interface

X

The NNI interface.

NNI VLAN IDS

X

The NNI VLAN identifier. The ID can be a single VLAN ID or a range, for example, 1-2 or 5-100.

Configure Switch Port

X

Configures the switch port. When configuring the first NNI on an interface, set to True. If an NNI has been previously configured on the interface, set to False.

Caution If Configure Switch Port is set to True, all previously configured NNIs on the port are destroyed.

Activate Access on UNI and NNI Interfaces

To activate UNIs and NNIs on an access device:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create access.

Step 2 From the Activation menu, choose Activation.

Step 3 Do one of the following:

•To provision a new activation, expand the Service > Access trees, choose Create Access and click Next.

•To provision a new activation using a completed one as a starting point, click Clone Activation, choose an access activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Activate Access on UNI Interfaces screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Activate Access on UNI Interfaces screen, do one of the following:

•To add a UNI interface, click Add.

•To edit an existing UNI interface, select it and click Edit.

•To delete an existing UNI interface, select it and click Delete.

If you clicked Add or Edit, the Activate Access on UNI Interfaces window appears with the UNI interface attributes.

Step 5 In the Select UNI Device field, choose a device from the drop-down list.

The UNI Interface field is populated based on the device selection.

Step 6 Complete the remaining attributes, as appropriate. See Table 3-8 for descriptions.

•Device

•Platform

•UNI Interface

•Add Selected QinQ

•CE VLAN ID

•Default Mapping

•UNI Interface Mode

•UNI SVLAN ID

•Configure Switch Mode

Step 7 Click Next.

Step 8 In the User Input Tab, review the UNI interface information by clicking Prev to review the device information, click Finish to add the device to the list of UNI accesses that will be created.

The Activate Access on UNI Interfaces screen appears with the first interface listed.

Step 9 If you want to add an additional access to UNI interfaces, complete Steps 4 through 8.

Repeat until all UNI interfaces are added. After you have added all the interfaces, proceed with the next step.

Step 10 Click Next in the Activate Access on UNI Interfaces screen.

Note You can either continue to activate access on the NNI Interface or click Next to procced with the UNI interface you added. To activate access on NNI Interface, complete Steps 11 through 15.

Step 11 In the Activate Access on NNI Interfaces screen, do one of the following:

•To add a NNI interface, click Add.

•To edit an existing NNI interface, select it and click Edit.

•To delete an existing NNI interface, select it and click Delete.

If you clicked Add or Edit, the Activate Access on NNI Interfaces window appears with the NNI interface attributes.

Step 12 In the Select NNI Device field, choose a device from the drop-down list.

The NNI Interface field is populated based on the device selection.

Step 13 Complete the remaining attributes. See Table 3-8 for descriptions.

•NNI Interface

•NNI VLAN ID

•Configure Switch Port

Step 14 Click Next.

Step 15 In the User Input Tab, review the NNI interface information by clicking Prev to review the device information, then click Finish to add the device to the list of NNI accesses that will be created.

The Activate Access on NNI Interfaces screen appears with the first interface listed.

Step 16 If you want to add an additional access to NNI interfaces, complete Steps 11 through 15.

Repeat until all NNI interfaces are added. After you have added all the interfaces, proceed with the next step.

Step 17 Click Next in the Activate Access on NNI Interfaces screen.

Step 18 In the User Input Tab, review the NNI interface information by clicking Prev to review the devices and interfaces that will be added.

Step 19 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 20 Click Finish to create NNI interface access.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation and displays the details of the activation in a CLI interface.

Step 21 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note If you deactivate the access service (see Deactivating a Service, page 4-6), the access service deactivation will completely remove the UNIs but only partially remove the NNIs. The deactivation will only remove the relevant VLAN IDs and leave other VLAN IDs configured on the NNI interface in place.

Note The activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

Layer 3 VPN

The Layer 3 VPN wizard configures (see Figure 3-5) VPN Routing and Forwarding instances (VRFS) on a PE router. The wizard assumes that BGP is already configured on PE and CE routers. The Layer 3 VPN wizard also configures VRF interfaces on PE routers for each VPN customers and configures PE-to-CE routing sessions using BGP.

This activation wizard allows you to configure each of the following:

•L3 VPN on PE

•VRF (create/remove)

•Route target (add/remove)

•VRF forwarding (add/remove to subinterface, VLAN interface)

•BGP (including add/remove neighbor)

The Layer 3 VPN can be provisioned on the following devices:

•Cisco 7600 Series

•Cisco ASR 9000 Series Routers

•Cisco ME 3600X Ethernet Access Switches and Cisco ME 3800X Carrier Ethernet Switch Routers

Note Verify that time stamping is disabled on devices where you plan to provision the Layer 3 VPN.

Figure 3-5 Layer 3 VPN

Layer 3 VPN Inputs

Table 3-9 lists the inputs you need for activation of a Layer 3 VPN. An X in the Required column indicates the parameter is required.

Table 3-9 Layer 3 VPN Inputs

User Input

Required

Description

Add L3 VPN Sites Screen

Device

X

The device where you want to create the Layer 3 VPN.

Platform

X

The device platform, for example 7600 for Cisco 7600 Series Router. (This field cannot be changed.)

VRF Name

X

The VRF name.

Route Distinguisher

X

The route distinguisher; entered in one of two formats:

•as-number:number, where as-number is an AS number (a 2-byte value) and number is any 4-byte value. The AS number can be in the range 1 through 65,535.

•ip-address:number, where ip-address is an IP address (a 4-byte value) and number is any 2-byte value. The IP address can be any globally unique unicast address.

Max Routes

The maximum number of routes (Cisco 7600, Cisco ME 3600X Ethernet Access Switches, Cisco ME 3800X Carrier Ethernet Switch Routers only).

Max Routes Threshold

The percentage of capacity filled before threshold crossing alerts are generated. (Cisco 7600, Cisco ME 3600X Ethernet Access Switches, Cisco ME 3800X Carrier Ethernet Switch Routers)

Max Prefix

The maximum number of route prefixes (Cisco ASR 9000 only).

Max Prefix Threshold

The maximum route prefix threshold (Cisco ASR 9000 only).

Route Target

The route target. Route targets define the VRFs that will be exported or imported. Format is the same as the route distinguisher.

Route Target Type

Indicates the route target action. Options:

•Cisco 7600 Series Switches/Routers—Export, Import, Both, None.

•Cisco ASR 9000 Series Router—Export, Import, None.

•Cisco ME 3600X Ethernet Access Switches, Cisco ME 3800X Carrier Ethernet Switch Routers—Export, Import, Both, None.

Add L3 VPN Sites - Interface Screen

VRF Location

X

The location of the VRF. Options:

•Cisco 7600 Series Switches/Routers—VLAN interface or Subinterface.

•Cisco ASR 9000—Interface or Subinterface.

•Cisco ME 3600X Ethernet Access Switches, Cisco ME 3800X Carrier Ethernet Switch Routers -VLAN Interface

Interface Name

The interface, VLAN interface, or subinterface name.

VLAN ID

X

The VLAN identifier.

IP Address

X

The interface, VLAN interface, or subinterface IP address.

Subnet Mask

X

The interface, VLAN interface, or subinterface IP address subnet mask.

Activate Interface

X

Indicates whether or not inactive interfaces should be activated, true or false.

Add L3 VPN Sites - BGP

AS Number

The BGP AS number (read only).

Configure BGP Neighbor

X

Indicates whether you want to configure a BGP neighbor: True or False.

Peer Device IP

X

The peer device IP address.

Remote AS

X

The remote AS number.

AS Occurrences.

X

The number of AS occurrences.

Redistribute Connected

Redistribute directly-connected networks into the VRF BGP table: True or False.

Redistribute Static

Redistribute static routes into the VRF BGP table: True or False.

Add L3 VPN Sites - Additional Route Targets to Same Devices/VRFs

Configure Additional RT

X

Indicates whether or not an additional route target will be configured: True or False

Device

X

The device where the additional route target will be configured.

VRF Name

X

The VRF name.

Route Target

The route target. Route targets define the VRFs that will be exported or imported. Format is the same as the route distinguisher.

Route Target Type

Indicates the route target action: Export, Import, or Both.

To verify that the script deployed successfully, or to troubleshoot any aspect of its execution, see Viewing Service Activation Results, page 4-1.

Create a Layer 3 VPN

To create a Layer 3 VPN:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the Layer 3 VPN.

Step 2 From the Activation menu, choose Activation.

Step 3 Do one of the following:

•To provision a new activation, expand the L3 VPN tree, expand the L3VPN tree, choose Create Layer 3 VPN Service and click Next.

•To provision a new activation using a completed one as a starting point, click Clone Activation, choose a Layer 3 VPN activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Add L3 VPN Sites screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Add L3 VPN Sites screen, do one of the following:

•To add a Layer 3 VPN, click Add.

•To edit an existing Layer 3 VPN, select it and click Edit.

•To delete an existing Layer 3 VPN, select it and click Delete.

If you clicked Add or Edit, the Add L3 VPN Sites window appears. If you clicked Edit, the VPN attribute fields are populated.

Step 5 In the Add L3 VPN Sites screen, choose a device from the drop-down list.

The Platform field is automatically populated based on the selected device.

Step 6 Complete the remaining attributes. See Table 3-9 for descriptions.

•VRF Name

•Route Distinguisher

•Max Routes (Cisco 7600, Cisco ME 3600X Ethernet Access Switches, Cisco ME 3800X Carrier Ethernet Switch Routers)

•Max Routes Threshold (Cisco 7600, Cisco ME 3600X Ethernet Access Switches, Cisco ME 3800X Carrier Ethernet Switch Routers)

•Max Prefix (Cisco ASR 9000)

•Max Prefix Threshold (Cisco ASR 9000)

•Route Target

•Route Target Type

Step 7 Click Next.

Step 8 In the Add L3 VPN Sites - Interface screen, enter the interface attributes. See Table 3-9 for descriptions.

•VRF Location

•Interface Name

•VLAN ID

•IP Address

•Subnet Mask

•Activate Interface

Step 9 In the Add L3 VPN Sites - BGP screen, Configure BGP Neighbor field, choose True if you will provision a BGP neighbor on the site, or False if a BGP neighbor will not be provisioned.

Step 10 If you are provisioning BGP, complete the following BGP attributes.

See Table 3-9 for descriptions. If are not provisioning BGP, continue with Step 11.

•Peer Device IP

•Remote AS

•AS Occurrences.

•Redistribute Connected

•Redistribute Static

Step 11 In the User Input Tab, review the Layer 3 VPN site information by clicking Prev to review the information, click Finish to add the site to the list of sites that will be added to the VPN.

The Add L3 VPN Sites screen appears with the first site displayed.

Step 12 If you want to add an additional sites to the VPN, complete Steps 4 through 11.

Repeat until all the sites are added. After you have added all the devices, proceed with the next step.

Step 13 Click Next in the Add L3 VPN screen.

Step 14 In the User Input Tab, review the VPN information by clicking Prev to review the devices that will be added, then click Finish.

Step 15 In the Add L3 VPN Sites - Additional Route Targets to Same Devices/VRFs screen, do one of the following:

•To add additional route targets, click Add.

•To edit an existing route target, select it and click Edit.

•To delete an existing route target, select it and click Delete.

If you clicked Add or Edit, a Add L3 VPN Sites - Additional Route Targets to Same Devices/VRFs window appears. If you clicked Edit, the route target attribute fields are populated.

Step 16 In the Add L3 VPN Sites - Additional Route Targets to Same Devices/VRFs screen, complete the following fields:

•Configure Extra RT—Choose True.

•Device—Choose the device where you want to provision the additional RTs.

•VRF Name—Enter the VRF name.

•Route Target—Enter the route target.

•Route Target Type—Choose the RT type.

Step 17 Click Next.

Step 18 In the additional route target data validation screen, review the route target data. If you want to edit it, click Prev. When finished, click Finish.

Step 19 In the Add L3 VPN Sites - Additional Route Targets to Same Devices/VRFs screen, repeat Step 15 if you want to add or edit route targets. If not, click Next.

Step 20 In the User Input Tab, review the VPN information by clicking Prev to review the devices that will be added.

Step 21 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 22 Click Finish.

The Layer 3 VPN is added to the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 23 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note After completing the Layer 3 VPN, you must create the EFPs. See Create an Ethernet Flow Point

Note For Cisco 7600 Series, Cisco ME 3600X Ethernet Access Switches and Cisco ME 3800X Carrier Ethernet Switch Routers, the activation is added to the device running the configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

MToP Service Activations

MToP service activations include:

•MToP ATM Pseudowire

•MToP TDM Clock Pseudowire

•MToP TDM Pseudowire

•MToP Clock Synchronization Inputs

MToP ATM Pseudowire

The MToP Create ATM Pseudowire wizard creates ATM over MPLS pseudowires and ATM IMA over MPLS pseudowires, as shown in Figure 3-6.

Figure 3-6 ATM over MPLS Pseudowire

The pseudowires can be provisioned on ATM Permanent Virtual Paths (PVPs) and Permanent Virtual Circuits (PVCs). Supported ATM interfaces include:

•ATM interfaces on T1 and E1.

•IMA ATM interfaces

•Point-to-point subinterfaces

•ATM interfaces on SONET controllers

The MToP Create ATM Pseudowire wizard allows you to configure each of the following:

•MPLS label range

•MCPT timers on ATM Interface

•xConnect on ATM Interface using PVC (IMA and non-IMA)

•xConnect on ATM Interface using PVP (IMA and non-IMA)

The script will roll back the activation commands when there are errors.

The MToP ATM pseudowire can be provisioned on the following devices:

•Cisco 7600 Series Routers

•Cisco Catalyst 2900 Series Switches

•Cisco ASR 9000 (multi-segment support only)

Note Verify that time stamping is disabled on devices where you plan to provision the ATM pseudowire.

Note The Create MToP ATM Pseudowire Service wizard does not provision the device controllers. You must provision the controllers before starting this wizard. To provision T1 or E1 controllers on the Cisco 2900, see the Cisco MWR 2941-DC Mobile Wireless Edge Router Software Configuration Guide. To provision T1, E1, or SONET controllers on the Cisco 7600, see the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide.

MToP ATM Pseudowire Service Inputs

Table 3-10 lists the inputs you need for activation of an MToP ATM pseudowire service. An X in the Required column indicates the parameter is required.

Note Before you begin the ATM pseudowire service activation, interface staging for point-to-point activation must be completed. Point-to-point interface staging means creating subinterfaces under an ATM interface with point-to-point option such as: Interface ATM7/0/1.1 point-to-point.)

Table 3-10 MToP ATM Pseudowire Service Inputs

User Input

Required

Description

ATM Pseudowire Attributes Screen

Speed

X

The pseudowire speed, either E1 or T1.

Point to Point

X

Indicates whether or not the pseudowire is point-to-point: True or False.

Note If you select the point-to-point option, you can only use the point-to-point sub-interfaces; unless the interface is a Cisco 7600 IMA.

Xconnect Location

X

The ATM xconnect location, either PVC (Permanent Virtual Circuit) or PVP. (Permanent Virtual Path)

VC ID

X

The virtual circuit identifier. (Numeric only.)

MCPT Timer ID

X

The maximum cell packing timeouts (MCPT) timer identifier. This timer controls how long the PE router waits for ATM cells on the AC before packing them into an MPLS packet and transmitting across the backbone.

Note An MCPT timer ID can be configured on a point-to-point PVC or PVP. To do this, set the MCPT Timer values on the major interface. This should be completed first. Then create a point-to-point PVC or PVP using subinterfaces that are on the major interface and enter the MCPT Timer ID.

Cells Per Packet

X

If MCPT Timer ID is set to 1, 2, or 3., indicates the number of cells that are carried in each MPLS packet.

Configure Backup PW

X

Indicates whether or not a backup pseudowire is to be configured: True or False

Backup Tunnel ID

X

If Configure Backup PW is True, the backup tunnel identifier.

ATM Pseudowire Side A and Side B Screens

Device

X

The U-PE and N-PE device where the pseudowire is provisioned.

Platform

The device platform. This attribute is automatically populated after a device is chosen

IP Address

The U-PE and N-PE device IP address. This attribute is automatically populated after a device is chosen

Controller Type

X

The controller type: E1, T1 (Cisco 2900 only), or SONET (OC-3; Cisco 7600 only).

Interface Type

X

The interface type: Regular, IMA (Inverse Multiplexing for ATM), or Physical.

Note Cisco ANA NSA does not support point-to-point configurations on Cisco 7600 IMA interfaces.

ATM Logical Interface Name

X

The name of the ATM logical interface.

ATM Regular Interface Name

X

The name of the ATM regular interface.

ATM Sub-Interface Number

X

If Point to Point is True, the ATM subinterface number.

PVC ID

X

If the Xconnect Location is permanent virtual circuit (PVC), the PVC identifier.

PVP ID

X

If the Xconnect Location is permanent virtual path (PVP), the PVP identifier. (Numeric only.)

IMA Version

X

If Interface Type is IMA, the IMA version, either 1.0 or 1.1.

IMA Group ID

If Interface Type is IMA, the IMA group identifier.

Static Label

X

Indicates whether or not the static label is enabled: Enabled or Disabled.

Local PW Label

X

(Cisco 7600 only.) The local pseudowire label.

Remote PW Label

X

(Cisco 7600 only.) The remote pseudowire label.

Encapsulation Type

X

If the device supports encapsulation, the encapsulation type:

•None—No encapsulation.

•AAL0—ATM Adaptation Layer 0 (AAL0)

•AAL5—ATM Adaptation Layer 5 (AAL5)

Configure MCPT Timer

X

Indicates whether or not the MCPT timer is configured: True or False. False means retain the existing configuration as is. MCPT Timer values can only be configured on major interface.

MCPT Timer 1

X

The value of MCPT Timer 1.

MCPT Timer 2

X

The value of MCPT Timer 2.

MCPT Timer 3

X

The value of MCPT Timer 3.

Ignore-VPI

(Cisco 2900 only.) If Xconnect Location is PVC, indicates whether the ATM virtual path identifier should be ignored: True or False.

Pseudowire Class Name

The pseudowire class name.

Ignore-VPI-VCI

(Cisco 2900 only.) If Xconnect Location is PVP, indicates whether the ATM virtual path identifier (VPI) virtual circuit identifier (VCI) should be ignored: True or False.

Backup Pseudowire Class Name

If Configure Backup PW is True, the backup pseudowire class name.

Backup Device IP Address

X

If Configure Backup PW is True, the backup device IP address.

ATM Pseudowire S-PE Configuration Screen

Configure Multi-Segment Pseudowire

X

Indicates whether or not a multisegment pseudowire will be configured.

Second Segment Tunnel ID

X

If Configure Multi-Segment Pseudowire is True, the second segment tunnel identifier. (Numeric only.)

Device

X

If Configure Multi-Segment Pseudowire is True, the device where the pseudowire will be provisioned.

IP Address

X

If Configure Multi-Segment Pseudowire is True, the device IP address.

Pseudowire Class Name A Side

X

If Configure Multi-Segment Pseudowire is True, the A Side pseudowire class name.

Pseudowire Class Name B Side

X

If Configure Multi-Segment Pseudowire is True, the B Side pseudowire class name.

VFI Name

X

(Cisco 7600 only.) If Configure Multi-Segment Pseudowire is True, the VFI name.

Xconnect Group Name

X

(Cisco ASR 9000 only.) If Configure Multi-Segment Pseudowire is True, the Xconnect group name.

Xconnect Name

X

(Cisco ASR 9000 only.) If Configure Multi-Segment Pseudowire is True, the Xconnect name.

Create a MToP ATM Pseudowire Service

To create a MToP ATM pseudowire service:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the MToP ATM pseudowire service.

Step 2 Verify that the controllers where you want to provision the ATM pseudowire service are configured for T1, E1, or SONET, depending on the device and pseudowire service.

If the controllers are configured, continue with the next step. If not, do not continue. Configure the controllers using the procedures in the Cisco MWR 2941-DC Mobile Wireless Edge Router Software Configuration Guide or the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide, then start this procedure again.

Step 3 From the Activation menu, choose Activation.

Step 4 Do one of the following:

•To provision a new activation, expand the Service > MToP trees, choose Create MToP ATM Pseudowire Service and click Next.

•To provision a new activation using a completed one as a starting point, click Clone Activation, choose a MToP ATM pseudowire service activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Add L3 VPN Sites screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 5 In the ATM Pseudowire Attributes screen, do one of the following:

•To add an ATM pseudowire, click Add.

•To edit an existing ATM pseudowire, select it and click Edit.

•To delete an existing ATM pseudowire, select it and click Delete.

If you clicked Add or Edit, a ATM Pseudowire Attributes window appears. If you clicked Edit, the VPN attribute fields are populated.

Step 6 In the ATM Pseudowire Attributes screen, complete the following attributes.

See Table 3-10 for descriptions.

•Speed

•Point to Point

•Xconnect Location

•VC ID

•Cells Per Packet

•MCPT Timer ID

Step 7 Click Next.

Step 8 In the ATM Pseudowire A Side screen, complete the following attributes for the client device.

See Table 3-10 for descriptions. Not all attributes will appear, depending on the device and other attribute selections.

•Device

•IP Address

•Controller Type

•Interface Type

•ATM Logical Interface Name

•ATM Regular Interface Name

•PVC ID

•PVP ID

•IMA Version

•IMA Group ID

•Static Label

•Local PW Label

•Remote PW Label

•Encapsulation Type

•Configure MCPT Timer

•MCPT Timer 1

•MCPT Timer 2

•MCPT Timer 3

•Ignore-VPI

•Ignore-VPI-VCI

Step 9 Click Next.

Step 10 In the ATM Pseudowire B Side screen, complete the same pseudowire attributes for the network device that you completed for the A Side in Step 8.

Step 11 Click Next.

Step 12 In the ATM Pseudowire S-PE Configuration screen, complete the following attributes if the pseudowire is multisegment. Otherwise, click Next. See Table 3-10 for descriptions.

•Configure Multi-Segment Pseudowire—Enter True.

•Second Segment Tunnel ID

•Device

•Platform

•IP Address

•Pseudowire Class Name A Side

•Pseudowire Class Name A Side

•VFI Name

•Xconnect Group Name

•Xconnect Name

Step 13 Click Next.

Step 14 In the User Input Tab, review the ATM pseudowire information. Click Prev to edit any information, if needed.

Step 15 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 16 Click Finish.

The ATM pseudowire service is added to the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 17 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note The activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

MToP TDM Clock Pseudowire

The Create MToP TDM Clock Pseudowire wizard activates a TDM over MPLS pseudowire with clocking using the CEOPS card on Cisco 7600 and Cisco MWR 2941 devices as shown in Figure 3-7,

Figure 3-7 TDM over MPLS Pseudowires Using the CEOPS card on the 7600 (sample)

The wizard also includes the clocking pseudowire as shown in Figure 3-8.

Figure 3-8 Clocking Pseudowire

The MToP TDM Pseudowire wizard activates TDM based adaptive clocking on Cisco MWR 2941 Cell Site Router. The wizard allows you to configure the following:

•Structure-agnostic and structure-aware TDM over MPLS.

•Virtual interfaces using the controller commands.

•xConnect under the virtual interface.

•xConnect to the virtual interface.

•Clocking pseudowire.

•Recovered clock.

•T1 and E1 controllers.

Note Channelization is not configured.

The MToP TDM Pseudowire service can be provisioned on the following devices:

•Cisco 7600 Series

•Cisco MWR 2941 Cell Site Router

Note Verify that time stamping is disabled on devices where you plan to provision the TDM clock pseudowire.

Note The Create MToP TDM Clock Pseudowire wizard does not provision the device controllers. You must provision the controllers before starting this wizard. To provision T1 or E1 controllers on the Cisco 2900, see the Cisco MWR 2941-DC Mobile Wireless Edge Router Software Configuration Guide. To provision T1, E1, or SONET (OC-3) controllers on the Cisco 7600, see the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide.

MToP TDM Clock Pseudowire Inputs

Table 3-11 lists the inputs you need for activation of an MToP TDM clock pseudowire. An X in the Required column indicates the parameter is required.

Table 3-11 MToP TDM Clock Pseudowire Inputs

User Input

Required

Description

TDM Clocking Pseudowire Attributes Screen

Clock Speed

X

The clock speed, either T1 or E1.

Clock Tunnel ID

X

The clock tunnel identifier.

TDM Clocking Pseudowire Side A and Side B Screens

Device

X

The device on the clocking pseudowire side A.

Platform

X

The platform of the device selected in the Device field. (Read-only.)

Clock Virtual CEM Interface

X

A CEM interface refers to an E1 or T1 interface configured for circuit emulation. A virtual CEM interface is used for out-of-band clocking. A virtual CEM interface is created when clock recovery is configured for out-of-band clocking by configuring a master or slave clock.

Note To provision this field, a virtual CEM must be provisioned on the device. This can be obtained from the Clock item in the Cisco ANA NetworkVision Logical Inventory.

Clock Controller Interface Name

X

If Clock Mode is set to Master, the clock controller interface name. (Cisco 7600 only.)

Clock Mode (Master/Slave)

X

The clock mode: Master or Slave. (Cisco 7600 only.)

Clock Mode (Recovered/Slave)

X

The clock mode: Recovered or Slave. (Cisco MWR 2900 only.)

Clock CEM Group ID

X

The clock CEM group identifier.

Clock Peer IP Address

X

The clock peer IP address.

Create a MToP TDM Clocking Pseudowire

To create a MToP TDM clocking pseudowire:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the MToP TDM clock pseudowire.

Step 2 Verify that the controllers where you want to provision the TDM clock pseudowire are configured for T1, E1, or SONET, depending on the device and pseudowire service.

If the controllers are configured, continue with the next step. If not, do not continue. Configure the controllers using the procedures in the Cisco MWR 2941-DC Mobile Wireless Edge Router Software Configuration Guide or the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide, then start this procedure again.

Step 3 From the Activation menu, choose Activation.

Step 4 Expand the Service > MToP trees and choose Create MToP TDM Clock Pseudowire.

Step 5 To create a new TDM clock pseudowire, complete the following steps. To use an existing activation as a starting point for the new one, continue with Step 6.

a. Click Next.

b. In the Create TDM Clocking Pseudowire screen, click Add.

c. Continue with Step 7.

Step 6 To use an existing TDM clock pseudowire activation as a starting point for the new one, complete the following steps:

a. Click Clone Activation,

b. In the Service Activation List window choose a TDM clock pseudowire activation and click OK.

The completed pseudowires appear in the Add TDM Clocking Pseudowire screen.

c. Choose a pseudowire and click Edit.

Note If you start with a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 7 In the TDM Clocking Pseudowire Attributes screen, complete the following attributes.

See Table 3-11 for descriptions.

•Clock Speed

•Tunnel ID

Step 8 Click Next.

Step 9 In the TDM Clock Side A screen, complete the following attributes.

See Table 3-11 for descriptions. Not all fields will appear, depending on your field option selections.

•Device

•Clock Virtual CEM Interface

•Clock Mode

•Clock Controller Interface Name

•Clock CEM Group ID

•Clock Peer IP Address

Step 10 Click Next.

Step 11 In the TDM Clocking Side Z screen, complete the following attributes:

•Device

•Clock Virtual CEM Interface

•Clock Mode

•Clock Controller Interface Name

•Clock CEM Group ID

•Clock Peer IP Address

Step 12 Click Next.

Step 13 In the User Input Tab, review the TDM pseudowire information. Click Prev to edit any information, if needed.

Step 14 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 15 Click Finish.

The TDM pseudowire service is added to the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 16 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note For Cisco 7600 Series, the activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

MToP TDM Pseudowire

The MToP TDM Pseudowire wizard activates TDM over MPLS pseudowires using the CEOPS card on Cisco 7600 devices as shown in Figure 3-9,

Figure 3-9 TDM over MPLS Pseudowires Using the CEOPS card on the 7600 (sample)

The MToP TDM Pseudowire wizard activates TDM based adaptive clocking on Cisco MWR 2941 Cell Site Router. The wizard allows you to configure the following:

•Structure-agnostic and structure-aware TDM over MPLS.

•Virtual interfaces using the controller commands.

•T1, T3, E1, and E3 controllers.

•xConnect under the virtual interface.

•xConnect to the virtual interface.

•Pseudowire creation.

•MSPW stitch up.

The MToP TDM Pseudowire wizard creates CEM groups with unframed and time slot options. It also creates pseudowires under CEM interfaces.

Note Channelization is not configured.

The MToP TDM Pseudowire service can be provisioned on the following devices:

•Cisco 7600 Series

•Cisco MWR 2941 Cell Site Router

Note Verify that time stamping is disabled on devices where you plan to provision the TDM pseudowire.

Note The Create MToP TDM Pseudowire wizard does not provision the device controllers. You must provision the controllers before starting this wizard. To provision T1 or E1 controllers on the Cisco 2900, see the Cisco MWR 2941-DC Mobile Wireless Edge Router Software Configuration Guide. To provision T1, E1, or SONET (OC-3) controllers on the Cisco 7600, see the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide.

MToP TDM Pseudowire Inputs

Table 3-12 lists the inputs you need to create an MToP TDM pseudowire. An X in the Required column indicates the parameter is required.

Table 3-12 MToP TDM Pseudowire Inputs

User Input

Required

Description

TDM Pseudowire Attributes Screen

Tunnel ID

X

If PW Type is Regular or Both, The pseudowire tunnel identifier. (Numeric only.)

Configure Backup PW

X

Indicates whether a backup pseudowire should be configured: True or False.

Backup Tunnel ID

X

If Configure Backup PW is True, the backup tunnel identifier. (Numeric only.)

Speed

X

The tunnel speed: T1, E1, T3, or E3.

Mode

X

The tunnel mode: unframed, timeslot.

Time Slot

X

The time slot ranges for the controllers: Valid ranges:

•T1—1 to 24

•E1—1 to 31

•T3—1 to 672

•E3—1 to 489

Valid time slot entries include:

•A single time slot (n).

•A list of time slots (n, n, n).

•A range of time slots (n-n).

•A combination of single, list, and range time slots, for example, (n, n, n-n).

Where n = valid time slot within the T1, E1, T3, or E3 ranges.

TDM Pseudowire Side A and Side B Screens

Device

X

The Side A or Side Z device where the pseudowire will be provisioned.

Platform

X

The model of the device. (Read only.)

Controller Interface Name

X

The controller interface name.

CEM Group ID

X

The circuit emulation (CEM) group identifier. CEM provides a bridge between a TDM network and a packet network such as MPLS. Valid ranges:

•T1—0 to 23

•E1—0 to 30

•T3—0 to 671

•E3—0 to 479

IP Address

X

The device IP address.

Pseudowire Class Name

X

The pseudowire class name.

Backup Pseudowire Class Name

X

If Configure Backup PW is set to True, the backup pseudowire class name.

Backup Device IP Address

X

If Configure Backup PW is set to True, the backup device IP address.

TDM Pseudowire S-PE Configuration Screen

Configure Multi-Segment Pseudowire

X

Indicates whether a multi-segment pseudowire is to be provisioned: True or False.

Second Segment Tunnel ID

X

If Configure Multi-Segment Pseudowire is true, the second segment tunnel identifier. (Numeric only)

Device

X

The device.

Platform

X

The model of the device selected in the Device field. (Read only.)

IP Address

X

The device IP addresses

Pseudowire Class Name Side A

X

The Side A pseudowire class name.

Pseudowire Class Name Side B

X

The Side B pseudowire class name.

VFI Name

The VFI name. (Cisco 7600 only.)

Xconnect Group Name

X

The Xconnect group name. (Cisco ASR 9000 only.)

Xconnect Name

X

The Xconnect name. (Cisco ASR 9000 only.)

Create a MToP TDM Pseudowire

To create a MToP TDM pseudowire:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the MToP TDM pseudowire.

Step 2 Verify that the controllers where you want to provision the TDM pseudowire are configured for T1, E1,T3, or E3, depending on the device and pseudowire.

If the controllers are configured, continue with the next step. If not, do not continue. Configure the controllers using the procedures in the Cisco MWR 2941-DC Mobile Wireless Edge Router Software Configuration Guide or the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide, then start this procedure again.

Step 3 From the Activation menu, choose Activation.

Step 4 Expand the Service > MToP trees and choose Create MToP TDM Pseudowire Service.

Step 5 To create a new TDM pseudowire, complete the following steps. To use an existing activation as a starting point for the new one, continue with Step 6.

a. Click Next.

b. In the Create TDM Pseudowire screen, click Add.

c. Continue with Step 7.

Step 6 To use an existing TDM pseudowire activation as a starting point for the new one, complete the following steps:

a. Click Clone Activation,

b. In the Service Activation List window choose a TDM pseudowire activation and click OK.

The completed pseudowires appear in the Add TDM Pseudowire screen.

c. Choose a pseudowire and click Edit.

Note If you start with a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 7 In the TDM Pseudowire Attributes screen, complete the following attributes. See Table 3-12 for descriptions.

•Tunnel ID

•Configure Backup PW

•Speed

•Mode

•Time Slot

Step 8 Click Next.

Step 9 In the TDM Pseudowire Side A screen, complete the following attributes.

See Table 3-12 for descriptions. Not all fields will appear, depending on the choices you make in each field.

•Device

•Platform

•Controller Interface Name

•CEM Group ID

•IP Address

•Pseudowire Class Name

•Backup Pseudowire Class Name

•Backup Device IP Address

Step 10 In the TDM Pseudowire Side B screen, complete the following attributes.

•Device

•Platform

•Controller Interface Name

•CEM Group ID

•IP Address

•Pseudowire Class Name

•Backup Pseudowire Class Name

•Backup Device IP Address

Step 11 Click Next.

Step 12 In the TDM Pseudowire S-PE Configuration screen, complete the following fields if the pseudowire is multisegment. If not, click Next.

See Table 3-12 for descriptions. Not all fields will appear, depending the device you select.

•Configure Multi-Segment Pseudowire—Enter True.

•Second Segment Tunnel ID

•Device

•Platform

•IP Address

•Pseudowire Class Name Side A

•Pseudowire Class Name Side B

•VFI Name

•Xconnect Group Name

•Xconnect Name

Step 13 Click Next.

Step 14 In the User Input Tab, review the TDM pseudowire information. Click Prev to edit any information, if needed.

Step 15 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 16 Click Finish.

The TDM pseudowire service is added to the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 17 After the activation is completed, you can view activation details by clicking Activation > Show Recent Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note For Cisco 7600 Series and Cisco MWR 2941 Cell Site Router, the activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

MToP Clocking Synchronization

The MToP Clocking Synchronization wizard activates clocking synchronization. Provisioned attributes include:

•Virtual interface

•xConnect to the virtual interface

•Network clocking for Cisco 7600.

•Network clocking and PTP for Cisco 2941

•PTP v2 1.5888 (Cisco MWR 2941 only)

Note Sync E is not supported.

The MTop Clocking Synchronization service can be provisioned on the following devices:

•Cisco 7600 Series Router

•Cisco MWR 2941 Cell Site Router

Note Verify that time stamping is disabled on devices where you plan to activate MToP clocking synchronization.

Note The Create MToP Clocking Synchronization wizard does not provision the device controllers. You must provision the controllers before starting this wizard. To provision T1 or E1 controllers on the Cisco 2900, see the Cisco MWR 2941-DC Mobile Wireless Edge Router Software Configuration Guide. To provision T1, E1, or SONET (OC-3) controllers on the Cisco 7600, see the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide.

MToP Clock Synchronization Inputs

Table 3-13 lists the inputs you need for activation of an MToP clocking synchronization. An X in the Required column indicates the parameter is required.

Table 3-13 MToP Clocking Synchronization Inputs

User Input

Required

Description

MToP Synchronization Configuration Screen

Device

X

The device

Platform

X

The platform is automatically populated after the device is chosen. (Read only.)

Synchronization Type

X

The synchronization type: Network or P2Pv2. (PTPv2 applies to Cisco 2941 only.)

Speed

X

The tunnel speed: T1, E1, T3, or E3.

Controller Interface Name

X

The controller interface name. This field is automatically populated based on the Speed attribute.

Clock Source Priority

X

The clock source priority, 1 through 6, with 1 being the highest priority. (Cisco 7600 only.)

Clock Source

X

The clock identifier: Controller, Interface, Slot, or System.

Slot

X

If Clock Source is Slot, the slot.

Hold Timeout

The hold time period (Cisco MWR 2941 only).

Priority

The clock priority, 1 through 23, which 23 being the highest priority. This applies to the Cisco MWR 2900 only.

Clock Interface Type

X

(Cisco MWR 2941 only.) The method by which clocking information is provided:

•BITS—Timing is supplied by a Building Integrated Timing Supply (BITS) port clock.

•T1/E1—Clocking is provided via an E1 or T1 interface.

•Packet-Timing—Clocking is provided over a packet-based network.

•Synchronous Ethernet—Clocking is provided by Synchronous Ethernet.

•None—Clocking is provided by a source other than the above.

Network Clocking Mode

X

(Cisco MWW 2941 only.) The action to take if the master device fails:

•Revert—Use the master device again after it recovers and functions correctly for a specified amount of time.

•Non-revert—Do not use the master device again after it recovers from the failure.

•None—The clocking mode is not provided.

Create a MToP Clock Synchronization

To create a MToP clock synchronization:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the MToP clock synchronization.

Step 2 From the Activation menu, choose Activation.

Step 3 To create a new clock synchronization activation, complete the following steps. To use an existing activation as a starting point for the new one, continue with Step 4.

a. Click Next.

b. In the Clock Synchronization Configuration screen, click Add.

c. Continue with Step 5.

Step 4 To use an existing clock synchronization activation as a starting point for the new one, complete the following steps:

a. Click Clone Activation,

b. In the Service Activation List window choose a clock synchronization activation and click OK.

The completed pseudowires appear in the Clock Synchronization Configuration screen.

c. Choose an activation and click Edit.

Note If you start with a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 5 In the Clock Synchronization Configuration screen, complete the following attributes.

See Table 3-13 for descriptions. Not all attribute fields will appear, depending on the device and options you choose in other attribute fields.

•Device

•Platform

•Synchronization Type

•Speed

•Controller Interface Name

•ATM Interface Name

•Clock Source Priority

•Clock Source

•Slot

•Mode

•Hold Timeout

•Priority

•Clock Interface Type

•Network Clocking Mode

Step 6 Click Next.

Step 7 In the User Input Tab, review the MToP clocking synchronization information. Click Prev to edit any information, if needed.

Step 8 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 9 Click Finish.

The MToP clocking synchronization service is added to the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 10 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note The activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

HSI Service Activations

You can use the HSI Point to Multipoint wizard to create multiple high-speed Internet activations. The HSI Point to Multipoint wizard can be provisioned on the Cisco 7600 Series routers.

Note Verify that time stamping is disabled on devices where you plan to provision the HSI service activation.

HSI point-to-multipoint wizard sequence:

•Create an EFP with all-in-one, 1:N, or 1:1 matching.

•Allow VLAN ID manipulation options none, push, pop or translate:

–Push—Outer VLAN ID or both inner and outer VLAN ID.

–Pop—Outer VLAN ID or both inner and outer VLAN ID.

–Translate—1-1 only.

•Create a bridge domain; apply no shutdown on the bridge domain and UNI.

•Associate the EFP with the previously configured bridge domain.

•Optionally attach a MAC ACL on the EFP.

•Optionally configure MAC security on the EFP with these configuration options:

–Maximum MAC address

–Secure aging time

–Secure violation mode (none, protect or restrict).

•Optionally attach QoS policies with these options:

–Either ingress, egress, or both.

–For Cisco ASR 9000 Series Routers, support shared policy attachment.

•Create a single pseudowire between the multipoint side and the single point.

HSI Point to Multipoint Inputs

Table 3-14 lists the inputs you need for activation of an HSI point to multipoint activation. An X in the Required column indicates the parameter is required.

Table 3-14 HSI Point to Multipoint Activation Inputs

User Input

Required

Description

Add HSI Multipoint Screen

Device

X

The device where the HSI point to multipoint activation will be created.

Platform

(Read only). The Platform attribute is automatically populated.

Local Peering IP

X

The local peering IP address of.

UNI ID

X

The UNI identifier.

EFP ID

X

The EFP identifier

Outer VLAN ID

The outer VLAN ID in QinQ implementations. The outer ID is assigned to S-VLANs. Valid outer VLAN ID entries include:

•" " (blank) or "any" to indicate any ID value is acceptable.

•A single VLAN ID (nnn).

•A list of VLAN IDs (nnn, nnn, nnn).

•A range of VLAN IDs (nnn-nnn).

•A combination of single, list, and range IDs, for example, (nnn, nnn, nnn-nnn).

Where nnn = valid VLAN ID.

If an inner VLAN ID is entered, some restrictions apply. See the Inner VLAN ID field for information.

Inner VLAN ID

The inner VLAN ID in QinQ implementations. The inner ID is assigned to CE-VLANs. Valid inner VLAN ID entries are the same as the outer VLAN IDs. You can enter " ", "any", a single VLAN ID, a list of VLAN IDs, a range of VLAN IDs, or combination of single, list, and range VLAN IDs.

Inner VLAN ID restrictions include:

•Requires an outer VLAN ID.

•Is not valid with multiple outer VLAN IDs.

•Multiple inner VLAN IDs are only supported with a single outer VLAN ID.

VLAN ID Preservation

X

The VLAN ID process applied to VLAN IDs:

•None—No VLAN ID processing is applied.

•Push—The VLAN ID is imposed on to the incoming frames.

•Pop—The VLAN ID is removed.

•Translate—The VLAN ID is translated.

Pop Action

X

When VLAN ID Preservation is set to Pop, the pop action:

•None—No pop action is applied.

•1—Remove the outer VLAN ID.

•2—Remove both outer and inner VLAN IDs.

Push Outer VLAN ID

When VLAN ID Preservation is set to Push, specifies the outer (customer) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Push Inner VLAN ID

When VLAN ID Preservation is set to Push, specifies the inner (service provider) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Translate Outer VLAN ID

X

When VLAN ID Preservation is set to Translate, specifies the outer (customer) VLAN IDs that will be translated.

Translate Inner VLAN ID

X

When VLAN ID Preservation is set to Translate, specifies the inner (provider) VLAN IDs that will be translated.

VC ID

X

The virtual circuit identifier. (Numeric only).

S-VLAN ID

X

The VLAN identifier.

Enable Split Horizon

X

Indicates whether to enable split horizon: True or False. Split horizon prevents a router from advertising a route back out the interface from which the route was learned.

Enable IGMP Snoop

X

Internet Group Management Protocol; if enabled (True), provides the ability to send Layer 2 multicast frames from CPE to remote peer CPE.

Add HSI Multipoint Feature

MAC Access List Name

The Access Control List name.

Enable MAC Security

X

Indicates whether or not the MAC security feature is enabled: True or False. If enabled, you can complete the Maximum Secure Addresses, Secure Aging Time, and Secure Violation Mode attributes to limit and control the EFP MAC addresses. Additionally, you can use the MAC Security Policy wizard to define specific MAC addresses to which the MAC security policies apply. For information, see Add MAC Secure Addresses.

Maximum Secure Addresses

If Enable MAC Security is set to True, sets the maximum number of addresses that can be stored in the EFP MAC address table.

Secure Aging Time

If Enable MAC Security is set to True, allows you to set the aging time of the addresses in the MAC address table to <n> minutes. By default, this affects only dynamically learned addresses.

Secure Violation Mode

If Enable MAC Security is set to True, allows you to define the MAC address violation behavior:

•None (Shutdown, default):

–The ingress frame is dropped.

–The service instance on which the offending frame arrived is shut down.

–The violation count is incremental, and the violating address is recorded for later CLI display.

–The event and the response are logged to the syslog.

•Restrict:

–The ingress frame is dropped.

–The violation count is incremental, and the violating address is recorded for display.

–The event and the response are logged to the SYSLOG.

•Protect—The ingress frame is dropped.

Attach Bandwidth Profile

X

Indicates whether a QoS policy should be attached: True or False. The QoS policy must be created before completing this wizard. See QoS Policy.

Direction

X

If Attach Bandwidth Profile is set to True, indicates the direction the policy should be applied:

•Ingress—The QoS policy is applied to ingress frames.

•Egress—The QoS policy is applied to egress frames.

•Both—The QoS policy is applied to both ingress and egress frames.

Ingress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Ingress or Both, indicates the bandwidth profile that should be applied to ingress frames.

Egress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Egress or Both, indicates the bandwidth profile that should be applied to egress frames.

Add HSI Single Point

Device

X

The device where the HSI point to multipoint activation will be created.

Platform

(Read only). The Platform attribute is automatically populated.

Local Peering IP

X

The local peering IP address.

UNI ID

X

The UNI identifier.

EFP ID

X

The EFP identifier

Outer VLAN ID

The outer VLAN ID in QinQ implementations. The outer ID is assigned to S-VLANs. Valid outer VLAN ID entries include:

•" " (blank) or "any" to indicate any ID value is acceptable.

•A single VLAN ID (nnn).

•A list of VLAN IDs (nnn, nnn, nnn).

•A range of VLAN IDs (nnn-nnn).

•A combination of single, list, and range IDs, for example, (nnn, nnn, nnn-nnn).

Where nnn = valid VLAN ID.

If an inner VLAN ID is entered, some restrictions apply. See the Inner VLAN ID field for information.

Inner VLAN ID

The inner VLAN ID in QinQ implementations. The inner ID is assigned to CE-VLANs. Valid inner VLAN ID entries are the same as the outer VLAN IDs. You can enter " ", "any", a single VLAN ID, a list of VLAN IDs, a range of VLAN IDs, or combination of single, list and range VLAN IDs.

Inner VLAN ID restrictions include:

•Requires an outer VLAN ID.

•Is not valid with multiple outer VLAN IDs.

•Multiple inner VLAN IDs are only supported with a single outer VLAN ID.

VLAN ID Preservation

X

The VLAN ID process applied to VLAN IDs:

•None—No VLAN ID processing is applied.

•Push—The VLAN ID is imposed on to the incoming frames.

•Pop—The VLAN ID is removed.

•Translate—The VLAN ID is translated.

Pop Action

X

When VLAN ID Preservation is set to Pop, the pop action:

•None—No pop action is applied.

•1—Remove the outer VLAN ID.

•2—Remove both outer and inner VLAN IDs.

Push Outer VLAN ID

When VLAN ID Preservation is set to Push, specifies the outer (customer) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Push Inner VLAN ID

When VLAN ID Preservation is set to Push, specifies the inner (provider) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Translate Outer VLAN ID

X

When VLAN ID Preservation is set to Translate, specifies the outer (customer) VLAN IDs that will be translated.

Translate Inner VLAN ID

X

When VLAN ID Preservation is set to Translate, specifies the inner (provider) VLAN IDs that will be translated.

To verify that the service activation executed successfully, or to troubleshoot any aspect of its execution, see Viewing Service Activation Results, page 4-1.

Create an HSI Point to Multipoint Activation

To activate an HSI point to multipoint:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the multipoint EFP.

Step 2 From the Activation menu, choose Activation.

Step 3 Expand the Residential HSI tree, choose Create HSI Point to Multipoint and click Next.

Step 4 In the Add HSI Multipoint screen Device field, choose a device from the drop-down list.

The Platform, Local Peering IP, and UNI ID attributes are populated with values.

Step 5 Complete the remaining attributes.

See Table 3-14 for descriptions. Not all attributes will appear, depending on your attribute selections.

•UNI ID

•EFP ID

•Outer VLAN ID

•Inner VLAN ID

•VLAN ID Preservation

•Pop Action

•Push Outer VLAN ID

•Push Inner VLAN ID

•Translate Inner VLAN ID

•VC ID

•S-VLAN ID

•Enable Split Horizon

•Enable IGMP Snoop

Step 6 Click Next.

Step 7 In the Add HSI Multipoint Feature screen, complete the following attributes.

See Table 3-14 for descriptions.

•MAC Access List name

•Enable MAC Security

•Maximum Secure Addresses

•Secure Aging Time

•Secure Violation Mode

•Attach Bandwidth Profile

•Direction

•Ingress Bandwidth Profile Name

•Egress Bandwidth Profile Name

Step 8 Click Next.

Step 9 In the Add HSI Single Point screen Device field, choose a device from the drop-down list.

The Platform, Device IP, and UNI ID attributes are populated with values.

Step 10 Complete the following attributes for the HSI single point.

See Table 3-14 for descriptions.

•UNI ID

•EFP ID

•Outer VLAN ID

•Inner VLAN ID

•VLAN ID Preservation

•Pop Action

•Push Outer VLAN ID

•Push Inner VLAN ID

•Translate Inner VLAN ID

Step 11 Click Next.

Step 12 In the User Input Tab, review the HSI point to multipoint information. If you need to edit any data, click Prev.

Step 13 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 14 After you have reviewed the information, click Finish.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 15 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note After completing the HSI point to multipoint activation, you must create the EFPs. See Create an Ethernet Flow Point

Note The activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

Ethernet Flow Point

You can use the Create Multipoint EFP wizard to create multipoint EFPs for E-LAN VPLS hubs,

Layer 3 VPNs, and HSI point to multipoint activations. The EFP can be provisioned on the following devices:

•Cisco ASR 9000 Series

•Cisco 7600 Series

Note Verify that time stamping is disabled on devices where you plan to provision the multipoint EFP.

The Create Multipoint EFP sequence:

•Create an EFP on the UNI with all-in-one, 1:N, or 1:1 matching.

•Allow VLAN ID manipulation options none, push, pop, or translate:

–Push—Outer VLAN ID or inner VLAN and outer VLAN ID.

–Pop—Outer VLAN ID or both inner and outer VLAN ID.

–Translate—1-1 only for Cisco 7600; 1-1, 1-2, 2-1, 2-2 for Cisco ASR 9000 Series Router.

•Associate EFP with the previously configured bridge domain.

•Optionally attach a MAC ACL.

•Optionally configure MAC security with these configuration options

–Maximum MAC address

–Secure aging time

–Secure violation mode (none, protect, or restrict)

• Optionally attach QoS policies with these options:

–Ingress, egress, or both ingress and egress.

–For Cisco ASR 9000, support shared policy attachment.

Note For an overview on Ethernet flow point technology, see Ethernet Flow Points, page 2-5.

Multipoint EFP Inputs

Table 3-15 lists the inputs you need for activation of the multipoint EFP. An X in the Required column indicates the parameter is required.

Table 3-15 Multipoint EFP Activation Inputs

User Input

Required

Description

First Add Multiple EFPs Screen

Device

X

The device where the EFP will be created.

Platform

(Read only). The model of the device selected in the Device field.

UNI ID

X

The UNI identifier.

EFP ID

X

The Ethernet flow point identifier.

Outer VLAN ID

The outer VLAN ID in QinQ implementations. The outer ID is assigned to S-VLANs. Valid outer VLAN ID entries include:

•" " (blank) or "any" to indicate any ID value is acceptable.

•A single VLAN ID (nnn).

•A list of VLAN IDs (nnn, nnn, nnn).

•A range of VLAN IDs (nnn-nnn).

•A combination of single, list, and range IDs, for example, (nnn, nnn, nnn-nnn).

Where nnn = valid VLAN ID.

If an inner VLAN ID is entered, some restrictions apply. See the Inner VLAN ID field for information.

Inner VLAN ID

The inner VLAN ID in QinQ implementations. The inner ID is assigned to CE-VLANs. Valid inner VLAN ID entries are the same as the outer VLAN IDs. You can enter " ", "any", a single VLAN ID, a list of VLAN IDs, a range of VLAN IDs, or combination of single, list, and range VLAN IDs.

Inner VLAN ID restrictions include:

•Requires an outer VLAN ID.

•Is not valid with multiple outer VLAN IDs.

•Multiple inner VLAN IDs are only supported with a single outer VLAN ID.

VLAN ID Preservation

X

The VLAN ID process applied to VLAN IDs:

•None—No VLAN ID processing is applied.

•Pop—The VLAN ID is removed.

•Push—The VLAN ID is imposed on to the incoming frames.

•Translate—The VLAN ID is translated.

Pop Action

X

When VLAN ID Preservation is set to Pop, the pop action:

•None—No pop action is applied.

•1—Remove the outer VLAN ID.

•2—Remove both outer and inner VLAN IDs.

Push Outer VLAN ID

When VLAN ID Preservation is set to Push, specifies the outer (customer) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Push Inner VLAN ID

When VLAN ID Preservation is set to Push, specifies the inner (service provider) VLAN IDs that will be imposed (pushed) onto the incoming frames that fulfill the match criteria.

Translate Action

X

When VLAN ID Preservation is set to Translate, the translate action:

•None

•1-1

•1-2

•2-1

•2-2

For option descriptions, see Table 3-2.

Translate Outer VLAN ID

X

When VLAN ID Preservation is set to Translate, specifies the outer (customer) VLAN IDs that will be translated.

S-VLAN ID

X

(Cisco 7600 only) The VLAN identifier.

Bridge Group Name

X

(Cisco ASR 9000 Series Routers only) The bridge group name.

Bridge Domain Name

X

(Cisco ASR 9000 Series Routers only) The bridge group domain name.

Enable Split Horizon

X

Indicates whether to enable split horizon: True or False. Split horizon prevents a router from advertising a route back out the interface from which the route was learned.

Enable IGMP Snoop

X

(Cisco 7600 only) Internet Group Management Protocol; if enabled (True), provides the ability to send Layer 2 multicast frames from CPE to remote peer CPE.

Second Add Multiple EFPs Screen

MAC Access List Name

The Access Control List name.

Enable MAC Security

X

Indicates whether or not the MAC security feature is enabled: True or False. If enabled, you can complete the Maximum Secure Addresses, Secure Aging Time, and Secure Violation Mode attributes to limit and control the EFP MAC addresses. Additionally, you can use the MAC Security Policy wizard to define specific MAC addresses to which the MAC security policies apply. For information, see Add MAC Secure Addresses.

Maximum Secure Addresses

If Enable MAC Security is set to True, sets the maximum number of addresses that can be stored in the EFP MAC address table.

Secure Aging Time

If Enable MAC Security is set to True, allows you to set the aging time of the addresses in the MAC address table to <n> minutes. By default, this affects only dynamically learned addresses.

Secure Violation Mode

If Enable MAC Security is set to True, allows you to define the MAC address violation behavior:

•None (Shutdown, default):

–The ingress frame is dropped.

–The service instance on which the offending frame arrived is shut down.

–The violation count is incremental, and the violating address is recorded for later CLI display.

–The event and the response are logged to the syslog.

•Restrict:

–The ingress frame is dropped.

–The violation count is incremental, and the violating address is recorded for display.

–The event and the response are logged to the SYSLOG.

•Protect—The ingress frame is dropped.

Attach Bandwidth Profile

X

Indicates whether a QoS policy should be attached: True or False.

Direction

X

If Attach Bandwidth Profile is set to True, indicates the direction the policy should be applied:

•Ingress—The QoS policy is applied to ingress frames.

•Egress—The QoS policy is applied to egress frames.

•Both—The QoS policy is applied to both ingress and egress frames.

Ingress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Ingress or Both, indicates the bandwidth profile that should be applied to ingress frames.

Egress Bandwidth Profile Name

X

If Attach Bandwidth Profile is set to True and Direction is set to Egress or Both, indicates the bandwidth profile that should be applied to egress frames.

Ingress Shared Bandwidth Profile Name

(Cisco ASR 9000 Series Routers only.) If Attach Bandwidth Profile is set to True and Direction is set to Ingress or Both, indicates the shared bandwidth profile that should be applied to ingress frames.

Egress Shared Bandwidth Profile Name

(Cisco ASR 9000 Series Routers only.) If Attach Bandwidth Profile is set to True and Direction is set to Egress or Both, indicates the shared bandwidth profile that should be applied to egress frames.

To verify that the service activation executed successfully, or to troubleshoot any aspect of its execution, see Viewing Service Activation Results, page 4-1.

Create an Ethernet Flow Point

To create the EFP:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the EFP.

Step 2 From the Activation menu, choose Activation.

Step 3 Expand the Service > E-LAN, L3VPN, or Residential HSI trees and choose Create Multipoint EFP.

Step 4 To create a new multipoint EFP, complete the following steps. To use an existing activation as a starting point for the new one, continue with Step 5.

a. Click Next.

b. In the Add Multiple EFP screen, click Add.

c. Continue with Step 6.

Step 5 To use an existing multipoint EFP activation as a starting point for the new one, complete the following steps:

a. Click Clone Activation,

b. In the Service Activation List window choose a multpoint EFP activation and click OK.

The completed EFPs appear in the Add TDM Pseudowire screen.

c. Choose a EFP and click Edit.

Note If you start with a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 6 In the first Add Multiple EFP screen, click Add or Edit (if you started the activation with an existing one and want to edit the existing attributes).

Step 7 In the Device field, choose a device from the drop-down list.

The Platform and UNI ID fields are populated with the device model and UNI IDs on the device.

Step 8 Complete the remaining attributes. See Table 3-15 for descriptions.

•UNI ID

•EFP ID

•Outer VLAN ID

•Inner VLAN ID

•VLAN ID Preservation

•Push Outer VLAN ID

•Push Inner VLAN ID

•Translate Inner VLAN ID

•S-VLAN ID

•Enable Split Horizon

•Enable Igmp Snoop

Step 9 Click Next.

Step 10 In the second Add Multiple EFP screen, enter the following attributes:

•MAC Access List name

•Enable MAC Security

•Maximum Secure Addresses

•Secure Aging Time

•Attach Bandwidth Profile

•Direction

•Ingress Bandwidth Profile Name

•Egress Bandwidth Profile Name

•Ingress Shared Bandwidth Profile Name

•Egress Shared Bandwidth Profile Name

Step 11 Click Next.

Step 12 In the User Input Tab, review the multipoint EFP information by clicking Prev to review the device information.

Step 13 Click Finish to add the device to the list of EFPs that will be created.

The Add Multiple EFPs screen appears with the first device listed.

Step 14 If you want to add an additional EFP, complete Steps 6 through 12.

Repeat until all devices are added. After you have added all the devices, proceed with the next step.

Step 15 Click Next in the Add Multiple EFPs screen.

Step 16 In the User Input Tab, review the EFP information by clicking Prev to review the devices that will be added.

Step 17 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 18 Click Finish to create the EFPs.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 19 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note For Cisco 7600 Series, the activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

Policy Activations

The following sections provide overviews and procedures for completing the network service activations:

•Layer 2 Access Control List

•QoS Policy

•Add MAC Secure Addresses

Layer 2 Access Control List

The Layer 2 ACL wizard creates a MAC ACL with permit and deny statements. The wizard allows you to configure each of the following:

•MAC ACLs

•Permit-deny conditions

•MAC ACL on switchport interface (SI).

The Layer 2 ACL can be provisioned on the Cisco 7600 Series router.

Note Verify that time stamping is disabled on devices where you plan to provision the Layer 2 ACL.

Layer 2 ACL Inputs

Table 3-16 lists the inputs you need to create a Layer 2 ACL. An X in the Required column indicates the parameter is required.

Table 3-16 Layer 2 ACL Activation Inputs

User Input

Required

Description

Create L2 Access Policy Screen

Device

X

The device where you want to create the Layer 2 ACL.

Access List Name

X

The ACL name.

Add Access List Entries Screen

Condition

X

The ACL condition: permit or deny

Source Type

X

The ACL source type: Any, Host, or MAC Address/Mask

Source Address

If Source Type is Host, enter the source MAC address.

Source Mask

If Source Type is Host, the source IP address mask.

Destination Type

X

The ACL destination type: any, host, or MAC address/mask

Destination Address

If Destination Type is Host, the destination MAC address.

Destination Mask

If Destination Type is Host, the destination MAC address mask.

To verify that the script deployed successfully, or to troubleshoot any aspect of its execution, see Viewing Service Activation Results, page 4-1.

Create a Layer 2 ACL

To create a Layer 2 ACL:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the Layer 2 ACL.

Step 2 From the Activation menu, choose Activation.

Step 3 Do one of the following:

•To provision a new activation, expand the Policy > ACL trees, choose Create Layer 2 ACL and click Next.

•To provision a new activation using a completed one as a starting point, click Clone Activation, choose an ACL activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Add Access List Entries screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

If you are creating a new ACL, continue with Step 4. If you are starting with a completed ACL activation, continue with Step 6.

Step 4 In the Create L2 Access Policy screen, complete the following steps to add a device:

a. Click the Device field.

b. Display the Cisco ANA NetworkVision window.

c. In the navigation tree or map view, right-click the device you want to add and choose Activation > Add to Activation.

The device populates the Device field.

Step 5 In the Access List Name field, enter the ACL name, then click Next.

Step 6 In the Add MAC Access List Entries screen, do one of the following:

•To add an ACL, click Add.

•To edit an existing ACL, select it and click Edit.

•To delete an existing ACL, select it and click Delete.

If you clicked Add or Edit, the Add MAC Access List Entries window appears. If you clicked Edit, the ACL attribute fields are populated.

Step 7 Complete the ACL attributes. See Table 3-16 for descriptions.

•Condition

•Source Type

•Source Address

•Source Mask

•Destination Type

•Destination Address

•Destination Mask

Step 8 Click Next.

Step 9 In the User Input Tab, review the ACL information by clicking Prev to review the ACL entries.

Step 10 Click Finish to add the ACL.

The Add MAC Access List Entries screen appears with the first ACL listed.

Step 11 If you want to add an additional ACL, complete Steps 6 through 9.

Repeat until all ACLs are added. After you have added all ACLs, proceed with the next step.

Step 12 Click Next in the Add MAC Access List Entries screen.

Step 13 In the User Input Tab, review the E-LAN spoke information by clicking Prev to review the devices that will be added.

Step 14 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 15 Click Finish to create the E-LAN spokes.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 16 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note The activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

QoS Policy

You can create, edit, and remove flat and hierarchical global QoS class and policy maps for reference by service instances.

The QoS policies can be provisioned on the following devices:

•Cisco ASR 9000 Series Routers

•Cisco 7600 Series

Note Verify that time stamping is disabled on devices where you plan to provision the QoS policy.

QoS Policy Inputs

Table 3-17 lists the inputs you need to create QoS policies. An X in the Required column indicates the parameter is required.

Table 3-17 QoS Policy Inputs

User Input

Required

Description

Create QoS Policy - Class Map Screen

QoS Type

X

The QoS type: Flat or Hierarchical.

Class Map Name

X

The class map name.

Class Map Match Type

X

The class map match type: match-all or map any.

Class Map Class of Service

X

The QoS service level for the class map: 1 (best effort) to 7 (Layer 2Network Control Reserved Traffic).

Configure Second Class Map

X

If the QoS Type is Hierarchical, indicates whether the second class map is defined: True or False.

Second Class Map Name

X

The second class map name.

Second Class Map Match Type

X

The second class map match type: match-all or map any.

Second Class Map Class of Service

X

The QoS service level for the third class map: 1 (best effort) to 7 (Layer 2 Network Control Reserved Traffic).

Configure Third Class Map

X

If the QoS Type is Hierarchical, indicates whether the third class map is defined: True or False.

Third Class Map Name

X

The third class map name.

Third Class Map Match Type

X

The third class map match type: match-all or map any.

Third Class Map Class of Service

X

The QoS service level for the third class map: 1 (best effort) to 7 (Layer 2Network Control Reserved Traffic).

Create QoS Policy - Policy Map Screen

Policy Map Name

X

The policy map name.

Class Map Priority

X

The class map priority.

Class Map Police CIR

X

The class map police committed information rate (CIR).

Class Map Bandwidth

X

The class map bandwidth.

Second Class Map Priority

X

The second class map priority.

Second Class Map Police CIR

X

The second class map police CIR.

Second Class Map Bandwidth

X

The second class map bandwidth.

Third Class Map Priority

X

The third class map priority.

Third Class Map Police CIR

X

The third class map CIR.

Third Class Map Bandwidth

X

The third class map bandwidth.

Parent Policy Map Name

X

The parent policy map name.

Parent Policy Type

X

The parent policy type.

Shape Average

The shape average.

Bandwidth Remaining Ratio

The bandwidth remaining ration.

Bandwidth

The bandwidth.

Apply QoS Policy to Devices

Device

The device to which the QoS policies will be applied.

Platform

(Read-only) The model of the device selected in the Device field.

Create a QoS Policy

To create a QoS policy:

Step 1 Log into Cisco ANA NetworkVision containing the devices where you want to create the QoS policy.

Step 2 From the Activation menu, choose Activation.

Step 3 Do one of the following:

•To provision a new activation, expand the Policy > QoS trees, choose Create QoS Policy and click Next.

•To provision a new activation using a completed one as a starting point, click Clone Activation, choose a QoS policy activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Create QoS Policy - Class Map screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Create QoS Policy - Class Map screen, choose a QoS type from the QoS Type field, either Flat or Hierarchical.

If you chose a hierarchical QoS policy, the Class Map, Second Class Map, and Third Class Map attributes are available for provisioning. If you chose a flat QoS policy, only the Class Map attributes are available.

Step 5 Complete the QoS class map attributes. See Table 3-17 for descriptions.

•Class Map Name

•Class Map Match Type

•Class Map Class of Service

•Configure Second Class Map

•Second Class Map Name

•Second Class Map Match Type

•Second Class Map Class of Service

•Configure Third Class Map

•Third Class Map Name

•Third Class Map Match Type

•Third Class Map Class of Service

Step 6 Click Next.

Step 7 In the Create QoS Policy - Policy Map screen, enter the policy map attributes. See Table 3-17 for descriptions.

•Policy Map Name

•Class Map Priority

•Class Map Police CIR

•Class Map Bandwidth

•Second Class Map Priority

•Second Class Map Police CIR

•Second Class Map Bandwidth

•Third Class Map Priority

•Third Class Map Police CIR

•Third Class Map Bandwidth

Step 8 Click Next.

Step 9 In the Create QoS Policy - Parent Policy Map, provision the QoS parent policy map. See Table 3-17 for descriptions.

•Parent Policy Map Name

•Parent Policy Type

•Shape Average

•Bandwidth Remaining Ratio

•Bandwidth

Step 10 Click Next.

Step 11 In the Apply QoS Policy to Devices screen, do one of the following:

•To add the QoS policy, click Add.

•To edit an existing QoS policy, select it and click Edit.

•To delete an existing QoS policy, select it and click Delete.

If you clicked Add or Edit, the Apply QoS Policy to Devices window appears.

Step 12 In the Device field, choose a device.

The Platform field is automatically populated with the platform of the device chosen in the Device field. It cannot be changed.

Step 13 Click Next.

Step 14 In the User Input Tab, review the QoS policy information by clicking Prev to review the information.

Step 15 Click Finish to add the QoS policy to the list of policies that will be added.

The Apply QoS Policy to Devices screen appears with the first site displayed.

Step 16 If you want to add an additional sites to the VPN, complete Steps 4 through 11.

Repeat until all the policies are added. After you have added all the policies, proceed with the next step.

Step 17 Click Next in the Apply QoS Policy to Devices screen.

Step 18 In the User Input Tab, review the QoS policy information.

Step 19 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 20 Click Finish to add the policy to the list of policies that will be added. If you want to go back and edit the inputs. click Prev to return to the previous screen.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 21 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note For Cisco 7600 Series, the activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.

Add MAC Secure Addresses

If MAC security is enabled for an EFP or E-LAN H-VPLS hub or spoke, you can use the Add MAC Secure Addresses wizard to define a set of MAC addresses to add to the permit table. The MAC security policies can be provisioned on the Cisco 7600 Series routers.

Note Verify that time stamping is disabled on devices where you plan to provision the MAC secure addresses.

Add MAC Secure Addresses Inputs

Table 3-18 lists the inputs you need to create MAC security policies. An X in the Required column indicates the parameter is required.

Table 3-18 MAC Secure Addresses Inputs

User Input

Required

Description

Add MAC Security Screen

Device

X

The device where you want to provision the additional MAC security policy.

Platform

X

The platform of the device that is chosen in the Device field. This field is read-only.

UNI Interface

The UNI interface.

EFP ID

X

The EFP identifier; the EFP must exist on the device.

Maximum Secure Addresses

Sets the maximum number of addresses that can be stored in the MAC address table. This parameter only applies to dynamically-learned addresses.

Aging time

Sets the aging time of the addresses in the MAC address table to <n> minutes. By default, this affects only dynamically learned addresses.

Violation Mode

Defines the MAC address violation behavior:

•None (Shutdown, default):

–The ingress frame is dropped.

–The service instance on which the offending frame arrived is shut down.

–The violation count is increased, and the violating address is recorded for later CLI display.

–The event and the response are logged to the SYSLOG.

•Restrict:

–The ingress frame is dropped.

–The violation count is increased, and the violating address is recorded for display.

–The event and the response are logged to the syslog.

•Protect—The ingress frame is dropped.

Add MAC Secure Addresses

MAC Secure Address

X

The MAC addresses to add to the permit table.

Add MAC Secure Addresses

To add MAC secure addresses:

Step 1 Log into Cisco ANA NetworkVision.

Step 2 From the Activation menu, choose Activation.

Step 3 Do one of the following:

•To provision a new activation, expand the Policy > MAC Secure Address trees, choose Add MAC Secure Address and click Next.

•To provision a new activation using a completed one as a starting point, click Clone Activation, choose a MAC security policy activation in the Service Activation List window, and click OK.

The data values of the completed activation appear in the Add MAC Secure Addresses screen.

Note If you use a completed activation, the activation attribute values appear in the wizard screens. Instead of provisioning them for the first time, you edit the values, as needed, to complete the new activation.

Step 4 In the Add MAC Security screen, choose a device in the Device field.

The platform of the device you selected populates the Platform field. It cannot be changed.

Step 5 Complete the remaining MAC security attributes. See Table 3-18 for descriptions.

•UNI Interface

•EFP ID

•Maximum Secure Addresses

•Aging time

•Violation Mode

•Platform

Step 6 Click Next.

Step 7 In the Add MAC Secure Address screen, do one of the following:

•To add a MAC address, click Add.

•To edit an existing MAC address, select it and click Edit.

•To delete an existing MAC address, select it and click Delete.

If you clicked Add or Edit, the Add MAC Secure Addresses window appears.

Step 8 In the MAC Secure Address, enter a MAC address.

Step 9 Click Next.

Step 10 In the User Input Tab, review the MAC address information by clicking Prev to review the information.

Step 11 Click Finish to add the address to the list of addresses that will be added.

The Add MAC Secure Address screen appears with the first address displayed.

Step 12 If you want to add an additional addresses, complete Steps 7 through 10.

Repeat until all the addresses are added. After you have added all the policies, proceed with the next step.

Step 13 Click Next in the Add MAC Secure Addresses screen.

Step 14 In the User Input Tab, review the addresses by clicking Prev to review the addresses o which the MAC security policy will be added.

Step 15 Click the Preview Configuration Tab to view the details of the activation. For more information, see Preview Configuration in a Device, page 4-8.

Step 16 Click Finish to add the policy and addresses.

The activation is performed on the devices and interfaces indicated. The Run Activation screen communicates the status of the activation.

Step 17 After the activation is completed, you can view activation details by clicking Activation > Show Service Activations.

The Service Activation List window appears. For more information, see Viewing Service Activation Results, page 4-1.

Note The activation is added to the device running configuration. To add it to the startup configuration, see Applying Activations to Device Startup Configurations, page 4-8.