Brocade Network OS Administrator’s Guide v4.1.1 - Manual (Page 680)

Verifying that port profiles do not conflict
1. Enter the show port-profile name pp1_name name pp2_name validate command to validate
whether multiple port-profiles applied on an interface can co-exist without conflict.
switch# show port-profile name pp1 name pp2 validate
Port-Profile Port-Profile Conflicts
-----------------------------------------------------------------------------
pp1 pp2
vlan-profile vlan-profile No
qos-profile qos-profile No
security-profile security-profile No
2. If a conflict exists, reconfigure one of the port-profiles to avoid the conflict.
Refer to Configuring AMPP on page 327 for information about the rules for co-existence.
Verifying the Ethernet Name Server
AMPP requires each VCS Fabric switch in the cluster have the same view of the MAC address table.
Any differences in the view indicate a failure of the Ethernet Name Server (ENS). Refer to
ENS not
working correctly on page 682 for details.
Verifying an ESX host
Verify that each ESX host has the correct Converged Network Adapter (CNA) installed with
appropriate drivers, and does not use the Cisco Nexus 1000V software switch, as that switch might
send out specially crafted packets.
Panic reboots are continuous
If your switch is having continuous panic reboots, perform the following procedure.
1. Bring the switch to a stable state with the original binary or swap the other partition with a good
image.
a)
In bootenv, execute setenv OSLoadOptions 2, saveenv, and reset.
b) Immediately after reboot before panic, try to login and execute do chkconfig fabos off.
This boots the switch in single-user mode, with just Linux OS and not loading the Network
OS modules. Make the needed changes to the filesystem, such as changing the partition
by using bootenv or replacing the image with original good binaries.
In single-user mode the network is not accessible, so use the command ifconfig eth0 for
any network support. Furthermore, the command init 3 boots the switch after reboot for
case a above. Otherwise, reset the switch by using chkconfig fabos on; reboot.
2. If the switch comes to a halt after five repeated reboots, try cleaning up the DCMD database with
the following command:
rm -rf /etc/fabos/Dcmd/*.cfg; rm -rf /etc/fabos/Dcmd/WaveDatabase; rm -rf /etc/
fabos/Ccmd/*.cfg; rm -rf /etc/fabos/Ccmd/WaveDatabase; reboot "/sbin/reboot -f"
3. Download a good build to return the switch to a stable state.
CID card is corrupted
In the case of a corrupted CID card, perform the following steps.
Verifying that port profiles do not conflict
680 Network OS Administrator’s Guide
53-1003225-04