Intel SBXL52 Hardware Maintenance Manual - Page 115

Problem determination tips, Operating system software

Get Intel SBXL52 - Server Compute Blade PDF manuals and user guides View all Intel SBXL52 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 115 highlights

Notes: 1. If the problem goes away when you remove an I/O adapter from the system and replacing that I/O adapter does not correct the problem, suspect the system board. 2. If you suspect a networking problem and all the system tests pass, suspect a network cabling problem external to the system. Problem determination tips Due to the variety of hardware and software combinations that can be encountered, use the following information to assist you in problem determination. If possible, have this information available when requesting assistance from Service Support and Engineering functions. • Machine type and model • Microprocessor or hard disk upgrades • Failure symptom - Do diagnostics fail? - What, when, where, single, or multiple systems? - Is the failure repeatable? - Has this configuration ever worked? - If it has been working, what changes were made prior to it failing? - Is this the original reported failure? • Diagnostics version - Type and version level • Hardware configuration - Print (print screen) configuration currently in use - BIOS level • Operating system software - Type and version level ✏ NOTE To eliminate confusion, identical systems are considered identical only if they: 1. Are the exact machine type and models 2. Have the same BIOS level 3. Have the same adapters/attachments in the same locations 4. Have the same address jumpers/terminators/cabling 5. Have the same software versions and levels 6. Have the same diagnostics code (version) 7. Have the same configuration options set in the system 8. Have the same setup for the operation system control files Comparing the configuration and software set-up between "working" and "non-working" systems will often lead to problem resolution. Symptom-to-FRU index 101

  • 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
Symptom-to-FRU index
101
Notes:
1.
If the problem goes away when you remove an I/O adapter from the system and replacing that
I/O adapter does not correct the problem, suspect the system board.
2.
If you suspect a networking problem and all the system tests pass, suspect a network cabling
problem external to the system.
Problem determination tips
Due to the variety of hardware and software combinations that can be encountered, use the following
information to assist you in problem determination. If possible, have this information available when
requesting assistance from Service Support and Engineering functions.
•
Machine type and model
•
Microprocessor or hard disk upgrades
•
Failure symptom
—
Do diagnostics fail?
—
What, when, where, single, or multiple systems?
—
Is the failure repeatable?
—
Has this configuration ever worked?
—
If it has been working, what changes were made prior to it failing?
—
Is this the original reported failure?
•
Diagnostics version
—
Type and version level
•
Hardware configuration
—
Print (print screen) configuration currently in use
—
BIOS level
•
Operating system software
—
Type and version level
NOTE
To eliminate confusion, identical systems are considered identical only if they:
1.
Are the exact machine type and models
2.
Have the same BIOS level
3.
Have the same adapters/attachments in the same locations
4.
Have the same address jumpers/terminators/cabling
5.
Have the same software versions and levels
6.
Have the same diagnostics code (version)
7.
Have the same configuration options set in the system
8.
Have the same setup for the operation system control files
Comparing the configuration and software set-up between "working" and "non-working"
systems will often lead to problem resolution.