Weird log messages

[DeichShaf]

We're running mostly with 6850 but some newer devices are 6450 with firmware 6.6.4.177.R01 (which is quite old)

Within the log files we see the following messages which are not mentioned within our documentation and i'd like to know what their meaning is:

Code: Select all

MON JAN 19 11:39:40 2015         SYSTEM    info I2C_do_transaction: i2cread get fail! tmp_len[30] = len[64] - rxtx_len[0] channe
MON JAN 19 11:39:40 2015         SYSTEM    info [Count.]l addr = 82, data_addr = 0 len = 64
MON JAN 19 11:39:40 2015         SYSTEM    info ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒: Power Supply = 4596420 i2cRandomRead ERROR
I2C READ GET RECEIVE2015         SYSTEM    info
MON JAN 19 11:39:41 2015         SYSTEM    info I2C_do_transaction: i2cread get fail! tmp_len[30] = len[64] - rxtx_len[0] channe
MON JAN 19 11:39:41 2015         SYSTEM    info [Count.]l addr = 82, data_addr = 0 len = 64
MON JAN 19 11:39:41 2015         SYSTEM    info ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒: Power Supply = 4596420 i2cRandomRead ERROR

Later on the log states, that the power supply is operational.

The next bit bothers me since we're experiencing some troubles with DHCP:

Code: Select all

MON JAN 19 11:40:01 2015    DHCP-SERVER   alarm Load initial policy file failed.  Error=13893637
MON JAN 19 11:40:01 2015    DHCP-SERVER   alarm Cannot open QDHCP configuration file: /flash/switch/dhcpd.conf.  Error=13893637
MON JAN 19 11:40:01 2015    DHCP-SERVER   alarm Cannot open QDHCP configuration file: /flash/switch/dhcpd.conf.lastgood.  Error=
MON JAN 19 11:40:01 2015    DHCP-SERVER   alarm [Count.]13893637

And some other I2C related messages we don't understand either:

Code: Select all

I2C READ GET RECEIVE2015         SYSTEM    info
MON JAN 19 11:40:21 2015         SYSTEM    info I2C_do_transaction: i2cread get fail! tmp_len[20] = len[20] - rxtx_len[0] channe
MON JAN 19 11:40:21 2015         SYSTEM    info [Count.]l addr = 80, data_addr = 0 len = 20
MON JAN 19 11:40:21 2015         SYSTEM   alert i2cReadPartialSFPSep: sfpModuleId 23 i2cRandomRead ERROR retry 1
I2C READ GET RECEIVE2015         SYSTEM    info
MON JAN 19 11:40:21 2015         SYSTEM    info I2C_do_transaction: i2cread get fail! tmp_len[20] = len[20] - rxtx_len[0] channe
MON JAN 19 11:40:21 2015         SYSTEM    info [Count.]l addr = 80, data_addr = 0 len = 20
MON JAN 19 11:40:21 2015         SYSTEM   alert i2cReadPartialSFPSep: sfpModuleId 23 i2cRandomRead ERROR retry 2
I2C READ GET RECEIVE2015         SYSTEM    info
MON JAN 19 11:40:21 2015         SYSTEM    info I2C_do_transaction: i2cread get fail! tmp_len[20] = len[20] - rxtx_len[0] channe
MON JAN 19 11:40:21 2015         SYSTEM    info [Count.]l addr = 80, data_addr = 0 len = 20
MON JAN 19 11:40:21 2015         SYSTEM   alert i2cReadPartialSFPSep: sfpModuleId 23 i2cRandomRead ERROR retry 3
I2C READ GET RECEIVE2015         SYSTEM    info
MON JAN 19 11:40:21 2015         SYSTEM    info I2C_do_transaction: i2cread get fail! tmp_len[20] = len[20] - rxtx_len[0] channe
MON JAN 19 11:40:21 2015         SYSTEM    info [Count.]l addr = 80, data_addr = 0 len = 20
MON JAN 19 11:40:21 2015         SYSTEM   alert i2cReadPartialSFPSep: sfpModuleId 23 i2cRandomRead ERROR retry 4
I2C READ GET RECEIVE2015         SYSTEM    info
MON JAN 19 11:40:21 2015         SYSTEM    info I2C_do_transaction: i2cread get fail! tmp_len[20] = len[20] - rxtx_len[0] channe
MON JAN 19 11:40:21 2015         SYSTEM    info [Count.]l addr = 80, data_addr = 0 len = 20
MON JAN 19 11:40:21 2015         SYSTEM   alert i2cReadPartialSFPSep: sfpModuleId 23 i2cRandomRead ERROR retry 5

I'm not sure whether the switch has to be replaced or not, but as far as i can remember from other devices using IIC it is defintely no good if communications on that bus is unsuccessful. Are there any suggestions what to do (except from replacing the firmware, which we will of course do asap) or where to obtain further information?

Thanks and regards
Sven Wagner

[rekeds]

latest firmware?

[devnull]

Try latest Firmware.

The QDHCP errors are normal if you do not use the dhcp server inside the switch.
The i2cread are not usual, i would open a SR to clarify.
For "i2cReadPartialSFPSep" do you use alcatel certified SFPs?