Configuring the DCP – S12700 V200R011C10 Configuration Guide – Network Management and Monitoring – Huawei

Run the

instance

instance-id

command to create a measurement
instance and enter the IPFPM-DCP instance view.

By default, no measurement instance exists on a DCP.

(Optional) Run the

authentication-mode

key-id

[

]

password

command to configure the authentication mode and
password for the measurement instance.

By default, no authentication mode or password is configured
for a measurement instance.

If no authentication mode or password
is configured for a measurement instance, the authentication mode
and password configured in the IPFPM-DCP view (step 4) are used for
this instance. If the authentication mode and password are configured
for a measurement instance, the configuration in this step is used.

Run the

mcp

mcp-id

[

port-number

] [

vpn-instance-name

|

] command to associate the MCP ID with the measurement instance,
and configure the UDP port number through which the DCP and MCP communicate
with each other.

By default, no MCP ID is associated with a measurement instance,
and the DCP and MCP communicate with each other through UDP port 65030.
If no MCP ID is associated with the measurement instance, the MCP
ID specified in the IPFPM-DCP view (step 6) is used. If an MCP ID
is associated with the measurement instance, the configuration in
this step is used.

mcp id

command.

• If the two MCP IDs are the same, the MCP accepts the packet, and
  then summarizes and calculates the statistics data.
• If the two MCP IDs are different, the MCP considers the packet
  invalid and discards it.

The DCP receives statistics data from TLPs, and sends the statistics data to the destination IP address, which is the MCP ID associated with the measurement instance. When receiving the packet carrying the measurement result from the DCP, the MCP compares the MCP ID in the packet with the MCP ID locally configured by thecommand.

Define a target flow in the measurement instance.

A target flow is the objective in iPCA measurement,
and can be defined by any combinations of source IP address, destination
IP address, protocol type, DSCP value, source port number, and destination
port number. Specifying more attributes can make the target flow accurate.
Therefore, it is recommended that you specify more attributes to improve
precision of measurement results.

A target flow is
transmitted in a certain direction. If a target flow
is unidirectional, only a forward flow or a backward flow needs to
be configured. If a target flow is bidirectional (the source and destination
addresses of forward and backward flows mirror to each other), only
a bidirectional symmetrical flow needs to be configured. The system
then automatically generates two symmetrical unidirectional flows.
If the source and destination addresses are not mirrored, two unidirectional
flows need to be configured.

A measurement instance
can contain only one unidirectional flow or bidirectional flow (two
unidirectional flows logically). Different measurement instances cannot
contain the same target flow. That is, a target flow cannot belong
to both instance A and instance B, and the forward flow and backward
flow in the same measurement instance cannot be the same.

• Define a unidirectional flow.

  • When the protocol of a target flow is TCP or UDP, run the following
    command:

    flow { forward | backward } { protocol { tcp | udp } { source-port src-port-number1 [ to src-port-number2 ] | destination-port dest-port-number1 [ to dest-port-number2 ] } * | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

  • When the protocol of a target flow is not TCP or UDP, run the
    following command:

    flow { forward | backward } { protocol protocol-number | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

• Define a bidirectional symmetrical flow.

  • When the protocol of a target flow is TCP or UDP, run the following
    command:

    flow bidirectional { protocol { tcp | udp } { source-port src-port-number1 [ to src-port-number2 ] | destination-port dest-port-number1 [ to dest-port-number2 ] } * | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

  • When the protocol of a target flow is not TCP or UDP, run the
    following command:

    flow bidirectional { protocol protocol-number | dscp dscp-value | source src-ip-address [ src-mask-length ] | destination dest-ip-address [ dest-mask-length ] } *

If the target flow entering a DCP has been fragmented,
the device counts only the first fragment. Therefore, if a transit
device on the network has fragmented the target flow, the measurement
result may be inaccurate.

When you define a bidirectional symmetrical
flow, you must specify the source and destination IP addresses.

Run the

interval

interval

command to set the measurement interval.

Before changing the measurement interval, disable packet
loss measurement in the IPFPM-DCP instance view.

The measurement
interval of a measurement instance cannot be changed when the measurement
instance is running. If the measurement interval of a running measurement
instance is changed, the statistics reported by MCP may be inaccurate.
To change the measurement interval, run the measure
disable command in the IPFPM-MCP instance view to
disable the measurement, and then run the measure
enable command to enable the measurement.

By default, the measurement interval is 10 seconds.

(Optional) Run the

description

text

command to configure the description
of the measurement instance.

By default, a measurement instance does not have a description,
and the instance is identified by an ID in integer format. The description
helps you understand the service monitored by the measurement instance
and avoids misuse on the measurement instance. For example, if a measurement
instance is configured to measure packet loss in the traffic from
headquarters to branch 1, the description of the instance can be set
to HeaderToBranch1.

Run the

tlp

tlp-id

{

|

} {

|

} command
to configure the TLPs of the measurement instance and their roles.

TLPs are the measurement points in the measurement instance.
They collect data and generate statistics. By default, no TLP is configured.

in-point indicates that the device
colors the target flow; out-point indicates
that the device removes the color flag from the target flow. ingress indicates that the target flow arrives at the
TLP; egress indicates that the target flow
leaves the TLP.