The MA5600T/MA5603T/MA5608T provides end users with services through the ONT. The MA5600T/MA5603T/MA5608T can manage the ONT and the ONT can work in the normal state only after the channel between the MA5600T/MA5603T/MA5608T and the ONT is available.
The GPON ONT profile is already created. Configuring a GPON ONT Capability Profile and Configuring a GPON ONT Alarm Profile are already completed.
The MA5600T/MA5603T/MA5608T uses the ONT Management and Control Interface (OMCI) protocol to manage and configure the GPON ONT, and supports the offline configuration of the ONT. The ONT does not need to save the configuration information locally. This helps to provision services.
Table 1 lists the default settings of the GPON ONT.
Figure 1 shows the process of configuring a GPON ONT.
Figure 1 Process of configuring a GPON ONT
1.Add a GPON ONT.
a.Run the interface gpon command to enter the GPON mode.
b.Run the port portid ont-auto-find command to enable the auto-find function of the ONT. After the function is enabled, you can add an ONT according to the information reported by the system. By default, the ONT auto-find function of a GPON port is disabled.
NOTE: An auto-find ONT is in the auto-find state. The auto-find ONT can work in the normal state only after it is confirmed or added.
c.Run the ont add command to add an ONT offline, or run the ont confirm command to confirm the auto-find ONT.
When ONTs are added or confirmed, the system provides four authentication modes: SN, password, SN+password, LOID+CHECKCODE.
SN authentication: The OLT detects the serial number (SN) reported by an ONT. If the SN is consistent with the OLT configuration, authentication is passed and the ONT goes online. This mode requires recording all ONT SNs. Hence, it is used to confirm auto discovery ONTs and is not applicable to adding ONTs in batches.
Password authentication: The OLT detects the password reported by an ONT. If the password is consistent with the OLT configuration, the ONT goes online normally. This mode requires planning ONT passwords and does not require manually recording ONT SNs. Hence, it is applicable to adding ONTs in batches. The password authentication provides two discovery modes: always-on and once-on.
always-on: After first password authentication is passed, no SN is allocated and password authentication is always used in subsequent authentications. This discovery mode is easy for future maintenance. In the always-on discovery mode, configuration is not required to be modified when an ONT is replaced and only the password is required. The always-on discovery mode has lower security. If other users know the password, the users will illegally have service permissions.
Once-on: After first password authentication is passed, an SN is automatically allocated and password+SN authentication is used in subsequent authentications. An ONT can go online only after the correct password and SN are entered. The once-on authentication mode has high security. After an ONT is replaced or the password is mistakenly changed, the ONT needs to be configured again, which requires more maintenance effort.
SN+password authentication: The OLT detects the password and SN reported by an ONT. If the password and SN are consistent with the OLT configuration, the ONT goes online normally. This authentication mode has the highest security but it requires manually recording ONT SNs.
LOID+CHECKCODE authentication: defined by a telecom operator. In this authentication mode, LOID has 24 bytes, and CHECKCODE has 12 bytes and is optional. Whether 24 bytes or 36 bytes are used for authentication depends on data planning, which is unified over the entire network. The OLT determines whether LOID+CHECKCODE reported by the ONT is the same as the configured one. If they are the same, the ONT authentication is passed. If they are different, the OLT obtains the ONT password and compares it with the last 10 bytes of the LOID. If they are the same, the ONT authentication is also passed. This operation is for compatibility with the ONTs using password authentication.
Adding ONTs in offline mode is applicable to the batch deployment scenario. All ONTs are added to the OLT to complete service provisioning beforehand. When a use subscribes to the service, an installation engineer takes an ONT to the user's house and completes configurations. After the ONT goes online and passes authentication (generally the password authentication mode or LOID authentication mode is used), the service is provisioned.
Adding ONTs in auto discovery mode is applicable to the scenario where a small number of ONTs are added. When users subscribe to the service, installation engineers take ONTs to the users' houses. After the ONTs go online, the OLT confirms the ONTs one by one. Generally, the MAC address authentication mode is used to confirm the ONTs.
If the ONU is an independent NE and is directly managed by the NMS through the SNMP management mode, select the SNMP management mode. For this mode, you only need to configure the parameters for the GPON line and the parameters for the management channel on the OLT.
If the ONU is not an independent NE and all its configuration data is issued by the OLT through OMCI, select the OMCI management mode. For this mode, you need to configure all parameters (including line parameters, UNI port parameters, and service parameters) that are required for the ONU on the OLT. Generally, the ONT management mode is set to the OMCI mode.
d.(Optional) When the ONT management mode is the SNMP mode, you need to configure the SNMP management parameters for the ONT. The procedure is as follows:
i.Run the ont ipconfig command to configure the management IP address of the ONT.
The IP address should not be in the same subnet for the IP address of the VLAN port.
ii.Run the ont snmp-profile command to bind the ONT with an SNMP profile.
Run the snmp-profile add command to add an SNMP profile before the configuration.
iii.Run the ont snmp-route command to configure a static route for the NMS server, that is, configure the IP address of the next hop.
2.(Optional) Configure the VLAN of the ONT port.
Run the ont port vlan command to configure the VLAN of the ONT port. By default, all the ports on the ONT belong to VLAN 1.
3.(Optional) Configure the default VLAN (native VLAN) for the ONT port.
Run the ont port native-vlan command to configure the default VLAN for the ONT port. By default, the default VLAN ID of the ONT port is 1.
If the packets reported from a user (such a PC) to the ONT are untagged, the packets are tagged with the default VLAN of the port on the ONT and then reported to the OLT.
If the packets reported from a user to the ONT are tagged, you need to configure the port VLAN of the ONT to be the same as the VLAN in the user tag. The packets are not tagged with the default VLAN of the port on the ONT but are reported to the OLT with the user tag.
4.Bind an alarm profile.
Run the ont alarm-profile command to bind an alarm profile. Ensure that Configuring a GPON ONT Alarm Profile is completed before the configuration.
5.Bind a DBA profile.
Run the tcont bind-profile command to bind a DBA profile to a T-CONT.
A DBA profile can be bound to a T-CONT after an ONT is added.
6.Configure a GEM port.
a.Run the gemport add command to add a GEM port. When adding a GEM port, select the correct attribute according to the service type.
b.Run the ont gemport bind command to bind the GEM port to an ONT T-CONT, that is, allocating the T-CONT resources to the GEM port.
NOTE: If traffic streams are configured on a GEM port and an ONT is the working ONT in a single-homing protection group, the GEM port cannot be bound to or unbound from the ONT.
c.Run the ont gemport mapping command to create the mapping between the GEM port and the ONT-side service.
7.Activate the ONT.
Run the ont activate command to activate the ONT. The ONT can transmit services only when it is in the activated state.
After being added, the ONT is in the activated state by default. The step is required only when the ONT is in the deactivated state.
8.Query the ONT status.
Run the display ont info command to query the ONT running status, configuration status, and matching status.
To add five ONTs in offline mode with password authentication mode (ONT passwords are 0100000001-0100000005), set the discovery mode of password authentication to always-on, and bind ONT capability profile 10, do as follows:
huawei(config)#interface gpon 0/2 huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000001 always-on profile-id 10 manage-mode omci huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000002 always-on profile-id 10 manage-mode omci huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000003 always-on profile-id 10 manage-mode omci huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000004 always-on profile-id 10 manage-mode omci huawei(config-if-gpon-0/2)#ont add 0 password-auth 0100000005 always-on profile-id 10 manage-mode omci
To add an ONT that is managed by the OLT through the OMCI protocol, confirm this ONT according to the SN 3230313185885B41 automatically reported by the system, and bind the ONT with capability profile 3 that match the ONT, do as follows:
huawei(config)#interface gpon 0/2 huawei(config-if-gpon-0/2)#port 0 ont-auto-find enable huawei(config-if-gpon-0/2)#ont confirm 0 sn-auth 3230313185885B41 profile-id 3 manage-mode omci
To add an ONU that is managed as an independent NE and whose SN is known as 3230313185885641, bind the ONU with capability profile 4 that matches the ONU, configure the NMS parameters for the ONU, and set the management VLAN to 100, do as follows:
huawei(config)#snmp-profile add profile-id 1 v2c public private 10.10.5.53 161 huawei huawei(config)#interface gpon 0/2 huawei(config-if-gpon-0/2)#ont add 0 2 sn-auth 3230313185885641 profile-id 4 manage-mode snmp huawei(config-if-gpon-0/2)#ont ipconfig 0 2 static ip-address 10.20.20.20 mask 255.255.255.0 gateway 10.10.20.1 vlan 100 huawei(config-if-gpon-0/2)#ont snmp-profile 0 2 profile-id 1 huawei(config-if-gpon-0/2)#ont snmp-route 0 2 ip-address 10.10.20.190 mask 255.255.255.0 next-hop 10.10.20.100