Got it

AR Router Maintenance Guide-FAQ(Device Management)

Latest reply: Apr 12, 2018 15:03:06 2216 2 0 0 0

2.3  Device Management

2.3.1  Which Models of AR Series Routers Support PoE?

Currently, the following models and interfaces support PoE function:
  • Model: AR207V-P, AR201VW-P; Supporting interface: Ethernet0/0/0–Ethernet0/0/7
  • Model: AR151W-P; Supporting interface: Ethernet0/0/0–Ethernet0/0/3
  • Model: AR1220V, AR1220W, and AR1220VW; Supporting interface: Ethernet0/0/4–Ethernet0/0/7
  • Model: AR1220EV, AR1220EVW; Supporting interface: GigabitEthernet0/0/4–GigabitEthernet0/0/7
  • Model: AR169-P-M9, AR169W-P-M9, AR169RW-P-M9, AR161FW-P-M5; Supporting interface: GigabitEthernet0/0/0–GigabitEthernet0/0/3
  • Model: AR2204-48GE-P, AR2204-51GE-P, AR2204-27GE-P; Supporting interface: GigabitEthernet0/0/3–GigabitEthernet0/0/10

2.3.2  How Many Ports Can Mirror Traffic to One Observing Port?

AR series routers allow multiple ports to mirror traffic to one observing port. There is no limit to the number of ports. The traffic mirrored to the observing port, however, cannot exceed the maximum forwarding traffic of the observing port, namely, maximum bandwidth of the observing port.

2.3.3  If Mirroring Is Configured on the Main Interface, Will the Traffic of the Sub-interface Be Mirrored to the Observing Port?

Yes.

2.3.4  Can an Interface Be Configured as a Mirroring Port and an Observing Port at the Same Time?

An interface cannot be configured as a mirroring port and an observing port at the same time. This is because the mirroring port and the observing port are exclusive.

2.3.5  Can Mirrored Packets Be Saved?

Yes. Run the capture-packet command to configure the packet capturing function. The packets captured can be displayed directly on a terminal or be stored in the storage media of the device.

2.3.6  How Are Log Files Saved?

The log files are saved when a storage device such as a Flash memory, a USB flash drive or an SD card is available.

In the user view, run the save logfile command to save log files.

2.3.7  Can I Configure the Path for Storing Log Files of AR Series Routers?

By default, the log files of AR1200 series routers are stored on the USB flash drive, and the log files of AR2200, AR3600, and AR3200 are stored on the SD card. If USB flash drive or SD card is unavailable, log files cannot be stored.
6711c418de1945a6a6d6c41745fe9374 NOTE:

From V200R005C10, the log files of AR1200 series are saved in the flash memory by default.

The AR3600 series routers are released from V200R006C10.

Run the info-center logfile path command to configure the path where log files are stored.

2.3.8  How Can I View Log Information?

  • Run the display logbuffer command to view log information in the log buffer.

  • Run the display logfile command to view log information in the log files.

2.3.9  Which File System Do AR Series Routers Support for USB Flash Drives and SD Cards?

The AR series routers support only the FAT32 file system for USB flash drives and SD cards.

2.3.10  How Can I Check the Fan Software on the AR2240, AR3670 and AR3260?

Run the display version slot fan command to view the fan software. The Software Version field indicates the software version.
6711c418de1945a6a6d6c41745fe9374 NOTE:

The AR3600 (SRUX5) series routers are released from V200R006C10.

2.3.11  When Different Types of SRUs Are Installed on AR2240 or AR3200, Must Different System Software Versions Be Used to Match these SRUs?

You do not need to use different system software versions to match different SRUs. The same system software is used on no matter which type of SRU is installed. This is true for AR3200.

2.3.12  Are Spaces Allowed in the ESN of an AR Router?

A space in an ESN of an AR router is an invalid character.

2.3.13  Why Cannot Command Line Operation Logs Be Displayed in the Log Buffer and How Can These Logs Be Displayed in the Log Buffer?

By default, only warning logs are displayed in the log buffer. Command line operation logs are at the notifications level, which is lower than warning. Therefore, command line operation logs will not be displayed in the log buffer.

To view command line operation logs in the log buffer, perform the following operations:

  1. Run the system-view command to enter the system view.
  2. Run the info-center source default channel logbuffer log level notifications command to allow logs of the notifications level to be displayed in the log buffer.

2.3.14  Why Cannot an AR Router Send Trap Messages?

SNMP provides the trap function to control the output of trap messages. An AR router generates trap messages only when the trap function has been enabled on the AR router.

Perform the following operations to enable the trap function on an AR router:

  1. Run the system-view command to enter the system view.
  2. Run the snmp-agent trap enable command to enable the AR router to send trap messages to the NMS.
  3. Run the snmp-agent target-host trap-paramsname paramsname v1 securityname securityname [ binding-private-value ] [ trap-filterprofilename filterprofilename ] [ private-netmanager ] command to set parameters for sending trap messages.
    6711c418de1945a6a6d6c41745fe9374 NOTE:
    • V200R001C01 and later versions support binding-private-value.
    • V200R002C00 and later versions support private-netmanager.
  4. Run the snmp-agent target-host trap-hostname hostname address ipv4-addr [ udp-port udp-portid ] [ public-net | vpn-instance vpn-instance-name ] trap-paramsname paramsname command to specify the destination host for receiving trap messages and error codes.
    6711c418de1945a6a6d6c41745fe9374 NOTE:

    The default destination UDP port number is 162. To ensure secure communication between the NMS and managed devices, run the udp-port command to change the UDP port number to a non-well-known port number.

2.3.15  How Can I Check the Reason that a Board Is Reset?

Run the display reset-reason command to check whether a board is reset actively or passively.
  • If the message "Reason: A link fault fails to be rectified." is displayed, the board is actively reset.
  • If the preceding message is not displayed, the board is passively reset.

2.3.16  How Can I Check the Running Duration of a Board?

Run the display version command in any view. The message "LPU X: uptime is X week, X day, X hour, X minutes" is displayed next to each board version information list. This message indicates the running duration of the board. For example, if "LPU 2 : uptime is 0 week, 0 day, 6 hours, 1 minute" is displayed, LPU 2 has been running for 6 hours and 1 minutes after registration.

2.3.17  How Can I View the Working Mode of a Board That Supports Working Mode Switchover?

Run the display workmode command in any view to view the board working mode of a specified slot or all slots.

2.3.18  Device Startup Failure Causes and Solutions

Common Cause Solution

When you press Ctrl+B to display the BootROM menu, the router fails to start. After entering the BootROM menu to complete the configuration, directly restart the router or restart the router using a specified system software. If you do not restart the router, the router remains in suspended state. As a result, the router fails to start.

Check whether the system software is correct. If not, configure correct system software and restart the router.

The system software does not exist or is damaged.

Contact technical support personnel.

The BootROM is damaged.

Initialization fails.

There are other causes such as hardware and power supply problems.

2.3.19  What Is the PoE Output Voltage of AR1200 Series?

The PoE output voltage is 48 V. The standard PD converts 48 V voltage into its voltage, and a non-standard PD must connect to a PoE splitter to convert 48 V voltage into its voltage.

2.3.20  How Do I Make an Index File for USB-based Deployment?

Before using a USB flash drive to configure the router, check whether the index file of the USB flash drive exists. You can edit the index file to perform deployment.

To edit the index file on the PC, perform the following operations:
  1. Create a text file.
  2. Edit the index file.
  3. Save the .txt file as USB_AR.ini.
  4. Copy the USB_AR.ini file to the root directory of the USB flash drive.

In versions earlier than V200R005C00, the format of the index file for USB-based deployment is as follows:

BEGIN AR
[USB CONFIG]
SN=
EMS_ONLINE_STATE=
[UPGRADE INFO]
OPTION=
AUTOFLAG=
PASSWORD=
DEVICENUM=
[DEVICEn DESCRIPTION]
OPTION=
ESN=
MAC=
VERSION=
DIRECTORY=
FILENUM=
TYPEn=
FILENAMEn=
END AR

In V200R005C00 and later versions, the format of the index file for USB-based deployment is as follows:

BEGIN AR
[USB CONFIG]
SN=
EMS_ONLINE_STATE=
[UPGRADE INFO]
OPTION=
DEVICENUM=
[DEVICEn DESCRIPTION]
OPTION=
ESN=
MAC=
VERSION=
DIRECTORY=
FILENUM=
TYPEn=
FILENAMEn=
HMACn=
END AR
Table 2-33  Fields in the index file

Field

Description

BEGIN AR

Start tag of the index file. This field cannot be modified.

USB CONFIG

USB flash drive configuration. This field cannot be modified.

SN

Data change time in the format YearMonthDay.HourMinuteSecond.

For example, the value 20110628.080910 indicates 2011-06-28 00:09.

NOTE:
The SN field is a USB-based deployment flag. A device has a default USB-based deployment flag. If the USB_AR.ini file exists in the USB flash drive, the device checks whether the default USB-based deployment flag and the SN value in the USB_AR.ini file are the same. If they are different, the USB-based deployment process is triggered. If the deployment succeeds, the value of the default USB-based deployment flag on the device is changed to the SN value in the USB_AR.ini file.

EMS_ONLINE_STATE

Indicates whether the NMS is online. The options are as follows:
  • YES: The NMS is online.
  • NO: The NMS is offline.

UPGRADE INFO

Upgrade information header. This field cannot be modified.

OPTION

Upgrade mode flag. The field has a fixed value of AUTO.

AUTOFLAG

Whether password authentication is performed:
  • 0: password authentication is not performed.
  • 1: password authentication is performed.
NOTE:

This field is supported in versions from V200R002C01 to versions earlier than V200R005C00..

PASSWORD

Authentication password in USB-based deployment. This parameter is mandatory when the value of AUTOFLAG is 1. The password must be the same as the password configured using the set usb autoupdate password command. The value is a string of 1 to 64 characters without spaces.

NOTE:

This field is supported in versions from V200R002C01 to versions earlier than V200R005C00.

DEVICENUM

Number of devices to be upgraded using this index file.

  • To upgrade the software version of one device, set the value of the DEVICENUM field to 1 and use the device's ESN and MAC address.

  • To upgrade software versions of multiple devices to the same version, set the value of the DEVICENUM field to 1 and use the default ESN and MAC address.

  • To upgrade software versions of multiple devices to different versions, set the value of the DEVICENUM field to the number of devices to be upgraded and use devices' ESNs and MAC addresses.

DEVICEn DESCRIPTION

Description information header of device n. The value of n is an integer that ranges from 1 to 100.

NOTE:
The value n must be set when you make the index file.

OPTION

This field determines whether USB-based deployment is required for the device. The value OK indicates that USB-based deployment is required, and the value NOK indicates that USB-based deployment is not required.

ESN

Serial number of a device. If the value of this field is DEFAULT, the index file is applicable to all devices. Otherwise, the index file is applicable to a specific device.

NOTE:

If this field is left empty, this field matches all devices.

MAC

MAC address of a device. If the value of this field is DEFAULT, the index file is applicable to all devices. Otherwise, the index file is applicable to a specific device.

NOTE:

If this field is left empty, this field matches all devices.

VERSION

Version number after the upgrade.

NOTE:

If the software version is unknown, set this field to any value.

DIRECTORY

Path for storing deployment files.
  • If the value is DEFAULT, the deployment files are stored in the root directory of the USB flash drive.
  • If the value is /abc, the deployment files are stored in the abc directory.
NOTE:

If this field is left empty, the deployment files are saved in the root directory of the USB flash drive.

FILENUM

Number of files to be loaded.

If only the system software needs to be loaded, the value of this field is set to 1. If the system software and patch file need to be loaded, the value of this field is set to 2.

TYPEn

Upgrade file type. The options are as follows:
  • SYSTEM-SOFTWARE: system software.
  • SYSTEM-CONFIG: configuration file.
    NOTE:

    If the device supports the voice function and works as a PBX, the configuration file is SYSTEM-CONFIG_PBX.

    If the device supports the voice function and works as a SIPAG, the configuration file is SYSTEM-CONFIG_AG.

  • SYSTEM-PAT: patch file.
  • SYSTEM-LICENSE: license file.
  • SYSTEM-VOICE: voice file.
  • USER-DEFINE: user-defined file.

The value of n starts from 1.

FILENAMEn

Upgrade file name. For example, if the value of the TYPE1 field is SYSTEM-SOFTWARE and the name of the system software corresponding to the U disk is system-software.cc, the value of the FILENAME1 field is system-software.cc.

The value of n starts from 1.

HMACn

HMAC used to verify a file to be downloaded. The MAC is a 64-byte character string that is calculated for a specific file using a file checker based on the HMAC-SHA256 algorithm. The key used to calculate the HMAC must be the same as the password configured by the set usb autoupdate password command.

The value of n starts with 1.

NOTE:

This field is optional and supported in V200R005C00 and later versions.

END AR

End tag of the index file.

2.3.21  Board Registration Failure Troubleshooting

  1. Check whether the board is installed properly.

    Run the display device command to check whether the Online field is Present. If not, the board is not installed properly. Reinstall the board or install the board into another slot.

  2. Check whether the board is compatible with the device version.

    Run the display elabel command to check the BOM field of the board. You can determine whether the board is compatible with the device version based on the value of the BOM field. If the board is compatible with the device version, upgrade the device version.

  3. If the fault persists, contact technical support personnel.

2.3.22  Does the AR Support Periodical Transmission of Logs to the Log Host?

No, the AR does not support periodical transmission of logs to the log host. However, the AR can send logs to the log host.

2.3.23  Can Several AR Routers Send Logs to the Same Log Host?

Yes, several AR routers can send logs to the same log host.

2.3.24  Can a PC Running the Windows Operating System Be Used as a Log Host?

Yes, a PC running the Windows operating system can be used as a log host only when it has third-party software installed such as Kiwi Syslog Daemon.

2.3.25  Mirroring Functions Supported by the Device

6711c418de1945a6a6d6c41745fe9374 NOTE:

Some personal communication information may be collected or stored to detect transmission faults and errors. Huawei cannot collect or store user communication information without permission. It is recommended that relevant functions used to collect or store user communication information be enabled under applicable laws and regulations. During user communication information collection and storage, measures must be taken to protect user communication information.

The device supports the following two types of mirroring functions:

  • Port mirroring

    A packet passing through a mirrored interface is copied and then sent to a specified monitoring device for analysis and monitoring. All packets passing through the mirrored interface are copied.

  • Flow mirroring

    A packet passing through a mirrored interface and matching a traffic classification rule is copied and then sent to a specified monitoring device for analysis and monitoring. A traffic policy matching flow mirroring is applied to the mirroring interface, and packets matching traffic classification rules on the mirrored interface are copied.

6711c418de1945a6a6d6c41745fe9374 NOTE:

The device does not provide packet parsing, and packet capture software is required to parse packets.

2.3.26  How Do I Obtain the ESN of the Device?

The Electronic Serial Number (ESN) of the device is unique. The ESN of the device is required when you request a license. You can run the display esn command to view the ESN of the device.

2.3.27  How Do I Disable the Information Center?

Run the undo info-center enable command in the system view to disable the information center. After the undo info-center enable command is executed, logs including logs generated by the undo info-center enable command, traps, and debugging messages are not recorded.

2.3.28  How Do I Solve the DHCP Configuration Loss Problem After Device Restart?

After the device restarts, there is a low probability that the DHCP configuration is lost.

Auto-Config is enabled by default. About two and a half minutes after the device restarts, the Auto-Config module checks whether the configuration file exists and determine whether the Auto-Config process is executed. If the save command is used at this time, files conflict. As a result, the Auto-Config module determines that the configuration file does not exist, and incorrectly executes the Auto-Config process. In this case, information about option fields or intermediate file required for executing the Auto-Config process is not configured on the DHCP server. Consequently, the Auto-Config process is suspended, and the DHCP configuration (including the configuration during configuration recovery and the Auto-Config process) is deleted.

After the device restarts, run the undo autoconfig enable command in the system view to disable Auto-Config.

2.3.29  Changes of Local Port Mirroring Commands

Starting from V200R002C00, observe-port-index is deleted from observe-port [ observe-port-index ] interface interface-type interface-number and port-mirroring to observe-port observe-port-index { both | inbound | outbound }.

V200R001

Command used to configure an observing interface: observe-port [ observe-port-index ] interface interface-type interface-number

Command used to configure a mirrored interface: port-mirroring to observe-port observe-port-index { both | inbound | outbound }

To configure local port mirroring, perform the following operations:
  1. Run the system-view command to enter the system view.
  2. Run the observe-port [ observe-port-index ] interface interface-type interface-number command to configure a local observing interface.
  3. Run the interface interface-type interface-number command to enter the view of a specified interface.
  4. Run the port-mirroring to observe-port observe-port-index { both | inbound | outbound } command to configure a local mirrored interface.

V200R002 and Later Versions

Command used to configure an observing interface: observe-port interface interface-type interface-number

Command used to configure a mirrored interface: mirror to observe-port { both | inbound | outbound }

To configure local port mirroring, perform the following operations:
  1. Run the system-view command to enter the system view.
  2. Run the observe-port interface interface-type interface-number command to configure a local observing interface.
  3. Run the interface interface-type interface-number command to enter the view of a specified interface.
  4. Run the mirror to observe-port { both | inbound | outbound } command to configure a local mirrored interface.

2.3.30  Mapping between modules and IDs

You can use display memory-alloc mid command to check the memory allocated to a module. The mapping between modules and IDs is as follows
Table 2-34  Mechanism Module
Module ID Module ID Module ID Module ID Module ID Module ID Module ID Module ID Module ID
VOS_PID_SYS 0x0 IAS_PID_RESERVE9 0x1f IAS_PID_RESERVE62 0x3e PID_OAM 0x5d PID_PUB 0x7c PID_DMM 0x9b PID_PCCW_CPE 0xba PID_MSC 0xd9 PID_ATMPING 0xfb
VOS_PID_TIMER 0x1 VOS_SMP_PID_CLI 0x20 PID_ATTM 0x3f IAS_PID_RESERVE94 0x5e PID_VCM 0x7d PID_SDP 0x9c PID_NETCONF 0xbb PID_NETSW 0xda PID_TCM 0xfc
VOS_PID_SYSMT 0x2 VOS_PID_EXEC 0x21 PID_PSCM 0x40 IAS_PID_RESERVE95 0x5f PID_H248STACK 0x7e PID_TPA 0x9d PID_WEB 0xbc PID_BPUB 0xdb PID_STM1 0xfd
VOS_PID_HTMAILS 0x3 VOS_PID_LINE 0x22 PID_SFWD_DELIVERY 0x41 PID_RTM 0x60 PID_H248SP 0x7f PID_VIFM 0x9e PID_AUTOBACKUP 0xbd PID_IDXCONV 0xdc PID_E1T1 0xfe
VOS_PID_ADAPT 0x4 VOS_PID_MODEM 0x23 PID_ALM 0x42 PID_VRPFIB 0x61 IAS_PID_RESERVE128 0x80 PID_VCFG 0x9f PID_SFTPC 0xbe PID_ETH 0xdd PID_ET1 0xff
VOS_PID_BAK 0x5 VOS_PID_VTY 0x24 PID_MS 0x43 PID_SOCK 0x62 PID_SNTPC 0x81 PID_VRM 0xa0 PID_VMS 0xbf PID_XPON 0xde PID_EMUL_STANDBY 0x100
VOS_PID_SMOOTH 0x6 VOS_PID_CFGPLANE 0x25 PID_TEST 0x44 PID_CRB 0x63 PID_DNSC 0x82 PID_R2RS 0xa1 PID_GPONONU 0xc0 PID_GEM 0xdf PID_XDSLNNI 0x101
VOS_PID_ARBAGNT 0x7 IAS_PID_RESERVE38 0x26 PID_INFC 0x45 PID_IF 0x64 IAS_PID_RESERVE131 0x83 PID_R2CFG 0xa2 PID_VPRODUCT 0xc1 PID_AGG 0xe0 PID_PBXBCM 0x102
VOS_PID_ARBSERV 0x8 VOS_PID_PING 0x27 PID_SNMP 0x46 PID_MAP 0x65 IAS_PID_RESERVE132 0x84 PID_BULK 0xa3 PID_VMIF 0xc2 PID_VETH 0xe1 PID_PBXSCM 0x103
VOS_PID_DBKNL 0x9 VOS_PID_TELNET 0x28 PID_MPM 0x47 PID_FC 0x66 IAS_PID_RESERVE133 0x85 PID_E2E 0xa4 PID_VARP 0xc3 PID_ETHRM 0xe2 PID_PBXSSM 0x104
VOS_PID_DDMS 0xa VOS_PID_TRACERT 0x29 IAS_PID_RESERVE72 0x48 PID_L2TP 0x67 PID_DISPATCH 0x86 PID_XDSL 0xa5 PID_SYSCFG 0xc4 PID_L2SS 0xe3 PID_PBXCCM 0x105
VOS_PID_Monitor 0xb VOS_PID_CFM 0x2a IAS_PID_RESERVE73 0x49 PID_UCM 0x68 PID_L2UA 0x87 IAS_PID_RESERVE166 0xa6 PID_VPM 0xc5 PID_L2QOS 0xe4 PID_PBXUCC 0x106
VOS_PID_PATCH 0xc PID_NTP 0x2b IAS_PID_RESERVE74 0x4a PID_SCM 0x69 PID_SCTP 0x88 IAS_PID_RESERVE167 0xa7 PID_ETHOAM 0xc6 PID_SFWD_SEND 0xe5 PID_PBXTAM 0x107
VOS_PID_PATCHLOAD 0xd VOS_PID_CLIPROXY 0x2c PID_PAT 0x4b PID_AAA 0x6a PID_QOSTST 0x89 PID_SIPDSS1 0xa8 PID_PDT 0xc7 PID_ATM 0xe6 PID_PBXSDB 0x108
VOS_PID_INSPECT 0xe VOS_PID_DIAG 0x2d PID_DBG 0x4c PID_LAM 0x6b PID_VSNAP 0x8a PID_VOLC 0xa9 PID_PDT 0xc8 PID_SIPSP 0xe7 PID_PBXRM 0x109
VOS_PID_HM 0xf PID_BRD 0x2e IAS_PID_RESERVE77 0x4d PID_RDS 0x6c PID_VTRACE 0x8b PID_VAM 0xaa PID_EPONMDU 0xc9 PID_SIPDMM 0xe8 PID_AT0 0x10a
VOS_PID_MCC 0x10 PID_PHY 0x2f PID_LOAD 0x4e PID_RT_POLICY 0x6d PID_VSTAT 0x8c PID_MAD 0xab PID_VFS 0xca PID_SIPCOM 0xe9 PID_SIPDLG 0x10b
PID_NTPC 0x11 PID_BCM 0x30 PID_E1T1 0x4f PID_RT_RIP 0x6e PID_AMDF 0x8d PID_L3 0xac PID_SRM 0xcb PID_SIPEM 0xea PID_DSP 0x10c
PID_SNTPS 0x12 IAS_PID_RESERVE49 0x31 PID_SYN 0x50 PID_RT_OSPF 0x6f PID_PG 0x8e PID_L2P 0xad PID_LICENSE 0xcc PID_SIPMP 0xeb PID_CWMP 0x110
PID_SNTPC 0x13 IAS_PID_RESERVE50 0x32 PID_FTP 0x51 PID_RT_SHOW 0x70 PID_UNM 0x8f PID_L2M 0xae PID_PDT 0xcd PID_SIPPA 0xec PID_FM 0x111
VOS_PID_TFTP 0x14 PID_DB 0x33 PID_ML 0x52 PID_L2 0x71 PID_AUTOLOAD 0x90 PID_H248PA 0xaf PID_PDT 0xce PID_SIPSTACK 0xed PID_POTS_DRV 0x112
VOS_PID_VFS 0x15 PID_DCM 0x34 PID_V5MNGT 0x53 PID_PER 0x72 PID_PS 0x91 PID_PTOPO 0xb0 PID_PDT 0xcf PID_SFWD_SETCAP 0xee PID_AT0_DRV 0x113
VOS_PID_ZIP 0x16 PID_DEV 0x35 PID_LCFSM 0x54 PID_IMA 0x73 PID_MIRO 0x92 IAS_PID_RESERVE177 0xb1 PID_PDT 0xd0 PID_DDM 0xf2 PID_ALLMODULE 0x114
IAS_PID_RESERVE1 0x17 PID_PM 0x36 PID_LCTRL 0x55 PID_TRACE 0x74 PID_TI 0x93 PID_CLK 0xb2 PID_PDT 0xd1 PID_BRDXPONNNI 0xf3 VOS_PID_BUTT 0x115
IAS_PID_RESERVE2 0x18 PID_SPC 0x37 PID_BCC 0x56 PID_EMM 0x75 PID_MIF 0x94 PID_BTV 0xb3 PID_ANCP 0xd2 PID_CICM 0xf4 N/A N/A
IAS_PID_RESERVE3 0x19 PID_CM 0x38 PID_PSTN 0x57 PID_MBSIMAN 0x76 IAS_PID_RESERVE149 0x95 PID_IC 0xb4 PID_PDT 0xd3 PID_RMM 0xf5 N/A N/A
IAS_PID_RESERVE4 0x1a PID_XPOA 0x39 PID_CTRL 0x58 PID_CIMAICP 0x77 PID_NTE 0x96 PID_CFM 0xb5 PID_PDT 0xd4 PID_OLC 0xf6 N/A N/A
IAS_PID_RESERVE5 0x1b PID_LACP 0x3a PID_RSRC 0x59 PID_CIMAFSM 0x78 PID_MGCPSP 0x97 PID_SSH 0xb6 PID_PDT 0xd5 PID_AMPPUB 0xf7 N/A N/A
IAS_PID_RESERVE6 0x1c PID_PPP 0x3b PID_PROT 0x5a PID_ADSLM 0x79 PID_MGCPREG 0x98 PID_RSA 0xb7 PID_PDT 0xd6 PID_BTVTM 0xf8 N/A N/A
IAS_PID_RESERVE7 0x1d PID_RM 0x3c PID_V5FR 0x5b PID_OAMDRV 0x7a PID_MGCPCFG 0x99 PID_HA 0xb8 PID_CFGR 0xd7 PID_VSPPDT 0xf9 N/A N/A
IAS_PID_RESERVE8 0x1e IAS_PID_RESERVE59 0x3d PID_IAD 0x5c PID_E3DRV 0x7b PID_MGCPSTACK 0x9a PID_HM 0xb9 PID_OMSHL 0xd8 PID_BBADP 0xfa N/A N/A
Table 2-35  Service Module
Module ID Module ID Module ID Module ID Module ID Module ID Module ID Module ID Module ID Module ID
DOPRA_MID_START 0x00000000 MID_TRUNK_ADP 0xFF090000 MID_QOS 0xFF210000 MID_DCC_PKT 0xFF380000 MID_SYSMANMIB 0xFF520000 MID_VASP_SECLOG 0xFF6D0000 MID_VASP_ADP 0xFF830000 MID_VASP_SVPN_UM 0xFF980000 MID_LLDPADP 0xFFFD0000 MID_IMA_SM 0xFFA80000
VRP_MID_STAR 0XC0000000 MID_CX_DRV_ADP_MAC 0xFF0A0000 MID_QOSADP 0xFF220000 MID_MIRR 0xFF390000 MID_MODEM_PDT 0xFF530000 MID_VASP_ASPF 0xFF6E0000 MID_NS_ADP 0xFF840000 MID_VASP_SVPN_WP 0xFF990000 MID_TIME 0xFFFE0000 MID_IMA_PM 0xFFA90000
MID_PPPOE 0XC0070000 MID_TRAFSTAT 0xFF0B0000 MID_IPMCMFIB 0xFF230000 MID_SACL 0xFF3A0000 MID_AAA 0xFF5A0000 MID_VASP_FILTER 0xFF6F0000 MID_VASP_MNG 0xFF850000 MID_VASP_SVPN_FS 0xFF9A0000 MID_AMPADP 0xFFFF0000 MID_IMA_GSHDSL 0xFFB20000
MID_PPPOE_CLIENT 0XC0080000 MID_VLANSWITCH 0xFF0C0000 MID_ADP_MCAST 0xFF240000 MID_XOT 0xFF3B0000 MID_RADIUS 0xFF5B0000 MID_VASP_STAT 0xFF700000 MID_VRPADP_CLI 0xFF860000 MID_VASP_SVPN_PF 0xFF9B0000 MID_ISDN_CC_PDT 0xFF260000 MID_IMA_ICP 0xFFAF0000
MID_PPP 0XC04A0000 MID_HIG 0xFF100000 MID_MCAST 0xFF250000 MID_WAN 0xFF400000 MID_TAC 0xFF5C0000 MID_VASP_NAT 0xFF710000 MID_ARLOG 0xFF870000 MID_VASP_SVPN_IF 0xFF9C0000 MID_ISDN_Q931_PDT 0xFF270000 MID_IMA_ADP 0xFF580000
MID_NETSTREAM 0XC04C0000 MID_DEFEND 0xFF110000 MID_ISDN_CC 0xFF260000 MID_AREM 0xFF410000 MID_AM 0xFF5D0000 MID_LB 0xFF720000 MID_MNODE 0xFF880000 MID_IPSI 0xFF9D0000 MID_ISDN_Q921_PDT 0xFF280000 MID_WWAN 0xFF3D0000
MID_PPP_MP 0XC04F0000 MID_ADP_MSTP 0xFF120000 MID_ISDN_Q931 0xFF270000 MID_CDEV 0xFF420000 MID_SAM 0xFF5E0000 MID_VASP_IPSEC 0xFF730000 MID_SIMU 0xFF890000 MID_DLSW 0xFF9E0000 MID_CHDLCADP 0xFF290000 MID_WWAN_PDT 0xFF540000
MID_HWCM 0XC0550000 MID_LDT 0xFF130000 MID_ISDN_Q921 0xFF280000 MID_ECM 0xFF430000 MID_EAPOL 0xFF5F0000 MID_VASP_ACLADA 0xFF740000 MID_DIAGNOSE 0xFF8A0000 MID_DLSW_LLC2 0xFF9F0000 MID_FRADP 0xFF2A0000 MID_MODEM_PDT 0xFF530000
MID_ACL 0XC06C0000 MID_CX_DRV_ADP_STP 0xFF140000 MID_CHDLCADP 0xFF290000 MID_POE 0xFF440000 MID_PORTAL 0xFF600000 MID_DHCPSNP 0xFF750000 MID_PHY 0xFF8B0000 MID_SDLC 0xFFA00000 MID_L2TP 0xFF340000 MID_DLSW 0xFF9E0000
MID_ENTITYMIB 0xC0DC0000 MID_CX_DRV_ADP_IBC 0xFF150000 MID_FRADP 0xFF2A0000 MID_ATM_ADP 0xFF450000 MID_TM 0xFF610000 MID_WEB 0xFF760000 MID_ENTITY_TRAP 0xFF8C0000 MID_DAR 0xFFA10000 MID_DCC 0xFF360000 MID_DLSW_LLC2 0xFF9F0000
MID_ENTITYEXTMIB 0xC0DD0000 MID_ADP_RRPP 0xFF160000 MID_L3ADP_MAIN 0xFF2B0000 MID_UDPH 0xFF460000 MID_DHCP 0xFF620000 MID_DNSE 0xFF770000 MID_SUPT 0xFF8D0000 MID_VOICE 0xFFF10000 MID_DCC_PKT 0xFF380000 MID_SDLC 0xFFA00000
MID_IFNET 0xCFF00000 MID_GVRP 0xFF170000 MID_L3ADP_IO 0xFF2C0000 MID_UDPH_IO 0xFF470000 MID_CM 0xFF630000 MID_FRQOS 0xFF780000 MID_ADA_BFD 0xFF8E0000 MID_CWMP_ADP 0xFFF20000 MID_PPP 0xC04A0000 MID_WEBSERVER 0x40010000
IPOS_MID_START 0XD0000000 MID_ADP_GVRP 0xFF180000 MID_NDADA 0xFF2D0000 MID_MPLS_PRODUCT_IO 0xFF480000 MID_VASP_FW 0xFF640000 MID_NHRP 0xFF790000 MID_BFDSEC 0xFF8F0000 MID_WLAN_PDT 0xFFF30000 MID_PPP_MP 0xC04F0000 MID_NETCONF 0x40020000
MID_RESERVED_FOR_PRODUCT_START 0xFF000000 MID_BPDUADP 0xFF190000 MID_MPLS_PRODUCT 0xFF2E0000 MID_LED 0xFF490000 MID_VASP_ALP 0xFF650000 MID_RTPRO_MLDSNPG 0xFF7B0000 MID_DRVIVER 0xFF900000 MID_L2IF 0xFFF50000 MID_PPPOE 0xC0070000 PID_WEB 188
MID_L2IFPPI 0xFF010000 MID_CXL2IF 0xFF1A0000 MID_QINQAGT 0xFF310000 MID_S7800E_VOS_ADPT 0xFF4A0000 MID_VASP_FW_AGE 0xFF660000 MID_ETHADP 0xFF7C0000 MID_FM_9300 0xFF910000 MID_CLKSRC 0xFFF60000 MID_PPPOE_CLIENT 0xC0080000 PID_NETCONF 187
MID_L2ADP 0xFF020000 MID_GFPI 0xFF1B0000 MID_ELAB 0xFF320000 MID_VCONSOLE 0xFF4B0000 MID_VASP_PAM 0xFF670000 MID_DDNS 0xFF7D0000 MID_FMCK_9300 0xFF920000 MID_DFT 0xFFF70000 MID_WAN 0xFF400000 N/A N/A
MID_MAC_SYN 0xFF030000 MID_FECD_MBUF 0xFF1C0000 MID_HEM 0xFF330000 MID_FACT 0xFF4C0000 MID_VASP_FWDBG 0xFF680000 MID_VOS_IPC 0xFF7E0000 MID_PKI 0xFF930000 MID_CX_DRV_ADP_INIT 0xFFF80000 MID_ATM_ADP 0xFF450000 N/A N/A
MID_IFPDT 0xFF050000 MID_SECE 0xFF1D0000 MID_L2TP 0xFF340000 MID_LOAD_AUTOLOAD 0xFF4D0000 MID_VASP_BLS 0xFF690000 MID_ADPT_MAIN 0xFF7F0000 MID_L3ADP_NDADA_MB 0xFF940000 MID_SSMPADP 0xFFF90000 MID_LAPB_AR 0xFF560000 N/A N/A
MID_IFADP 0xFF060000 MID_ACLE 0xFF1E0000 MID_FORWARD 0xFF350000 MID_ENVMON 0xFF4F0000 MID_VASP_WLS 0xFF6A0000 MID_ADPT_IO 0xFF800000 MID_L3ADP_NDADA_IO 0xFF950000 MID_AUTOCFG 0xFFFA0000 MID_X25_AR 0xFF570000 N/A N/A
MID_IFAGT 0xFF070000 MID_MQC 0xFF1F0000 MID_DCC 0xFF360000 MID_MEM 0xFF500000 MID_VASP_ZONE 0xFF6B0000 MID_BRIDGE 0xFF810000 MID_VASP_SSLA 0xFF960000 MID_AR_RMON 0xFFFB0000 MID_XOT 0xFF3B0000 N/A N/A
MID_IMS 0xFF080000 MID_IB_BACKUP 0xFF200000 MID_DDRS 0xFF370000 MID_MTR 0xFF510000 MID_VASP_SECATK 0xFF6C0000 MID_MON 0xFF820000 MID_VASP_SVPN_CM 0xFF970000 MID_AR_RMON2 0xFFFC0000 MID_RTA 0xFF590000 N/A N/A

2.4  Interface Management

From group: Router
  • x
  • convention:

WoodWood
Created Aug 30, 2017 04:04:02

:)
View more
  • x
  • convention:

wissal
MVE Created Apr 12, 2018 15:03:06

clear and useful document, thanks
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.