Topic
  • 9 replies
  • Latest Post - ‏2013-05-17T11:07:11Z by Guy Kempny
chandlerbing02
chandlerbing02
9 Posts

Pinned topic Can't ping SAS RAID Controller on BladeCenter S

‏2012-02-06T17:54:56Z |
Strange problem. I was able to ping, configure and assign LUNs using SCM or telnet. We are also using BNT 1/10GbE switch modules. After this switch was configured I was not able to ping or connect to the RAID Controllers anymore which could be just a coincidence. I get Destination host unreachable to the IP Address of the Mgmt module. The RAID Switch modules are still pingable. I have tried restarting both RAID and MGMT Modules to no avail. I need to expand the LUN and there's no way to do it without being able to connect. Anybody have any ideas?
Updated on 2013-03-14T16:38:06Z at 2013-03-14T16:38:06Z by SystemAdmin
  • gez
    gez
    275 Posts

    Re: Can't ping SAS RAID Controller on BladeCenter S

    ‏2012-02-10T18:39:03Z  
    make sure the smgt interfaces on the bnt switch are up and allow vlan 4095
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: Can't ping SAS RAID Controller on BladeCenter S

    ‏2012-10-24T15:07:35Z  
    • gez
    • ‏2012-02-10T18:39:03Z
    make sure the smgt interfaces on the bnt switch are up and allow vlan 4095
    Hi gez ... i've read many forums since some days but i can't find a solution for "nearly" the same problem of this thread-topic. This is my first BC-S (8886-K2G) with the following HW-Config:

    • 4x AC-Power
    • 2x BNT Layer 2/3 Copper Gigabit Ethernet Switch Module (32R1869)
    • 1x AMM (Firmware BPET62R and BPET62T - tried both)
    • 1x SAS RAID Controller (43W3630 - FW-Versions:
    SAS RAID Ctrl Mod Boot ROM S0CD01D 12/21/2007 0308
    + Main Application 1 S0SW01D 12/17/2009 R107+
    + Main Application 2 S0CP00A 01/01/2000 C00A+
    + Main Application 3 S0CL122007 02/23/2011 2119+
    + Main Application 4 S0BT10A 02/08/2010 0121+
    + Main Application 5 S0SE00C 09/04/2008 0107 )+

    • NO BACKUP BATTERY MODULE inserted at the moment !!!
    • NO BLADE MODULES inserted at the moment !!!
    • 1x "Test-SAS-HDD" inserted at the moment
    • 1x DSM installed

    MY PROBLEM: via AMM-Web-Gui i entered the ip's to the SAS-Switch-Module and the RAID-Module.
    After saving the ip's to this module(s) i restarted the IO-Modul in Bay3 and from my Managment-
    Client i started a "ping -t 172.16.48.246" to the SAS-Switch ... it works fine .. means the
    pings get answered correctly. The SAS-Switch i can configure via SCM too.
    But when i want to "ping -t 172.16.48.245" to the RAID-Module i get only 6-16 pings answered
    correctly and after them i get a "destination host unreachable" from the AMM-IP. This works
    three times ... when looking at the event log of the amm i see "I/O module has restarted."
    for three times also. During this short reachable moments a can access to the RAID-Module via
    telnet but there is not enough time to enter some commands after logging in :-( .

    The VLAN-ID of the RAID-Mod is 4095, the MGT1-Port on both switches is at VLAN 4095 also, all
    other ports are at VLAN1 at the moment, the external ports are enabled but not connected to any
    network.

    Should i could ping the RAID-module without the bnt-switches in the bc-s-chassis?
    And why i can ping thes RAID-module only for a short moments?
    And why do this module three restarts after without my interaction?

    Any idea? Thanks a lot !!
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: Can't ping SAS RAID Controller on BladeCenter S

    ‏2012-12-07T20:24:38Z  
    Hi gez ... i've read many forums since some days but i can't find a solution for "nearly" the same problem of this thread-topic. This is my first BC-S (8886-K2G) with the following HW-Config:

    • 4x AC-Power
    • 2x BNT Layer 2/3 Copper Gigabit Ethernet Switch Module (32R1869)
    • 1x AMM (Firmware BPET62R and BPET62T - tried both)
    • 1x SAS RAID Controller (43W3630 - FW-Versions:
    SAS RAID Ctrl Mod Boot ROM S0CD01D 12/21/2007 0308
    + Main Application 1 S0SW01D 12/17/2009 R107+
    + Main Application 2 S0CP00A 01/01/2000 C00A+
    + Main Application 3 S0CL122007 02/23/2011 2119+
    + Main Application 4 S0BT10A 02/08/2010 0121+
    + Main Application 5 S0SE00C 09/04/2008 0107 )+

    • NO BACKUP BATTERY MODULE inserted at the moment !!!
    • NO BLADE MODULES inserted at the moment !!!
    • 1x "Test-SAS-HDD" inserted at the moment
    • 1x DSM installed

    MY PROBLEM: via AMM-Web-Gui i entered the ip's to the SAS-Switch-Module and the RAID-Module.
    After saving the ip's to this module(s) i restarted the IO-Modul in Bay3 and from my Managment-
    Client i started a "ping -t 172.16.48.246" to the SAS-Switch ... it works fine .. means the
    pings get answered correctly. The SAS-Switch i can configure via SCM too.
    But when i want to "ping -t 172.16.48.245" to the RAID-Module i get only 6-16 pings answered
    correctly and after them i get a "destination host unreachable" from the AMM-IP. This works
    three times ... when looking at the event log of the amm i see "I/O module has restarted."
    for three times also. During this short reachable moments a can access to the RAID-Module via
    telnet but there is not enough time to enter some commands after logging in :-( .

    The VLAN-ID of the RAID-Mod is 4095, the MGT1-Port on both switches is at VLAN 4095 also, all
    other ports are at VLAN1 at the moment, the external ports are enabled but not connected to any
    network.

    Should i could ping the RAID-module without the bnt-switches in the bc-s-chassis?
    And why i can ping thes RAID-module only for a short moments?
    And why do this module three restarts after without my interaction?

    Any idea? Thanks a lot !!
    Hi Experts ...
    my problem isn't solved yet :-( ... i ordered a battery unit and wait for shipping.
    I hope some of you can answer the following questions:

    • I've read in some IBM-ressources that i need TWO SAS RAID Modules to work? :-O
    For example in Implementing the IBM BladeCenter S Chassis (page 57)
    The SAS RAID Controller Module is only supported in a dual controller
    configuration. Therefore, you must populate I/O Bay 3 and 4 each with a SAS
    RAID Controller Module.
    Could this be the reason why i can't access to my controller (see my config above)

    • Is it possible that i can't reach the controller because there is no bbu installed ?

    • Is it possible to debug the boot sequence of the sas raid module? I try to get some
    detailed infos why this module is pingable for 5-10 requests and than "dies" .

    If the ordered BBU won't solve my problem i've no ideas anymore.
    Got the experts in this forum have some answers or ideas for me????

    Thanks a lot.
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: Can't ping SAS RAID Controller on BladeCenter S

    ‏2012-12-08T17:06:52Z  
    Hi Experts ...
    my problem isn't solved yet :-( ... i ordered a battery unit and wait for shipping.
    I hope some of you can answer the following questions:

    • I've read in some IBM-ressources that i need TWO SAS RAID Modules to work? :-O
    For example in Implementing the IBM BladeCenter S Chassis (page 57)
    The SAS RAID Controller Module is only supported in a dual controller
    configuration. Therefore, you must populate I/O Bay 3 and 4 each with a SAS
    RAID Controller Module.
    Could this be the reason why i can't access to my controller (see my config above)

    • Is it possible that i can't reach the controller because there is no bbu installed ?

    • Is it possible to debug the boot sequence of the sas raid module? I try to get some
    detailed infos why this module is pingable for 5-10 requests and than "dies" .

    If the ordered BBU won't solve my problem i've no ideas anymore.
    Got the experts in this forum have some answers or ideas for me????

    Thanks a lot.
    Here is my latest service.txt from the amm-service-data-tool attached.

    The next problem seems,that the blade in slot 5 can't ger the correct cpu infos via the amm :-/
    I added two 8C E5-2650 (BX80621E52650) ... and hope a firmware update for the hs23 will solve
    the problem. The HS23 BIOS identify the cpu's and the memory dimms correct.
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: Can't ping SAS RAID Controller on BladeCenter S

    ‏2013-01-01T15:29:33Z  
    Here is my latest service.txt from the amm-service-data-tool attached.

    The next problem seems,that the blade in slot 5 can't ger the correct cpu infos via the amm :-/
    I added two 8C E5-2650 (BX80621E52650) ... and hope a firmware update for the hs23 will solve
    the problem. The HS23 BIOS identify the cpu's and the memory dimms correct.
    Hi Experts,

    i added a new bbu last week but the problem is still the same ;-(( ... The amm service data
    for the SAS RAID Controller (43W3630) means:

    Network interface info:
    Fail to get the info data. Err(0x1)

    Enviroment data:

    Network data:
    MAC address: 00:1A:64:9E:95:82
    IP Address: 172.16.48.247
    Subnet Mask: 255.255.255.0
    Gateway: 172.16.48.250
    2nd MAC address: 00:1A:64:9E:15:24
    2nd IP Address: 172.16.48.245
    2nd Subnet Mask: 255.255.255.0
    2nd Gateway: 172.16.48.250
    VLAN ID: 4095
    Configuration Management Status: Enabled
    Power State: on
    Stacking Mode: n/a
    Protected Mode: n/a
    POST results available: Module completed POST successfully.
    IOM External ports configuration (current): Enabled
    IOM External ports configuration: Enabled

    The latest service-data-file is attached ... any ideas ???
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: Can't ping SAS RAID Controller on BladeCenter S

    ‏2013-03-14T16:38:06Z  
    Hi Experts,

    i added a new bbu last week but the problem is still the same ;-(( ... The amm service data
    for the SAS RAID Controller (43W3630) means:

    Network interface info:
    Fail to get the info data. Err(0x1)

    Enviroment data:

    Network data:
    MAC address: 00:1A:64:9E:95:82
    IP Address: 172.16.48.247
    Subnet Mask: 255.255.255.0
    Gateway: 172.16.48.250
    2nd MAC address: 00:1A:64:9E:15:24
    2nd IP Address: 172.16.48.245
    2nd Subnet Mask: 255.255.255.0
    2nd Gateway: 172.16.48.250
    VLAN ID: 4095
    Configuration Management Status: Enabled
    Power State: on
    Stacking Mode: n/a
    Protected Mode: n/a
    POST results available: Module completed POST successfully.
    IOM External ports configuration (current): Enabled
    IOM External ports configuration: Enabled

    The latest service-data-file is attached ... any ideas ???
    The problem is that in order to only support 1 RSSM module, your firmware must be FW 1.24.011 or above. I would recommend flashing to the latest version of the FW on fixcentral using one of the 3 documented methods. Windows, Linux, or SCM is required. Good luck!
  • C8PG_CH_Lin
    C8PG_CH_Lin
    3 Posts

    Re: Can't ping SAS RAID Controller on BladeCenter S

    ‏2013-04-18T05:19:31Z  
    Hi Experts,

    i added a new bbu last week but the problem is still the same ;-(( ... The amm service data
    for the SAS RAID Controller (43W3630) means:

    Network interface info:
    Fail to get the info data. Err(0x1)

    Enviroment data:

    Network data:
    MAC address: 00:1A:64:9E:95:82
    IP Address: 172.16.48.247
    Subnet Mask: 255.255.255.0
    Gateway: 172.16.48.250
    2nd MAC address: 00:1A:64:9E:15:24
    2nd IP Address: 172.16.48.245
    2nd Subnet Mask: 255.255.255.0
    2nd Gateway: 172.16.48.250
    VLAN ID: 4095
    Configuration Management Status: Enabled
    Power State: on
    Stacking Mode: n/a
    Protected Mode: n/a
    POST results available: Module completed POST successfully.
    IOM External ports configuration (current): Enabled
    IOM External ports configuration: Enabled

    The latest service-data-file is attached ... any ideas ???

    Have you tried to reseat the MT or powercycling the AMM?

    Can you describe your problem more in detail?

    Thanks.

  • t-kobayashi@jp
    t-kobayashi@jp
    1 Post

    Re: Can't ping SAS RAID Controller on BladeCenter S

    ‏2013-04-25T03:57:56Z  
    Hi Experts,

    i added a new bbu last week but the problem is still the same ;-(( ... The amm service data
    for the SAS RAID Controller (43W3630) means:

    Network interface info:
    Fail to get the info data. Err(0x1)

    Enviroment data:

    Network data:
    MAC address: 00:1A:64:9E:95:82
    IP Address: 172.16.48.247
    Subnet Mask: 255.255.255.0
    Gateway: 172.16.48.250
    2nd MAC address: 00:1A:64:9E:15:24
    2nd IP Address: 172.16.48.245
    2nd Subnet Mask: 255.255.255.0
    2nd Gateway: 172.16.48.250
    VLAN ID: 4095
    Configuration Management Status: Enabled
    Power State: on
    Stacking Mode: n/a
    Protected Mode: n/a
    POST results available: Module completed POST successfully.
    IOM External ports configuration (current): Enabled
    IOM External ports configuration: Enabled

    The latest service-data-file is attached ... any ideas ???

     

    I'm having exactly same problems.
    I can't access to RAID's IP address via ping, telnet and SCM, also.
     
    Did you solved problem ?
    if so, please advise me.
     
    many thanks.
     
  • Guy Kempny
    Guy Kempny
    18 Posts

    Re: Can't ping SAS RAID Controller on BladeCenter S

    ‏2013-05-17T11:07:11Z  

     

    I'm having exactly same problems.
    I can't access to RAID's IP address via ping, telnet and SCM, also.
     
    Did you solved problem ?
    if so, please advise me.
     
    many thanks.
     

    1. Firmware 1.2.4.011 or higher for 1 SAS RAID Controller card being supported in bay 3.

    2. What are the firmwares of the HDD in the DSM modules. My suspicions is that if the HDD firmware are higher than the SAS RAID Controller card firmware may cause issues.

    3. The SAS RAID Controller card IP address and the AMM must be on the same subnet.

    Pls see the new draft implementing the baldecenter S for more assistance and post any comments and feedback!

    http://www.redbooks.ibm.com/Redbooks.nsf/RedpieceAbstracts/sg247682.html?Open

    What happens if you have the AMM and the network module connect together via an external network rather than using the internal chassis connectivity.