Wednesday, February 8, 2017

Scenario 1: ODU0 non-convergence mode (Any->ODU0[->ODU1]->ODU2->OTU2)

This section describes the configuration process of the LOA board works in ODU0 non-convergence mode.

Legend Information

Figure 1 shows legend information about U2000 operations.
Figure 1 Legend Information

Application Diagram

Figure 2 lists the condition where the LOA board works in ODU0 non-convergence mode.
Figure 2 Position of the LOA in a WDM(OSN 6800 OR OSN 8800) system (Scenario 1: ODU0 non-convergence mode (Any->ODU0[->ODU1]->ODU2->OTU2))


Related:

When customized for North America unable to configure OSN1800.



Posted by at No comments:

Commissioning Procedure (OTN)

This section describes the general commissioning procedures for the OTN system.
The commissioning procedures for the equipment can be divided into two parts: optical power commissioning and network commissioning.
  • Optical power commissioning procedures individually commission the optical power values of NEs and boards based on the optical signal flow. They also remove the abnormal attenuation of lines or boards based on the requirements of optical power, and the gain and insertion losses of the boards.
  • Network commissioning procedures include the commissioning protection function, commissioning feature function, testing bit errors, and other functional commissioning operations at the network level.
 NOTE:
For the ASON network, the commissioning procedures and requirements refer to Automatic Commissioning Process and Commissioning Items for ASON Network.
Figure 1 and Figure 2 provides the general commissioning procedures.
Figure 1 General commissioning procedures for OptiX OSN 8800/OSN 6800

Figure 2 General commissioning procedures for OptiX OSN 3800


You can perform the commissioning and configuration during deployment of the equipment by using either the iManager U2000 (U2000 for short) or the OptiX iManager U2000 Web LCT (Web LCT for short). All the operations that can be performed on the Web LCT can be performed on the U2000. Compared with U2000, the Web LCT has lower requirements on the computer hardware and can be started quickly.
Table 1 lists the tasks for the commissioning and configuration during deployment.

Table 1 List of tasks for the commissioning and configuration during deployment
No. Task Mandatory/Optional Tool
1 Creating NEs in Batches. Mandatory U2000 or Web LCT
2 Creating Optical NEs. Mandatory U2000
3 Setting NE Power Consumption Threshold. Mandatory U2000
4 Uploading the NE Data. Mandatory U2000
5 Setting NE ID and IP. Mandatory U2000 or Web LCT
6 Synchronizing the NE Time with the U2000/Web LCT Server Manually. Mandatory U2000 or Web LCT
7 Setting Performance Monitoring Parameters of an NE. Mandatory U2000 or Web LCT
8 Setting Manually Extended ECC Communication. Perform this task when the network uses HWECC for communication and more than four Huawei equipment NEs use the extended ECC for communication. Optional U2000
Configuring IP over DCC. Perform this task when the network uses IP over DCC for communication. Optional U2000
Configuring OSI over DCC. Perform this task when the network uses OSI over DCC for communication. Optional U2000
10 Checking Network-Wide Software Version. Optional U2000
11 Configuring Boards. Mandatory U2000 or Web LCT
12 Creating Fiber Connections in Graphic Mode. Perform this task on the U2000. Mandatory on the U2000 U2000
13 Creating Single-Station Optical Cross-Connection. Perform this task when ROADM stations are configured on the actual network. Optional according to the network U2000 or Web LCT
14 Creating OCh Trails by Trail Search. Perform this task on the U2000. Mandatory on the U2000 U2000
15 Configuring the OSNR Detection Based on Optical Doctor. Perform this task on the U2000. Optional U2000
16 Commission optical power by using one of the following methods as required:
  • Commissioning Optical Power on Site
  • Remotely Commissioning Optical Power
NOTE:
This document uses a 40-channel system as an example to describe optical power commissioning. The optical power commissioning methods for an 80-channel system are similar. The main difference is that the 40-channel system and 80-channel system have different requirements on nominal single-wavelength optical power and single-wavelength incident optical power for OA boards.
 Mandatory U2000 or Web LCT
17 Configuring Services. Mandatory U2000
18 Configuring System Features. Mandatory U2000
19 Viewing Current Alarms on an NE and Removing Abnormal Alarms. Mandatory U2000 or Web LCT
20 Testing Protection Switching. Mandatory U2000
21 Testing Data Features. Mandatory U2000
22 Testing System Features. Mandatory U2000
23 Testing Ethernet Service Channels. Mandatory U2000
24 Configuring Orderwire of OTN System and Configuring the Orderwire Phone in an OCS System. Optional U2000 or Web LCT
25 Testing Orderwire Functions. Optional U2000 or Web LCT
26 Testing Bit Errors. Mandatory OTN analyzer or SDH analyzer
27 Checking the entire network against the Checklist for Commissioning During Deployment. Ensure that the network configurations are correct. Mandatory U2000 or Web LCT
28 Backing Up the NE Database to the SCC Board.
Related:

How to Use the Ethernet Test Frames on the OptiX OSN 6800?

Posted by at No comments:
Labels: , ,

Configuration Procedures

Six port working modes are available for the LOA board on the NMS. The port for the None (not for ports) mode does not require configurations. The other five modes require configurations.

General Configuration Procedure

In the flowchart, the mandatory actions are required for each port working mode and optional actions vary according to port working modes.
The optional actions must be configured in the following scenarios:
  • Configure the port type: Port Type must be set to Client Side Color Optical Port when colored optical signals are received on the client side.
  • Configure the timeslot configuration mode: ODU Timeslot Configuration Mode must be set for the line side of the LOA board.
    • When the signal flow is from ODU0 or ODUflex to ODU2, ODU Timeslot Configuration Mode must be set to Assign random.
    • When the signal flow is ODU0 -> ODU1 -> ODU2, ODU Timeslot Configuration Mode must be set to Assign consecutive.
    • When the signal flow is from Any or ODU1 to ODU2 directly, ODU Timeslot Configuration Mode can be set to Assign consecutive or Assign random. However, the value must be the same as the value that is set on the interconnected LOA or line board.
  • Configure the service mode: When Service Type is set to OTU1, Service Mode must be set to OTN Mode first.
  • Configure the ODUflex tolerance(ppm): when the port of the TOA board works in ODUflex mode, this parameter can be configured. This parameter is reserved and optional in configuring service types which are currently supported.
  • Configure cross-connections from the client side to LP ports: This action is required only for the ODU0 non-convergence mode and ODU1 convergence mode.
The following describes the configuration procedure and involved parameter settings for each mode.
  • Table 1 describes the configuration procedure for the ODU0 non-convergence mode.
  • Table 2 describes the configuration procedure for the ODU1 non-convergence mode.
  • Table 3 describes the configuration procedure for the ODU1_ODU0 mode.
  • Table 4 describes the configuration procedure for the ODUflex non-convergence mode.
  • Table 5 describes the configuration procedure for the ODU2 non-convergence mode.

Configuration Procedure for the ODU0 Non-Convergence Mode

Table 1 Configuration procedure
No. Action Description
1 Configure the port working mode. Optional
  • Parameter settings: The default value of Port Working Mode is ODU0 non-convergence mode (Any->ODU0[->ODU1]->ODU2->OTU2). If the default value is used, skip this step.
  • Operation description: For details about the configuration procedure, see Configuring the Working Mode.
2 Configure the port type. Optional
  • Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port.
  • Operation description: For details about the configuration procedure, see Modifying Port.
3 Configure the timeslot configuration mode. Optional
  • Parameter settings: The value of ODU Timeslot Configuration Mode varies according to the two signal flows in the ODU0 non-convergence mode.
    • When the signal flow is Any->ODU0->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign random.
    • When the signal flow is Any->ODU0->ODU1->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign consecutive.
  • Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the the dropdown list. Set ODU Timeslot Configuration Mode for the WDM side port.
4 Configure the service type. Mandatory
  • Parameter settings: The available values for Service Type are FE, GE(TTT-GMP), GE(GFP-T), STM-1/OC-3, STM-4/OC-12, FC100, ESCON, FICON, FDDI, SDI, and DVB-ASI.
  • Operation description: For details about the configuration procedure, see Configuring the Service Type.
NOTE:
Two channels (channel 1 and channel 2) are available at each LP port. Set the service type for only one of the two channels. When the LOA board is interconnected with a TN52TOM board, the channel where you set the service type must be the same as the channel where the service type is set on the TN52TOM board. When the LOA board is interconnected with another board, set the service type for channel 1.
5 Configure cross-connections from the client side to LP ports on the LOA board. Mandatory
  • Parameter settings:
    • Level and Service Type:
      • If you set Service Type to GE in step 4, retain the default value (GE) for Level.
      • If you set Service Type to a value other than GE in step 4, set Level to Any and then set Service Type to the same value that you set in step 4.
    • Direction: Set it to Bidirectional.
    • Source Slot/Sink Slot: Set the two parameters to the ID of the slot where the LOA board is housed.
    • Source Optical Port: Set it to a port in the range of 3(RX1/TX1) to 10(RX8/TX8).
    • Source Optical Channel: Set it to 1.
    • Sink Optical Port: Set it to a port in the range of 201(ClientLP1/ClientLP1) to 208(ClientLP8/ClientLP8). Ensure that the client-side port matches an LP port. That is, if you set the source optical port to RXi/TXi, set the sink optical port to ClientLPi.
    • Sink Optical Channel: 1 or 2. Set it to the channel for which you configure the service type in step 4.
  • Operation description: Configure cross-connections from the client side to each LP port. For details about the configuration procedure, see Creating Cross-Connections.
6 Configure ODU0-level cross-connections from LP ports to the WDM side on the LOA board. Mandatory
  • Parameter settings: See Table 6.
  • Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.

Configuration Procedure for the ODU1 Non-Convergence Mode

Table 2 Configuration procedure
No. Action Description
1 Configure the port working mode. Mandatory
  • Parameter settings: Set Port Working Mode to ODU1 non-convergence mode (OTU1/Any->ODU1->ODU2->OTU2).
  • Operation description: For details about the configuration procedure, see Configuring the Working Mode.
2 Configure the port type. Optional
  • Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port.
  • Operation description: For details about the configuration procedure, see Modifying Port.
3 Configure the timeslot configuration mode. Optional
  • Parameter settings: Set ODU Timeslot Configuration Mode to Assign consecutive or Assign random.
  • Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the dropdown list. Set ODU Timeslot Configuration Mode for the WDM side port.
4 Configure the service mode. Optional
  • Parameter settings: The default value of Service Mode is Client Mode. When you set Service Type to OTU1, set Service Mode to OTN Mode.
  • Operation description: For details about the configuration procedure, see Configuring the Service Mode.
5 Configure the service type. Mandatory
  • Parameter settings: The available values for Service Type are HDSDI, HDSDIRBR, FC200, FICON Express, OTU1, STM16, or OC-48.
  • Operation description: For details about the configuration procedure, see Configuring the Service Type.
6 Configure ODUk-level cross-connections from LP ports to the WDM side on the LOA board. Mandatory
  • Parameter settings: See Table 6.
  • Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.

Configuration Procedure for the ODU1_ODU0 Mode

Table 3 Configuration procedure
No. Action Description
1 Configure the port working mode. Mandatory
  • Parameter settings: Set Port Working Mode to ODU1_ODU0 mode (OTU1->ODU1->ODU0[->ODU1]->ODU2->OTU2).
  • Operation description: For details about the configuration procedure, see Configuring the Working Mode.
2 Configure the port type. Optional
  • Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port.
  • Operation description: For details about the configuration procedure, see Modifying Port.
3 Configure the timeslot configuration mode. Optional
  • Parameter settings: The value of ODU Timeslot Configuration Mode varies according to the two signal flows in the ODU1_ODU0 mode.
    • When the signal flow is OTU1->ODU1->ODU0->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign random.
    • When the signal flow is OTU1->ODU1->ODU0->ODU1->ODU2->OTU2, set ODU Timeslot Configuration Mode to Assign consecutive.
  • Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the the dropdown list. Set ODU Timeslot Configuration Mode for the WDM side port.
4 Configure the service mode. Mandatory
  • Parameter settings: Set Service Mode to OTN Mode.
  • Operation description: For details about the configuration procedure, see Configuring the Service Mode.
5 Configure the service type. Mandatory
  • Parameter settings: The available values for Service Type is OTU1 only.
  • Operation description: For details about the configuration procedure, see Configuring the Service Type.
6 Configure ODUk-level cross-connections from LP ports to the WDM side on the LOA board. Mandatory
  • Parameter settings: See Table 6.
  • Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.

Configuration Procedure for the ODUflex Non-Convergence Mode

Table 4 Configuration procedure
No. Action Description
1 Configure the port working mode. Mandatory
  • Parameter settings: Set Port Working Mode to ODUflex non-convergence mode (Any->ODUflex->ODU2->OTU2).
  • Operation description: For details about the configuration procedure, see Configuring the Working Mode.
NOTE:
When the RX1/TX1 port receives the FC800 service, set Port Working Mode to ODUflex non-convergence mode (Any->ODUflex->ODU2->OTU2) only for port LP1. And set Port Working Mode to None (not for ports) for the other seven LP ports.
2 Configure the port type. Optional
  • Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port.
  • Operation description: For details about the configuration procedure, see Modifying Port.
3 Configure the timeslot configuration mode. Mandatory
  • Parameter settings: The default value of ODU Timeslot Configuration Mode is Assign random. If the default value is used, skip this step.
  • Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the the dropdown list. Set ODU Timeslot Configuration Mode to Assign random for the WDM side port.
4 Configure the service type. Mandatory
  • Parameter settings: The available values for Service Type are 3GSDI, 3GSDIRBR, FC-400, or FC-800. FC-800 is only for the RX1/TX1 port.
  • Operation description: For details about the configuration procedure, see Configuring the Service Type.
NOTE:
  • The FICON4G service and the FC400 service are processed identically. For the FICON4G service, you can configure it as the FC400 service on the U2000.
  • The FICON8G service and the FC800 service are processed identically. For the FICON8G service, you can configure it as the FC800 service on the U2000.
5 Configure the ODUflex tolerance(ppm). Optional
  • Parameter settings: For the transmission of 3G-SDI services, set this parameter to 10; for the transmission of other services, set this parameter to 100.
  • Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface > Advanced Attributes from the Function Tree. In the displayed window, set ODUflex tolerance(ppm) for the required ports.
6 Configure ODUk-level cross-connections from LP ports to the WDM side on the LOA board. Mandatory
  • Parameter settings: See Table 6.
  • Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.

Configuration Procedure for the ODU2 Non-Convergence Mode

Table 5 Configuration procedure
No. Action Description
1 Configure the port working mode. Mandatory
  • Parameter settings: Before setting Port Working Mode to ODU2 non-convergence mode (Any->ODU2->OTU2) for port LP1, set to None (not for ports) for the other seven LP ports.
  • Operation description: For details about the configuration procedure, see Configuring the Working Mode.
2 Configure the port type. Optional
  • Parameter settings: The default value of Port Type is Client Side Grey Optical Port. If colored optical signals are received on the client side, set Port Type to Client Side Color Optical Port.
  • Operation description: For details about the configuration procedure, see Modifying Port.
3 Configure the timeslot configuration mode. Mandatory
  • Parameter settings: Set ODU Timeslot Configuration Mode to Assign random or Assign consecutive.
  • Operation description: In the NE Explorer, select the LOA board and choose Configuration > WDM Interface from the Function Tree. Click By Function and choose ODU Timeslot Configuration Mode from the the dropdown list. Set ODU Timeslot Configuration Mode for the WDM side port.
4 Configure the service type. Mandatory
  • Parameter settings: Set Service Type to FC800 only for the RX1/TX1 port.
  • Operation description: For details about the configuration procedure, see Configuring the Service Type.
5 Configure ODUk-level cross-connections from LP ports to the WDM side on the LOA board. Mandatory
  • Parameter settings: See Table 6.
  • Operation description: Configure cross-connections from each LP port to the WDM side. For details about the configuration procedure, see Creating Cross-Connections.
Related:

End-to-End GE Services Cannot Be Created on the OptiX OSN 6800


Posted by at No comments:
Labels: ,

Tuesday, February 7, 2017

(Optional) Configuring the Overseas Parameters

By default, the overseas parameters are configured according to the Chinese standards. In the actual service configuration, the attributes such as the upper and lower thresholds of the flash-hooking duration can be configured according to the local standards to ensure that the response of the user terminal complies with the local standards. Thunder-link provide OLT, MA5683T, MA5680T

Procedure

  1. Run the oversea parameters command to configure the overseas parameters.
  2. Run the display oversea parameters command to check whether the overseas parameters are the same as those in the data plan.

Example

To set the upper flash-hooking threshold (overseas feature parameter 0) to 800 ms (in compliance with the Hong Kong standard) and the lower flash-hooking threshold (overseas feature parameter 1) to 100 ms (in compliance with the Hong Kong standard), do as follows:
huawei(config)#oversea parameters 0 800
huawei(config)#oversea parameters 1 100
huawei(config)#display oversea parameters
{ <cr>|name<U><0,99> }:                                                          
                                                                                
  Command:                                                                      
          display oversea parameters                                            
  ----------------------------------------------------------------------------- 
  Parameter name index: 0     Parameter value: 800                              
  Mean: Hooking upper threshold(ms), reference: China:350, HongKong:800         
  ----------------------------------------------------------------------------- 
  Parameter name index: 1     Parameter value: 100                               
  Mean: Hooking lower threshold(ms), reference: China:100, HongKong:100         
  ----------------------------------------------------------------------------- 
  Parameter name index: 2     Parameter value: 0                                
  Mean: Flag of applying PARKED LINE FEED or not when user port is locked, 0:not
 apply, 1:apply                                                                 
  ----------------------------------------------------------------------------- 
  Parameter name index: 3     Parameter value: 0                                
  Mean: The detect time of flash upper limit to onhook, default value: 0ms      
  ----------------------------------------------------------------------------- 
  Parameter name index: 4     Parameter value: 0                                
  Mean: DTMF Detector Tuning, 0:Q.24, 1:Russia                                  
----------------------------------------------------------------------------- 
  Parameter name index: 5     Parameter value: 0                                
  Mean: Flag of changing TEI value for software switch, 0:no change, 1:set TEI  
value to 1, 2:set TEI value to 0. Default: 0                                    
  ----------------------------------------------------------------------------- 





Related:



What’s the Failure of I-Type PDU Backplane on MA5600T due to Overcurrent


















Posted by



at





No comments:
  


















Labels:
,
,

























(Optional) Configuring the System Parameters












This topic describes how to configure the system parameters including the 
overseas version flag and message waiting indication (MWI) mode according to the 
local standards to ensure that the response of the user terminal complies with 
the local standards. Thunder-link where you can buy OLT, DSLAM there.







Procedure


    

  1. Run the system parameters command to configure the 
system parameters. 

    2. 

  2. Run the display system parameters command to check 
whether the system parameters are the same as those in the data plan. 

    3. 









Example

To configure the overseas version flag (system parameter 1) to Hong Kong 
(parameter value 1), do as follows:


huawei(config)#system parameters 1 1                      
huawei(config)#display system parameters 1
  ----------------------------------------------------------------------------- 
  Parameter name index: 1     Parameter value: 1                                
  Mean: Overseas version flag, 0:China, 1:HongKong, 2:Brazil, 3:Egypt, 4:       
Singapore, 5:Thailand, 6:France, 7:Britain MSFUK, 8:Britain ETSI, 9:Bulgaria,   
10:Reserved, 11:Austria, 12:Hungary, 13:Poland                                  
  ----------------------------------------------------------------------------- 
















Posted by



at





No comments:
  


















Labels:
,

























(Optional) Configuring Digitmap for SIP Interfaces 












The digitmap, also called number list, refers to the dialing plan on the 
access gateway (AG), which is used to detect and report dialing events received 
at the termination point. The digitmap defines number collection rules. It 
allows dialing events to be reported by groups, which reduces signaling 
exchanges between the AG and IMS.Thunder-link support MA5683T, MA5680T







Prerequisites





 NOTICE: 


The digitmap configuration is relatively complicated. The information such as 
the meanings and usage of the characters in a digitmap is defined in the 
protocol, and is not described here. This topic provides only some basic 
information. You are advised to refer to digitmap description in SIP standard 
before configuring a digitmap.














Context


    

  • Different digitmaps are required for different services. A digitmap group 
includes different digitmaps, providing customized digitmaps to accommodate to 
users' requirements. In this way, signaling exchanges are reduced between the AG 
and IMS.

    • 

  • A digitmap consists of digit and character strings. When the received 
dialing sequence matches one of the character strings, you can infer that all 
numbers are received.

    • 

  • The priority sequence of the digitmap is: user digitmap group > interface 
digitmap group > global local digitmaps. If a digitmap group used by a user 
does not have corresponding digitmaps, this user does not have the corresponding 
digitmaps. For example, digitmap group A is configured in user attributes, and 
digitmap group B is configured in the interface of the user. Besides, two-stage 
out-group digitmaps are not specified in digitmap group A, but two-stage 
out-group digitmaps are specified in digitmap group B. When digitmaps are used, 
the user does not load any two-stage out-group digitmaps because digitmap group 
A with a highest priority does not have two-stage out-group digitmaps (although 
two-stage out-group digitmaps are specified in digitmap group B and local 
digitmaps have two-stage out-group digitmaps). If the user cannot find any 
user-level or interface-level digitmap groups, the user uses global local 
digitmaps.

    • 

  • If digitmaps are not configured, the system provides a default digitmap for 
the user, in which all telephone numbers can be matched.
    • 


Table 1 provides the 
characters defined in the SIP protocol for digitmaps. For details, refer to the 
SIP standard, which provides a better guide to the digitmap configuration.







Table 1 SIP digitmap format




Digit or Character

Description






0-9

Indicates dialed digits 0-9. 




A-D

-




E

Indicates the asterisk (*) in dual tone multiple frequency (DTMF) 
mode.




F

Indicates the pound key (#) in DTMF mode.




X

Indicates a wildcard, which is a digit ranging from 0 to 9.




S

Indicates the short timer. After the timer times out; that is, the dialing 
plan matching is complete, the system reports numbers one by one if numbers 
remain.




L

Indicates the long timer. After the timer times out; that is, the dialing 
plan matching is complete, the system reports numbers one by one if numbers 
remain.




Z

Indicates duration modifier, which is a dialing event with a long duration. 
The dialing event is located in front of the event symbol with a specified 
position. When the duration of the dialing event exceeds the threshold, the 
dialing event satisfies this position.




.

Indicates that 0 or multiple digits or characters can exist before this 
character.




|

Is used to isolate character strings. Each character string is a selectable 
dialing plan.




[]

Indicates that one of the digits or characters in the square bracket is 
selected.














Procedure


    

  • Configure a digitmap. 

      

    1. In global configuration mode, run the local-digitmap 
add command to add a local preset digitmap. 

      2. 

    2. (Optional) In SIP mode, run the 
digitmap-timer(sip) command to configure a digitmap 
timer. 
      3. 

    

    • 

  • Configure a digitmap group. 

      

    1. In global configuration mode, run the 
local-digitmap add command to add a local preset 
digitmap. 

      2. 

    2. (Optional) In SIP mode, run the 
digitmap-timer(sip) command to configure a digitmap 
timer. 

      3. 

    3. Run the local-digitmap-group add 
command to add a digitmap group. 

      4. 

    4. Run the local-digitmap-group 
include command to add local digitmap members to the digitmap 
group. 


The new digitmap group takes effect only when the user uses it in the next 
call.
      


      


      5. 

    5. Run the mg-digitmap-group command 
to configure the digitmap group used by the interface. The new digitmap group 
takes effect only when the user uses it in the next call. 

      6. 

    6. Run the sippstnuser attribute set 
command to configure the digitmap group used by the user. The new digitmap group 
takes effect only when the user uses it in the next call. 

      7. 

    

    • 









Example

For example, according to the data plan, digitmap group 1 is applied to users 
connected to the 0/6/0 port in the SIP interface. The digitmap group includes 
normal digitmaps and emergency digitmaps, whose formats are 8882xxxx and 
8000xxxx respectively.


huawei(config)#local-digitmap add huawei normal 8882xxxx sip
huawei(config)#local-digitmap add huawei1 emergency 8000xxxx sip
huawei(config)#local-digitmap-group add DigitmapGroup1
huawei(config)#local-digitmap-group include DigitmapGroup1 huawei
huawei(config)#local-digitmap-group include DigitmapGroup1 huawei2
huawei(config)#interface sip 1
huawei(config-if-sip-1)#mg-digitmap-group DigitmapGroup1
huawei(config-if-sip-1)#quit
huawei(config)#esl user
huawei(config-esl-user)#sippstnuser attribute set 0/6/0 cliptransseq digitmap-group DigitmapGroup1




Related:

















Posted by



at





No comments:
  


















Labels:
,

















          

        

          

        

Monday, February 6, 2017


          

        









The MSTP Configuration of stp root












Function Description

The multiple spanning tree protocol (MSTP) applies to the redundant network. 
MSTP is an improvement of STP and RSTP. MSTP prevents the proliferation and 
infinite cycling of the packets in the loop network. In addition, MSTP provides 
multiple redundant paths for VLAN data transmission to achieve the load-sharing 
purpose. The MA5680T/MA5683T/MA5608T supports MSTP, 
which is compatible with the STP and RSTP. It supports MSTP loop network that 
helps meet various networking requirements.






Function



The stp root command is used to set the current device as 
the root bridge of a specified spanning tree instance or to back up the root 
bridge. The tree network topology must have a root. When you need to specify the 
root of the spanning tree instance, run this command. After the current device 
is set as a root bridge, the current device is the root of the spanning tree and 
the device transmits Bridge Protocol Data Unit (BPDU) packets to the exterior at 
intervals. 


The undo stp root command is used to cancel setting the 
current device as the root bridge of a specified spanning tree instance or to 
back up the root bridge. When you need to renew the root bridge after the 
network topology is changed, run this command. After the setting of the current 
device as the root bridge is canceled, the role of the current device in the 
current topology is changed.




 NOTE: 


After the current device is set as a root bridge or a root bridge is backed 
up, the system priority of the device will be automatically changed to the 
default setting, and users are not allowed to modify the system priority of the 
device. 












Format



stp [ instance instance-id ] 
root { primary | secondary } 



undo stp [ instance instance-id ] 
root








Parameters











Parameter

Description

Value






instance instance-id

Indicates the spanning tree instance ID. The value 0 indicates the Common And 
Internal Spanning Tree (CIST) instance and other value indicate the Multiple 
Spanning Tree Instance (MSTI). 

Numeral type. Range: 0-16. 




primary

Sets the device as the root bridge of the specified spanning tree instance. 
When you need to set the device as the root bridge, use this parameter.

-




secondary

Sets the device as the backup root bridge of the specified spanning tree 
instance. When you need to set the device as the backup root bridge, use this 
parameter.

-














Modes



Global config mode








Level



Operator level








Usage Guidelines




    

  • By default, the device is neither a root bridge nor a backup root bridge. 

    • 

  • If you do not configure parameter instance 
instance-id, the configuration takes effect only on the CIST instance. 
If parameter instance-id is configured to 0, the current device is set 
as the root bridge or backup root bridge of CIST. 

    • 

  • One spanning tree instance can be configured with only one root bridge, but 
one or multiple backup root bridges. 

      

    • When the root bridge fails or is powered off, the backup root bridge is used 
as the root bridge of the specified spanning tree instance. 

      • 

    • Among multiple configured backup root bridges, the one with the smallest MAC 
address is used as the root bridge of the specified spanning tree instance. 

      • 

    

    • 

  • Root types the current device in different spanning tree instances are 
independent from each other. The current device can be the root bridge or backup 
root bridge in one or multiple spanning tree instances. In a spanning tree 
instance, a device cannot be root bridge and backup root bridge simultaneously. 

    
 NOTE: 

    

      

    • Do not configure one spanning tree instance with multiple root bridges. 
Otherwise, the calculation result will be unexpected. 

      • 

    • You can set the current device as the root of multiple spanning tree 
instances. You can set multiple backup roots for a spanning tree. 

      • 

    • Generally, it is recommended to specify a root and multiple backup roots for 
a spanning tree. 
      • 

    

    

    

    • 











Example



To set the current device as the root bridge of spanning tree instance 1, do 
as follows: 


huawei(config)#stp instance                                                     
{ INTEGER<0-16> }:1                                                          
{ priority<K>|root<K> }:root                                                    
{ primary<K>|secondary<K> }:primary                                             
                                                                                
  Command:                                                                      
          stp instance 1 root primary  

To set the current device as the backup root bridge of spanning tree instance 
2, do as follows: 


huawei(config)#stp instance                                                     
{ INTERGER<0-16> }:2                                                          
{ priority<K>|root<K> }:root                                                    
{ primary<K>|secondary<K> }:secondary                                           
                                                                                
  Command:                                                                      
          stp instance 2 root secondary  

To cancel setting the current device as the root bridge of spanning tree 
instance 1, do as follows:


huawei(config)#undo stp instance                                                
{ INTERGER<0-16> }:1                                                          
{ priority<K>|root<K> }:root                                                    
                                                                                
  Command:                                                                      
          undo stp instance 1 root  












System Response




    

  • The system does not display any message after the 
command is executed successfully.
    • 















Posted by



at





No comments:
  


















Labels:
,
,

















        

      









Subscribe to:
Posts (Atom)