HP StorageWorks 8/80 Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53- - Page 74

SNMP issues, Gathering additional information, FIPS issues

Get HP StorageWorks 8/80 - SAN Switch PDF manuals and user guides View all HP StorageWorks 8/80 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 74 highlights

6 SNMP issues SNMP issues This section describes symptoms with associated causes and recommended actions for SNMP-related issues. Symptom SNMP management station server is unable to receive traps from fabric. Probable cause and recommended action There are several causes related to this generic issue. You will need to verify the following: • There are no port filters in the firewalls between the fabric and the SNMP management station. • If your SNMP management station is a dual-homed server, check that the routing tables are set up correctly for your network. If you continue to have problems, collect the data in the next section and contact your switch support provider. Gathering additional information In addition to supportSave -n, gather the following command output: • agtCfgShow • ipAddrShow • the MIB browser snapshot with the problem (like Adventnet screen snapshot) for a MIB variable FIPS issues This section describes symptoms with associated causes and recommended actions for problems related to FIPS. Symptom When FIPS is turned on the switch constantly reboots. Probable cause and recommended action When FIPS is turned on the switch runs conditional tests each time it is rebooted. These tests run random number generators and are executed to verify the randomness of the random number generator. The conditional tests are executed each time prior to using the random number provided by the random number generator. The results of all self-tests, for both power-up and conditional, are recorded in the system log or are output to the local console. This includes logging both passing and failing results. If the tests fail on your switch it will constantly reboot. Because boot PROM access is disabled you will not be able to exit out of the reboot. You will need to send the switch back to your switch service provider for repair. 60 Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-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
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
60
Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
SNMP issues
6
SNMP issues
This section describes symptoms with associated causes and recommended actions for
SNMP-related issues.
Symptom
SNMP management station server is unable to receive traps from fabric.
Probable cause and recommended action
There are several causes related to this generic issue. You will need to verify the following:
•
There are no port filters in the firewalls between the fabric and the SNMP management
station.
•
If your SNMP management station is a dual-homed server, check that the routing tables are
set up correctly for your network.
If you continue to have problems, collect the data in the next section and contact your switch
support provider.
Gathering additional information
In addition to
supportSave -n
, gather the following command output:
•
agtCfgShow
•
ipAddrShow
•
the MIB browser snapshot with the problem (like Adventnet screen snapshot) for a MIB
variable
FIPS issues
This section describes symptoms with associated causes and recommended actions for problems
related to FIPS.
Symptom
When FIPS is turned on the switch constantly reboots.
Probable cause and recommended action
When FIPS is turned on the switch runs conditional tests each time it is rebooted. These tests run
random number generators and are executed to verify the randomness of the random number
generator. The conditional tests are executed each time prior to using the random number
provided by the random number generator.
The results of all self-tests, for both power-up and conditional, are recorded in the system log or are
output to the local console. This includes logging both passing and failing results. If the tests fail on
your switch it will constantly reboot. Because boot PROM access is disabled you will not be able to
exit out of the reboot. You will need to send the switch back to your switch service provider for
repair.