₦airaland Forum

Issue Description
Which Switch Models Support the PoE Function?
Solution
Fixed switches

You can use the display device command to check a switch's product name and determine whether the switch supports the PoE function according to its product name.
• If the product name contains PWR, this switch model supports the PoE function.
• If the product name does not contain PWR, this switch model does not support the PoE function.
Modular switches
Among modular switches, only the Huawei S7700 series switches support the PoE function. The PoE card of an S7700 is ES0D0G48VA00.

Supports the MSTP protocol, featuring the loop protection function.
Supports the RRPP protocol, implementing rapid switching in a ring network.
Supports the LACP and inter-board aggregation features, increasing the bandwidth and providing the protection function.
Supports bidirectional forwarding detection (BFD), improving the reliability of IP applications (such as real-time voice service) and providing support to the network stability for service providers.
Supports the smart link application, which implements the redundancy backup and quick migration of active and standby links, ensuring the high reliability and high-speed convergence.
Supports Type B redundancy protection for the GPON, ensuring that the services are not interrupted when the backbone optical fiber is faulty.
Supports GPON Type C redundancy protection, improving the device reliability.

The TID format determines how various user terminal IDs on the MG interface are generated.

Prerequisites
NOTICE:
The configuration of the TID format is relatively complicated. The information such as the syntax rules with which the terminal prefix must comply and the requirements for the character string of the TID template is defined in the protocol, and is not described here. This topic describes only some basic information. It is recommended that you refer to the TID description in ITU-T H248.1 (applicable to H.248) or RFC 3435 (applicable to MGCP) before configuring the TID format.

Context
The TID format consists of the terminal prefix and the TID template. The TID template defines the generation mode of the TID excluding the terminal prefix. A TID consists of a terminal prefix and a character string generated by a TID template.

The TID templates that are bound to various types of users on the MG interface determine whether the users support terminal layering.
If the parameter list of the TID template includes only keyword "G", the TID template is used by the non-layering users. Users bound with this template do not support terminal layering.
If the parameter list of the TID template includes only keywords "F", "S", "P", "B" ("B" is not available to PSTN users), the TID template is used by the layering users. Users bound with this template support terminal layering.
NOTE:
The meaning of each keyword is as follows:
F indicates the subrack ID.
S indicates the slot ID.
P indicates the port ID.
B indicates the B channel ID (only for ISDN BRA and ISDN PRA terminals).
G indicates the general permanent termination index.
R indicates the RTP ephemeral termination index (only for the RTP ephemeral termination, which exists only when the system protocol is H.248. This termination is not involved unless special remarks are provided.)
When adding a user that supports terminal layering, you cannot and do not have to specify the parameter terminalid because the system automatically allocates a terminal ID. When adding a user that does not support terminal layering, you must specify the parameter terminalid.

You can run the display tid-format(h248) command or display tid-format(mgcp) command to query the TID formats of various types of users on the current MG interface. In the query result, template-index indicates the index of the TID template that is bound to the type of users. Then, run the display tid-template command to check whether the TID template supports the layering configuration. Hence, you can check whether the user supports terminal layering.

Precaution
There are 19 default TID templates (templates 0-18) in the system. The default TID templates can be referenced, but cannot be added, modified, or deleted.
The configuration of terminal layering on the MG must be the same as that on the MGC.
If certain type of terminals exists on an interface and the interface is not disabled, the terminal prefix of this type of terminals cannot be modified.
If a certain type of terminals exists on an interface, the TID format (including the terminal prefix and the index of the TID template) of this type of terminals cannot be changed.
The terminal prefix must comply with the following syntax rules: The prefix must not exceed 64 characters. Only letters, digits, "_", and "/" are the characters allowed for input. The first character must be a letter, and the last character must not be a digit.
The length of the TID, which is generated by combining the TID template and the terminal prefix that you configured, must not exceed 64 characters.
Procedure
If the system protocol is H.248, to configure the TID format on the current MG interface, do as follows:
Run the display tid-template command to query the information about the default TID template of the system.
If the default TID template cannot meet the service requirements, run the tid-template add command to add a TID template that meets the service requirements. If the default TID template meets the service requirements, proceed to 3.
Run the interface h248 command to enter the H.248 mode.
Configure the TID templates and the terminal prefix of various types of users on the current MG (VAG).

NOTICE:
The terminal prefix of PSTN, BRA and PRA must be all identical or unique.
In the H.248 mode, run the tid-format rtp command to configure the TID template and the terminal prefix of the RTP ephemeral termination.
In the H.248 mode, run the tid-format pstn command to configure the TID template and the terminal prefix of the PSTN user.
In the H.248 mode, run the tid-format bra command to configure the TID template and the terminal prefix of the ISDN BRA user.
In the H.248 mode, run the tid-format pra command to configure the TID template and the terminal prefix of the ISDN PRA user.

Run the display tid-format(h248) command to check whether the TID templates and the terminal prefixes of various types of users on the current MG interface are the same as those in the data plan.
If the system protocol is MGCP, to configure the TID format on the current MG interface, do as follows:
Run the display tid-template command to query the information about the default TID template of the system.
If the default TID template cannot meet the service requirements, run the tid-template add command to add a TID template that meets the service requirements. If the default TID template meets the service requirements, proceed to 3.
Run the interface mgcp command to enter the MGCP , GPBD, GPFD mode.
Configure the TID templates and the terminal prefix of various types of users on the current MG (VAG).

In the MGCP mode, run the tid-format pstn command to configure the TID template and the terminal prefix of the PSTN user.
In the MGCP mode, run the tid-format bra command to configure the TID template and the terminal prefix of the ISDN BRA user.
In the MGCP mode, run the tid-format pra command to configure the TID template and the terminal prefix of the ISDN PRA user.

Run the display tid-format(mgcp) command to check whether the TID templates and the terminal prefixes of various types of users on the current MG interface are the same as those in the data plan.

The switch supports the remote upgrade of the BootROM.

Log in to the switch where the BootROM needs to be upgraded through Telnet, and then run the upgrade basic-bootrom system-filename command in the system view to upgrade the BootROM.

Configure a Switch(such as S9700) to Send Debugging Information to the Log Server
To configure a switch to send debugging information to the log server, run the following command in the system view.

[HUAWEI] info-center source default channel 2 debug state on
[HUAWEI] info-center loghost x.x.x.xBy default, a switch sends only logs and traps to the log server.

The NTP Synchronization Interval on the Switch
The maximum NTP synchronization interval on the switch is 210 seconds. The interval for clock synchronization between the NTP client and server is not fixed and depends on the clock precision. A higher clock precision results in a longer synchronization interval. The synchronization interval depends on the following factors:
Time difference between the client and server
Frequency offset of the clock on the client compared with the clock on the server.

Configure an IP Address for the Management Interface of a Switch
The management interface is a Layer 3 interface that can be configured with an IP address. To configure an IP address for the management interface, run the following commands:
<HUAWEI> system-view
[HUAWEI] interface meth 0/0/1
[HUAWEI-MEth0/0/1] ip address 192.168.1.2 24
[HUAWEI-MEth0/0/1] NOTE:
Only some switch models have management interfaces. On these switch models, other physical interfaces cannot be configured with IP addresses.

A hot patch package (a .pkg file) is an NE-level logical package. It is first loaded onto the flash memory of the active SCC board and then automatically dispensed to those boards to be upgraded.
For V100R009 or later, multiple .pkg files may be available. For details about how to select an appropriate package file, see section 2.2.6 "Selecting an Appropriate Hot Patch Package for a V100R009 NE or Later."
The following figure shows the state transition during a hot patch package upgrade (steps 3 to 7 are the same as those of a board-level hot patch upgrade).
Note:
1: Downloading the hot patch package to the NE
2: Loading the patch files to the target boards
3: Loading patch files to the memory
4: Activating the patch files
5: Deactivating the patch files
6: Committing the patch files
7: Deleting the hot patch package
8: One-key installation of the hot patch package

The basic working principle of the H801GSCA board is as follows:
l The control module is the control core of the entire board.
l The conversion module supports transparent transmission of the information.
l The link management module manages the GE links.
l The power module supplies power to other functional modules of the board.
l The clock module provides clock signals for other functional modules of the board.

The basic working principle of the H801GICG board is as follows:
l The control module loads the board software, controls the running of the software, and
manages the entire board.
l The conversion module supports transparent transmission of the information.
l The power module supplies power to other functional modules of the board.

Check the status of the NE database and make sure that the database is ready for storing data. This is to ensure that the NE works as expected after the upgrade. Please get the tool "OptiX OSN 8800_6800_3800 CheckDataBase_Tool_EN.zip" for checking database by "Software Center > Version Software > Optical Network Product Line > Optical Network Tools > WDM Tools".

About OptiX OSN 8800/OSN 6800/3800
Step 1 Right-click NE1 in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the NE Explorer, click NE1 and choose Configuration > Packet Configuration > IP Ping
Test.
Step 3 Click Add and set the proxy IP address in the Proxy IP Address List area.
NOTE
In far-end IP ping tests, the configured proxy IP address ensures that IP ping packets are forwarded through the proxy IP address.
Step 4 Click Apply.
Step 5 Set Enable, VLAN ID, VLAN Priority, IP Address, and IP Mask for a UNI of NE2 by
referring to the configuration steps applicable to NE1.
NOTE
The UNI IP address configured on NE2 must be the same as the proxy IP address configured on NE1.
Before using the far-end IP ping function, ensure that the IP ping function has been enabled on both the near-end port and far-end port.
----End

To quickly and accurately locate and resolve a fault in the optical transport system, maintenance
personnel must have sufficient background knowledge and service skills and be familiar with
the network and the equipment used. This topic outlines the skills and knowledge that
maintenance personnel require for troubleshooting the OptiX OTN equipment.
Background Knowledge
WDM fundamentals
The WDM system alarm generation mechanism
Troubleshooting methods for common alarms
Basic Operations
Basic transmission equipment operations
lBasic network management system (NMS) operations
For basic NMS operations, refer to the OptiX iManager U2000 Operator Guide or the on-line
help.
Common Test Instruments
Commonly needed transmission system test instruments include optical power meter, SDH/
SONET tester, SmartBits tester, optical spectrum analyzer, OTDR and communication signal
analyzer. Refer to the respective operator guide for more information.
Network Layout
The network layout of the project
The service configuration, wavelength assignment, optical distribution frame (ODF), fiber
routing, board version, and equipment layout in each office.
The current equipment running status in local office
The relevant engineering files and documents (which need to be updated periodically)
On-Site Data Collection
This process includes periodic data collection both when the equipment is running normally and
when faults occur. Before handling the fault, maintenance personnel should first collect and
store the on-site data. For more information about data collection,

Huawei MA5683T is a aggregation Optical Line Terminal (OLT), it supports up to 6 service slots and can support maximum 12,000 subscribers (GPON). A typical MA5683T configuration includes one MA5683T Chassis, two Main Control Board SCUN/SCUK, two Power Board PRTE, one uplink board GICF (2 GE Optical with SFP Module), one 8 Port GPON board GPBD (with C+ SFP Module). Besides that one typical configuration, Thunder-link.com also offers more bundle line, to meet your different requirement on various scenario. In addition, Thunder-link.com provides self configuration page, where you can configure your own MA5683T by selecting boards and items yourself. With our professional technical support to rich your experience.

The OptiX OSN 8800 is recognized as the platform with the highest integration level in the industry. One OptiX OSN 8800 subrack supports access of 320/640 x 10G services and two OptiX OSN 8800 subracks can be housed in one standard ETSI cabinet. The OptiX OSN 8800 can accommodate mass IP services and provide centralized grooming and unified management. Because one OptiX OSN 8800 subrack is equivalent to multiple subracks of other WDM equipment, the OptiX OSN 8800 saves 80% of the equipment footprint and reduces power consumption per bandwidth by 55%. OptiX OSN 8800 devices can be directly connected instead of through ODFs and therefore is highly reliable.