Thunder-link.com: MA5616

Showing posts with label MA5616. Show all posts

Thursday, May 12, 2016

What’s the Line Encryption of GPON

Context

In the PON system, downstream data is broadcast to all ONUs. As a result, downstream data destined for certain ONUs or all ONUs may be intercepted by illegal users.

Figure 1 Downstream data transmit process

Working Principle

Line encryption technologies are required to eliminate the data theft risk, Figure 2 shows line encryption process.

Figure 2 Line encryption process

· The encryption algorithm to be used is the advanced encryption standard (AES).

· The 10G GPON systems use the AES-128 encryption algorithm.

Highlight and Application

· The line encryption algorithms neither increase overhead nor decrease bandwidth usages.

· The line encryption algorithms will not prolong transmission delays.

· Enable line encryption if the usage scenarios promote high security requirements

More related:

How to Control Board Failure After an MxU Service Port Is Bound to a Rate Unlimited

What’s the Service Interruption on the MA5616?

How to Upgrade the LSW Chip of the H801SCUN Board

Tuesday, March 29, 2016

Warning of Failed Cascading on the MA5616 Equipped with the JDSU GE Optical Module

Keywords: MA5616, H831CCUC, JDSU (optical module vendor), GE optical module, GE optical port cascading, cascading failure

Summary: An MA5616 equipped with the H831CCUC control board uses the JDSU-provided GE optical module with BOM number 34060286 for upstream cascading. The cascading fails and the LINK indicator on the control board is not on.

Product Line: Access Network Product Line Product Model: MA5616

[Problem Description]

Trigger conditions

Two MA5616s (equipped with H831CCUC control boards) use the GE optical port for cascading. The GE optical module is provided by JDSU and the BOM number is 34060286.

Figure 1 JDSU-provided GE optical module

Symptom

The cascading fails and the LINK indicator on the control board is not on.

Identification method

1. Perform the following three steps to verify that the device, optical link, and optical module are functional.

a Verify that the device is functional.

The device is powered on and displays information using the serial port. The system displays the message "Press any key to get started." Use the user name and password to log in to the device. Query the board information. The system displays "normal", indicating that the device and board are functional.

MA5616(config)#display board 0

-------------------------------------------------------------------------

SlotID BoardName Status SubType0 SubType1 Online/Offline

-------------------------------------------------------------------------

0 H831CCUC Active_normal UP2A

5 H831PDIA Normal

-------------------------------------------------------------------------

MA5616(config)#display board 0/0

---------------------------------------

Board Name : H831CCUC

Board Status : Active normal

---------------------------------------

Subboard[0]: H831UP2A Status: Normal

-----------------------------------------------------------------------------

Port Port MAC Register Link Role Active

Type State State State

-----------------------------------------------------------------------------

0 GE optic normal - auto auto off active offline

-----------------------------------------------------------------------------

------------------------------------------------------------------------------

Port Port COMBO Optic MDI Speed Duplex Flow- Active Link

Type Mode Status (Mbps) Ctrl State

------------------------------------------------------------------------------

1 GE - absence - auto auto off active offline

------------------------------------------------------------------------------

Note: For a 1000 M, electrical port in the full-duplex mode, setting MDI to

any value is invalid

b Verify that the optical link is functional.

Ensure that an orange multi-mode LC/PC optical fiber is used. After the optical link starts to work, run the following command to query the transmit and receive optical power: (The range for the transmit optical power is –9.5 dBm to –2.5 dBm, and the range for the receive optical power is –17 dBm to 0.)

MA5616(config-if-eth-0/0)#display port ddm-info 1

Command:

display port ddm-info 1

Temperature(C) : 32.550000

Supply voltage(V) : 3.300000

TX bias current(mA) : 4.550000

TX power(dBm) : -5.010000

RX power(dBm) : -6.160000

c Verify that the optical module is functional.

Verify that the optical module is free of any visible damage and is not removed. Insert the optical module to the optical port and run the following commands to verify that the optical module is functional:

MA5616(config)#interface eth 0/0

MA5616(config-if-eth-0/0)#display port opticstate 1

Note: The type of optical module does not fully support the SFF-8472

standard. The queried information may be incorrect or unspecified

Optics module information

Identifier : SFP

Ext.Identifier : GBIC/SFP function is defined by serial

ID only

Connector : LC

Transceiver

Infiniband compliance codes : Invalid

SONET compliance codes : Invalid

GE compliance codes : 1000BASE-SX

Link length : short distance

Transmitter technology : shortwave laser

Transmission media : multi-mode, 62.5m

Speed : Invalid

Encoding : 8B10B

BR,Nominal : 2100 MBits/sec

Length(9um)-km : 0 km

Length(9um) : 0.0 km

Length(50um) : 500 m

Length(62.5um) : 300 m

Length(Copper) : 0 m

Vendor name : JDSU

Vendor OUI : 412

Vendor PN : PLRXPL-VI-S24-HW

Vendor rev : 1

Wavelength : 850 nm

Cc_base : 0x7f

Options : Invalid

BR,max : Unspecified

BR,min : Unspecified

Vendor SN : CC17QQ322

Date code : 12 04 18

Diagnostic Monitoring Type : Internally Calibrated

Enhanced Options : Optional Alarm/warning flags implemented

for all monitored quantities

SFF-8472 Compliance : Includes functionality described in Rev-

10.2 SFF-8472

CC_EXT : 0xec

Vendor specific :

20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

2. Check whether the LINK indicator on the control board is on. If the indicator is not on, the cascading fails.

3. Query the link status of the cascaded optical port. If the system displays "offline", the cascading fails.

MA5616(config-if-eth-0/0)#display port state all

------------------------------------------------------------------------------

Port Port COMBO Optic MDI Speed Duplex Flow- Active Link

Type Mode Status (Mbps) Ctrl State

------------------------------------------------------------------------------

0 GE optic normal - auto auto off active offline

1 GE - normal - auto auto off active offline

------------------------------------------------------------------------------

Note: For a 1000 M, electrical port in the full-duplex mode, setting MDI to

any value is invalid

----End

[Root Cause]

An error occurs when the JDSU-provided GE optical module is used with the H831CCUC control board. The LOS decision mechanism of the JDSU-provided GE optical module conflicts with that of the H831CCUC control board. As a result, the handshake fails, causing a cascading failure.

[Impact and Risk]

The MA5616 equipped with the H831CCUC control board is delivered with the JDSU-provided GE optical module (BOM number: 34060286). If the GE optical module is used for cascading, the cascading fails, affecting deployment.

[Measures and Solutions]

Recovery measures

None

Preventive measure

Configure the MAC chip register in the software.

Solution

Upgrade the control board to V800R310C00SPC103 on new sites in which the cascading is used.

[Attachment]

None

[Rectification Scope and Time Requirements]

None

[Prewarning Expiration Condition]

None

More blog:

What’s the IGMP Framework on the Device

What’s the Service Interruption on the MA5616?

How to Upgrade the LSW Chip of the H801SCUN Board

Friday, March 25, 2016

How to Control Board Failure After an MxU Service Port Is Bound to a Rate Unlimited

Abstract: In MxU V800R306C01, V800R307C00, and V800R307C01, the MxU control board fails after the following operations are performed:

Product Line: Access network product line Product Model: MA5616

l Create a rate unlimited traffic profile (traffic table ip) through the U2000 or N2000.

l Bind the traffic profile to a service port on the MxU.

Restart the MxU.

[Problem Description]

Trigger conditions:

This issue occurs after all the following requirements are met:

1. A rate unlimited profile is created on the MxU through the U2000 NMS.

2. The MxU version is V800R306C01, V800R307C00, or V800R307C01.

3. The created profile is bound to a service port on the MxU.

Symptoms：

After the MxU is restarted, the control board fails. As a result, service boards fail to register with the control board and the MxU cannot be managed by the NMS.

HUAWEI(config)#display board 0

-------------------------------------------------------------------------

SlotID BoardName Status SubType0 SubType1 Online/Offline

-------------------------------------------------------------------------

0 H821EPUA Active_failed Unmanageable

1 H821EPFB Failed Online

2 H821ASNB Failed Online

-------------------------------------------------------------------------

Identification methods：

If a control board fails after the MxU is restarted, perform the following operations to determine that the fault is caused by the issue described in this pre-warning:

1. Verify that the MxU version is V800R306C01, V800R307C00, or V800R307C01.

2. Verify that a rate unlimited profile exists on the MxU and it is bound to a service port on the MxU.

The following configurations are used as an example:

traffic table ip index 7 name "NOCAR" cir off color-mode color-blind priority 0 priority-policy local-setting

……

service-port 0 vlan 1049 eth 0/1/1 multi-service user-vlan untagged rx-cttr 7 tx-cttr 7

service-port 1 vlan 1050 eth 0/1/2 multi-service user-vlan untagged rx-cttr 7 tx-cttr 7

3. Query MxU last words. If the following highlighted error codes are displayed for l2qos files, the fault is caused by the issue described in this prewarning.

HUAWEI(su)%%display lastwords all

……

l2qos_traff 1315 0 0 1 0x7b0 0x7b0

l2qos_traff 1316 0 0 1 0x9c4000 0x9c4000

l2qos_traff 1317 0 0 1 0x9c4000 0x9c4000

l2qos_traff 1424 0 0 1 0x68bafe 0x68bafe

[Root Cause]

In MxU V800R306C01, V800R307C00, or V800R307C01, if a rate unlimited profile is created through the NMS, the MxU database may malfunction. The traffic profile cannot restore from the database after the MxU is restarted. In this case, if the traffic profile is bound to a service port on the MxU, the service port cannot find the traffic profile in the recovered data. As a result, the MxU hardware fails to be configured and accordingly, the control board fails.

[Impact and Risk]

The control board fails, services on the MxU fail, and the MxU cannot be managed by the NMS.

[Measures and Solutions]

Recovery measures：

Workarounds

1. If an abnormal traffic profile has been loaded to the MxU on the live network but the MxU has not been restarted, delete the traffic profile from the NMS and use a functional traffic profile.

2. If the MxU has been restarted and the control board fails, create the service port that is bound to the abnormal traffic profile on the MxU by running commands. Then, save the data.

The procedure is as follows:

Step 1: Run the display saved-configuration command to query the original configuration.

If a service port is bound to the abnormal traffic profile, change the traffic profile to a functional one.

The following configurations are used as an example, where traffic profile 7 is the abnormal profile:

HUAWEI(config)#display saved-configuration

[MA5600V800R305: 12301]

[global-config]

<global-config>

traffic table ip index 7 cir 51200 cbs 1024000 pir 102400 pbs 1024000 priority

user-cos 0 priority-policy local-setting

[public-config]

<public-config>

snmp-agent local-engineid 800007DB0300E0FC112233

[vlan-config]

<vlan-config>

vlan 200

[bbs-config]

<bbs-config>

service-port 0 vlan 200 eth 0/1/1 user-vlan untagged rx-cttr 7 tx-cttr 7

return

Step 2: Load the modified configuration file to the MxU or manually change the traffic profile ID to the one of a functional traffic profile.

The following manual configurations are used as an example:

service-port 0 vlan 200 eth 0/1/1 user-vlan untagged rx-cttr 6 tx-cttr 6

Step 3: Create the service port with the preceding configurations by running commands.

Step 4: Save the data.

Preventive measures：

For the MA562X or MA5616, upgrade the version to V800R308C00SPC508 or later to resolve this issue.

For MA5620E V800R307 or MA5620G V800R307, the V800R312C00SPC205 is being developed, which resolves this issue and will be released in the end of 2013.

Solution：

For the MA562X or MA5616, upgrade the version to V800R308C00SPC508 or later to resolve this issue.

For MA5620E V800R307 or MA5620G V800R307, the V800R312C00SPC205 is being developed, which resolves this issue and will be released in the end of 2013.

[Warning Conditions]

The warning does not take effect when the trigger conditions are not met.

[Attachment]

None

More blog: