GEM ports are added in xPON distributed mode but they are not bound to an ONT.
After the distributed mode is changed to the profile mode, these GEM ports are still
in the system and become distributed GEM ports. In V800R006C02, if the system
has distributed GEM ports, redundant data is generated. As a result, display of service
ports changes and services fail after the system is upgraded from a version earlier than
V800R009C00 to V800R009C00 or a later version. These two problems affect the
Internet access service and may occur on a large number of devices.
[Problem Description]
Trigger conditions:
1. In V800R006C02, the system changes from the distributed mode to profile mode.
2. The system has GEM ports that are not bound to an ONT。
3. The system is upgraded from V800R006C02 to V800R009C00 or a later version.
There is a high probability that display of service ports changes and services fail when
these three conditions are met.
Symptom:
The ONT ID and GEM index of a service port cannot be displayed, but the GEM port ID
is displayed. As shown in the following query result, VPI is displayed as -, and services fail.
MA5600T(config)#display service-port port 0/4/0
{ <cr>|autosense<K>|ont<K>|sort-by<K> }:
Command:
display service-port port 0/4/0
Switch-Oriented Flow List
----------------------------------------------------------------------------
INDEX VLAN VLAN PORT F/ S/ P VPI VCI FLOW FLOW RX TX STATE
ID ATTR TYPE TYPE PARA
----------------------------------------------------------------------------
1 100 common gpon 0/4 /0 - 130 vlan 10 - - down
2 100 common gpon 0/4 /0 0 0 vlan 10 - - down
----------------------------------------------------------------------------
Total : 2 (Up/Down : 0/2)
Identification method:
Check whether the system has a distributed GEM port.
MA5600T(config)#display current-configuration section gpon
{ <cr>||<K> }:
Command:
display current-configuration section gpon
[MA5600V800R010: 5900]
#
[gpon]
<gpon-0/4>
interface gpon 0/4
GEM Port add 0 GEM Port-ID 128-137 eth
ont add 0 0 sn-auth "1111111111111111" omci ont-lineprofile-id 100
ont-srvprofile-id 100 desc "ONT_NO_DESCRIPTION"
sippstnuser add 0 0 1
ont add 0 1 sn-auth "2222222222222222" omci ont-lineprofile-id 0
ont-srvprofile-id 101 desc "ONT_NO_DESCRIPTION"
ont port native-vlan 0 1 eth 1 vlan 1 priority 3
#
return
If the configuration in red is displayed in the command output, the system has
a distributed GEM port. (Normally, GEM Port add is not displayed in GPON
interface mode.)
[Root Cause]
In V800R006C02, if the system has GEM ports that are not bound to an ONT
and the system changes from the distributed mode to the profile mode, these
GEM ports become distributed GEM ports. However, these GEM ports should
have been changed to be GEM ports on a line profile for management and usage.
Distributed GEM ports trigger disorder and redundant data. Consequently, the
system has two identical GEM port IDs (the GEM port ID should have been
unique), between which, one is applied by the distributed GEM port and the other
one is applied by the line profile according to the ONT ID and GEM index.
In versions earlier than V800R009C00, the system saves the ONT ID and GEM
index of a service port, displays them and generates corresponding configurations
directly. However, in V800R009C00 and later versions, the system supports
expandability between modules so that the system queries the information about
a service port based on the GEM port ID and displays the query information.
Because of distributed GEM ports in the system, the GEM port ID is not unique
and resources occupied by a distributed GEM port may be queried. Then,
configurations are generated based on these resources. As a result, problems
occur.
[Impact and Risk]
In the preceding scenario, upgrades will be affected. For example, if the system
is upgraded from V800R007C00 to V800R011, configurations will be incorrect
and services will fail. These problems may occur on a large number of devices.
[Measures and Solutions]
All distributed GEM ports in the system need to be deleted. The following uses slot
4 as an example to delete all its distributed GEM ports.
Recovery measures:
1. Query distributed GEM ports.
MA5600T(config)#display current-configuration section gpon
{ <cr>||<K> }:
Command:
display current-configuration section gpon
[MA5600V800R010: 5900]
#
[gpon]
<gpon-0/4>
interface gpon 0/4
GEM Port add 0 GEM Port-ID 128-137 eth
ont add 0 0 sn-auth "1111111111111111" omci ont-lineprofile-id 100
ont-srvprofile-id 100 desc "ONT_NO_DESCRIPTION"
sippstnuser add 0 0 1
ont add 0 1 sn-auth "2222222222222222" omci ont-lineprofile-id 0
ont-srvprofile-id 101 desc "ONT_NO_DESCRIPTION"
ont port native-vlan 0 1 eth 1 vlan 1 priority 3
#
return
4. Delete the distributed GEM port.
Check whether this distributed GEM port has a service port.
MA5600T(config)#display service-port port 0/4/0
{ <cr>|autosense<K>|ont<K>|sort-by<K> }:
Command:
display service-port port 0/4/0
Switch-Oriented Flow List
----------------------------------------------------------------------------
INDEX VLAN VLAN PORT F/ S/ P VPI VCI FLOW FLOW RX TX STATE
ID ATTR TYPE TYPE PARA
----------------------------------------------------------------------------
1 100 common gpon 0/4 /0 - 130 vlan 10 - - down
2 100 common gpon 0/4 /0 0 0 vlan 10 - - down
----------------------------------------------------------------------------
Total : 2 (Up/Down : 0/2)
If yes, delete the service port. If no, delete the distributed GEM port.
MA5600T(config)#undo service-port 1
Delete the distributed GEM port.
MA5600T(config)#interface gpon 0/4
MA5600T(config-if-gpon-0/4)#unbound-GEM Port delete 0 GEM Port-ID 128-137
Deleting GEM ports succeeded: 10
Deleting GEM ports failed: 0
5. Save the data.
MA5600T(config-if-gpon-0/4)#quit
MA5600T(config)#save
{ <cr>|configuration<K>|data<K> }:
Command:
save
6. Perform an active/standby switchover or reset the system.
MA5600T(config)#system switch-over
Are you sure to switch over? (y/n)[n]:y
MA5600T(config)#reboot system
Please check whether data has saved, the unsaved data will lose if reboot
system, are you sure to reboot system? (y/n)[n]:y
Workarounds:
1. Check whether the system has a distributed GEM port before an upgrade
using the CLI or preventative maintenance script.
MA5600T(config)#display current-configuration section gpon
{ <cr>||<K> }:
Command:
display current-configuration section gpon
[MA5600V800R010: 5900]
#
[gpon]
<gpon-0/4>
interface gpon 0/4
GEM Port add 0 GEM Port-ID 128-137 eth
ont add 0 0 sn-auth "1111111111111111" omci ont-lineprofile-id 100
ont-srvprofile-id 100 desc "ONT_NO_DESCRIPTION"
sippstnuser add 0 0 1
ont add 0 1 sn-auth "2222222222222222" omci ont-lineprofile-id 0
ont-srvprofile-id 101 desc "ONT_NO_DESCRIPTION"
ont port native-vlan 0 1 eth 1 vlan 1 priority 3
#
return
7. Delete the distributed GEM port.
Check whether this distributed GEM port has a service port.
MA5600T(config)#display service-port port 0/4/0
{ <cr>|autosense<K>|ont<K>|sort-by<K> }:
Command:
display service-port port 0/4/0
Switch-Oriented Flow List
----------------------------------------------------------------------------
INDEX VLAN VLAN PORT F/ S/ P VPI VCI FLOW FLOW RX TX STATE
ID ATTR TYPE TYPE PARA
----------------------------------------------------------------------------
1 100 common gpon 0/4 /0 - 130 vlan 10 - - down
2 100 common gpon 0/4 /0 0 0 vlan 10 - - down
----------------------------------------------------------------------------
Total : 2 (Up/Down : 0/2)
If yes, delete the service port. If no, delete the distributed
GEM port.
MA5600T(config)#undo service-port 1
Delete the distributed GEM port.
MA5600T(config)#interface gpon 0/4
MA5600T(config-if-gpon-0/4)#unbound-GEM Port delete 0 GEM Port-ID 128-137
Deleting GEM ports succeeded: 10
Deleting GEM ports failed: 0
8. Save the data.
MA5600T(config-if-gpon-0/4)#quit
MA5600T(config)#save
{ <cr>|configuration<K>|data<K> }:
Command:
save
Preventive measures:
None
More blog:
No comments:
Post a Comment