Start a Conversation

Unsolved

J

1 Rookie

 • 

14 Posts

1393

November 17th, 2021 04:00

VNX 5300 VM's - Network Issue (routing problem??)

Hi,

 

I am new to Dell equipment (VNX 5300) and I am trying to solve an issue. We had a power failure, the UPS went down and so did the environment since then the VM's on the Blade Servers have not been able to communicate with each other or the gateway.

When I try to ping the Ip i.e. 10.239.65.202 from 10.239.65.101
Reply from 10.239.65.101. Destination host is unreachable

The VM's within blade servers cannot ping each other within the chassis or the gateway. The PowerEdge M1000e chassis can ping the gateway, there are PowerConnect's connected via fibre to Cisco Nexsus

• The Chassis default gateway is 10.239.74.1/24
• The VM's in Blade servers default gateway is 10.239.65.1/24


I have logged onto the Cisco switches and I can ping the gateway 10.239.65.1 and 10.239.74.1, I can ping the PowerConnects switches.
The configs on the Cisco Nexsus switches seem to be the same as they were before the power failure, I logged onto the PowerConnects to see if it had kept the VLAN configs they all seem to be there.

 

The environment was configured by someone else who had left the company and nothing was handed over, I am just trying to make sense of everything.

I am not where the issue may be. Any help would be much appreciated.

 

Kind Regards

Moderator

 • 

7.6K Posts

November 17th, 2021 10:00

Hello Jade,

Here is a link to a kb that maybe of assistance. https://dell.to/3254aAh

1 Rookie

 • 

14 Posts

November 18th, 2021 00:00

Hi DELL-Sam L

 

I can't seem to get the link, I receive the below error message.

Jade_0-1637225406916.png

Thanks

 

Moderator

 • 

7.6K Posts

November 18th, 2021 14:00

Here is what the article states.

 

Instructions

 What is the power-up and power-down sequence for a CLARiiON or VNX Block series storage system?



Powering up the storage system
  1. Verify the following:
     
    • Master switch/circuit breakers for each cabinet/rack power strip are off.
       
    • The power cord for SP A is plugged into the SPS and the power cord retention bails are in place.
       
    • The power cord for SP B is plugged into the nearest power distribution unit on a different circuit feed from the SPS and power cord retention bails are in place. (In systems with two SPSs, plug SP B into its corresponding SPS.)
       
    • The serial connection between management module A and the SPS is in place. (In systems with two SPSs, each management module has a serial connection to its corresponding SPS.)
       
    • The power cord for LCC A on the first DAE (EA 0, bus 0; often called the DAE-OS) is plugged into the SPS and the power cord retention bails are in place.
       
    • The power cord for LCC B is plugged into the nearest power distribution unit on a different circuit feed than the SPS. (In systems with two SPSs, each LCC plugs into its corresponding SPS.)
       
    • The power cords for the SPSs and any other DAEs are plugged into the cabinet   s power strips.
       
    • The power switches on the SPSs are in the on position.
       
    • Any other devices in the cabinet are correctly installed and ready for power-up.
       
  2. Turn on the master switch/circuit breakers for each cabinet/rack power strip.

In the 40U-C cabinet, master switches are on the power distribution panels (PDPs). The power-up is complete when the CPU power light on each SP is steady green. The CPU status lights are visible on the SPE when the front bezel is removed. If amber LEDs on the front or back of the storage system remain on for more than 10 minutes, make sure the storage system is correctly cabled, and then refer to the troubleshooting flowcharts for your storage system on the CLARiiON Tools page on the EMC Powerlink website (https://dell.to/30JTA1t). If you cannot determine any reasons for the fault, contact your authorized service provider.

The storage system can take 8 to 10 minutes to complete a typical power-up. Amber warning LEDs flash during the power on self-test (POST) and then go off. The front fault LED and the SPS recharge LEDs commonly stay on for several minutes while the SPSs are charging.

Powering down the storage system:

  1. Stop all I/O activity to the SPE. If the server(s) connected to the SPE is running the Linux or UNIX operating system, back up critical data and then unmount the file systems. Stopping I/O allows the SP to destage cache data, and may take some time. The length of time depends on criteria such as the size of the cache, the amount of data in the cache, the type of data in the cache, and the target location on the disks, but it is typically less than one minute. We recommend that you wait five minutes before proceeding.
     
  2. After five minutes, use the power switch on each SPS to turn off power. Storage processors and DAE LCCs connected to the SPS power down within two minutes.
     
  3. For a system with a single SPS, wait two minutes and then unplug the power cables for SP B on the SPE and LCC B on DAE 0, bus 0. This turns off power to the SPE and the first DAE (EA 0, bus 0). You do not need to turn off power to the other connected DAEs.
     
  4. Power off the rest of the equipment in the rack - all DAE's

Caution! Never unplug the power supplies to shut down an SPE. Bypassing the SPS in that manner prevents the storage system from saving write cache data to the vault drives, and results in data loss. You will lose access to data, and the storage processor log displays an error message similar to the following: Enclosure 0 Disk 5 0x90a (Can   t Assign - Cache Dirty) 0 0xafb40 0x14362c. Contact your service provider if this situation occurs.

1 Rookie

 • 

14 Posts

November 19th, 2021 00:00

Thanks Dell-Sam L

So power down and powering up sequence is related to the Chassis and IDRAC not having any communication/routing to the Cisco Nexsus Switches?

1 Rookie

 • 

14 Posts

November 19th, 2021 04:00

Hi DELL-SAM L

I should let you know that one of the PowerConnect switches is not connected to the environment and has faulted, this was a issue before before the environment turned off. Slot A-2.

Moderator

 • 

7.6K Posts

November 19th, 2021 15:00

Hello Jade,

If you look in unisphere are you seeing your servers connected?

1 Rookie

 • 

14 Posts

November 24th, 2021 16:00

Hi DELL-Sam L,

 

I see the below,

Jade_0-1637801790266.png

 

1 Rookie

 • 

14 Posts

November 24th, 2021 17:00

Hi DELL-Sam L,

 

I also just though of this after I made the diagram but is it connected to the Dell PowerEdgeM1000e?? see below

Jade_1-1637803601143.png

 

Moderator

 • 

9.3K Posts

November 26th, 2021 07:00

Is the m1000e reachable from the nexus switches?

1 Rookie

 • 

14 Posts

November 28th, 2021 00:00

Hi DELL-Josh Cr

Yes, so I can ping the M1000e from the Nexsus switches . That cable is not plugged into the Nexsus switches, it is in our Patch Panel which then goes to our core switch. 

Really appreciate your help.

Moderator

 • 

7.6K Posts

November 29th, 2021 08:00

Hello Jade,

To me it sounds like you are having a cabling issue between your switches and your patch panel.  I would double check your connections as there is something that is not connected that needs to be.

1 Rookie

 • 

14 Posts

December 2nd, 2021 23:00

Hi Dell-Sam L

I saw this post by ransome_b




Jade_0-1638516121190.png

 

This is the exact issue I am facing. I am able to ping gateways 10.239.74.1 and 10.239.65.1 from my Cisco Nexus Switch and the powerconnects. But the Window's server on 10.239.65.0/24 are unable to ping the gateways.

Moderator

 • 

7.6K Posts

December 3rd, 2021 12:00

Hello Jade,

I would open a support case on your server as there seems to be an issue with windows.

No Events found!

Top