Unsolved
This post is more than 5 years old
4 Posts
0
17432
April 22nd, 2011 03:00
Powerconnect 8024F iscsi_handlers.c warnings
Hi,
We have 2 Powerconnect 8024F switches that keep giving iscsi warning messages.
<187> APR 22 17:13:47 10.31.114.226-1 ISCSI[341074432]: iscsi_handlers.c(188) 171 %% Couldn't create static rule
Is there anyway to get rid of these warnings?
------------------------------------------------------------
console#show iscsi
iSCSI disabled
iSCSI CoS disabled
iSCSI vpt is 5
Session aging time: 10 min
Maximum number of sessions is 192
------------------------------------------------
iSCSI Targets and TCP Ports:
------------------------------------------------
TCP Port Target IP Address Name
---------------------------------------------------
iSCSI Static Rule Table
---------------------------------------------------
Index TCP Port IP Address IP Address Mask
1 9876 - -
2 25555 - -
3 9876 - -
-----------------------------------------------------------
Thanks,
nl
0 events found
kdonnan
4 Posts
0
April 30th, 2011 04:00
We have experienced the same issue with our PowerConnect M8024 blades.
Similar setup with the only difference being I have 32 similar entries in my iSCSI static rule table. The error happens twice every thirty seconds. on each switch.
we are on firmware version 4.1.0.6
Any ideas?
Thanks
dellnl
4 Posts
0
May 2nd, 2011 02:00
We also have M8024 blades on 4.1.0.6, but these don't have this issue.
I think there's a difference in firmware revision.
M8024 - 4.1.0.6, A19
8024F - 4.1.0.6, A05
What version do you have on the M8024's?
There are also 32 entries on the static rule table.
dellnl
4 Posts
0
May 2nd, 2011 02:00
The same sort of thing happens when you disable "ISDP Mode"
kdonnan
4 Posts
1
May 4th, 2011 08:00
The problem appears to be comming for LLDP.
We have Equallogic SANs and I believe the new powerconnect firmware has been designed to optimize for iSCSI. I don't believe Equallogic has approved this feature (yet). They currently recommend you turn off ISCSI services on the switch.
In our case LLDP was picking up the connection to the Equallogic ports and trying to inform the iSCSI service (which we have disabled) causing the error.
Disabling LLDP on the Equallogic SAN ports stopped the error.
-Kurt
dellnl
4 Posts
0
May 5th, 2011 02:00
After disabling LLDP the error messages stopped.
Thanks.