Trending Topics

Implement and configure AWS Backup for VMware Cloud on AWS VM workloads

Image
In our previous post we saw the design of the AWS Backup on VMC. In this post we’re going through the implementation steps As per the design and best practice, we are going to use the ENI for the Backup traffic CREATE A VPC ENDPOINT  TO CREATE AN INTERFACE ENDPOINT FOR AN AWS SERVICE 1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc    2. In the navigation pane, choose Endpoints 3. Choose Create endpoint 4. Name the endpoint   5. For Service category, choose AWS services 6. For Service name, search “ Backup ” and select “ backup-gateway ” service from the dropdown 7. For VPC, select the VPC which we used for SDDC deployment and extension 8. To create an interface endpoint for Amazon S3, you must “uncheck” Additional settings, Enable DNS name. This is because Amazon S3 does not support private DNS for interface VPC endpoints 9. For  Subnets , select one subnet per Availability Zone which we used for SDDC VMC selection  10. For Security group , sel

RHEL server LUN paths goes offline during failover




Description of problem:

Client is attempting to kickstart RHEL5 to a blade system with SAN attached
storage. The customer is hitting an issue where anaconda complains with the
following message at the beginning of the install:

On virt console 1:
Warning: /dev/sda is a read-only filesystem and hit OK to continue

On virt console 3:
parted exception: Warning: Unable to open /dev/sda read-write
(Read-only file system). /dev/sda has been opened read-only

The customer has to hit OK to accept this and the installation will then
complete successfully.

There are currently two LUNs presented from the SAN to the host. /dev/sda is
indeed read-only and apparently it is a gatekeeper type device that is
exported/presented to numerous hosts hence why it's read-only. /dev/sdb is the
second LUN device that we want to install to.

I've tried using the following entries in the kickstart file:
ignoredisk --drives=sda
clearpart --all --drives=sdb
partition /boot --fstype=ext3 --size=200 --ondisk=sdb
partition pv.03 --size=1 --grow --ondisk=sdb
<and create vg and lv......>

And removing the zerombr reference but the customer is still hitting the issue.

How reproducible:
1. Install via kickstart or manual
2. Kickstart profile uses 'ignoredisk=sda' to ignore first LUN
3. Still prompted by anaconda that sda is read-only
4. Hitting Ok or Ignore will continue the installation
Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. Install via kickstart or manual
2. Kickstart profile uses 'ignoredisk=sda' to ignore first LUN
3. Still prompted by anaconda that sda is read-only
4. Hitting Ok or Ignore will continue the installation

Actual results:
User prompted to hit OK when /dev/sda device is found to be read-only

Expected results:
ignoredisk directive in kickstart should indicate which devices to ignore and
not present a warning that it's read-only.



Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

DNS Scavenging.

AD LDS – Syncronizing AD LDS with Active Directory