Join Us! By joining you are opting in to receive e-mail. Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here. There are a few small issues I'd like to resolve before I install the server. The diagnostic tells me all the chracteristics of the drive, but the BIOS doesn't see it as a physial drive. I looked and kept getting redirected to other support pages.
The manuals ask for very specific ram for this system. Can I use any PC ram, or do I need to look for something specific? Thank you very much - in advance for your help.
This is my test project as I will be getting a Netfinity to replace my current NT server sometime in You really want to use the scsi controller on this beast. You really want to fill up the array. I recently got given a Netfinity -- great big old beast. The drive can seek and then notifies the controller when it has data. IDE can't talk to drive 2 while talking to drive 1.
Queued requests. A scsi device can accept multiple requests, either at once, or while other requests are in progress. Smart access. The disk can change the order of reads and writes debpending on the current location of the heads. IDE is ok for desktops. Servers tend to have a much more random access pattern. With out of order operations, the chances of a head being near the right spot to do one of the outstanding requests is much higher.
Preparing the rack enclosure. Installing the server in the rack enclosure Removing the rack model from a rack enclosure. Internal drives installation or removing. Keyboard and mouse connectors. Management port C. Memory modules. Installing or removing memory modules. Installing microprocessor upgrades. Installing or replacing a microprocessor.
Option installation. Preparing a tower model. Preparing a rack model. Parallel port connector. Power supplies. Power supply removal.
Rear fan assembly removal. SCSI connectors. Internal SCSI connector. External SCSI connector. SCSI jumpers. DASD backplane jumper block location Security. Installing a U-bolt and security cable. Serial port connectors. System board illustration. System board LEDs. System board connectors. System board switches. Bypassing an unknown power-on password Universal serial bus ports. Updating the server configuration.
Video port connector. Beep symptoms. No beep symptoms. Diagnostic error codes. Error symptoms. POST error codes. SCSI error codes. These programs are the primary method of testing the major components of the server: the system board, Ethernet controller, video controller, RAM, keyboard, mouse pointing device , diskette drive, serial port, and parallel port.
You can also use them to test some external devices. Also, if you cannot determine whether a problem is caused by the hardware or by the software, you can run the diagnostic programs to confirm that the hardware is working properly. When you run the diagnostic programs, a single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After the cause of the first error message is corrected, the other error messages might not occur the next time you run the test.
A failed system might be part of a shared DASD cluster two or more systems sharing the same external storage device s. Prior to running diagnostics, verify that the failing system is not part of a shared DASD cluster. A system might be part of a cluster if: The customer identifies the system as part of a cluster.
One or more external storage units are attached to the system and at least one of the attached storage units is additionally attached to another system or unidentifiable source. One or more systems are located near the failing system. If the failing system is suspected to be part of a shared DASD cluster, all diagnostic tests can be run except diagnostic tests which test the storage unit DASD residing in the storage unit or the storage adapter attached to the storage unit.
Notes 1. For systems that are part of a shared DASD cluster, run one test at a time in looped mode. Do not run all tests in looped mode, as this could enable the DASD diagnostic tests. If multiple error codes are displayed, diagnose the first error code displayed. If the computer hangs and no error is displayed, go to Undetermined problems on page Power Supply problems, see No beep symptoms on page Safety information, see Safety information on page For intermittent problems, check the error log; see, Error log on page Yes No Go to Step Shut down all systems related to the cluster.
Run storage test. Check all cables and power cords. Set all display controls to the middle position. Power-on all external devices. Power-on the computer. Check the error log, see Error log on page If an error was recorded by the system, see Symptom-to-FRU index on page Start the Diagnostic Programs.
See Running Diagnostic test programs on page Check for the following responses: 1. No beep. Readable instructions or the Main Menu. If necessary, refer to Running Diagnostic test programs on page If you receive an error, go to Symptom-to-FRU index on page If the diagnostics completed successfully and you still suspect a problem, see Undetermined problems on page Diagnostic tools Server problems can be caused by the hardware, the software, or a user error.
An example of a user error is pressing the wrong key on the keyboard. You can check the hardware by using the diagnostic test programs and the information in this section.
Note When you run the diagnostic test programs, a single problem can cause several error messages to occur. When this happens, work to correct the cause of the first error message.
After the cause is corrected, the other error messages probably will not occur the next time you run the tests. If the hardware is OK and you have not made an error, you might have a software problem. If you suspect that you have a software problem, refer to the information that comes with that software package. Diagnostic test programs: The server diagnostics test programs are stored in nonvolatile random-access memory NVRAM on the system board. These programs are the primary method of testing the system board, memory, and other standard features of the Netfinity Also, if you cannot determine whether a problem is caused by the hardware or by the software, you can run the test programs to confirm that the hardware is working properly.
The server diagnostic test programs can identify most problems associated with major components of the server: the system board, Ethernet controller, video controller, RAM, diskette drive, serial port, parallel port, keyboard, and mouse.
You can start the diagnostic test programs from the Startup panel, when the message Press F2 for Diagnostics appears. Test options let you batch groups of tests, specify test parameters for example, which memory DIMM you want to test , and specify the number of passes that you want to run 1 through You can also view the server configuration information from the Diagnostic Utility menu.
For example, you can view the interrupt request IRQ and direct memory access DMA assignments, memory usage, device drivers, and so on. Power-on self-test POST : When you turn on the server, it performs a series of tests to check the operation of server components and some options.
This series of tests is called the power-on self-test, or POST. POST does the following: Checks the operation of some basic system board operations Checks the memory Compares the current server configuration with the stored server configuration information Configures PCI adapters Starts the video operation Verifies that drives such as the diskette, CD-ROM, and hard disk drives are connected properly If you have a power-on password or administrator password set, you must type the password and press Enter before POST will continue.
While the memory is being tested, the amount of available memory appears on the screen. These numbers advance as the system progresses through POST and the final number that appears on the screen represents the amount of memory available. If POST detects a problem, an error message appears on the screen. A single problem can cause several error messages to appear.
After the cause is corrected, the other error messages probably will not appear the next time you turn on the system. One beep indicates successful completion of POST. Error messages: Error messages indicate that a problem exists; they are not intended to be used to identify a failing part.
Hardware error messages that occur can be text, numeric, or both. Messages generated by the software generally are text messages, but they also can be numeric. Diagnostic error messages: Diagnostic error messages occur when a test finds a problem with the server hardware.
These error messages are alphanumeric and they are saved in the Test Log. Software-generated error messages: These messages occur if a problem or conflict is found by an application program, the operating system, or both. Messages are generally text messages, but they also can be numeric. For information about these error messages, refer to the documentation that comes with the software. An optional device or adapter might come with an Option Diskette.
Option Diskettes usually contain option-specific diagnostic test programs or configuration files. If the optional device or adapter comes with an Option Diskette, follow the instructions that come with the option. Different instructions apply depending on whether the Option Diskette is startable or not. Diagnostic test programs This section includes useful information about navigating through the diagnostic test programs, as well as procedures for starting and stopping them.
These programs are designed to test the IBM Netfinity If you want to test a non-IBM product, refer to the information that comes with that product. Navigating through the diagnostic tests: Error messages in the Test Log are stored by diagnostic test session.
A diagnostic test session is defined as running one, all, or a selection of tests, one or more times. Moves the cursor down. Moves the cursor up. Toggles test selection between Yes and No. Moves to the next diagnostic test session in the log if any. Moves to the previous diagnostic test session in the log if any. Displays the appropriate Help information. Use the Up Arrow or Down Arrow key to scroll through the information. Pressing F1 from within a Help screen provides a help index from which you can select different categories.
Pressing Esc exits Help and returns to where you left off. Returns to the previous menu. When you start the diagnostic test programs from the Diagnostic Utility menu, you can select the tests, the way the tests run, and the number of times the tests run.
To run the diagnostic test programs, you must start the server with the highest level password. That is, if you enter the power-on password, and an administrator password is set, you cannot run the test programs.
You can only view the error messages in the test log. If an administrator password is set, you must enter the administrator password to run the diagnostic test programs. If the server stops during testing and you cannot continue, restart the server and try running the tests again. If the problem persists, see Error symptoms on page and look for the problem symptom. If the diagnostic tests do not find a problem, see Error symptoms on page and look for the problem symptom.
You might need a scratch diskette to obtain accurate test results when testing the diskette drive. The keyboard and mouse tests assume that a keyboard and mouse are attached to the server. To start the diagnostic tests: 1. Turn on the server and watch the screen.
If the system is turned on already, shut down the operating system and restart the server. When the message Press F2 for Diagnostics appears, press F2. If a power-on password or administrator password is set, the system prompts you for it. Type in the appropriate password; then, press Enter. The Diagnostic Programs screen appears. Select Extended or Basic from the top of the screen.
Select the test you want to run from the list that appears; then, follow the instructions that appear on the screen. The actions available include specifying the options for the tests to be run, such as the number of times to run the test, whether to stop on error, or whether to use a predefined overlay that describes the tests to be run. When the tests have completed, you can view the Test Log by selecting Utility from the top of the screen.
Also, you can view server configuration information such as system configuration, memory contents, interrupt request IRQ use, direct memory access DMA use, device drivers, and so on by selecting Hardware Info from the top of the screen.
If the hardware checks out OK but the problem persists during normal server operations, a software error might be the cause. If you suspect a software problem, refer to the information that comes with the software package.
If you are already running the diagnostic programs, continue with step 4 in this procedure. To view the Test Log: 1. After you run diagnostic tests or abort the diagnostic tests, the utility option appears at the top of the screen.
Select Utility from the top of the screen. Select View Test Log from the list that appears; then, follow instructions on the screen. Press Esc to return to the Diagnostic Programs screen. Select Quit from the top of the screen; then, select Exit Diags to exit from the diagnostic programs. The server restarts. Features The following table summarizes the features of the Netfinity - Type Additional service information The following additional service information supports Netfinity - Type Checking the system for damage on page Configuration overview on page Configuring the Ethernet controller on page Ethernet controller messages on page Failover for redundant Ethernet on page Identifying problems using status LEDs on page Recovering BIOS on page Resolving configuration conflicts on page Resolving resource conflicts on page Checking the system for damage This section provides instructions on what to do if the system might be damaged.
Look for loose cables and obvious damage. If any cables are loose, reconnect them securely. If you see no damage, turn on the system. If it works correctly, the system probably did not suffer any damage. If the system does not work correctly, turn it off and check the adapters and memory modules to ensure that they are connected correctly.
Reseat all adapters and memory modules. If the system still does not work correctly, run the diagnostic tests from diagnostic utility menu. For information about running tests, see Running Diagnostic test programs on page Turn off the server. Unplug the keyboard from the back of the server. Turn the keyboard upside down to drain excess liquid. Dry off the keyboard with a lint-free cloth. After the keyboard is completely dry, plug it in and turn on the server.
If it does not work correctly, replace the keyboard. If liquid gets inside the monitor: 1. Turn off the monitor. Unplug the monitor from the server and the electrical outlet. Let the monitor dry out.
If liquid gets inside the server: 1. Turn off the server and all attached devices. Unplug the server from the electrical outlet and all attached devices. Let the server dry out. Configuration overview You play a key role in how the server allocates resources to organize and interconnect hardware devices and software programs. This allocation process is referred to as configuration. The steps required to configure the server depend on the number and types of devices and programs that you install.
The server supports several types of adapters. Because of this flexibility, you can choose from among thousands of adapters and devices that comply with any of the following standards: Peripheral Component Interconnect PCI Industry Standard Architecture ISA Small Computer System Interface SCSI In general, the greater the number and variety of hardware devices and software programs that you install in the server, the more you will have to interact with the server and the devices to correctly configure the system.
Before installing a new device or program, read the documentation that comes with it. Reading the instructions helps you determine the steps required for installation and configuration.
The following actions are typically, but not always, required to configure the server. Set switches on the server system board. See System board switches on page for the meanings of the system board switches. Set jumpers or switches on the device. See the device installation instructions. Install the device in the server, see Locations on page Install software programs.
Refer to the information provided with the ServerGuide and Netfinity Manager Information section of this Server Library and with the operating system for more information. Resolve configuration conflicts. See Resolving resource conflicts on page You need to change the settings only to resolve configuration conflicts or to enable or change device functions.
While the server is powered off, the configuration information remains available for the next system startup. Review this chapter and the information that comes with the option before making changes. Also, record the current settings before making any changes. Note If you enter a power-on password and an administrator password has been set, a limited menu appears on the screen.
To run the system diagnostics, press F2 to select Diagnostic Utility. The Diagnostic Utility main menu appears. For information about running the system diagnostics, see Diagnostic test programs on page Disabling the defective PCI adapter should enable you to complete a normal startup when you restart the server.
Pressing F1 displays Help information for a selected menu item. If you enter only the power-on password and an administrator supervisor-level password is also set, a limited version of the menu appears. The choices on some menus might differ slightly, depending on the BIOS version that comes with the server.
To change configuration settings: 1. Use the Up Arrow key to select the item you want to change; then, press Enter. Select the configuration setting you want to change. Use the Right Arrow or Left Arrow key to highlight the menu, if needed. Use the Right Arrow or Left Arrow key to select the appropriate setting for the selected item. Repeat Steps 1 through 3 for each setting that you want to change. After making changes, you can select: Save Settings to save the selected changes.
Restore Settings to delete the selected changes. Load Default Settings to cancel the changes and restore the factory settings. The system prompts you to confirm your choice. Select this choice to display configuration information, such as the type and speed of the microprocessor, and amount of memory. Changes that you make to configuration settings appear on this summary screen.
You cannot edit the fields. Select this choice to display information about the Netfinity , Changes that you make on other menus might appear on this summary screen. Product data: Select this choice to view system information such as the machine type and model, the system serial number, the system board identifier, and the revision level or issue date of the flash electronically erasable programmable ROM EEPROM and BIOS.
System card data: Select this choice to view the system board model, submodel, system serial number, system board identifier, DASD backplane identifier, and identifiers for power supply 1 and power supply 2. Each port must have a unique port assignment. Note Serial port A can be shared by the system management processor and operating system. Serial port B is used by the operating system only. You can add serial ports by installing a serial adapter in an expansion slot.
See the documentation that comes with the serial adapter for information about port assignments. Bidirectional, ECP, and EPP are all bidirectional modes; in all three modes, data can be both read from and written to a device. Which one of these modes you choose depends on what mode the device supports. The maximum length of the cable must not exceed 3 meters 9. You can configure the mouse and diskette controller as enabled or disabled, and configure the type of diskette drive. You can view the type of video controller and the amount of video memory installed.
To display or change the port assignments: 1. Select a device or port; then, use the Left Arrow or Right Arrow key to advance through the settings available. The system date is in standard format for your country. Type the new information; the system saves the information as you type it.
System security: To control access to the information in the server, you can implement security features, such as adding passwords and defining a system owner's name that displays during startup.
Implementing these security measures helps you to ensure the integrity of the data and programs that are stored in the server. After setting a power-on password, you can enable the unattended-start mode. This locks the keyboard and mouse, but allows the server to start the operating system. The keyboard and mouse remain locked until you enter the correct password.
To set, change, or delete a password: 1. Select System Security. Select the password that you want to change. Follow the instructions on the screen. After you have set a power-on or administrator password, you must enter the password whenever you turn on the server.
The passwords do not appear on the screen as you type them. Type of Password No password set Results No password required to start system. You must enter the password to complete the system startup. If you forget the power-on password, you can regain access to the server by using switch 8 on the system board. See Using the power-on password menu on page 26 for details. If the administrator password is forgotten, it cannot be overridden or removed.
You must replace the system board. You can enter either password to complete the system startup. You can set, change, or delete both the administrator and power-on passwords, and allow a power-on password to be changed by the user. This might include changing or deleting the power-on password. If you forget the power-on password, and the administrator password has been set, use the administrator password at the password prompt. Using the power-on password menu: When a power-on password is set, you must enter a password each time you start the system.
To set a power-on password: 1. The Power-on Password menu appears. Type the password in the Enter Power-on Password data field. You can use any combination of up to seven characters AZ, az, and 09 for the power-on password. Keep a record of the password in a secure place. Move the cursor to the Enter Power-on Password Again data field and type the password again. Note A message appears if the two passwords do not match. If this happens, press Enter to return to the Power-On Password menu.
Select Change Power-on Password to save the new password; then, press Enter. A confirmation window appears. Press Enter to change the power-on password. Press Esc to return to the System Security menu. When a power-on password is set, POST does not complete until you enter the password. If you forget the power-on password, you can regain access to the server through one of the following methods: If an administrator password has been set, enter the administrator password at the power-on prompt see Using the administrator password menu on page 27 for details.
Use the Bypass-Power-On-Password switch on the system board to temporarily bypass the power-on password. See Option installation on page through Preparing a tower model on page or through Preparing a rack model on page for instructions on powering off the server and removing the cover.
Then, refer to the system board diagram inside the server for the location of the switch block. Locate switch 8 see System board switches on page Set switch 8 on the switch block to On, to bypass the power-on password. Turn the server off again. Set switch 8 back to Off. Restart the server. To delete a power-on password: 1. Select Delete Power-on Password; then, press Enter. Press Enter to delete the power-on password. Press Esc to cancel the request and return to the System Security menu.
To allow the server to start in unattended mode when a power-on password is set: Note If the password data field is set to On, the Unattended Start and Stop modes are not supported. Select Allow for unattended boot with password. If no power-on password is set on the server, this option has no effect. Important If an administrator password is set and then forgotten, it cannot be overridden or removed.
To set an administrator password: 1. Type the password in the Enter Administrator Password data field. A password can contain any combination of up to seven alphanumeric characters AZ, az, and Netfinity - Type Move the cursor to the Enter Administrator Password Again data field and type the password again.
If this happens, press Enter to return to the Administrator Password menu. Select Change Administrator Password to save the new password; then, press Enter. The password becomes effective immediately. To delete an administrator password: 1.
Select Delete Administrator Password; then, press Enter. Press Enter to delete the administrator password. To enable a user to change the power-on password: 1. Select Power-on password changeable by user. The System Security menu contains the Power-on Password choice. Defining a system owner's name: You can specify a system owner's name that displays during POST each time that the server is started. If you set an administrator password, only the administrator can set, change, or delete the system owner's name.
To set the system owner's name: 1. The System Owners Name screen appears. You can use any combination of up to 15 characters and spaces in the system owner's name.
Press Enter to set the name or change a previously defined name. You can select keyboard operating characteristics, such as the keyboard speed. You also can specify whether the keyboard number lock NumLock starts on or off. You also can enable the server to run in disketteless and monitorless operation. You can specify the startup sequence the server is to use to determine the device from which the operating system loads. For example, you can define a startup sequence that checks for a CD-ROM, then checks an installed hard disk drive, and then checks a network adapter.
You can enable a virus-detection test that checks at startup for changes in the master boot record. You also can also choose to run POST in the enhanced mode or in the quick mode. Advanced setup: Select Advanced Setup to change values for advanced hardware features, such as cache control, PCI bus control, memory settings, and advanced ISA settings. Note A warning message displays above the choices on this menu, to alert you that the system may malfunction if these options are configured incorrectly.
Follow the instructions on the screen carefully. Use the Left Arrow or Right Arrow key to highlight the options for the selected menu item. Core chipset control: Select this choice to modify settings that control features of the core chip set on the system board.
The chipset control choices are: Use this setting to control the in order queue IOQ depth in the system. The value can be varied from 1 to 8. This value should normally be set at 8 default Grant Timers Use this setting to enable or disable the grant timer mechanism for each of the 5 PCI slots. Enabling this will cause grant to be asserted to a PCI bus agent for a minimum of two clocks. This setting should normally be set to disable default IOQ Depth.
PCI bus control Note This page shows the interrupts and the correct interrupt assigned to the devices. Cache control: Select this choice to define the microprocessor cache state as enabled or disabled, and to define the microprocessor cache type as Write-back or Write-through. Selecting write-back mode will provide the maximum system performance. Memory settings: Select this choice to view the server banks of memory and to enable or disable selected rows of memory within those banks.
If a memory error is detected during POST or memory configuration, the server can automatically disable the failing row of memory and continue operating with reduced memory capacity.
If this occurs, you must manually enable the row of memory after the problem is corrected. Service Processor IRQ settings: Use this selection to specify the IRQ the system-management processor is to use and to synchronize the service processor clock to the system clock.
However, many ISA adapters are not Plug and Play devices and you must allocate the system resources that the adapter will use. Select Plug and Play; then, use the Up Arrow and Down Arrow key to highlight the system resource that you want to change. Error log: Select Error Log to view the three most recent power-on self-test POST errors the system has generated, or to view the system error log.
You can clear both error logs from this screen by selecting Clear Error Logs. Configuring PCI features and options: PCI devices automatically communicate with the server configuration information. This usually results in automatic configuration of a PCI device.
If a conflict does occur, see Resolving resource conflicts on page Multiple-function PCI adapters use more than one interrupt. Verify that the IRQ assignments are correct. The Netfinity server uses a rotational interrupt technique to configure PCI adapters. This technique enables you to install a variety of PCI adapters that currently do not support sharing of PCI interrupts. For information on manually overriding the interrupt setting, see PCI bus control on page Configuring the Ethernet controller The Netfinity comes with an Ethernet controller on the system board.
When you connect the server to the network, the Ethernet controller automatically detects the data-transfer rate 10 Mbps or Mbps on the network and then sets the controller to operate at the appropriate rate. This process is also known as auto-negotiation. This auto-negotiation occurs without software intervention.
Auto-negotiation works only if the hub or switch to which the server is connected also supports auto-negotiation. If the hub or switch does not support auto-negotiation, the speed 10 Mbps or Mbps will still be detected correctly, but half-duplex mode will always be selected.
A full-duplex switch that does not support auto-negotiation will not attach to the Netfinity in full-duplex mode. In this case, if you want the network to operate in full-duplex mode, you must manually override the settings to obtain a full-duplex connection. To do this, the server must have a device driver that supports manual overrides. Use the ServerGuide CDs to install this device driver. Refer to the ServerGuide and Netfinity Manager Information section of this Server Library for instructions on installing device drivers.
Verify that you have installed the appropriate device driver. Also, refer to the Ethernet documentation for additional information on operating modes, manual overrides, and device drivers. You must install a device driver to enable the operating system to address the Ethernet controller. Library for instructions on installing device drivers, or for more information about the ServerGuide CDs.
Fast Ethernet operates at a data rate of up to Mbps. However, except for the different operating speeds, Fast Ethernet and standard Ethernet are structurally identical. Most applications and protocols that are currently installed on a standard Ethernet system can be seamlessly migrated to a Fast Ethernet system.
Because of the equivalence of the two types of Ethernet, mixed Ethernet and Fast Ethernet systems also can be designed and implemented. The bandwidth required at each workstation connected to a server is generally far less than the bandwidth required at the server. This is because the server might have to handle the bandwidth of multiple workstations at the same time.
A cost-effective solution to the bandwidth requirements of this type of system is a mixed Ethernet and Fast Ethernet network. This mixed network consists of standard Ethernet connections at the workstations and Fast Ethernet connections at the servers.
You do not have to set any jumpers or configure the controller for the operating system before you use the Ethernet controller. The Ethernet controller supports the operating systems that the server supports. Review the network-adapter documentation for any additional configuration requirements. The explanation and recommended action are included with each message.
Explanation: The user entered an incorrect parameter keyword. Action: Reload the driver using the correct keyword. Explanation: The adapter did not respond when the driver tried to initialize it. If the Ethernet adapter is enabled, go to Diagnostic test programs on page 10 to run the diagnostic utility. See PCI bus control on page 30 for information on setting the interrupt requests.
If the IRQ settings are correct, replace the system board. Explanation: The cable might be disconnected from the server Ethernet port. Action: Verify that a cable is connected to the Ethernet port.
This new adapter could not be found. If the adapter is seated correctly, replace the adapter. Explanation: The driver tried to allocate some resources that were not available.
Action: Add or free some memory in the server. Then, restart the server. Explanation: The driver failed to allocate the memory needed for normal operation. Action: Add more memory, or free some memory resources in the server. Explanation: An attempt was made to initialize a given hardware interrupt. The attempt was not successful.
Make sure that the interrupt request numbers are set correctly. Explanation: An error occurred while the driver was trying to register with the LSL. Action: Restart the server. Explanation: The driver parameter block is too small. Explanation: The driver media parameter block is too small. Explanation: You tried to load a new frame type for the existing controller. The hardware assumptions made in doing so are incorrect. This error can also occur if you try to specify a mode such as, redundancy that conflicts with another specified mode.
Action: Make sure that the hardware configuration matches the software settings. See PCI bus control on page 30 for information on viewing and changing interrupt requests. Explanation: The IEEE address has a group bit indicating that an address belongs to a group of stations. This bit is used only as a destination address; it cannot be used as a source address. You tried to enter a source address with this bit set.
The driver cleared the group bit of the source address. Action: None necessary, message is for information only. Explanation: The local bit in the IEEE address format indicates that the addresses are being managed locally. If you use the node address override capabilities of this driver to enter a new address, the local bit must be set.
You entered an address without the local bit set. The driver has set the local bit. Explanation: The driver cannot find an Ethernet controller in the server. If the problem persists, go to Diagnostic test programs on page 10 to run the diagnostic utility. Action: Check and correct the configuration. Explanation: The driver could not allocate the requested buffers. Action: Check the system configuration. INI file to reduce the number of Txbuffers and Rxbuffers specified for the driver.
INI file. INI entry. Explanation: The driver cannot find an Ethernet controller. See PCI routing on page Explanation: The driver cannot locate the PCI bus on the server. Action: Go to Diagnostic test programs on page 10 to run the diagnostic utility. Grouping Mode is disabled.
Explanation: The failover option requires an adapter that is compatible with the device driver of the Ethernet controller on the system board. No such adapter was found. Action: Make sure the correct adapter is installed. Switching over to the Secondary Adapter. Explanation: The system detected a problem with the primary Ethernet connection and has transferred all network traffic to the secondary Ethernet controller.
Action: Identify the cause of the failure on the primary Ethernet connection. Restoring the operational state of the primary connection will cause the network traffic to automatically transfer to the primary Ethernet controller.
Explanation: The primary Ethernet connection is now operating correctly. Network traffic will automatically transfer to the primary Ethernet controller. Action: None needed, message is for information only. Please check the Streams parameters. Explanation: On a SunSoft Solaris system, this message indicates that the system is out of Streams memory blocks.
Explanation: The system is out of Streams memory blocks. Interrupts already enabled. Action: Modify the hardware settings. Action: Verify that additional Ethernet adapters are present or replace the Ethernet adapter that fails to respond.
Reset initiated! Explanation: The SunSoft Solaris driver has been reset due to a device fault. Action: Ignore this message if you are sure that this is what you want to do.
Unknown interrupt type. Out of range interrupt number. Out of range IPL. Vector already shared at different IPL. C file to delete the DMA parameter. Failover for redundant Ethernet The Netfinity has an integrated Ethernet controller. If you install this NIC adapter and connect it to the same logical segment as the primary Ethernet controller, you can configure the server to support a failover function.
You can configure either the integrated Ethernet controller or the NIC adapter as the primary Ethernet controller. In failover mode, if the primary Ethernet controller detects a link failure, all Ethernet traffic associated with it is switched to the redundant secondary controller.
This switching occurs without any user intervention. Applications with active sessions do not experience any data loss. When the primary link is restored to an operational state, the Ethernet traffic automatically switches back to the primary Ethernet controller. Only one controller in the redundant pair is active at any given time.
For example, if the primary Ethernet controller is active, then the secondary Ethernet controller cannot be used for any other network operation. See the documentation that comes with the adapter for more information. The setup required for each operating system follows. Install the redundant NIC adapter according to the instructions provided with the adapter and in Installing or removing adapters on page Note Only one driver instance needs to be loaded for each redundant pair of Ethernet controllers.
Refer to System board illustration on page for the locations and slot. The integrated controller is located in slot 9. LOG file when a failover occurs: a. The failover function is now enabled. Configuring Failover on Windows NT 1.
Highlight one of the adapters that will be in the redundant pair and then select the Properties Check the Grouping box. This will show the possible combinations for redundant pairs. Select the adapter pair you want and then select OK. Note that the integrated Ethernet controller is located at PCI bus 1, slot 9. Select Close to exit from the Network setup. When you restart the server, the failover function will be in effect. EXE was run , a pop-up message is generated also.
Configuring Failover on IntraNetWare 1. The slot number associated with the integrated Ethernet controller can vary depending upon the. To determine the slot number, load the driver with no parameters. The driver will display the available slot numbers. The slot number that is greater than will be the slot number of the integrated Ethernet controller. When the slot number of the integrated Ethernet controller is determined, reload the driver with the appropriate parameters. When the driver is loaded, bind it to a protocol stack.
If a failover occurs: A message is generated to the operating system console. The custom counters for the device driver contain variables that define the state of the failover function and the location of the redundant pair. You can use the NetWare Monitor to view the custom counters. These LEDs are part of the diagnostics built into the server. By following the path of lights, you can quickly identify the type of system error that occurred. Hard disk drive trays For more information, see Controls on page See Front panel indicators on page 85 for the location of these LEDs.
The following table describes the ac Power LEDs. There is an ac power problem.
0コメント