Gadz-1-MIB: View SNMP OID List / Download MIB

Setting this object results in the reset of the device. The context of warm vs cold is a function of the device's abilities. Enumeration: 'cold': 2, 'warm': 1.

When the sysDiagnostic object is written, it causes a diagnostic function to be executed. When read, it returns 0 for a successful completion of the test, 1 for test in process, and greater than 1 for an error indication of the test. Refer to device documentation for the exact definition of the error codes for the device

The entity that last configured, or is currently configuring the zoning policy.

The timeout value to be used in configuring the zoning agent. The default value is 30 seconds.

The status of the current zoning policy configuration. Enumeration: 'request-invalid': 2, 'no-current-owner': 0, 'request-in-progress': 3, 'request-valid': 1.

The control of the current zoning policy configuration. The procedure for zoning policy configuration is as follows: - user reads nlActiveZoneTable AND/OR nlActiveZoneMemberTable to determine current zone configuration and makes any local edits. - user continually reads back nlZoningPolicyStatus until 'no_current_owner' is received. - user writes its address to nlZoningPolicyControlOwner in order to lock zoning control and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - user can validate that it has successfully locked zone policy control by reading back its own address from nlZoningPolicyControlOwner. - user (optionally) writes timeout value to nlZoningPolicyTimeout, and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - user writes 'clear-zoning-configuration' to nlZoningPolicyControl to clear existing ta nlZoningPolicyControl to clear existing table and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - user continually adds zone OR zone member entries by writing to the appropriate objects using index 0 of the table, and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - after the last entry is made, user writes 'create_table' to nlZoningPolicyControl, and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - OR the user writes 'default-zoning-configuration' to load the default zoning configuration and then continually reads back nlZoningPolicyStatus until 'request_valid' is received. - user writes 'clear_owner' to nlZoningPolicyControl (or waits for the zoning timeout to occur) to release ownership of zoning policy configuration. Enumeration: 'clear-zoning-configuration': 2, 'create-table': 1, 'default-zoning-configuration': 3, 'clear-owner': 0.

The last error condition string returned from the zoning agent.

Number of Pending configured zones for this proxied domain

The Pending Zone Table. - this is the zone table the NMS is building up in the proxy domain, before activating it.

nlPendingZone table entry

An identifier which uniquely identifies a zone in the nlPendingZoneTable

Specifies the name of the zone. This name is also unique in the Pending Zone Table

Specifies the type of the zone Enumeration: 'edgeDevice': 1.

Specifies A sequence of zone member indicies for this zone. Write to this object to add a set of zone members to a zone.

Specifies state of lip propagation policy 0: No lips should propagate into the zone 1: Only SCSI targets are allowed to propagate lips into the zone. 2: Lips are allowed to propagate into the zone from all devices.

Number of pending zone members for this proxied domain

Pending Zone Member Table. This table keeps track of the pending zone members that the current snmp zone configuration session has written to the device. If nothing has been written to this table since the start of the current session, then this table will have no entries. Members are added to this table by writing a zone member name to the nlPendingZoneMemberName at an index of 0.

nlPendingZoneMember table entry

An identifier which uniquely identifies a zone member.

Specifies the name of the zone member. To add an entry to the list of zone member names, a write should be done to index 0.

Specifies the type of this zone member. The type of the zone member dicates the structure of the PendingZoneMemberID. To add an entry to the list of zone member type, a write should be done to index 0. Note that a type of zero is only valid on a get operation. Currently, wwnZoneMember is not supported Enumeration: 'typeNotYetAssigned': 0, 'portZoneMember': 1, 'wwnZoneMember': 3, 'hardAssignedALPAZoneMember': 2.

Specifies the intrinsic ID of this zone member. To add an entry to the list of zone member names, a write should be done to index 0. If the ZoneMemberType is PortZoneMember, the structure is: BYTE 0: The Proxy Management ID of the InterConnect device that this port belongs to. If 0, then this is a 'phantom' zone member, in that it does not have a corresponding device ID. Essentially, a phantom zone member is a zone member that has been created, but not yet bound to a proxied device. Use bytes 2 and 3 to correctly determine the ID of this zone member. BYTE 1: The Port Number on the InterConnect Device. BYTE 2: The device ID of the chassis that contains the slot that contains this port. (only valid if byte 0 equals 0) BYTE 3: The slot number of the slot that contains this port. (only valid if byte 0 is 0) If the ZoneMemberType is HardAssignedALPAZoneMember, then the structure is: BYTE 0: The Proxy Management ID of the InterConnect device that this port belongs to. If 0, then this is a 'phantom' zone member, in that it does not have a corresponding device ID. Essentially, a phantom zone member is a zone member that has been created, but not yet bound to a proxied device. Use bytes 3 and 4 to correctly determine the ID of this zone member. BYTE 1: The Port Number on the InterConnect Device. BYTE 2: The hard-assigned AL_PA of the NL_Node. BYTE 3: The device ID of the chassis that contains the slot that contains this port. (only valid if byte 0 equals 0) BYTE 4: The slot number of the slot that contains this port. (only valid if byte 0 is 0) If the ZoneMemberType is WWNZoneMember, the structure is: BYTE 0 -> size of string : The WWN of the zone member.

Number of active configured zones for this proxied domain. When this object is read the 'Zoning Configuration Event' bit in the devEventStatus object will be reset to zero.

Active Zone Table.

nlActiveZone table entry

An identifier which uniquely identifies a zone.

Specifies the name of the zone

Specifies the type of the zone Enumeration: 'edgeDevice': 1.

Specifies the address space this zone is in. An address space defines a set of Zones whose members share the same FC-AL address range.

Specifies A sequence of zone member indexes for this zone. List is terminated by a value of zero.

Specifies state of lip propagation policy 0: No lips should propagate into the zone 1: Only SCSI targets are allowed to propagate lips into the zone. 2: Lips are allowed to propagate into the zone from all devices.

Number of configured zone members for this proxied domain

Active Zone Member Table.

nlActiveZoneMember table entry

An identifier which uniquely identifies a zone member.

Specifies the name of the zone member

Specifies the type of this zone member. The type of the zone member dictates the structure of the ActiveZoneMemberID Enumeration: 'portZoneMember': 1, 'wwnZoneMember': 3, 'hardAssignedALPAZoneMember': 2.

Specifies the intrinsic ID of this zone member. The structure definition is identical to that of nlPendingZoneMemberID.

The file name to be downloaded from the TFTP server when a download is next requested via this MIB. This value is set to the zero length string when no file name has been specified.

The file name of the switch operational code to be executed on power up. This value is set to the zero length string when no file name has been specified.

The IP address of the TFTP server that contains the boot image to load when a download is next requested via this MIB. This value is set to `0.0.0.0' when no IP address has been specified.

The IntraCom ID of the device to download to. A value of 0 specifies the IntraCom master (i.e., the proxy agent). Values greater than 0 specify proxied devices.

When this object is set to downloadToPROM(2), the device will discontinue its normal operation and begin download of the image specified by downloadFile to the specified IntraCom target from the server specified by downloadTFTPServer using the TFTP protocol. The new image is written to the flash EPROM memory after its checksum has been verified to be correct. When the download process is completed, the device will warm boot to restart the newly loaded firmware. When the device is not downloading, this object will have a value of notDownloading(1). For some Gadzoox devices, there is a window of opportunity to cancel a download. Setting this object to the value 'notDownloading' during the TFTP file transfer from the downloadTFTPServer will cancel the current download for Gadzoox hub products. Enumeration: 'downloadToPROM': 2, 'notDownloading': 1.

The status of the last download procedure, if any. This object will have a value of downloadStatusUnknown(2) if no download process has been performed. Enumeration: 'downloadNoResponseFromServer': 4, 'downloadStatusUnknown': 2, 'downloadAlreadyInProgress': 9, 'downloadCancelled': 10, 'downloadSuccess': 1, 'downloadTftpAccessViolation': 8, 'downloadIncompatibleImage': 6, 'downloadChecksumError': 5, 'downloadGeneralError': 3, 'downloadTftpFileNotFound': 7.

Number of retries for each download attempt.

Timeout value (in seconds) for each download retry.

The file name of the backup configuration files. The switches current configuration is saved in the backup configuration file. The switches configuration is also restored from the configuration file.

The IP address of the TFTP server that the backup configuration file will be saved to and restored from. This value is set to `0.0.0.0' when no IP address has been specified.

When this object is set to backupConfig(1), the device will write it's current configuration files as downloadCfgFileFileName.* to the server specified by downloadCfgFileServerIp. When this object is set to restoreConfig(2), the device will be reconfigured based on the downloadCfgFileFileName.* files located on the server specified by downloadCfgFileServerIp. Enumeration: 'restoreConfig': 3, 'backupConfig': 2, 'noAction': 1.

The status of the last know backup/restore procedure, if any. This object will have a value of BackUpRestoreStatusUnknown(2) if no backup/restore process has been performed. Enumeration: 'backUpRestoreNoResponseFromServer': 8, 'backUpRestoreTftpDriverError': 7, 'backUpRestoreIncomplete': 3, 'backUpRestoreFileNotFound': 9, 'backUpRestoreStatusUnknown': 2, 'backUpRestoreNoFileNameSpecified': 5, 'backUpRestoreCouldNotWriteFile': 10, 'backUpRestoreNoIpAddressSpecified': 6, 'backUpRestoreSuccess': 1, 'backUpRestoreGeneralError': 4.

The maximum number of 'Proxy Managed Interconnect Devices' that can be supported from this agent.

The number of 'Proxy Managed Interconnect Devices' currently connected to this agent.

A count of the number of times 'Proxy Managed Interconnect Devices' have been added to or removed from this agent.

An Element Identifier to identify the physical IC board that contains the proxy agent. It's format is only relevant to Gadzoox service personnel.

An 'Element Identifier' to identify the firmware version of this SNMP proxy. The format of this identifier is as follows: MM.mm = majorVersion.minorVersion 02.04 as an example.

CRC conducted on the Topology Table. Read: A change in this value indicates a change to the proxy domain ('Proxy Managed Interconnect Device' addition, deletion, or move). Write: A write will return OK if the value written equals the current Topology Table CRC and an ERROR if the value written does not equal the current Topology Table CRC.

Register for Proxy Agent events. Events are 'Proxy Managed Interconnect Device' specific representing alarm-type events such as temperature/fan fault or change in port status

Sequential Device ID indication of any 'Proxy Managed Interconnect Device' events. Each successive read of this object will cycle to the next ID in the list that has outstanding events

A table of devices currently connected to the same Proxy Domain as this agent.

Proxy Device Entry

An integer, ranging consecutively from 1 to proxyCurMembers, which uniquely identifies a particular proxied device. It is not guaranteed, nor should it be assumed, that this identifier will remain constant for any given proxied device.

The authoritative identification of the box which provides an easy and unambiguous means for determining the type of box.

An' Element Identifier' to identify the product type and serial number of this device.

An 'Element Identifier' to identify the primary IC board for the proxied device.

An 'Element Identifier' to identify the firmware version of this proxied device.

This bit-mapped register defines event indicators for the proxied device. Each bit in this register represents a single event defined as follows. Register Definition: BYTE 0 Bit 0: Port Event to clear bit access capPimPortStatus Bit 1: Chassis Event (Fan/Blower, Power, Temperature) to clear bit access capChasEventStatus Bit 2: Configuration Event to clear bit access capChasModuleStatus Bit 3: PIM Event to clear bit access capPimEventStatus Bit 4: Zoning Configuration Event to clear bit access nlActiveZoneCount

Resets the proxied device. 'Cold' reset will initialize the device to the power-on state and execute a full self-test diagnostic. 'Warm' reset does the same but does not perform a destructive memory test. Note that some devices don't support a distinction between warm and cold reset (all resets are cold resets Enumeration: 'cold': 2, 'warm': 1.

When the this object is written, it causes a diagnostic function to be executed. When read, it returns 0 for a successful completion of the test, 1 for test in process, and greater than 1 for an error indication of the test. Refer to device documentation for the exact definition of the error codes for the device. For the Capellix switch the bit-mapped constant codes are defined as: PostInitialRamError = 0x2, PostRamError = 0x4, PostInitClockError = 0x8, PostSeepError = 0x10, PostValidFfsError = 0x20, PostInitializeFfsError = 0x40, PostDownloadError = 0x80, all other bits are reserved.

The value of the device's sysUpTime at the time this object was last initialized. If the object has not been initialized since the last reinitialization of the proxy agent, then this object has a zero value.

Total number of hours that the device has be on. This is a persistent value that survives power cycle.

User definable ASCII string to indication contact name for the device. This is a persistent value that survives power cycles.

User definable ASCII string to indication location for the device. This is a persistent value that survives power cycles.

Toplogy Link. A unique octet triplet that associates a proxied device to the overall topology of the proxy domain. Register Definition: BYTE 1 : Parent IntraCom ID. This is the ID of the device that provides the next link up to the proxy device in the IntraCom management hierarchy. For the proxy agent, this value is zero. BYTE 2 : Parent Port. This is the port on the parent device that is connected to this device. BYTE 3 : Uplink Port. This is the port on this device that is connected to the parent device.

Time (in 100ths of seconds) that Beacon LED is on. A value of zero (with devBeaconOffTime non-zero) will turn the LED permanently off. This object is not supported in this version of the MIB

Time (in 100ths of seconds) that Beacon LED is off. A value of zero (with devBeaconOnTime non-zero) will turn the LED permanently on.B

State of Fault LED, 0=OFF, 1=ON.

Number of configured ports for this proxied device. In the case of a chassis based device, this object represents the number of slots in the box

Description data for this proxied device: Byte 3: OEM 1 Gadzoox (open market) 2 Hewlett Packard 3 Compaq 4 3Com 5 Sun Byte 2: masterType: 0 this is a slave hub 1 this is a permanent master hub, 2 this is a removable master hub, Byte 1: mediaConfig: 1 MEDIA_CONFIG_TYPE_10CO (m3) 2 MEDIA_CONFIG_TYPE_10SW_0LW (m4) 3 MEDIA_CONFIG_TYPE_8SW_2LW (m4) 4 MEDIA_CONFIG_TYPE_12GBIC (m5) 5 MEDIA_CONFIG_TYPE_12GBIC_FIB_COP (m5) 6 MEDIA_CONFIG_TYPE_6GBIC_FIB (m5) 7 MEDIA_CONFIG_TYPE_6GBIC_FIB_COP (m5) 10 MEDIA_CONFIG_TYPE_AS_3GBIC (as2) 17 MEDIA_CONFIG_TYPE_SWITCH_1U_8HSSDC (cap jr) 18 MEDIA_CONFIG_TYPE_SWITCH_1U_8SW (cap jr) 19 MEDIA_CONFIG_TYPE_SWITCH_1U_8GBIC (cap jr) 20 MEDIA_CONFIG_TYPE_CHASSIS_2U_3SLOT (cap) 21 MEDIA_CONFIG_TYPE_CHASSIS_3U_3SLOT (cap) 30 MEDIA_CONFIG_TYPE_CHASSIS_PIM_8CO) (cap) 31 MEDIA_CONFIG_TYPE_CHASSIS_PIM_8SW) (cap) 32 MEDIA_CONFIG_TYPE_CHASSIS_PIM_6GBIC) (cap) 33 MEDIA_CONFIG_TYPE_CHASSIS_PIM_12SW_1GBIC) (cap) 34 MEDIA_CONFIG_TYPE_CHASSIS_PIM_11HSSDC_1GBIC) (cap) 35 MEDIA_CONFIG_TYPE_CHASSIS_PIM_ILS(cap - inter-loop module) 36 MEDIA_CONFIG_TYPE_SWITCH_1U_PIM_3GBIC) (cap jr) Byte 0: numPowerSupply 0 NUM_POWER_SUPPLY_0 1 NUM_POWER_SUPPLY_1 2 NUM_POWER_SUPPLY_2 3 NUM_POWER_SUPPLY_3

An ASCII string to identify this device.

This bit-mapped register declares this SNMP Proxy Agent as the one and only 'active' proxy agent from a possible set of potential SNMP Proxy Agents. Other potential SNMP Proxy Agents must have this value set to 'Disable'. Currently, it is the responsibility of the SNMP manager application to administer this object. Register Definition: BYTE 1 Bit 1: Proxy Control & Status Enable/Disable this device as the SNMP Proxy Agent. Note that this value is always read as 1 from a device that can only act as a proxy master. Setting this object on a device that can only act as proxy master has no effect

A table of serial GBIC information, indexed by device and port. Only GBIC-based devices must implement this table. Each port of a GBIC-based device will have a corresponding row, regardless of whether or not the port contains a serial GBIC; if the port does not contain a serial GBIC or if the serial GBIC information has not yet been fully read, then the value of gbicEntryValid is 'invalid'. The gbic device platforms requires a certain minimal level of firmware to support serial GBIC information. The FeatureMask object indicates whether or not this feature is supported via the SGBIC bit. If this feature is not supported on a given device, then the gbicEntryValid object will have the value 'invalid' for all ports on that device.

GBIC table entry

An identifier which uniquely identifies a device.

An identifier which uniquely identifies a device port.

A flag that indicates whether or not this entry contains valid information. Enumeration: 'valid': 1, 'invalid': 0.

An encoded string that provides information for the serial GBIC associated with this entry's device and port indices. This value is only valid if the associated gbicEntryValid value is 1.

A table of IP addresses to which traps should be sent.

trap table entry

An identifier which uniquely identifies the device to send the trap to.

The IP address of the device to send the trap to. To add an entry to the list of Trap IP addresses, a write should be done to index 0. To delete an entry from the list of Trap IP addresses, a write should be done to the desired index to be deleted with the IpAddress to be deleted. This will cause the Trap IP address table to shrink by one entry. To read the list of Trap IP addresses, indexes starting at 1 and incrementing should be used. An error indication will be returned when the end of the table is reached.

The deviceID of the device with the trap condition.

The type of device with the trap condition. The definition of this field is identical to devType.

The event status of the device with the trap condition. The definition of this field is identical to devEventStatus.

The environmental status of the device with the trap condition. The definition of this field depends on the type of device for which this trap was sent.

The port status of the device with the trap condition. The definition of this field depends on the type of device for whom this trap was sent. The assumption is that the port status for each port fits in 1 byte.

The port attributes of the device with the trap condition. The definition of this field depends on the type of device for whom this trap was sent. The assumption is that the port attributes for each port fits in 1 byte.

The Configuration Status of the device with the trap condition. The definition of this field depends on the type of device for whom this trap was sent. Examples of this event include inserting or removing a plug-in card.

The Lip status of the device with the trap condition. The definition of this field depends on the type of device for whom this trap was sent. Examples of this event include changes to the m5LIPStatus field.

The maximumnum number of IP addresses that can be specified as recepients of traps that are sent from this device.

A table of Capellix chassis devices currently connected to the same agent.

capChas table entry

An identifier which uniquely identifies this device.

A bitmask indicating the features supported on this device. Certain MIB objects are supported only if the underlying feature is supported, as indicated by this object. Feature support may differ between devices due to hardware or software versions. At the present time all features are enabled, so this object is meaningless.

This 2 byte bit-mapped register defines the asynchronous events that can occur on the chassis. When this object is read the 'Chassis Event' bit in the devEventStatus object will be reset to zero. Values: 0 = no fault, 1 = fault. Register Definition: BYTE 0 Bit 0: Fan 1 fault (left-most fan, from back of chassis) Bit 1: Fan 2 fault Bit 2: Fan 3 fault Bit 3: Fan 4 fault (right-most fan, from back of chassis) Bit 4: Power Supply 1 fault Bit 5: Power Supply 2 fault (if high availability unit) Bit 6: Power Supply 3 fault (if high availability unit) Bit 7: Reserved BYTE 1 Bit 0: Temperature fault Bits 1-3: Reserved: Bit 4: POST fault Bits 5-7: Reserved:

This bitmapped object indicates state of each of the chassis LEDs. Values: 0 = LED is OFF, 1 = LED in ON. Register Definition: BYTE 0: Bit 0: power LED Bit 1: fault LED Bit 2: initialization LED Bit 3-7: Reserved BYTE 1: Bit 0: fan tray 1 LED Bit 1: fan tray 2 LED Bit 2-3: Reserved Bit 4: power supply 1 LED Bit 5: power supply 2 LED Bit 6: power supply 3 LED Bit 7: Reserved

This bitmapped object indicates the presence of optional chassis modules (PIMs, power supplies, fan trays) that may or may not be installed in the chassis. A value of '1' indicates the presence of a module. When this object is read the 'Configuration Event' bit in the devEventStatus object will be reset to zero. Register Definition: BYTE 0: Bit 0: slot 1 PIM presence Bit 1: slot 2 PIM presence Bit 2: slot 3 PIM presence Bit 3: Reserved Bit 4: fan tray 1 presence Bit 5: fan tray 2 presence Bit 6-7: reserved BYTE 1: Bit 0: power supply 1 presence Bit 1: power supply 2 presence Bit 2: power supply 3 presence Bit 3-7: Reserved

World Wide Name associated with this chassis.

Internal Temperature of the chassis (in degrees C).

Maximum Allowable Internal Temperature of the chassis .

User-configurable Maximum Internal Temperature Threshold of the chassis.

User-configurable SAN Doctor function of the chassis.

Capellix chassis slot table entry

An identifier which uniquely identifies the Capellix chassis that contains this PIM.

The slot index of this PIM on this chassis.

An identifier which uniquely identifies this PIM in the proxy domain. If this value is 0, this PIM is not managealbe by this chassis.

Description data for this PIM The enumeration of the bytes in this object are identicial to that defined in the object devType.

The value of this object indicates the general status of this PIM. Enumeration: 'unknown': 0, 'present-but-inactive': 3, 'present-and-active': 2, 'empty': 1.

The (potential) IP address of this PIM. If a PIM does not support an IP address, this value is 0.

A table of Capellix chassis PIMs currently connected to the same agent.

capPim table entry

An identifier which uniquely identifies this PIM.

A bitmask indicating the features supported on this device. Certain MIB objects are supported only if the underlying feature is supported, as indicated by this object. Feature support may differ between devices due to hardware or software versions. At the present time all features are enabled, so this object is meaningless.

This 2 byte bit-mapped register defines the asynchronous events that can occur on the PIM. When this object is read the 'PIM Event' bit in the devEventStatus object will be reset to zero. Register Definition: BYTE 0: Bit 0: power supply temperature Bit 1: power level Bit 2: POST fault Bit 3-7: reserved BYTE 1: Reserved

This bitmapped object indicates state of each of the PIM LEDs. Values: 0 = LED is OFF, 1 = LED in ON. Register Definition: BYTE 0: Bit 0: power LED Bit 1: fault LED Bit 2-7: reserved BYTES 1-2: PIM port LEDs BYTE 1, Bits 0-7 = ports 1-8 BYTE 2, Bits 0-7 = ports 9-16 Note that this object is not supported in this release of the MIB

A 16 byte bitmapped octet string that describes the attributes of each of the ports on this PIM. Bytes 0 - 15 describe ports 1 - 16 respectively. Register Definition: Bit Meaning --- ------- 7 Reserved (IntraComm) 6-0 Media type: 0 = GBIC Optical ShortWave 1 = GBIC Optical LongWave 2 = GBIC Optical ShortWave 3 = GBIC Copper Style DB-9 connector 4 = reserved 5 = GBIC Copper Style-2 connector (from parallel ID) 6 = GBIC type information available via serial ID 7 = No GBIC installed 8 = Fixed Copper DB9 9 = Fixed Optical ShortWare - 1.06 Gigabit 10 = Fixed Optical High Density 11 = Unknown 12 = Fixed Copper HSSDC

This 16 byte bitmapped object describes the status of each of the ports on the PIM. The layout of the bits in each byte is as follows: Bit Meaning --- ------- 3-0 encoded state: 0: No GBIC installed 1: Force bypassed by Management 2: Bypassed due to no incomming signal 3: Bypassed due to no outgoin signal 4: Bypassed due to fault: K28.5 denstiy 5: Bypassed due to fault: Running disparity 6: Bypassed due to fault: Mis-aligned K28.5 7: Bypassed due to fault: RLE 8: Bypassed because port is not in any zone 9: Bypassed waiting Cut-In authorization 10: Enabled and initializing 11: Enabled and active 12: Force bypassed by SAN Doctor When this object is read the 'Port Event' bit in the devEventStatus object will be reset to zero.

A table of port objects for the Capellix PIM's

cap port table entry

An identifier which uniquely identifies the capellix PIM that contains this port.

The index of this port on the device.

Port Type 0: unknown 1: initiator 2: target 3: both initator and target

Force Port Bypass Control 0: forced port bypass mode is DISABLED 1: forced port bypass mode is ENABLED

Lip Generation Type 0: generate LIP F7 (if LIP generation is enabled) 1: generate LIP F8 (if LIP generation is enabled)

The total number of detected ALPAs for this port. indicates detection of ALPA 1, and so on. This count is cleared upon either loop initialization or bypass of this port. Bit values can also be cleared manually via capAlpaClear.

Bitmap of ALPAs detected on this port. Bytes 0-15 form an LoopID bitmap similar in form to the bitmaps used in FC-AL address assignment (LIFA/LIPA/LIHA/LISA). If bit 7 of byte 0 is set, then LoopID 0 has been detected on this port. Bit 6 of byte 0 indicates detection of LoopID 1, and so on. This is bitmap is cleared upon either loop initialization or bypass of this port.

Counts the number of times that this port was the first to detect a LIP during loop initialization.

Information to be sent describing an LIP trap from an IntraCom device. Note that this trap may not be supported on some Gadzoox devices

Information to be sent describing an topology change trap from an IntraCom device (subcode=2)

Information to be sent describing an environmental trap from an IntraCom device (subcode=3)

Information to be sent describing an port status trap from an IntraCom device (subcode=4)

Information to be sent describing an configuration trap from an IntraCom device (subcode=5)