Wednesday, December 2, 2020

SAN LUNs/Disks are not detecting by OS post SAN storage Power outage.

SAN LUNs/Disks are not detecting by OS post SAN storage Power outage.

 

Recently one of the Customer experienced SAN power outage. Many Servers with make HP, IBM, CISCO and various OS flavors were impacted. Post SAN Storage (Fiber Channel) recovery SAN disks were automatically discovered after the Server reboot.

 

However, for many IBM Servers mainly BladeCenter HS22 irrespective of OS, SAN drives did not reconnect after the Server reboot as well.

We had to perform below Steps to reconnect the SAN storage.

  1. Login to IBM bladecenter Advanced management Module
  2. Navigate to I/O Module Task
  3. SelectàAdmin/Power/Restart
  4. SelectàRestart Module(s) and Run standard Diagnostics
  5. ClickàPerform action 
  6. Reboot/Start the Server.












Excel/Office files are taking very long time to open; Virtual memory/Page file configuration is not saving on Microsoft Windows Server 2016

This blog post is to share few issues with Microsoft ‘System Monitor’ (Sysmon).


Sysmon is a Windows system service  that helps to log system activity to the Windows event log. Many customers are relaying on this tool to collect additional logging, which helps to identify malicious or anomalous activity on their environment.

Below are the two symptoms identified with Sysmon driver version 11 on Microsoft Windows Server 2016.

1.Excel/Office files are taking very long time to open/SMB share is too slow.

If anyone try to access files from a Server installed with Sysmon Version11, the client may experience poor performance. For example, when they try to open an Excel file from another Machine may take more than a minutes and it gets stuck at 0% opening excel window. Pic below;










2.Virtual memory/Page file configuration is not saving.

It create a random paging file, not as per the desired configuration, what we set for ‘Initial and Maximum’ size at ‘System properties-Advanced-Performance Option’. Suppose we configure 2048 Mb, the System page file would appear a lower value instead of configured 2048Mb post server reboot.

As part of troubleshooting, Sysmon version11.0 was removed and reinstalled with Sysmon Version12.0, which resolved both the above issues.


[Solved] HP ILO, iBMC Remote console and Virtual Media Applets are not working.

HP ILO, iBMC Remote console and Virtual Media Applets are not working.

            Remote Server management using Integrated Lights-out Management Module (ILO) for HP Servers and Integrated Baseboard Management Controller (iBMC) for IBM servers have many challenges due to the enhanced security features of Java JVM, Web browsers and Operating System hardening. Most of the case the Remote Console (Java applet-based console) will not open with many errors.

 

This post will help you with a workaround to access the ILO/iBMC console using Integrated Remote Console or Java JVM web console.

Common Issues when connecting to Server Console form ILO/iBMC.

1. Microsoft Internet Explorer is required to Run Integrated Remote Console. When connecting Remote Console using Integrated Remote Console.










Follow below steps to resolve above described issue.

On Internet Explorer ➤Click on Gear/Tool icon➤Compatibility View Settings➤ Add ILO/iBMC IP.

Restart Internet Explorer and Try again.










2.Remote Console KVM from a Java Applet based is throwing ClassNotFoundExepetion Error.















Follow below steps to resolve this error.

Click Windows Start Menu➤Control Panel➤Click on Java icon from ‘All control Panel Items’

Select Security➤Edit Site List➤ Add ‘ILO/iBMC IP address followed by *.

And add ‘ILO/iBMC IP’ address followed by :443











Next Click on ‘Java Control Panel’ Advanced Menu, Scroll down and deselect TLS1.1, TLS1.2, and TLS1.3

Enable TLS 1.0 Only 









Re-open Internet Explorer browser and follow below steps to access ILO Console.

Login to ILO➤ Remote Console➤Select Remote Console KVM Java Applet Based➤Click on Continue for Security related Warnings 








Select “I accept the risk and want to Run this Application”












Finally!!! You will have access to Java JVM remote console. The Virtual Media Applet also would connect without any issues.