Configuring Traffic Policing For An Ac; Inspecting Vcs - HP 12500 Series Configuration Manual

NOTE:
Up to 4094 service instances can be configured on a Layer 2 Ethernet interface.
•
The xconnect peer command is available for service instances with the ID in the range of 1 to 4094.
•

Configuring traffic policing for an AC

Traffic policing limits the packet transmit rate to avoid network congestion.
A PE uses an attachment circuit (AC) interface to connect to a CE. To perform traffic policing for an AC:
• If the AC interface is a Layer 3 interface, configure QoS on the Layer 3 interface then create a
Martini MPLS L2VPN connection on the interface.
If the AC interface is a Layer 2 interface, create a service instance on the interface, apply global
•
committed access rate (CAR) actions for the service instance, and then create a Martini MPLS
L2VPN connection for the service instance.
This configuration task describes how to apply a global CAR action for a service instance.
Configuration prerequisites
Use the qos car command in system view to configure a global CAR action. For more information about
CAR, see ACL and QoS Configuration Guide.
Configuration procedure
After you apply a global CAR action in service instance view, the device polices the inbound or
outbound traffic matching the service instance according to the applied global CAR action.
To apply a global CAR action for a service instance:
To do...
Enter system view
Enter the view of the Layer 2 Ethernet
interface connected to the CE
Enter service instance view
Apply a global CAR action to the
inbound or outbound traffic on the AC
NOTE:
To configure traffic policing for an AC, you must first configure this task before you create a Martini MPLS
L2VPN connection.

Inspecting VCs

On an MPLS L2VPN network, you can use the MPLS LSP ping function to check the VC connectivity and
get necessary information for troubleshooting VC failures
On the local PE, the MPLS LSP ping function adds the label of the VC to be inspected into MPLS Echo
Request messages so that the messages will travel along the VC. The local PE determines whether the VC
is valid and reachable according to the replies received from the peer PE.
Use the command...
system-view
interface interface-type
interface-number
service-instance instance-id
car { inbound | outbound } name
car-name
180
Remarks
—
—
—
Required
By default, no global CAR is
applied to an AC.