EasyManuals Logo
Home>HPE>Network Router>FlexNetwork MSR Series

HPE FlexNetwork MSR Series Comware 5 Layer 2 - Wan Access Configuration Guide

HPE FlexNetwork MSR Series
420 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #330 background imageLoading...
Page #330 background image
319
Matching mode Description Example
left-ext
Extended left-most matching
mode, in which the alias string is
in the form of $1234….
"$1234 …" will match 1234679
and 1234872, but will not match
123468 and 12346890.
right
Right-most matching mode, in
which the alias string is in the
form of 1234$.
"1234$" will match 791234 and
6901234, but will not match
7912345 and 6212534.
right-ext
Extended rightmost matching
mode, the alias string is in the
form of ….1234$.
"….1234$" will match 79001234
and 86901234, but will not
match 7912345 and
506212534.
strict
Strict matching mode, in which
the alias string is in the form of
$1234$.
"$1234$" can only match 1234.
whole
Whole matching mode, in which
the alias string is in the form
of ........
"…..…" will match all the valid
X.121 addresses of 8 digits in
length.
whole-ext
Extended whole matching
mode, in which the alias string
can only be *.
"*" will match all the valid X.121
addresses.
• Attributes related to the address code block in calling or called packets
As defined in the X.25 protocol, a call packet must carry the information set of both the calling
DTE address (source address) and the called DTE address (destination address). This address
information set is called "address code block." In a call accept packet, some networks require
that both (the calling DTE address and the called DTE address) be carried, some networks
require that only one of the two be carried, and some others require that neither should be
carried. To adapt to the differences between various networks, make selections as required.
• Default upper layer protocol that X.25 bears
An X.25 call request packet includes a CUD field indicating the upper layer protocol type carried
over the X.25 protocol. When receiving an X.25 call, the device will check the CUD field in the
packet. If receiving a call carrying an unidentifiable CUD field, the router will deny it. However,
an upper layer protocol can be specified as the default protocol on the X.25. When X.25
receives a call with an unrecognizable CUD, it will treat it with the customized default upper
layer protocol.
• The user facility adding/removing function
The user facility adding and removing functions are applicable to only main interfaces. They
work as follows on a main interface:
{ The user facility adding function is applicable to only the incoming packets. With the function,
the main interface checks incoming call setup negotiation packets for the window size and
maximum packet size fields. If the two fields are carried, the packets are not processed; if
not, the two fields are added to the packets.
{ The user facility removing function is applicable to only the outgoing packets. With the
function, the main interface checks outgoing call-setup negotiation packets for the window
size and maximum packet size fields. If the two fields are not carried, the packets are not
processed; if the two fields are carried, they are removed before the packets are sent out.
Configuration procedure
To configure X.25 interface supplementary parameters:
Step Command Remarks
1. Enter system view.
system-view
N/A

Table of Contents

Other manuals for HPE FlexNetwork MSR Series

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the HPE FlexNetwork MSR Series and is the answer not in the manual?

HPE FlexNetwork MSR Series Specifications

General IconGeneral
BrandHPE
ModelFlexNetwork MSR Series
CategoryNetwork Router
LanguageEnglish

Related product manuals