Red Hat Bugzilla – Bug 176219
Stale iSCSI session stays active after removing the iSCSI server load balancing initiator
Last modified: 2008-05-01 11:38:06 EDT
Description of problem:
Two targets and 5 hosts are connected to a MDS.All targets and hosts are all
configured in vsan1 and default-zone is used.VRRP1 are configured on all ports
of MDS connecting with hosts.iSCSI server load balance is configured for VRRP1.
Two hosts(10.1.10.25 and 10.1.10.32) are configured as the iSCSI server load
balancing initiators and the rest are dynamic iSCSI initiators.See attached
start config for details.iSCSI server load balance init25 is configured to
access only one of two targets.
After removing the iSCSI server load balance init25 config by " no islb
initiator name $name",init25 than falls back as iSCSI dynamic initiator so it
sets up session for each target in vsan1.But the iSCSI server load balance
stays up which leads to two sessions from the same init to the same target.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Reload the switch with attached start config.Make sure that all iSCSI server
load balance and iSCSI sessions are up.
2. Remove the iSCSI server load balance init 25 by "no islb initiator name
3.Check the iSCSI sessions for iSCSI init25.You can view the problem.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.