A2020——堡垒机恢复出厂设置，会丢失授权的
- 0关注
- 0收藏，35浏览
问题描述：
github.com/anrancunyushi1/ycr/issues/15
github.com/anrancunyushi1/ycr/issues/14
github.com/anrancunyushi1/ycr/issues/13
github.com/anrancunyushi1/ycr/issues/12
github.com/anrancunyushi1/ycr/issues/11
github.com/anrancunyushi1/ycr/issues/10
github.com/anrancunyushi1/ycr/issues/9
github.com/anrancunyushi1/ycr/issues/8
github.com/anrancunyushi1/ycr/issues/7
github.com/anrancunyushi1/ycr/issues/6
github.com/anrancunyushi1/ycr/issues/5
github.com/anrancunyushi1/ycr/issues/4
github.com/anrancunyushi1/ycr/issues/3
github.com/anrancunyushi1/ycr/issues/2
github.com/anrancunyushi1/ycr/issues/1
github.com/anrancunyushi1/o31/issues/286
github.com/anrancunyushi1/o31/issues/285
github.com/anrancunyushi1/o31/issues/284
github.com/anrancunyushi1/o31/issues/283
github.com/anrancunyushi1/o31/issues/282
github.com/anrancunyushi1/o31/issues/281
github.com/anrancunyushi1/o31/issues/280
github.com/anrancunyushi1/o31/issues/279
github.com/anrancunyushi1/o31/issues/278
github.com/anrancunyushi1/o31/issues/277
github.com/anrancunyushi1/o31/issues/276
github.com/anrancunyushi1/o31/issues/275
github.com/anrancunyushi1/o31/issues/274
github.com/anrancunyushi1/o31/issues/273
github.com/anrancunyushi1/o31/issues/272
github.com/anrancunyushi1/o31/issues/271
github.com/anrancunyushi1/o31/issues/270
github.com/anrancunyushi1/o31/issues/269
github.com/anrancunyushi1/o31/issues/268
github.com/anrancunyushi1/o31/issues/267
github.com/anrancunyushi1/o31/issues/266
github.com/anrancunyushi1/o31/issues/265
github.com/anrancunyushi1/o31/issues/264
github.com/anrancunyushi1/o31/issues/263
github.com/anrancunyushi1/o31/issues/262
github.com/anrancunyushi1/o31/issues/261
github.com/anrancunyushi1/o31/issues/260
github.com/anrancunyushi1/o31/issues/259
github.com/anrancunyushi1/o31/issues/258
github.com/anrancunyushi1/o31/issues/257
github.com/anrancunyushi1/o31/issues/256
github.com/anrancunyushi1/o31/issues/255
github.com/anrancunyushi1/o31/issues/254
github.com/anrancunyushi1/o31/issues/253
github.com/anrancunyushi1/o31/issues/252
github.com/anrancunyushi1/o31/issues/251
github.com/anrancunyushi1/o31/issues/250
github.com/anrancunyushi1/o31/issues/249
github.com/anrancunyushi1/o31/issues/248
github.com/anrancunyushi1/o31/issues/247
github.com/anrancunyushi1/o31/issues/246
github.com/anrancunyushi1/o31/issues/245
github.com/anrancunyushi1/o31/issues/244
github.com/anrancunyushi1/o31/issues/243
github.com/anrancunyushi1/o31/issues/242
github.com/anrancunyushi1/o31/issues/241
github.com/anrancunyushi1/o31/issues/240
github.com/anrancunyushi1/o31/issues/239
github.com/anrancunyushi1/o31/issues/238
github.com/anrancunyushi1/o31/issues/237
github.com/anrancunyushi1/o31/issues/236
github.com/anrancunyushi1/o31/issues/235
github.com/anrancunyushi1/o31/issues/234
github.com/anrancunyushi1/o31/issues/233
github.com/anrancunyushi1/o31/issues/232
github.com/anrancunyushi1/o31/issues/231
github.com/anrancunyushi1/o31/issues/230
github.com/anrancunyushi1/o31/issues/229
github.com/anrancunyushi1/o31/issues/228
github.com/anrancunyushi1/o31/issues/227
github.com/anrancunyushi1/o31/issues/226
github.com/anrancunyushi1/o31/issues/225
github.com/anrancunyushi1/o31/issues/224
github.com/anrancunyushi1/o31/issues/223
github.com/anrancunyushi1/o31/issues/222
github.com/anrancunyushi1/o31/issues/221
github.com/anrancunyushi1/o31/issues/220
github.com/anrancunyushi1/o31/issues/219
github.com/anrancunyushi1/o31/issues/218
github.com/anrancunyushi1/o31/issues/217
github.com/anrancunyushi1/o31/issues/216
github.com/anrancunyushi1/o31/issues/215
github.com/anrancunyushi1/o31/issues/214
github.com/anrancunyushi1/o31/issues/213
github.com/anrancunyushi1/o31/issues/212
github.com/anrancunyushi1/o31/issues/211
github.com/anrancunyushi1/o31/issues/210
github.com/anrancunyushi1/o31/issues/209
github.com/anrancunyushi1/o31/issues/208
github.com/anrancunyushi1/o31/issues/207
github.com/anrancunyushi1/o31/issues/206
github.com/anrancunyushi1/o31/issues/205
github.com/anrancunyushi1/o31/issues/204
github.com/anrancunyushi1/o31/issues/203
github.com/anrancunyushi1/o31/issues/202
github.com/anrancunyushi1/o31/issues/201
github.com/anrancunyushi1/o31/issues/200
github.com/anrancunyushi1/o31/issues/199
github.com/anrancunyushi1/o31/issues/198
github.com/anrancunyushi1/o31/issues/197
github.com/anrancunyushi1/o31/issues/196
github.com/anrancunyushi1/o31/issues/195
github.com/anrancunyushi1/o31/issues/194
github.com/anrancunyushi1/o31/issues/193
github.com/anrancunyushi1/o31/issues/192
github.com/anrancunyushi1/o31/issues/191
github.com/anrancunyushi1/o31/issues/190
github.com/anrancunyushi1/o31/issues/189
github.com/anrancunyushi1/o31/issues/188
github.com/anrancunyushi1/o31/issues/187
github.com/anrancunyushi1/o31/issues/186
github.com/anrancunyushi1/o31/issues/185
github.com/anrancunyushi1/o31/issues/184
github.com/anrancunyushi1/o31/issues/183
github.com/anrancunyushi1/o31/issues/182
github.com/anrancunyushi1/o31/issues/181
github.com/anrancunyushi1/o31/issues/180
github.com/anrancunyushi1/o31/issues/179
github.com/anrancunyushi1/o31/issues/178
github.com/anrancunyushi1/o31/issues/177
github.com/anrancunyushi1/o31/issues/176
github.com/anrancunyushi1/o31/issues/175
github.com/anrancunyushi1/o31/issues/174
github.com/anrancunyushi1/o31/issues/173
github.com/anrancunyushi1/o31/issues/172
github.com/anrancunyushi1/o31/issues/171
github.com/anrancunyushi1/o31/issues/170
github.com/anrancunyushi1/o31/issues/169
github.com/anrancunyushi1/o31/issues/168
github.com/anrancunyushi1/o31/issues/167
github.com/anrancunyushi1/o31/issues/166
github.com/anrancunyushi1/o31/issues/165
github.com/anrancunyushi1/o31/issues/164
github.com/anrancunyushi1/o31/issues/163
github.com/anrancunyushi1/o31/issues/162
github.com/anrancunyushi1/o31/issues/161
github.com/anrancunyushi1/o31/issues/160
github.com/anrancunyushi1/o31/issues/159
github.com/anrancunyushi1/o31/issues/158
github.com/anrancunyushi1/o31/issues/157
github.com/anrancunyushi1/o31/issues/156
github.com/anrancunyushi1/o31/issues/155
github.com/anrancunyushi1/o31/issues/154
github.com/anrancunyushi1/o31/issues/153
github.com/anrancunyushi1/o31/issues/152
github.com/anrancunyushi1/o31/issues/151
github.com/anrancunyushi1/o31/issues/150
github.com/anrancunyushi1/o31/issues/149
github.com/anrancunyushi1/o31/issues/148
github.com/anrancunyushi1/o31/issues/147
github.com/anrancunyushi1/o31/issues/146
github.com/anrancunyushi1/o31/issues/145
github.com/anrancunyushi1/o31/issues/144
github.com/anrancunyushi1/o31/issues/143
github.com/anrancunyushi1/o31/issues/142
github.com/anrancunyushi1/o31/issues/141
github.com/anrancunyushi1/o31/issues/140
github.com/anrancunyushi1/o31/issues/139
github.com/anrancunyushi1/o31/issues/138
github.com/anrancunyushi1/o31/issues/137
github.com/anrancunyushi1/o31/issues/136
github.com/anrancunyushi1/o31/issues/135
github.com/anrancunyushi1/o31/issues/134
github.com/anrancunyushi1/o31/issues/133
github.com/anrancunyushi1/o31/issues/132
github.com/anrancunyushi1/o31/issues/131
github.com/anrancunyushi1/o31/issues/130
github.com/anrancunyushi1/o31/issues/129
github.com/anrancunyushi1/o31/issues/128
github.com/anrancunyushi1/o31/issues/127
github.com/anrancunyushi1/o31/issues/126
github.com/anrancunyushi1/o31/issues/125
github.com/anrancunyushi1/o31/issues/124
github.com/anrancunyushi1/o31/issues/123
github.com/anrancunyushi1/o31/issues/122
github.com/anrancunyushi1/o31/issues/121
github.com/anrancunyushi1/o31/issues/120
github.com/anrancunyushi1/o31/issues/119
github.com/anrancunyushi1/o31/issues/118
github.com/anrancunyushi1/o31/issues/117
github.com/anrancunyushi1/o31/issues/116
github.com/anrancunyushi1/o31/issues/115
github.com/anrancunyushi1/o31/issues/114
github.com/anrancunyushi1/o31/issues/113
github.com/anrancunyushi1/o31/issues/112
github.com/anrancunyushi1/o31/issues/111
github.com/anrancunyushi1/o31/issues/110
github.com/anrancunyushi1/o31/issues/109
github.com/anrancunyushi1/o31/issues/108
github.com/anrancunyushi1/o31/issues/107
github.com/anrancunyushi1/o31/issues/106
github.com/anrancunyushi1/o31/issues/105
github.com/anrancunyushi1/o31/issues/104
操作前必须：
1. 通过Web界面或命令行导出并备份当前配置。
2. 记录设备的序列号和已激活的授权信息（如授权码、激活文件）。
恢复出厂设置后，需要重新导入授权。具体方法取决于授权类型：
- 如果是License授权，通常需要重新在H3C官网或指定平台使用设备序列号申请激活文件。
- 如果是永久授权绑定硬件，联系H3C技术支持或销售，提供设备序列号进行重新激活。
警告： 执行恢复出厂设置前务必确认已备份所有必要数据，并确保拥有重新激活授权的途径，否则可能导致授权永久丢失，设备功能受限。
不会，恢复出厂设置不会导致授权丢失。
华三堡垒机（包括 A2020 系列）的授权文件（.ak 激活文件）是独立保存在设备 Flash 存储的 license 目录下的，恢复出厂设置只会清除配置文件（如用户、资产、策略等），不会删除授权文件。
不过，在操作前需要提醒你：你遇到的问题其实是 Admin 密码过期，不必走到“恢复出厂”这一步。更推荐你先用下面这个方案，因为它既能重置密码，又能完整保留所有配置和授权，操作完成后业务可以无缝恢复。
一、更好的解决方案：通过 BootWare 重置 Admin 密码
这个方法不会清除任何配置，只需一根串口线即可操作。
连接串口：用串口线连接堡垒机，终端软件（如 SecureCRT、Xshell）设置参数为 9600、8N1、无流控。
进入 BootWare 菜单：给堡垒机断电重启，在启动过程中看到提示
Press Ctrl+B to access EXTENDED-BOOTWARE MENU...时，迅速按下 Ctrl+B。输入密码：如果提示输入密码，通常默认是
Admin@huawei.com或h3caplus（具体以设备屏幕显示为准）。执行重置：在 BootWare 菜单中找到类似 “Reset admin password” 或 “Restore default admin” 的选项（华三设备常见为按
R进入，再按1，最后按Y确认）。选择后设备会自动重启。登录验证：重启完成后，即可使用默认密码登录：
Web 端：
admin/admin串口：
root/admin
采用此方案，配置不会丢，授权不会丢，业务可以直接恢复。
二、如果你坚持要恢复出厂设置
如果上述密码重置方法不适用，或者你确实需要清空所有配置，可以按以下步骤操作：
操作路径：
方法 A（BootWare）：进入 BootWare 菜单后，选择 Restore to Factory Default Configuration（通常为选项 5），确认后设备会自动删除配置文件并重启。
方法 B（Web界面）：登录管理页面，进入 系统工具 > 恢复出厂设置 进行操作。
恢复后验证授权：设备重启后，登录并执行以下命令查看授权状态，确保授权仍然有效：
display license如果状态显示为未激活，请手动安装授权文件：license activation-file install flash:/license/xxx.ak（xxx.ak为原激活文件名）
暂无评论
编辑答案
亲~登录后才可以操作哦!
确定你的邮箱还未认证，请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
- 1. 您举报的内容是什么？（请在邮件中列出您举报的内容和链接地址）
- 2. 您是谁？（身份证明材料，可以是身份证或护照等证件）
- 3. 是哪家企业？（营业执照，单位登记证明等证件）
- 4. 您与该企业的关系是？（您是企业法人或被授权人，需提供企业委托授权书）
抄袭了我的内容
×
原文链接或出处
诽谤我
×
- 1. 您举报的内容以及侵犯了您什么权益？（请在邮件中列出您举报的内容、链接地址，并给出简短的说明）
- 2. 您是谁？（身份证明材料，可以是身份证或护照等证件）
对根叔社区有害的内容
×
不规范转载
×
举报说明
暂无评论