Chinese
English
Problem Description
A bureau OSN3500 device is upgraded to version 5.21.18.50 from 5.21.16.13 by using analog packet loading method to hit the hot patch of V1R8C02B01LSPH011. Since the master control is N3GSCC, the hot patch packet method is used to hit the hot patch, after hitting it, it is found that the hot patch of the master board takes effect, while the hot patch of the crossover board is found to have not been hit after inquiring. The hotfix for the crossover board is not available after querying the hotfix.
Alarm InformationNo alarm, but the hotfix information of the single board cannot be queried:
:patch-get-info:9;
failed! cmd:0x0406 error:0x9da5 NSERR_PATCH_NULL
:patch-get-statemsg:9;
PATCH-STATE
ProgVer PatchVer TotalPatchNum RunPatchNum ActivePatchNum DeactivePatchNum CommPatchNum TempPatchNum
8.12T02 0 0 0 0 0 0
:patch-get-info:9;
failed! cmd:0x0406 error:0x9da5 NSERR_PATCH_NULL
:patch-get-statemsg:9;
PATCH-STATE
ProgVer PatchVer TotalPatchNum RunPatchNum ActivePatchNum DeactivePatchNum CommPatchNum TempPatchNum
8.12T02 0 0 0 0 0 0
Processing1, to confirm that the bdpkg.nfo file is not 8.12, you need to clear the package processing
2, clear the package command:sftm-clr-pkg:bid (bid for the patch can not take effect of the slot number of the single board), the single board reset bdpkg.nfo regeneration, to the patch package module to report the running version number, the problem is solved.
2, clear the package command:sftm-clr-pkg:bid (bid for the patch can not take effect of the slot number of the single board), the single board reset bdpkg.nfo regeneration, to the patch package module to report the running version number, the problem is solved.
Root Cause1, due to the patch package issued, you need to check whether the base version of the single board and the patch in the patch package of the base version of the same, if not the same is not issued; there will be a master board hotfix is in effect but the single board hotfix did not take effect.
2、How to check whether the base version of the single board matches? You can check the bdpkg.nfo file of the single board in question to confirm, the directory of the file is as follows: /ofs1/pkg/BDPKG.NFO
3. Use Ultra Edit file editor or writing pad to open this file, you can see the current version of the single board, as follows: t1xcs.hwx 6.31T01 /hwx/xcssoft.hwx; Where 6.31T01 is the current version of the single board, and the patch package requires cross matching is 8.12, did not match so the patch failed.
4, why the version will not match? The basic version of the single board to the patch package module to report the version of the rules are: if the bdpkg.nfo exists, then the bdpkg.nfo version to the report (single board reset up if there is no bdpkg.nfo will be generated according to the current version of the run, in addition to the package will be updated if the package is loaded to update the file), or else to the running version of the report. Since the previous version of the current network is R6 version, the bdpkg.nfo information of the board is definitely not the 8.12 version, even after upgrading to R8 version, due to the simulation of the package upgrade method, the method will not update the bdpkg.nfo file (board level/FTP upgrade and downgrade methods will not update this file), so there will be a mismatch of the version of the problem.
2、How to check whether the base version of the single board matches? You can check the bdpkg.nfo file of the single board in question to confirm, the directory of the file is as follows: /ofs1/pkg/BDPKG.NFO
3. Use Ultra Edit file editor or writing pad to open this file, you can see the current version of the single board, as follows: t1xcs.hwx 6.31T01 /hwx/xcssoft.hwx; Where 6.31T01 is the current version of the single board, and the patch package requires cross matching is 8.12, did not match so the patch failed.
4, why the version will not match? The basic version of the single board to the patch package module to report the version of the rules are: if the bdpkg.nfo exists, then the bdpkg.nfo version to the report (single board reset up if there is no bdpkg.nfo will be generated according to the current version of the run, in addition to the package will be updated if the package is loaded to update the file), or else to the running version of the report. Since the previous version of the current network is R6 version, the bdpkg.nfo information of the board is definitely not the 8.12 version, even after upgrading to R8 version, due to the simulation of the package upgrade method, the method will not update the bdpkg.nfo file (board level/FTP upgrade and downgrade methods will not update this file), so there will be a mismatch of the version of the problem.
Recommendations and SummaryOSN3500 board-level hotfixes may also encounter this phenomenon, you can check the bdpkg.nfo file to see if the version matching after a single hotfix failure.
Sell osn3500 SSN1SXCSA_Product Quotation_Sales Manufacturer_Product Features_Product Description_Huawei SDH Transmission Equipment Sales
Supply osn3500 SSN1SXCSA_Troubleshooting_Installation_Tuning_Technical Specifications_Technical Parameters_Huawei SDH Transmission Equipment Sales
