Alcatel Unleashed

normal erase via Miniboot / diskInit "flash" and then usb auto-copy bring no positive results... CF-Card low-level-format, new Filesystem (FAT) and the failure was disappeared - until now

greetz

"fsck" say " /flash Volume is OK"... (of bad clusters: 0) - its helps me to format the CF-card (low-level-format) - then install a new ""FAT" and put the images in "/flash/certified"... switch is running since 24h and the failure "Data: disk cache er...

thx, as mentioned in another post - I will try the filesystem check with "fschk" and I will share the result.

thx devnull! you mean erase the flash with "diskInit" (Miniboot) and then a normal AOS-installation via USB-Recovery?
Before I do this, I will try your other clue with "fschk". ThankYou

Hey Folks,

i have a following error on my OS6850-P48 (6.4.4.743.R01)...

Data: disk cache error: device f58dde8 block 0 errno c0003, disk read failed

Anybody knows that? It seems to have no impact for operation. It happens several times a day.
Thanks in advance!

Greetz!

hey kaifengw,

I now, its more than two years ago, but can you remember you how do you fix the "disk cache error" ?

info disk cache error: device f58dde8 block 0 errno c0003, disk read failed

You know its a hw issue?
Thanks in advance!

Thanks for the quick response...
we found the command to relay the qos-log messages to the local swlog/syslog.

qos log console
qos forward log
show qos config

In this switch config are not many policies, so no problem with flooding

Topic can be closed

Hey Folks!

is there a possibility, to foward the output from "show qos log" to a defined "swlog output socket x.x.x.x"?
The content of "swlog" comes on my syslog server - would be great to see the qos log also there.

Thanks in advance!

Greets

Hey silvio!

thank you for the quick response - it works!!

Best regards! Martin

Hey Folks! i had a little problem with a L3 multilayer switch (Alcatel-Lucent OS9616/OS9716-CFM2 6.4.4.645.R01). Principle, the device has two IP-interfaces (one mgnt, e.g. 192.168.10.2 "VLAN10" and on interface to a firewall, e.g. 10.10.100.42 "VLAN100"). There is a response fro...