Brocade Error Message Reference Guide v6.0.0 (53-1000600-01, April 2008)

478 Fabric OS Message Reference

53-1000600-01

ZONE-1004

Message <timestamp>, [ZONE-1004], <sequence-number>,, INFO, <system-name>, port <port

number>

enforcement changed to Session Based HARD Zoning.

Probable Cause Indicates that the zoning enforcement changed to session-based hard zoning. When a device is

zoned using both world-wide name (WWN) in one zone and <domain, portarea> in another, this will

cause that port to go session based hard zoning.

In session-based zoning, the zone enforcement is checked by the software. In hardware-enforced

zoning, zone or alias members are defined using <domain, portarea> exclusively or using WWNs

exclusively: that is, using one method or the other to define all objects in the zoning database. If the

devices on the port are defined by a mixture of port IDs and WWNs, the zone enforcement is

session based. If the S_ID list of the hardware-enforced zoning overflows (over the S_ID limit), the

hardware zone enforcement changes to session-based zoning.

Recommended

Action

No action is required.

Severity INFO

ZONE-1005

Message <timestamp>, [ZONE-1005], <sequence-number>,, INFO, <system-name>, HARD & SOFT

zones(<zone name>, <zone name>) definitions overlap.

Probable Cause Indicates that a port is zoned with mixed devices (world-wide name (WWN) and <domain,

portarea>). During zoning database cross checking, it is detected that either:

• A port zone member is also listed as a member of a Mixed zone,

• A world-wide name (WWN) zone member is also specified as a member of a Mixed zone.

You should use hard zone enforcement whenever possible. Hard zones are more secure than

“session-based hard zones”. Both types of zones will trap a port login (PLOGI), but hard zones will

filter out the I/O frames which”session-based” hard zones do not.

Recommended

Action

If hard zone enforcement is preferred, edit the zoning database to have the port zoned with devices

defined as either WWN or defined as <domain, portarea> but do not mix the methods used to

define these zone members.

Severity INFO