HP StorageWorks 2/16V Brocade Secure Fabric OS Administrator's Guide (53-10002 - Page 98

Table 4-5, Symptom, Possible Causes, Recommended Actions, secModeEnable, secPolicyShow, secFCSFailover

Page 98 highlights

4 Table 4-5 Recovery Processes (Continued) Symptom Possible Causes Recommended Actions Cannot execute commands from any switch in the fabric. All FCS switches have failed but secure mode is still enabled, preventing access to fabric. Type the secModeEnable command from the switch that you want to become the new primary FCS switch, and specify the FCS switches. Note: Specify adequate backup FCS switches to prevent a recurrence of this problem. Cannot access some or The MAC policies are all switches in the fabric. restricting access. Use a serial cable to connect to the primary FCS switch; then, enter the secPolicyShow command to review the MAC policies. Note: An empty MAC policy blocks all access through that management channel. Modify policies as necessary by either entering valid entries or deleting the empty policies. Cannot access primary FCS switch by any management method. Primary FCS switch has failed or lost all connections. Log in to the backup FCS switch that you want to become the new primary FCS switch and enter the secFCSFailover command to reassign the primary FCS role to a backup FCS switch. If no backup FCS switches are available, enter the secModeEnable command to specify a new primary FCS switch. Specify adequate backup FCS switches to prevent a recurrence. Troubleshoot the previous primary FCS switch as required. Cannot access a device or switch port listed in the SCC or in a DCC policy. Switch port might be disabled. Type the switchShow command. If the port in question is disabled, enter the portEnable command. If the switch port still cannot be accessed, enter the portEnable command for the port on the other switch. One or more CLI sessions is automatically logged out. Password might have been modified for login account in use, the secModeEnable command might have been issued, or switches might have changed switch roles (primary to backup, backup to primary, and so forth). Try closing and reopening CLI session. On chassis-based platforms, status messages from any logical switch are broadcast to the serial console and telnet sessions on all other logical switches. The status messages from any logical switch are normally broadcast to the serial console and telnet sessions on all logical switches. All broadcast messages display the switch instance. Messages that originate from a switch instance other than the one to which the telnet session is logged in can be ignored. CLI session freezes or cannot be established after secure mode is enabled. CP failed over and network Try closing and reopening CLI session. If this fails, request that routing cache(s) require your LAN administrator refresh the network router cache(s). updating. 4-18 Secure Fabric OS Administrator's Guide Publication Number: 53-1000244-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118

4-18
Secure Fabric OS Administrator’s Guide
Publication Number: 53-1000244-01
4
Cannot execute
commands from any
switch in the fabric.
All FCS switches have
failed but secure mode is
still enabled, preventing
access to fabric.
Type the
secModeEnable
command from the switch that you want
to become the new primary FCS switch, and specify the FCS
switches.
Note
: Specify adequate backup FCS switches to prevent a
recurrence of this problem.
Cannot access some or
all switches in the fabric.
The MAC policies are
restricting access.
Note:
An empty MAC
policy blocks all access
through that management
channel.
Use a serial cable to connect to the primary FCS switch; then, enter
the
secPolicyShow
command to review the MAC policies.
Modify policies as necessary by either entering valid entries or
deleting the empty policies.
Cannot access primary
FCS switch by any
management method.
Primary FCS switch has
failed or lost all
connections.
Log in to the backup FCS switch that you want to become the new
primary FCS switch and enter the
secFCSFailover
command to
reassign the primary FCS role to a backup FCS switch.
If no backup FCS switches are available, enter the
secModeEnable
command to specify a new primary FCS switch.
Specify adequate backup FCS switches to prevent a recurrence.
Troubleshoot the previous primary FCS switch as required.
Cannot access a device
or switch port listed in
the SCC or in a DCC
policy.
Switch port might be
disabled.
Type the
switchShow
command. If the port in question is disabled,
enter the
portEnable
command. If the switch port still cannot be
accessed, enter the
portEnable
command for the port on the other
switch.
One or more CLI
sessions is automatically
logged out.
Password might have been
modified for login account
in use, the
secModeEnable
command might have been
issued, or switches might
have changed switch roles
(primary to backup, backup
to primary, and so forth).
Try closing and reopening CLI session.
On chassis-based
platforms, status
messages from any
logical switch are
broadcast to the serial
console and telnet
sessions on all other
logical switches.
The status messages from
any logical switch are
normally broadcast to the
serial console and telnet
sessions on all logical
switches.
All broadcast messages display the switch instance. Messages that
originate from a switch instance other than the one to which the
telnet session is logged in can be ignored.
CLI session freezes or
cannot be established
after secure mode is
enabled.
CP failed over and network
routing cache(s) require
updating.
Try closing and reopening CLI session. If this fails, request that
your LAN administrator refresh the network router cache(s).
Table 4-5
Recovery Processes
(Continued)
Symptom
Possible Causes
Recommended Actions