Subnet2296 Rnc Rnciur v309

Template RNC GroundTemplate VV3.09

MODIND USERLABEL MCC MNC PROVER

Modify Indication User Label MCC MNC

A,D,M,P STRING o to 999 o to 999

Can't be empty

A DF2R 262 3 R7A DF3R 262 3 R7A RN1R 262 3 R7A RN2R 262 3 R7A DF21R 262 3 R7A DF22R 262 3 R7

Protocol Version

R4,R5,R6,R7

A:Add,D:Delete,M:Modify,P:Pass

This is a user-defined ID, which consists of no more than 40 characters.

If more than one MCC, separate each value by ";".

If more than one MNC, separate each value by ";".

For the CN office, R7 is recommended.The RNC office must be the same as the peer.

Parameters can be modified

NEID ANI NET DPC

Net Element ID Adjacent office ID Net type No Signaling point code

0 to 65535 0 to 512 NET1 to NET8

2126 4 NET1 3.45.12136 5 NET1 3.45.22016 6 NET1 3.40.02026 7 NET1 3.40.12226 8 NET1 3.46.02256 9 NET1 3.46.1

3.8.3 or 8.8.8 format,decimal

If RNC then 0 to 4095If MGW then 4096 to 65535If other office then 0 to 4095

When the lower-layer bearer is ATM and the NE type is CN/RNC, the Office ID 7 corresponding to the AAL2 adjacent office in the ATM office configuration must be the same.When the lower-layer bearer is IP and the NE type is CN/RNC, the adjacent NE derives from the Office ID configured for the adjacent office signaling point.

This field usually uses the default value at the RNC side. For local configuration, a maximum of 8 signaling points can be created, corresponding to network 1 to network 8. NET1 is recommended.

This is an interconnection parameter, which must remain the same as the peer setting.


NETYPE DOMAINTYPE SPTYPE SSF

Office type Domain type Signaling point type Sub-service field

SEP,STP,STEP

RNC SCN;ATM STEP NATIONAL SPCRNC SCN;ATM STEP NATIONAL SPCRNC SCN;ATM STEP NATIONAL SPCRNC SCN;ATM STEP NATIONAL SPCRNC IP;IP STEP NATIONAL SPCRNC IP;IP STEP NATIONAL SPC

RNC,MGW,MSCSERVER,SGSN,MSCSERVER+MGW,MSCSERVER+SGSN,SGSN+MGW,MSCSERVER+SGSN+MGW

SCN,IP,SCN;ATM,SCN;IP,IP;ATM,IP;IP

International SPC,Reserved international SPC,National SPC,Reserved National SPC

R4) where the MGW is separated from the MSCSERVER.3. MGW: connected with another MGW for use in the scenario (that is, R4) where the MGW is separated from the MSCSERVER.4. SGSN: connected with another SGSN for use.5: MSCSERVER+MGW: connected with the CS office for use in the scenario (that is, R99) where the MGW is integrated with the MSCSERVER as a whole office.6: MSCSERVER+SGSN: applicable when the MSCSERVER and SGSN share one signaling point. One of the NEs serves as the signaling transfer point.7: SGSN+MGW: applicable when the MGW and SGSN share one signaling point. One of the NEs serves as the signaling transfer point.8.

Depend on the actual situation. If the adjacent office and the local office are connected by means of ATM signaling, the signaling point of the adjacent office is in the SCN domain. In the case of IP connection, the signaling point of the adjacent office is in the IP domain.

SEP: Signaling End Point,STP: Signaling Transfer Point,STEP: Signaling Transfer/End PointSTEP is recommended.

International SPC: international network, with a code of 0x00H in the signaling.Reserved international SPC: reserved international network, with a code of 0x04H in the signaling,National SPC: national network, with a code of 0x08H in the signaling,Reserved National SPC: reserved national network, with a code of 0x0CH in the signaling.Fill in this field according to the real situation.


SPCTYPE AM ATMADDR

20 bytes, separate each byte with ".", decimal


SPC 14 BITS ASSOCIATED MODE 69.73.23.128.16.99.18.0.15.0.0.0.0.0.0.0.0.0.0.0SPC 14 BITS ASSOCIATED MODE 69.73.23.128.16.99.19.0.15.0.0.0.0.0.0.0.0.0.0.0SPC 14 BITS ASSOCIATED MODE 69.73.23.128.16.99.1.0.15.0.0.0.0.0.0.0.0.0.0.0SPC 14 BITS ASSOCIATED MODE 69.73.23.128.16.99.2.0.15.0.0.0.0.0.0.0.0.0.0.0SPC 14 BITS ASSOCIATED MODESPC 14 BITS ASSOCIATED MODE

Signaling point code type

Connection with local signaling point

ATM address(Decimal)

SPC 14 bits,SPC 24 bits

Associated Mode,Quasi-associated Mode

Depend on the real situation.

This field identifies whether the local office and the adjacent office are directly associated or quasi-associated in terms of signaling relation. Associated Mode means there are directly connected signaling links between the local office and the adjacent office. Quasi-associated Mode means there is no directly connected signaling link between the local office and the adjacent office, and they need one signaling transfer point or more in between. If the RNC and MSC are connected through transfer of the MGW, Quasi-associated Mode should be used.Fill in this field according to the real situation.

Fill in this field according to the real situation.Decimal format for each byte.



RNCRCPMODULE CSDEFAULTFLAG CSCAPWEIGHT CSNRIBITNUM

RNC home module

3 to 82 YES, NO 0 to 100 0 to 10

3 0 0 03 0 0 03 0 0 03 0 0 03 0 0 03 0 0 0

Default Office Flag in CS Domain

Capacity Weight in CS Domain

Network Resource Identifier Bit Num in CS Domain

When the destination office is of the RNC type, this field is valid, and the adjacent RNC must be homed to a certain CMP.

Valid only when the NE type is MSCSERVER, and uses NO when invalid. Of all the valid records corresponding to this field, there is one and only one record with a field value of YES, indicating the CS domain must have one and only one default office.

Valid in the case of IUFLEX networking. This field is valid only when the NE type is MSCSERVER, and uses 0 invariably when invalid, indicating disabling of the IU FLEX function of the corresponding CN.

Valid in the case of IUFLEX networking. This field is valid only when the NE type is MSCSERVER, and uses 0 invariably when invalid, indicating disabling of the IU FLEX function. In all the valid records corresponding to this field, the values of this field must be the same, that is, the CsNriBitNums of all the offices in the CS must be the same.



CSNRINUM CSNRI PSDEFAULTFLAG PSCAPWEIGHT

0 to 4 0 to 1023 YES, NO 0 to 100

0 65535;65535;65535;655 0 00 65535;65535;65535;655 0 00 65535;65535;65535;655 0 00 65535;65535;65535;655 0 00 65535;65535;65535;655 0 00 65535;65535;65535;655 0 0

Number of Network Resource Identifier in CS Domain

CS domain network resouce ID

Default Office Flag in PS Domain

Capacity Weight in PS Domain

Valid in the case of IUFLEX networking. This field is valid only when the NE type is MSCSERVER, and uses 0 invariably when invalid.

Valid in the case of IUFLEX networking. As an interconnection parameter, this parameter will appear in the TMSI allocated to the UE by the network.Separate each value by ";".

Valid in the case of IUFLEX networking. This field is valid only when the NE type is SGSN, and uses NO invariably when invalid. In all the valid records corresponding to this field, there is one and only one record with a field value of YES, indicating the CS domain must have one and only one default office.

Valid in the case of IUFLEX networking. This field is valid only when the NE type is SGSN, and uses 0 invariably when invalid.




PSNRIBITNUM PSNRINUM PSNRI Abbreviated Name

Parameter Name

0 to 10 0 to 4 0 to 1023 Parameter Value

Description

Remark

0 0 65535;65535;65535;655350 0 65535;65535;65535;655350 0 65535;65535;65535;655350 0 65535;65535;65535;655350 0 65535;65535;65535;655350 0 65535;65535;65535;65535

Network Resource Identifier Bit Num in PS Domain

Number of Network Resource Identifier in PS Domain

PS domain network resouce ID

Valid in the case of IUFLEX networking. This field is valid only when the NE type is SGSN, and uses 0 invariably when invalid, indicating disabling of the IU FLEX function. In all the valid records corresponding to this field, the values of this field must be the same, that is, the PsNriBitNums of all the offices in the PS must be the same.

Valid in the case of IUFLEX networking. This field is valid only when the NE type is SGSN, and uses 0 invariably when invalid.

Valid in the case of IUFLEX networking. As an interconnection parameter, this parameter will appear in the PTMSI allocated to the UE by the network.Separate each value by ";".




MODIND USERLABEL PVCID PVCSERVICE

Modify Indication User Label PVC ID PVC service Type

A,D,M,P STRING 1 to 12600

Can't be empty

A DF2R 11000 AAL5 SIGNALA DF2R 11001 AAL5 SIGNALA DF3R 11002 AAL5 SIGNALA DF3R 11003 AAL5 SIGNALA RN1R 11004 AAL5 SIGNALA RN1R 11005 AAL5 SIGNALA RN2R 11006 AAL5 SIGNALA RN2R 11007 AAL5 SIGNALA DF2R 11050 AAL2 DATAA DF2R 11051 AAL2 DATAA DF3R 11052 AAL2 DATAA DF3R 11053 AAL2 DATAA RN1R 11054 AAL2 DATAA RN1R 11055 AAL2 DATA

AAL5 Signal,AAL5 Data,AAL2 Data



As the unique identifier of one PVC in the RNC, this value cannot be repeated in the RNC.AAL5 Signal of IUCS is from 12000 to 12049AAL2 Data of IUCS is from 12050 to 12499AAL5 Signal of IUPS is from 12500 to 12509AAL5 Data of IUPS is from 12510 to 12599AAL5 Signal of IUR is from 11000 to 11049AAL2 Data of IUR is from 11050 to 11999

AAL5 Signal: the signaling over ATM,AAL5 Data: IUPS is the service over ATM,AAL2 Data: IUCS or IUR is the service over ATM.


A RN2R 11056 AAL2 DATAA RN2R 11057 AAL2 DATA

IFTYPE SUBSYSTEM UNIT CSUNIT

PVC interface type Subsystem No Unit No ATM Port No.

IUCS, IUPS, IUR 1 to 12 1 to 17

IUR 1 7 10IUR 5 8 10IUR 1 7 10IUR 5 8 10IUR 1 7 10IUR 5 8 10IUR 1 7 10IUR 5 8 10IUR 1 7 10IUR 5 8 10IUR 1 7 10IUR 5 8 10IUR 1 7 10IUR 5 8 10

IMAB: [1..30]SDTA: [14..43]APBI: [10..14]APBE: [4..7]APBE_2: [10..13]


This is the subsystem number of the interface board.

This is the slot number of the interface board.

ATM Port No. corresponds with the real physical port. For example, ATM Port No. 10 of APBE_2 corresponds with the first optical port.

IUR 1 7 10IUR 5 8 10

CVPI CVCI L2HSERVCATY

CVPI CVCI Service Type

1 to 511 1 to 65535 None.

7 46 CBR atmClpTran 30007 46 CBR atmClpTran 30007 47 CBR atmClpTran 30007 47 CBR atmClpTran 30007 44 CBR atmClpTran 30007 44 CBR atmClpTran 30007 45 CBR atmClpTran 30007 45 CBR atmClpTran 30008 46 CBR atmClpTran 90008 46 CBR atmClpTran 90008 47 CBR atmClpTran 90008 47 CBR atmClpTran 90008 44 CBR atmClpTran 90008 44 CBR atmClpTran 9000

L2HTRFTYPE

L2HTRFPARA1

Traffic Type

Peak cell rate for CLP=0+1(PCR0+1)(KBPS)

CBR, RTVBR, NRTVBR, ABR, UBR

atmClpTransparentNoScr,atmClpNoTaggingScrCdvt,atmNoClpNoScr

For the external CVPI/CVCI, this is unique in the office and must be identical to the value of the connected office. It is recommended to use a value smaller than or equal to 4.

For the external CVPI/CVCI, this is unique in the office and must be identical to the value of the connected office. It is recommended to use a value smaller than or equal to 256.

IU interface: CBR is recommended.IUR interface: CBR is recommended for signaling, while a combination of CBR and UBR is recommended for service.








8 45 CBR atmClpTran 90008 45 CBR atmClpTran 9000

ANI PATHGROUPID

Office ID PathGroup ID

None. None. None. None 1 to 512 0 to 2047

10000 0 0 0 410000 0 0 0 410000 0 0 0 510000 0 0 0 510000 0 0 0 610000 0 0 0 610000 0 0 0 710000 0 0 0 710000 0 0 0 4 200410000 0 0 0 4 200510000 0 0 0 5 200610000 0 0 0 5 200710000 0 0 0 6 200810000 0 0 0 6 2009

L2HTRFPARA2

L2HTRFPARA3

L2HTRFPARA4

L2HTRFPARA5

Traffic Description Parameter 2




Depend on the real situation. Usually, it’s SCR.

Depend on the real situation. Usually, it’s MBS.

Depend on the real situation. Usually, it’s CDVT.

Depend on the real situation. Usually, it’s CDVT.

This ID must be the same as the AAL2 adjacent office ID (ANI) configured in the RNC office configuration.

This ID is globally unique.



10000 0 0 0 7 201010000 0 0 0 7 2011

TRPATHID MODULE PATHID SERVICETYPE

AAL2 Traffic Path ID AAL2 Attached Module

32 to 127 3 to 83, 108 to 127 1 to 4160 RT,NRT1,NRT2,MIX

32 3 1 MIX33 4 2 MIX32 3 1 MIX33 4 2 MIX32 3 1 MIX33 4 2 MIX

AAL2 path intra-office S.N.

AAL2 Path Service Type

As the path ID of the AAL2 channel, this is globally unique and starts with 32 for the ATM office.

Select the number of the module to which this path is attached. The SMP module is recommended as the office of the IU/IUR interface.

As an interconnection parameter, this number must have the same configuration as the peer office.

RT: for bearing real-time service,NRT1: for bearing R99 non-real-time service,NRT2: for bearing HS non-real-time service,MIX: for bearing all types of service.RT is recommended for the IUCS interface.RT and MTX are recommended for the IUR interface.




32 3 1 MIX33 4 2 MIX

OWNER LINK SMPMODULE SLC

AAL2 Path Owner Signaling Link No Signaling Link code

1 to 9000 108 to 127 0 to 15

2004 124 02005 127 12006 124 02007 127 12008 124 02009 127 12010 124 02011 127 1

ADJACENT OFFICEADJACENT OFFICEADJACENT OFFICEADJACENT OFFICEADJACENT OFFICEADJACENT OFFICE

Signaling Link Attached Module

Local Office,Adjacent Office

If Local Office is configured, the AAL2 PATH ID will be allocated in the ascending order.If Adjacent Office is configured, the AAL2 PATH ID will be allocated in the descending order.For two interconnected RNCs, one end should be configured as the Local Office, while the other as the Adjacent Office.

This is a unique number inside the RNC

Just select the number of the module that manages this link. Now only the SMP module is available.

This field value is unique as the link of the same Office ID. For the signaling link of the same physical bearer, the signaling link code must have the same configuration as the peer office. As an interconnection parameter, this code must be compatible with the peer. Each office can have up to 16 signaling link codes.




ADJACENT OFFICEADJACENT OFFICE

DWDENIPADDR DTSUNIT Abbreviated Name

Destination IP address DT Unit-DT Sunit Parameter Name

IPV4 Parameter Value

Description

Remark

DT Unit: 1 to 17,DTB Sunit: 9 to 40SDTA/SDTB_2 Sunit: 9 to 71, 93 to 155

This is the IP address of the virtual peer interface board, and must be in the same network segment as the RNC interface board. This IP address is not an interconnection parameter. It is reflected in the binding relation between the ATM and IP, and has a 32-bit mask by default, which needs no modification.

The number of the slot where the DTB is located, the number of the E1 line inside the ATM access board. The ATM access board can accommodate 32 physical E1 lines or CSTM-1 fibers, each corresponding uniquely to one subunit number. The subunit number ranges from 9 to 71 and 93 to 155. Subunit 9 corresponds to the first physical E1 line, and the numbering rule follows the ascending order.Separate each value by ";".

MODIND OFFRTOFFICEID ROUTE_1 ROUTE_2

Modify Indication Adjacent office ID Normal Route No.

A,D,M,P 0 to 512 1 to 2000 1 to 2000

Can't be empty

A 4 4 0A 5 5 0A 6 6 0A 7 7 0

First Alternative Route No.


When the lower-layer bearer is ATM and the NE type is CN/RNC, the Office ID 7 corresponding to the AAL2 adjacent office in the ATM office configuration must be the same.When the lower-layer bearer is IP and the NE type is CN/RNC, the adjacent NE derives

This is the same as the Route Group No in the Create Local Route Info, that is, the shortest route to this office. We can adopt the signaling route number configured for the local RNC. If signalling domain type of neighbour office is IP, should leave blan



ROUTE_3 ROUTE_4 Abbreviated Name

Parameter Name

1 to 2000 1 to 2000 Parameter Value

Description

Remark

0 00 00 00 0

Second Alternative Route No.

Third Alternative Route No.



MODIND USERLABEL ASSOCID MODULE

Modify Indication User Label SCTP associating ID SMP Module ID

A,D,M,P STRING 2001 to 3000 108 to 127

Unique in RNC

Can't be empty

A DF21R 2226 127A DF22R 2256 127



If there are multiple SMPs and associations, these associations should be distributed evenly on each SMP.



OFFICEID PROPERTY LOCPORT REMPORT

Local-end port No Peer-end port No

1 to 512 Client,Server 1 to 65535 1 to 65535

8 CLIENT 2952 29529 CLIENT 2953 2953

Peer-end office of SCTP association

Application property of SCTP association

Enter the number of the office to which the association belongs according to the real situation.

For the two ends associated, at least one must serve as the Client.

This is the port number of the associated local end, and must be the same as the Peer-End Port No. configured for the associated peer end.

This is the port number of the associated local end, and must be the same as the Peer-End Port No. configured for the associated peer end.




LOCADDR1 REMADDR1 ASPID

Local-end IP address Peer-end IP address ASP ID

IPV4 IPV4 1 to 2048

Parameters can be modified Parameters can be modified

10.17.2.209;10.17.2.217 10.17.2.241;10.17.2.249 21210.17.2.209;10.17.2.217 10.17.2.225;10.17.2.233 215

This is the IP address 1 of the associated local end. For this address, one loop-back address must be configured first on the RPU, and here is chosen from the loop-back addresses configured on the RPU. Note that the IP1 and IP2 formats must be entered in the case of the multi-homing mode.

This is the IP address 1 of the associated peer end. This IP address is used by the peer end to terminate the signaling. Note that the IP1 and IP2 formats must be entered in the case of the multi-homing mode.

This is the ID number of the application server. One ASP corresponds to one and only one SCTP association, and one AS can have up to 16 ASPs.

MAXRTO MINRTO INITRTO HEARTBEAT

Max. value of RTO Minmum Value of RTO Heartbeat intervals

10 to 3000 10 to 1000 10 to 3000 10 to 6000

20 15 20 10020 15 20 100

Initialization value of RTO

This is the value of Max. value of RTO

This is the value of Minmum Value of RTO

This is the value of Initialization value of RTO

This is the value of Heartbeat intervals





DELAYACK Abbreviated Name

Delay ack time Parameter Name

0 to 20 Parameter Value

Description

Remark

1111

This is the value of Delay ack time


MODIND USERLABEL ASID ASPID

Modify Indication User Label AS ID ASP ID

A,D,M,P STRING 1 to 640 1 to 2048

Can't be empty

A DF21R 8 212A DF22R 9 215



Adopt the corresponding AS ID number

Separate each value by ";".


EXISTCONTEXT CONTEXTID TAG ASMODE

Routing context ID Traffic Mode Type

1 to 4294967295

FALSE 4294967295 IPSP CLIENT LOADSHAREFALSE 4294967295 IPSP CLIENT LOADSHARE

Whether routing context exists

APP Server AS Usage ID

TRUE, TRUE,TRUE, FALSE,FALSE, TRUE,FALSE, FALSE

SGP,ASP,IPSP SERVER,IPSP CLIENT,DOUBLE EXCHANGE MODEL

Loadshare,Override

Each group of values indicates whether the local end and the peer end are configured with routing context.Select TRUE if one ASP occurs to more than one AS, or select FALSE otherwise. In the RNC, one ASP usually occurs to one AS, so it is unnecessary to configure the routing context ID.

If one ASP occurs to more than one AS, it is necessary to specify which AS this message belongs to, that is, to specify the routing context. The routing context is used as a unique ID of an AS.

This is an interconnection parameter, so when the IUR and IU are interconnected, note that the two ends should be configured respectively as the IPSP Server and IPSP Client. Be sure to negotiate with the peer end for consistency to avoid configuration of both ends as the IPSP Server.If DOUBLE EXCHANGE MODEL is configured, the local end and the peer end are allowed to have different routing contexts.

There are two traffic modes: Loadshare and Override.N+K load sharing means the multiple ASPs in one AS are simultaneously in the service state, so that the messages can be transmitted through the ASPs in turn. The N value indicates the minimum number of ASPs that must be activated before the AS can be activated. The K value makes little sense now. Override means only one ASP is in the service state at certain time in one AS, while other ASPs are standing by and will substitute when the ASP in service breaks down. Select NO during normal running, or otherwise select YES for the test purpose.





MODEN MODEK ROUTEID ROUTEMODE

Route ID Mode

1 to 16 0 to 15 1 to 128

1 0 8 IKEBANA SORT1 0 9 IKEBANA SORT

N value of load sharing mode

K value of load sharing mode

Ikebana Sort,This Module Priority,Natural Sort

It is OK to select the default value, or as required, make the AS available only when multiple ASPs are activated.

With little sense, this value is not used now, and it is recommended to configure it to the difference between the total number of the associations and the N value.

Number the routes from 1. There are 128 M3UA routes at most.

Ikebana Sort: In the ASP list sorted in the background, the even-bit ASPs are sorted in the original order, while the odd-bit ASPs are sorted in the order reverse to the original.This Module Priority: The ASPs are resorted by means of the Ikebana Sort on the basis of the Natural Sort.Natural Sort: The ASPs are sorted in the order of entry.Ikebana Sort is recommended.




Abbreviated Name

Parameter Name

Parameter Value

Description

Remark

MODIND OFFICEID ROUTEID1 ROUTEID2Modify Indication Adjacent office ID Primary Route ID Secondary Route IDA,D,M,P 0 to 512 1 to 128 1 to 128

Can't be empty

A 8 8 0A 9 9 0


When the lower-layer bearer is ATM and the NE type is CN/RNC, the Office ID 7 corresponding to the AAL2 adjacent office in the ATM office configuration must be the same.When the lower-layer bearer is IP and the NE type is CN/RNC, the adjacent NE derives



Abbreviated NameParameter NameParameter Value

Description

Remark

MODIND USERLABEL PATHGROUPID FATHERID

Modify Indication User Label PathGroup ID

A,D,M,P STRING 2001 to 2047

Can't be empty

A DF21R 2030 65535A DF22R 2031 65535



This ID is unique in the RNC.


MODULE PATHGPBEARTYPE TXBITRATE

Home module Transport Path Bear Type

64 to 4000000


127 ETHERNET NOVLANTAG 300000127 ETHERNET NOVLANTAG 300000

Forword bandwidth(kbps)

Configure the actual physical bandwidth.



RXBITRATE Abbreviated Name

Parameter Name


Description

Remark

300000300000

Backward bandwidth(kbps)

Configure the actual physical bandwidth.


MODIND USERLABEL ANI TRPATHID

Modify Indication User Label ANI Path ID

A,D,M,P STRING 1 to 99 0 to 7

Can't be empty

A DF21R-1 8 1A DF21R-2 8 2A DF21R-3 8 3A DF22R-1 9 1A DF22R-2 9 2A DF22R-3 9 3



This value is unique in the RNC.

This ID is unique in the office.


PATHGROUPID DESTIPADDR IPNETMASK TXBITRATE

PathGroup ID

2001 to 2047 IPV4 STRING 64 to 1000000

2030 10.17.130.176 255.255.255.240 1000002030 10.17.130.192 255.255.255.240 1000002030 10.17.130.208 255.255.255.240 1000002031 10.17.130.128 255.255.255.240 1000002031 10.17.130.144 255.255.255.240 1000002031 10.17.130.160 255.255.255.240 100000

Destination service IP Address

Apply subnet mask to the IP address

Forward bandwidth(kbps)

This is a globally unique ID.

This is the service address of the peer office.

This field refers to the mask of the destination network number. This mask must start with consecutive binary 1, followed by 0 only. The network prefix and network mask must match each other, and the result of NOT mask AND prefix must be 0 (ip&~mask = 0).

If there is only one path in the path group, it is advised that this bandwidth should be identical to that of the path group. If there is more than one path, the bandwidth sum of all paths in the same path group should not exceed the bandwidth of the path group.





RXBITRATE Abbreviated Name

Parameter Name


Description

Remark

100000100000100000100000100000100000

Backword bandwidth(kbps)

If there is only one path in the path group, it is advised that this bandwidth should be identical to that of the path group. If there is more than one path, the bandwidth sum of all paths in the same path group should not exceed the bandwidth of the path group.


Subnet2296 Rnc Rnciur v309

Documents

modind modify indication

reserved international spc

network resource identifier

actual physical bandwidth

adjacent ne derives

atm access board

userlabel user label

aal2 adjacent office