Blocking zone merge after reboot, Removing stale translate domains, Using troubleshooting and diagnostic tools – Brocade Network OS Administrator’s Guide v4.1.1 User Manual
Page 714: Using layer 2 traceroute, Layer 2 traceroute packets, Blocking, Zone merge after reboot

Blocking zone merge after reboot
To be sure of blocking zone merge following a switch reboot, enter the no fabric isl enable command
to disable the ISL between neighboring Brocade VDX switches.
CAUTION
Brocade recommends that you do not use the shutdown command. If you use the shutdown
command, then following switch reboot, the zone merge could happen before the shutdown
command is replayed by the running configuration.
To block zone merge following reboot, follow these steps on each ISL port.
1. In global configuration mode, enter the interface tengigabitethernet (or interface
gigabitethernet) command to enter interface configuration mode.
2. Enter the no fabric isl enable command.
Removing stale translate domains
A translate domain becomes stale when the edge fabric it represents becomes unreachable. By
default, the stale translate domain is not deleted until the local edge fabric is rebuilt.
To delete a stale translate domain and avoid the disruption caused by rebuilding the local edge fabric,
complete the following steps.
1. Connect to the Fibre Channel router and log in using an account with admin permissions.
2. On the FC router, enter the fcrXlateConfig --show stalexd command to list any stale translate
domains.
3. Enter the fcrXlateConfig --delete stalexd command to delete the stale translate domain.
Refer to the Fabric OS Command Reference for details about the fcrXlateConfig command.
Using troubleshooting and diagnostic tools
This section describes the various troubleshooting and diagnostic tools available with Network OS and
provides some guidelines for their use
Gathering troubleshooting information
on page 667, which provides information about
Network OS supportSave files.
Using Layer 2 traceroute
TRILL OAM provides the l2traceroute command to verify the fabric path continuity. When the
l2traceroute command is used with extended options, it provides granular control over the Layer 2
path that a Layer 2 traceroute packet takes.
Layer 2 traceroute packets
To use the Layer 2 traceroute tool, you need to understand the structure of the Layer 2 traceroute
packet when observed on the wire, when it is a request frame, and when it is a response frame.
The figure below shows what a normal Layer 2 packet looks like when traversing through an Ethernet
fabric, without Layer 2 traceroute applied.
Blocking zone merge after reboot
714
Network OS Administrator’s Guide
53-1003225-04