Router
Customer want to use Bladecenter S+ HS23 blade , with Esxi 5.5 Sever installaed and all 800xa server virtualized.
Issues with Bladecenter is it can have only 2 Network which can be used out side and other 2 network is used for management network.
But our existing configuration has following networks
1 Client/Server Network Primary
2 Client/Server Network Secondary
3 Control Network Primary
4 Control Network Secondary
5 IEC61850 Network -1 (Ring Network)
6 IEC61850 Network -2 (Ring Network)
7 IEC61850 Network -3 (Ring Network)
8 IEC61850 Network -4 (Ring Network)
How this network can be connected to Blade which is only having two network ports. i am attaching the drawing as per by basic knowledge, can you please help on this.
Do we have any RNRP Router as a Hardware/Any router , which can be bought from ABB/Other vedor to get the connection to blade ?
Answers
Even though VLAN tagging could reduce the number of physical connections it is not a preferred solution (one storm may block all VLANs using same physical network connection).
If your server has two physical networks available for use you must limit your system to that or choose alternate hardware.
ABB is shortly releasing two routers, but that won't change much for you I'm afraid.
Use this procedure to troubleshoot SoL when the SoL is enabled but is not ready.
Problem From the SoL configuration page with the advanced management module interface, you see an indication that the blade server is enabled but not ready. Investigation Perform these steps to resolve the problem:- Verify that the Ethernet switch module installed in I/O module bay 1 is not a pass-thru module. The IBM copper pass-thru module does not support Serial over LAN.
- Verify that the Serial over LAN port assignment was not changed to the internal Ethernet port 2 in the blade server. The default SoL port assignment is internal Ethernet port 1 in the blade server, which connects to the switch module in I/O module bay 1. Most blade servers, except the BladeCenter HS40, provide a setting in the network controller firmware to change the SoL port assignment. This setting can be changed only when updating the blade server firmware.
- Verify that Serial over LAN is set up properly in the firmware (BIOS) for the blade server. Note: The blade may boot extremely slow and/or become unresponsive if COM 1 is configured for Serial over LAN instead of COM 2. For more information see the IBM BladeCenter Serial over LAN Setup Guide .
- Verify that the Serial over LAN IP address range (BSMP) is not already being used on the external network. The default BSMP address range starts at 10.1.1.80 and ends at 10.1.1.85 for all six blade servers in the BladeCenter S chassis. If any blade servers or other external devices use this range of addresses for production traffic, an IP conflict will occur and Serial over LAN traffic may be blocked.
You can change the Serial over LAN BSMP starting address using the advanced management module Web interface. Any IP address range can be used as long as the same addresses are not used for production traffic.
- If the blade server boots to an operating system, verify that the Ethernet drivers are loaded and up to date. A downlevel Ethernet driver under Linux can cause Serial over LAN to go into the Not Ready state.
- Verify that the blade servers are powered up. Some blade servers need to be powered up for Serial over LAN. It can take up to two minutes after some blade servers are powered up for SoL to be ready.
- Verify that the advanced management module can communicate with the switch module in I/O module bay 1. From the advanced management module Web interface, click .
- Verify that the switch module in I/O-module bay 1 is configured properly for Serial over LAN.
For most switch modules, you can use the default configuration settings for the advanced management module and the switch.
- Restart the blade server. From the advanced management module Web interface, click . Click the box next to the blade server, and then scroll down and select Restart Blade System Mgmt Processor.
- Make sure the blade server is powered up.
- Check the status of Serial over LAN.
- If it is ready, attempt to open an Serial over LAN console.
- From the advanced management module Web interface, click . Disable SoL for the blade server and then enable it again.
- Make sure the blade is powered up.
- Check the status of Serial over LAN.
- If it is ready, attempt to open a Serial over LAN console.
- Restart the advanced management module and check the status of Serial over LAN. If it is ready, attempt to open a Serial over LAN console.
- Restart the switch module in I/O module bay 1 and check the status of Serial over LAN. If it is ready, attempt to open a Serial over LAN console.
- Reset the blade server by powering it down, disengaging it from the BladeCenter S chassis (opening the release handles) and installing it again (closing the release handles).
- Power up the blade server and check the status of Serial over LAN. If it is ready, attempt to open a Serial over LAN console.
- Contact IBM support.
Add new comment