Filter
Top Products
360 Fabric OS Administrator’s Guide
53-1002745-02
Admin Domain considerations for Traffic Isolation Zoning
12
• To include a trunk group in a TI zone, you must include all ports of the trunk in the TI zone.
• If two N_Ports are online and have the same shared area, and one of them is configured in a
TI zone, then they both must be configured in that same TI zone. One of the online shared area
N_Ports should not remain outside the TI zone unless it is offline, then it may remain outside
the TI zone. This limitation does not apply to E_Ports that use the same shared area on FC4-48
and FC8-48 port blades.
• Ports that are in different TI zones cannot communicate with each other if failover is disabled.
• TI zone members that overlap must have the same TI failover policy across all TI zones to which
they belong. That is, if an overlapping member is part of a failover-disabled zone, then it can
belong only to other TI zones where the policy is also failover-disabled; the member cannot
overlap with failover-enabled TI zones.
• TI zones that have members with port index greater than 511 are not supported with Fabric OS
versions earlier than v6.4.0. If such a TI zone and Fabric OS version combination is detected,
a warning is issued. These configurations are not prevented, but their behavior is
unpredictable.
• When you merge two switches, if there is an effective configuration on the switches and
TI zones are present on either switch, the TI zones are not automatically activated after the
merge. Check the TI zone enabled status using the zone --show command, and if the TI Zone
Enabled status does not match across switches, issue the cfgEnable command.
• Use care when creating TI zones on ICL ports in topologies that span more than two switches
connected with ICLs. If a user-defined TI zone breaks the ICL connectivity requirements, a a
FSPF-1009 RASLOG entry and message is generated to notify you of this error condition.
ATTENTION
Removing a core blade when both ICL connections and lossless dynamic load sharing are enabled
may cause frame loss on a number of F_Ports.
Admin Domain considerations for Traffic Isolation Zoning
If you implement Admin Domains and TI zones, you should keep the following points in mind:
• TI zones are applicable only in AD0, and the E_Ports that are members of a TI zone must be in
the AD0 device list. Because TI zones must use D,I notation, the AD0 device list must be
declared using D,I notation for ports that are to be used in TI zones.
• A port used in a TI zone should not be a member of multiple Admin Domains.
• Use care if defining TI zones with ports that are shared across Admin Domains because of the
limitation that a given port can appear in only one TI zone.
Best practice: Do not use ports that are shared across Admin Domains in a TI zone.