Specifications

Optimized Node/Alias Implementation
Automated Security Manager processes Dragon events by locating the intruder IP address stored in the event
and then taking action. This search process is completed far more quickly on devices implementing the
"optimized" Node/Alias MIB table. The following table lists devices and firmware revisions supporting the
optimized Node/Alias MIB table.
Devices/Firmware that support "Optimized" Node/Alias:
Product Family Firmware
Version
Matrix E1
3.00.xx
3.01.xx
3.02.xx
Matrix E6/E7 (2nd/3rd Generation)
5.06.xx
5.07.xx
5.08.xx
Matrix N3/N7
Platinum and Gold
3.00.xx
4.00.xx
4.05.xx
4.11.xx
Matrix V2
2.03.xx
2.04.xx
NOTES: Support for Optimized Node/Alias −− The Automated Security Manager Incident Detail view
(right−click an entry in the Activity Monitor and select View Details) indicates whether a device
supports the optimized Node/Alias table or not:
"Reading ctAliasTable" means that the device does not support the optimized
Node/Alias table.
•
"Reading ctAliasProtocolAddressTable" means that the device does support the
optimized Node/Alias table.
•
Devices that do not support Node/Alias:
−− Matrix C1
−− SecureStack C2
−− Matrix E5
−− Matrix E1 (1G6xx−xx)
−− Vertical Horizon
−− AP 3000
−− RoamAbout R2
These devices do not support any form of Node/Alias. For these devices, the Automated
Security Manager search resolves the searched IP address to the corresponding MAC address
and does a MAC−based search to locate the physical port. Routers must be included in the
search scope in order to provide access to the routers' ARP cache. In addition, you must select
the ipRouteTable and ipCIDRRouteTable MIBs in the Automated Security Manager Options
Automated Security Manager Help
Optimized Node/Alias Implementation 10