Abstract: In MxU V800R306C01, V800R307C00, and V800R307C01, the MxU control board fails after the following operations are performed:
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:
No comments:
Post a Comment