DCWS-6028无线控制器曲折的升级过程

写的比较乱,但大概过程基本就是这样!

一、之前的升级步骤级失败原因分析:

我是按这个步骤升级的:

升级方法:

1、console控制AC,重启进入boot模式。

2、setconfig设置本机的ip和tftp服务器的ip,然后saveconfi

3、load <bootrom文件>

4、write boot.rom /f

5、load <config.rom文件>

6、write config.rom

7、重启AC,并进boot模式

8、load <img文件>

9、write nos.img /f

10、重启即可。查看版本为7.0版本。

厂家工程师说,应该先升级config.rom,再升级boot.rom。从小文件开始升级比较稳妥。

第一次升级到write DCWS-6028_7.0.3.0(R0011.0025)_nos.img /f这一步的时候,也是提示diss is full,我就用delete nos.img命令删除了原有的img,然后重启。

于是重启后就出现,下图的提示:

然后就是反复的重启了。这个时候dir看到的是如下的内容:

 

没有nos.img文件了,而报错也是提示找不到primary和backup的nos.img文件。

PS:感觉是因为升级的过程有问题,把文件搞乱了。系统启动找不到nos.img文件,所以总是循环报错。但是nos.img是确确实实升级上去并保存了,是存在的。最后我明白原因了,因为第一次升级完启动后,BOOT版本还是6.0的,不是7.0,所以也有可能是6.0的boot版本认不出7.0的nos.img,所以报错。

下图是7.0版本Boot的启动界面,这个才对。。

 

然后就是第二次升级的过程了(第二项内容),我重新理了理过程,尝试升级并升级成功的叙述!

二、第二次升级,CRT重新设置了颜色,为了截图更容易区分。

下图是新版本的命令:

 

但是BOOT下无法使用TFTP,提示找不到网卡,ping命令也不能用,不知道是什么原因。

用TFTP就提示这个错误(见下图)

 

 

但是无论如何也得把nos.img写进去啊!没办法,我只好用xmodem协议传了。Xmodem模式下9600的波特率速度只有1KB/S,整个传完得5个小时,太坑爹了!

我把波特率改成了115200,速度提升到了3KB/S,第一次传没反应,重启后又试了几次就可以了传了,重启完就变成9600了,要再改一次才行。

7.0版本的BOOT下又一个baudrate命令,可以查看和修改波特率。

“Baudrate 》回车”是查看波特率,“Baudrate 115200》回车”是设置波特率为115200。

 

第一次升级报了个错误,NOS.IMG丢了个文件。好在升级完之后,重启进BOOT,又可以用TFTP了,省了不少事。另外,7.0的BOOT命令有很大变化,DIR看不到原有的config.rom和boot.rom这两个文件了。

因为刚升级的nos.img有文件丢失,所以用TFTP重新升了一个上去,但是这次是用的长文件名DCWS-6028_7.0.3.0(R0011.0025)_nos.img升的。

 

另外,FLASH的大小只有32M,所以写入的时候会提示下图中的DISK IS FUUL的提示。

我的做法是:删除了nos.img,然后再执行

“write DCWS-6028_7.0.3.0(R0011.0025)_nos.img /f”命令,强制写入!

 

写入后重启,重启的过程如下:

PS:有几处提示找不到xxx.pem文件,我百度了一下,应该是密钥之类的东西吧!

我把报错的地方用红色字体标出来了。

U-Boot 2011.12-svn59078 (Jan 23 2013 - 15:13:34)MPC83XX, Build: jenkins-Ivy7.0_Wireless_6028_boot-8

Reset Status:

CPU:   e300c1, MPC8347_TBGA_A, Rev: 3.0 at 528 MHz, CSB: 264 MHz

I2C:   ready

DRAM: 512 MiB (DDR2, 64-bit, ECC off, 264 MHz)

Flash: 32 MiB

Using default environment

In:    serial

Out:   serial

Err:   serial

Net:   No ethernet found.

Bootrom version: 7.0.20

Creation date: Jan 23 2013 - 15:13:31

Testing RAM...

0x0A000000 RAM OK.

Loading flash:/dcws-6028_7.0.3.0(r0011.0025)_nos.img ...

## Booting kernel from Legacy Image at 04000100 ...

   Image Name:   Linux-2.6.21.1

   Image Type:   PowerPC Linux Kernel Image (gzip compressed)

   Data Size:    15486961 Bytes = 14.8 MiB

   Load Address: 00000000

   Entry Point: 00000000

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

BusyBox v1.19.3 (2012-03-12 20:53:06 CST) built-in shell (ash)

Enter 'help' for a list of built-in commands.

Current time is Thu Mar 29 00:29:04 2000

Switch Series Switch Operating System

Software Version 7.0.3.0(R0011.0025)

Compiled Apr 09 10:42:12 2013

28 Ethernet/IEEE 802.3 interface(s)

Mac Addr 00-03-0f-2b-ed-c4

%Mar 29 00:29:10 2000 OPENSSL: The file flash:/wsdh512.pem don't exist in the system!

%Mar 29 00:29:10 2000 OPENSSL: The system could't read Diffie Hellman parameters, so need to create!     //提示系统无法读取Diffie Hellman 参数,这个东西应该是个加密算法!

%Mar 29 00:29:10 2000 OPENSSL: The system is creating Diffie Hellman parameters, and it will take a few minutes! Please wait...    //系统要花几分钟重建

Loading factory config ...

%Mar 29 00:29:17 2000 %LINK-5-CHANGED: Interface Vlan1, changed state to UP

%Mar 29 00:29:19 2000 OPENSSL: The system successfully create Diffie Hellman weak parameters.

%Mar 29 00:33:38 2000 OPENSSL: The system successfully create Diffie Hellman strong parameters.      //大意是重建成功了!

web server is on

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/1, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/1, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/2, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/2, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/3, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/3, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/4, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/4, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/5, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/5, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/6, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/6, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/7, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/7, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/8, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/8, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/9, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/9, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/10, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/10, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/11, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/11, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/12, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/12, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/13, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/13, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/14, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/14, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/15, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/15, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/16, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/16, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/17, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/17, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/18, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/18, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/19, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/19, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/20, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/20, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/21, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/21, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/22, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/22, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/23, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/23, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/24, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/24, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/25, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/25, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/26, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/26, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/27, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/27, changed state to DOWN

%Mar 29 00:33:38 2000 %LINK-5-CHANGED: Interface Ethernet1/0/28, changed state to UP

%Mar 29 00:33:38 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/28, changed state to DOWN

%Mar 29 00:33:43 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0/18, changed state to UP

%Mar 29 00:33:44 2000 %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1,changed state to UP

Switch>%Mar 29 00:34:10 2000 WIRELESS_SSL: Certification file don't exist, so need to generate.

Can't find file "flash:/wssl2_cert.pem" error!

Can't find file "flash:/wssl2_key.pem" error!

%Mar 29 00:34:10 2000 WIRELESS_SSL: The system is creating certification file...

%Mar 29 00:34:10 2000 WIRELESS_SSL: The system is creating server RSA key pair...

%Mar 29 00:34:12 2000 WIRELESS_SSL: The system is verifying RSA key pair...

%Mar 29 00:34:20 2000 WIRELESS_SSL: The system write the RSA key into file flash:/wssl2_key.pem.

%Mar 29 00:34:28 2000 WIRELESS_SSL: The system write server certificate into file flash:/wssl2_cert.pem.        //这里也有几处错误,是我比较担心的,也没有重建之类的提示,所以不太放心!

Switch>   //等了半天没反应,我直接回车,结果就进到这里了

时间: 2024-10-01 20:12:14

DCWS-6028无线控制器曲折的升级过程的相关文章

浅谈站点升级过程中你必须注意到的几个小细节

  每一个站点为了提高安全性.用户的友好体验度等等,都免不了要对站点进行升级.而升级对于站点的SEO的影响又是刻骨铭心的.如果此时你的网站已经有不错的搜索结果排名.升级给网站所造成的冲击也是不可避免的.站长们都知道这个影响轻则会对网站的排名产生负面影响,严重的话很可能会因为处理不好而遭到搜索引擎不必要的惩罚.那么我们在升级过程中要如何降低对网站造成的影响呢?我们需要注意到很多问题,尤其是在一些小细节上.不然的话千里之堤将可能毁于蚁穴. 细节一:切忌直接在线上修改 一个站点的升级并不容易,期间可能

H3C无线控制器+FIT AP:企业组网的一个新选择

对于传统的网络的组建无法考虑到最新设备使用特点,这些设备包括笔记本.平板电脑.智能手机......这些设备都是采用无线接入的,未来的发展对于企业无线网络搭建和无线网络管理都将是我们需要考虑的. 目前这中基于无线网络控制器的解决方案包括有:无线网络控制器.瘦无线接入点(Fit AP).无线传感器.AAA服务器等.所有这些设备联合在一起,在有线局域网络的基础上以瘦AP和传感器为边界,无线控制器为核心的无线网络.该网络具有支持统一管理,且能够使移动和安全融为一体等先进特性.下面我就真的一个基本的网络拓

FreeBSD 6.2-RELEASE下用freebsd-update升级过程

FreeBSD 6.2-RELEASE下用freebsd-update升级过程: mail#uname -a FreeBSD mail.extmail.org 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Nov 2 13:04:30 UTC 2007 qiao@qiao.lpzq:/usr/src/sys/i386/compile/kernel_IPFW i386 mail#freebsd-update fetch install Looking up upd

用python和redis构建高性能监控平台思路与框架升级过程

关于python应用监控平台的话题 先说明,这不是人人业务的监控框架,是我在上一家公司,我所在部门的监控框架... 刚入行的时候,对于监控方面,用的是nagios和cacti. 两个都很强大的监控平台,可扩展性也都很不错.要是想用一个平台实现报警和性能信息的展示的话,他俩都需要加点东西.两个的合体可以考虑zabbix.操作和理解都挺简单的.唯一让人不爽的是存在myql里面,国外有个老外可以改到我钟爱的mongodb里面,但是我看不懂,也没有操作成功... php  这个真不会... 后来到了大公

魅族由器升级过程异常断电变砖怎么恢复

  TFTP升级攻略(仅适用于魅族路由器极速版) 准备工作:准备一根网线,一端接路由器中间的网口(LAN口),另一端接电脑网口.请将电脑Windows防火墙暂时关闭,否则会导致TFTP升级不成功!好,我们开始进行电脑设置. 一.进入电脑设置网卡固定IP,如图一操作,进入"控制面板"->网络和Internet->网络和共享中心的 "本地连接". 点击图二中的"属性",选择Internet协议版本4(TCP/IPv4),点击"属

Android系统Recovery工作原理之使用update.zip升级过程---updater-script脚本语法简介以及执行流程(转)

  目前update-script脚本格式是edify,其与amend有何区别,暂不讨论,我们只分析其中主要的语法,以及脚本的流程控制. 一.update-script脚本语法简介:           我们顺着所生成的脚本来看其中主要涉及的语法.         1.assert(condition):如果condition参数的计算结果为False,则停止脚本执行,否则继续执行脚本.         2.show_progress(frac,sec):frac表示进度完成的数值,sec表示整

从DB2 V9.7到V10.1升级过程实录

IBM DB2 V10.1 for Linux, Unix, and Windows,简称 DB2 V10.1,是 IBM 在 Linux,Unix 和 Windows 平台上的企业级数据库产品 DB2 for LUW 的http://www.aliyun.com/zixun/aggregation/29707.html">最新版本,它已于 2012 年 4 月正式发布.DB2 V10.1 提供了很多新的功能特性以及对一些老的 DB2 特性做了加强,关于 DB2 V10.1 的新特性,可以

记一次patch升级过程

记一次补丁升级过程从11.2.0.4.0 到11.2.0.4.3   1检查当前数据库PSU号: cd/DBSoft/Product/11.2.4/db_1/OPatch/ ./opatch version OPatch Version: 11.2.0.3.4 终于明白上面这个是OPatch工具的版本,不是不定的版本.注意补丁的版本看OUI version OPatch version : 11.2.0.3.4 补丁工具版本 OUI version : 11.2.0.4.0    补丁版本  

Web APi之控制器选择Action方法过程(九)

前言 前面我们叙述了关于控制器创建的详细过程,在前面完成了对控制器的激活之后,就是根据控制器信息来查找匹配的Action方法,这就是本节要讲的内容.当请求过来时首先经过宿主处理管道然后进入Web API消息处理管道,接着就是控制器的创建和执行控制器即选择匹配的Action方法最终并作出响应(在Action方法上还涉及到模型绑定.过滤器等,后续讲).从上知,这一系列大部分内容都已囊括,我们这一系列也就算快完事,在后面将根据这些管道事件以及相关的处理给出相应的练习来熟练掌握,希望此系列能帮助到想学习