VXworks corrupted with incomplete IP address of sw0

[KarstenHuhn]

Hi guys,

does anyone know how to correct a faulty ip address in VXworks?
The boot parameters (c command) have been set properly but VXworks seems to retain fragments of a faulty IP address "in the belly" (see picture).
-> "Attaching network interface sw0... Error setting inet address of sw0 to 192.1681"

VXworks is 5.4, system is a 3100 ICP.
I already tried FF command, but it didn't help - system doesn't boot anymore.

Thanks!

Karsten

 

[Billz66]

if you know all the parameters you should be able to enter the cd command to reset it back to default
then go through and enter the parameters carefully - DO NOT USE backspace
the parameters have to be entered correctly ( subnet in hex ffffff00 = 255.255.255.0)


If I never did anything I'd never done before , I'd never do anything.....

 

[KarstenHuhn]

Already did this... c and cd command are the same aren't they.
Anyhow, tried that and it still doesn't work.
VXworks still carries on to insert 192.1681 as IP address for sw0.

 

[Billz66]

cd should assign all parameters back to the default
c just starts the menu and then you have to step through


If I never did anything I'd never done before , I'd never do anything.....

 

[jpruder]

FWIW, I always choose c to verify settings before any @ when doing changes. Remember . deletes

 

[Billz66]

Might help us help you if you step through all the settings ( after pressing c) and send a screenshot

the main issues are caused by trying to fix a badly entered entry - you cant do that , if a mistake is made , step through and start again

If I never did anything I'd never done before , I'd never do anything.....

 

[KarstenHuhn]

Hi folks,

here's what I entered (look screenshot).
Still getting "Attaching network interface sw0... Error setting inet address of sw0 to 192.1681"

Karsten

 

[jpruder]

I don't know what the parameters for the 3100 would bem but alot looks missing and perhaps entered values are incorrect

 

[KarstenHuhn]

The problem is resolved.

I just copied the default system.cfg to the flash card again and the fault disappeared.

Thanks for your help, guys.

Karsten