Page 1 of 1

8650 cycle boots after dhcp restart

Posted: 20 Jan 2014 14:36
by itamar2910
Hello,

Last thing that I did was dhcp-server restart after uploading a new dhcp.conf file to /flash/switch with MAC binding.
(before this the dhcp server was working but without binding.)
since then the switch in cycle boot and dosent restarts.
I dont know what to do :( I read a bit about miniboot but I dont know what to delete or to recover.

attached is all the output I get from console when the switch reboots.
omniswitch.txt
Please assist.

Regards,
Itamar

Re: 8650 cycle boots after dhcp restart

Posted: 21 Jan 2014 03:50
by itamar2910
OK,
The switch load after deleting the dhcp files from /flash/switch folder.

Can some one please tell me is that is the correct configuration to DHCP binding.

Code: Select all

server-identifier sample.example.com;
    
subnet 10.135.130.0 netmask 255.255.255.0 {
	dynamic-dhcp range 10.135.130.100 10.35.30.200 {
	option subnet-mask 255.255.255.0;
	option routers 10.135.130.1;
	option domain-name-servers 10.135.120.21;
	option dhcp-lease-time 900;
	}
	manual-dhcp 00:0f:fe:a0:36:25 10.135.130.33{
	option subnet-mask 255.255.255.0;
	option routers 10.135.130.1;
	option domain-name-servers 10.135.120.21;
	}
}
Is it recommended to use the omniswitch as a DHCP server ?

any suggestion will be most welcome.

Itamar

Re: 8650 cycle boots after dhcp restart

Posted: 21 Jan 2014 06:17
by devnull
I guess you have a fairly old 6850 with only 64MB Flash? or your flash is full with pmds.

From the log output it seems as if the switch has crashed and created a pmd.. and now has no space left on the flash.

I would:
- interrupt the boot sequence to uboot and go to miniboot:

Code: Select all

Err:   serial

No ethernet found.
IDE:   Bus 0: OK 
  Device 0: Model: CF 64MB Firm: 06/07/29 Ser#: GHS3ABPCF07012200001
            Type: Removable Hard Disk
            Capacity: 62.5 MB = 0.0 GB (128000 x 512)
USB:   scanning bus for devices... 
      USB device not responding, giving up (status=80000000)
0 USB Devices found
Hit any key to stop autoboot:  0 
^^^^^^^^^^^^^^^^^^^^^^^^^Interrupt here

Code: Select all

=> setenv bootflags 0x1000
=> run miniboot

Code: Select all

## Booting image at ff900000 ...
   Image Name:   miniboot-6.4.4.213.R01
   Image Type:   PowerPC VxWorks Kernel Image (gzip compressed)
   Data Size:    1014773 Bytes = 991 kB
   Load Address: 00005000
   Entry Point:  00005000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Ethernet MAC address not copied to NV RAM
Loading .text @ 0x01000000 (1629912 bytes)
Loading .rodata @ 0x0118ded8 (349411 bytes)
Loading .data @ 0x011e33c0 (139148 bytes)
Clearing .sbss @ 0x01205350 (1560 bytes)
Clearing .bss @ 0x01206000 (1579460 bytes)
## Using bootline (@ 0x4200): flash(1,0)cmm:default h=192.168.10.1 e=192.168.10.1:ffffff00 cb=9600 cp=none cs=1 cw=8 cm=modemControlOff f=0x1000 
## Starting vxWorks at 0x01000000 ...
USB2 Host Stack Initialized.
USB Hub Driver InitiaDized 
USBD  Wind River Systems, Inc. 562 Initialized
M824xHCI Controller found.
Waiting to attach to USBD...one.
0xffffde0 (tRootTask): usbBulkDevInit() returned OK
usbCbiUfiDevInit() returned OK
CBI Class Driver Successfully Initialized
ataDrv call. 0 1 24 24 621 0 0

CS EEPROM Module ID: 4201221a , System type: 24 port Lite 100Base-T, with 4 combo ports, stacking - kite2


Adding 5597 symbCols for standalone.
heck Disk Running ...
dosChkLib : CLOCK_REALTIME is being reset to TUE JAN 21 15:41:40 2014
Value obtained from file system volume descriptor pointer: 0xf59b9d8
The old setting was THU JAN 01 00:00:00 1970
Accepted system dates are greater than THU DEC 27 00:00:00 1990
/flash/  - Volume is OK 


Boot parameters are:

 'flash(1,0)cmm:default e=10.255.24.81:ff000000 h=192.168.10.1 g=10.255.24.181 f=0x1000 cb=9600 cp=none cs=1 cw=8 cm=modemControlOff'


AOS miniboot version: 6.4.4.213.R01
VxWorks (for Alcatel CMM Motorola MPC8248) version VxWorks5.5.1
KERNEL: WIND version 2.6
Made on Jan 27 2011, 05:49:51.
Copyright Wind River Systems, Inc., 1984-2006

CPU: Motorola MPC8248.  Processor #0.
Memory Size: 0x10000000 (256 MB).  BSP version 1.2/1.

WARNING: Stopping in miniboot as directed by boot flags...
[Miniboot]->
in miniboot: remove the pmds (and probably the dhcp file):

Code: Select all

[Miniboot]->ls
network 
working 
boot.params 
boot.slot.cfg 
switch 
swlog1.log 
certified 
swlog2.log 
tech_support.log 
random-seed 
installed 
value = 0 = 0x0
[Miniboot]->ls "/flash/working"
/flash/working/. 
/flash/working/.. 
/flash/working/boot.cfg 
/flash/working/Ksecu.img 
/flash/working/K2os.img 
/flash/working/Kadvrout.img 
/flash/working/Kbase.img 
/flash/working/Kencrypt.img 
/flash/working/Keni.img 
/flash/working/software.lsm 
value = 0 = 0x0

rm "crash.pmd"
rm "network/dhcp.conf"

if you have Command that have parameters e.g. cp /flash/working/boot.cfg /flash/certified/boot.cfg

you need to seperate that by a comma:
cp "/flash/working/boot.cfg","/flash/certified/boot.cfg"

a "reboot" should than restart the switch.


Upgrade to latest code!

Re: 8650 cycle boots after dhcp restart

Posted: 21 Jan 2014 07:41
by itamar2910
thanks devnull,
removing the dhcpd files and rebooting the switch solved the issues.

after it rebooted I deleted all the crash files.

Regards,
Itamar

Re: 8650 cycle boots after dhcp restart

Posted: 22 Jan 2014 04:33
by itamar2910
Issue solved.
This is the 3rd time I am posting the solution:
as devnull wrote, I deleted the dhcpd.conf from the switch and boot it successfully.

Re: 8650 cycle boots after dhcp restart

Posted: 22 Jan 2014 10:08
by devnull
I have never used a Omniswitch for dhcp purposes, and your experiences do not encourage me ;-)

I have heard that it is used in some carrier/CPE whatever setups, so it should do.

AFAIK a switch should not crash because of a dhcp config, so you could/should update to latest code, test again and open a SR if the problem persists..

I can't tell you whether you config is ok..

If i remember correctly there was a crash bug in an old software (can't find the PR) when the switch nwould crash while using ":" instead of "-" in macaddresses..

so please try (as in the manual) with

manual-dhcp 00-0f-fe-a0-36-25 10.135.130.33
instead of
manual-dhcp 00:0f:fe:a0:36:25 10.135.130.33

Also the NT guide sets the { in it's own line..
have you tried copy/pasing from NT Guide?


which AOS release are you using?