Extreme Networks EPICenter 4.1, Software Installation Manual

Page: 525 / 546

DLCS Limitations
EPICenter Software Installation and User Guide 525
• When a host is moved from one port to another port on a switch, the old entry will not age out,
unless the host is rebooted or a user login operation is performed after the host is moved.
• DLCS information is dynamic. Therefore, if the switch is rebooted, the DLCS information is lost.
However, this information is still stored in the EPICenter database. To delete the information from
the policy system, you must explicitly delete the configuration parameters using the EPICenter
Policy Manager client.
Alternatively, you can delete the rebooted switch from the EPICenter database using the Delete Device
function in the Inventory Manager. Then re-add the switch using the Inventory Manager Add Device
function.
• DLCS is not currently supported on hosts with multiple NIC cards.
ISQ Improvements
ExtremeWare versions 6.1 or later do not require any Intra-Subnet QoS (ISQ) settings for DLCS.
However, a VLAN must have an IP address in order for DLCS to function on ports on that VLAN.
For ExtremeWare 5.x, ISQ has been improved to also allow the application of IP QoS for traffic on a
Layer 2 switch that is destined outside the served subnet. If your switch is running in L2 mode, and
you want to snoop Layer 4 (NetBIOS) packets, you can do so using ISQ.
To configure this capability, you will need the MAC address of the next-hop router (or the MAC address
of the WINS server, if the server is on the same subnet) and a list of the IP addresses of the WINS
servers. The IP packets to this MAC address and the specified IP addresses are then snooped.
After DLCS has been enabled, the following commands should be used for this configuration:
• Create a list of WINS servers whose packets should be snooped:
create isq-server < name >
• Add the WINS server IP addresses to this list:
config isq-server < name > add ipaddress < WINS-server-ipaddress1 >
config isq-server < name > add ipaddress < WINS-server-ipaddress2 >
•••
• Configure the MAC address of the next hop router:
config isq-server < name > add mac < mac-address-of-next-hop > vlan < vlan-name >