On 12/22/2010 11:22 PM, [email protected] wrote:
VLAN creation.
From what I've seen iSCSI support in DCB would work similar
to FCoE, ie the iSCSI traffic will be sent via a separate
VLAN. Which we would need to create, eventually.
So basically we would need something similar to 'fipvlan'
or integrate this functionality into open-iscsi.
Well there are more methods actually. Separating them into separate VLAN's
would tag them to the priority of the VLAN(8 in all) however sometimes the tag
is based on the application type port number.
So, in the iSCSI case the well known port number 3260 becomes the priority
decider.
I actually broke the code to support ports other than 3260 in a rhel
test release, and so I know people use other ports in real life setups
:) I would bet the vast majority of times it is 3260, but it is not
always so I do not think you can count on it if that is what you are saying.
Usecase - Tag all iSCSI traffic to a specific port type in a virtualized
environment. Its very cumbersome to manage vlans in the virtualized
environments.
Also ETS determines that within the same priority group the bandwidth could be
split further. Now, this could be per connection. My hunch is that we need
more flexible ways of splitting the bandwidth within a priority group per
connection via the lldpad.
What is ETS?
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
