Brocade Communications Systems IP250 user manual 136 53-1003056-01

5 SAN data collection

The Management application uses the short tick interval to ping the switch for a periodic reachability check. If the reachability check succeeds, then the Management application runs pending collectors triggered by an event. When no SNMP traps or syslog events occur, the Management application uses the lazy polling interval to schedule collection of configuration and status changes. The lazy polling interval process schedules any pending collectors for the next short tick. Therefore, the interval between collections when there are no SNMP traps or syslog events is the lazy polling interval plus the short tick interval. To increase polling efficiency, you can configure both the short tick interval (Check for state change every option) and the lazy polling interval (If no state change, poll switch every option) on the Options dialog box. For step-by-step instructions, refer to “Configuring asset polling” on page 168.

There are two types of collectors, fabric-level collectors and switch-level collectors. Fabric-level collectors gather fabric-level information. The Management application collects fabric-level data from the seed switch, for example, the NameServerCollector gathers data about all end devices present in the fabric.

The Management application uses the following Fabric-level collectors:

•DeviceFDMICollector – Collects FDMI-related information for end devices in the fabric.

•NameServerInfoCollector – Collects data about end devices in the fabric.

•ActiveZoneInfoCollector – Collects the active zone configuration in the fabric.

•ZoneInfoCollector – Collects the defined zone configuration in the fabric.

•TopologyCollector – Collects data about the ISLs in the fabric.

•TrunkInfoCollector – Collects data about trunks in the fabric.

•WtJarsCollector – Downloads the jar files needed to launch WebTools from the Management application.

Switch-level collectors gather individual switch-level information (such as, port details and so on). The Management application also uses specialty collectors which run only for switches that have a particular feature. For example the EncryptionBaseCollector only runs for encryption switches. The Management application uses the following Switch-level collectors:

•BottleneckConfigCollector – Collects data about bottleneck configuration on the switch.

•BottleneckStatusCollector – Collects data about the bottleneck status (whether or not a port is bottlenecked) for each port on the switch.

•EncryptionBaseCollector – Collects all encryption related data.

•GroupConfigChangeCollector – Collects encryption data related to HA Cluster, Target Containers, Crypto Host, and Crypto LUN.

•GroupConfigCollector – Collects group member and group collection data.

•FabricCollector – Collects the fabric members (switches) and persists the members in the application. This is the main collector that organizes fabric discovery.

•CeeSwitchCalCollector – Collects the association of a device port to a 10 G physical port on the DCB switch.

•DCBCollector – Collects data specific to the DCB switch.

•FportTrunkCollector – Collects data about F-port trunks present on the switch.

•GigePortCollector – Collects GigE-port data on the switch.

•LicenseCollector – Collects data about licenses on the switch.

•LiteSwitchAssetCollector – Collects the FMS mode setting on the switch.

136	Brocade Network Advisor IP User Manual
	53-1003056-01