RAD Data comm MPW-1 Specifications Page 70

  • Download
  • Add to my manuals
  • Print
  • Page
    / 108
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 69
Chapter 3 Configuration Installation and Operation Manual
3-26 Configuring Pseudowire Services MPW-1 MP-4100 Ver. 2.0
Parameter Function Values
Ingress Tunnel
Label
Specifies the inbound MPLS label used
for the pseudowire.
The parameter is displayed only when
Inbound Label Tagging is ENABLE.
This parameter is relevant only when
PSN Type is MPLS/ETH
The supported range is 16 to 1048575. Each
pseudowire must have a unique inbound MPLS
label. 0 means that no label has been defined.
Default: 0
Egress Tunnel
Tagging
Controls the use of an interworking
MPLS label for the transmit (outbound)
direction of the pseudowire.
This parameter is relevant only when
PSN Type is MPLS/ETH
ENABLE – Outbound tagging is enabled.
DISABLE – Outbound tagging is disabled.
Default: DISABLE
Egress Tunnel
Label
Specifies the outbound MPLS label
used for the pseudowire.
The parameter is displayed only when
Outbound Label Tagging is ENABLE.
This parameter is relevant only when
PSN Type is MPLS/ETH
The supported range is 16 to 1048575. 0 means
that no label has been defined.
Default: 0
EXP Bits Specifies the value of the outbound
EXP bits that indicate the requested
quality of service in the MPLS header
of the pseudowire.
This parameter is relevant only when
PSN Type is MPLS
The allowed range is is 7 (highest priority) to 0
(lowest priority).
Default: 0
VLAN Priority When VLAN Tagging is enabled for the
router interface used by this
pseudowire, specifies the Layer 2
priority assigned to the pseudowire
traffic using the selected VLAN.
When VLAN tagging is disabled, this
parameter is not relevant
The allowed range in accordance with IEEE
802.1p is 7 (highest priority) to 0 (lowest
priority).
Default: 0
Payload Format Selects the packet payload format.
The selection must be compatible with
the equipment at the far end of the
connection. Contact RAD Technical
Support Department if you need
additional information
V1 – Old packet payload format, defined as
experimental
in the relevant IETF drafts, can only
be used for TDMoIP CE pseudowires. Not
recommended for use.
Packet payload version V1 requires two UDP
sockets per pseudowire, whereas TDMoIP V2
requires a single UDP socket per pseudowire.
V2 – Current packet payload format. Requires
one UDP socket per pseudowire.
Default: V2
Configuring Pseudowire Service Parameters, and Attachment
Circuit Parameters
The pseudowire service parameters include two groups of parameters:
Page view 69
1 2 ... 65 66 67 68 69 70 71 72 73 74 75 ... 107 108

Comments to this Manuals

No comments