My disk00 went defunct and there is no /local file system present. If disk00 is part of the array, why would this failure cause the waas to go offline or not find /local? TAC is suggesting that I need to rebuild the box from the rescue cd and I want to avoid that.
You can obtain a detailed software RAID status, which includes the disk utilization, the number of disks on the WAE, and operational status, by using the EXEC command show disks details. The following example shows a two-disk system in which the disks are operating normally:
WAE# show disks details (Send me the output of the following command)
Physical disk information:
disk00: Normal (h00 c00 i00 l00 - DAS) 76324MB( 74.5GB)
disk01: Normal (h01 c00 i00 l00 - DAS) 76324MB( 74.5GB)
DEVICE NAME TYPE STATUS PHYSICAL DEVICES AND STATUS
/dev/md0 RAID-1 NORMAL OPERATION disk00/00[GOOD] disk01/00[GOOD]
/dev/md1 RAID-1 NORMAL OPERATION disk00/01[GOOD] disk01/01[GOOD]
/dev/md2 RAID-1 NORMAL OPERATION disk00/02[GOOD] disk01/02[GOOD]
/dev/md3 RAID-1 NORMAL OPERATION disk00/03[GOOD] disk01/03[GOOD]
/dev/md4 RAID-1 NORMAL OPERATION disk00/04[GOOD] disk01/04[GOOD]
/dev/md5 RAID-1 NORMAL OPERATION disk00/05[GOOD] disk01/05[GOOD]
/dev/md6 RAID-1 NORMAL OPERATION disk00/06[GOOD] disk01/06[GOOD]
Currently SW-RAID is not configured to change.
More common than a total disk failure is a partial disk failure. When errors occur in one or a few sectors of a disk, a partial failure has occurred. Because the RAID devices are configured on a partition by partition basis, some partitions may continue to operate using the respective disk partitions from both disk drives. Sector errors are typically detected when the software attempts to read an affected sector. After retrying the read operation internally a number of times, the disk drive eventually gives up, and returns an error to the operating system and the RAID driver code. The kernel RAID-1 code stops accessing the affected physical partition. The notification of these errors is visible using the show disks details EXEC command.
To attempt recovery from a partial disk failure, follow these steps:
Upon reboot, the standard RAID-1 resynchronization is performed. Resynchronization overwrites all of the failed drive's contents, giving the disk drive a chance to remap any bad sectors. If additional disk I/O errors subsequently occur in a short period of time, or if the disk drive cannot be detected by the software after a reboot, the disk drive has probably failed past the point of repair, and replacement is needed.
On systems with SCSI disk drives, another recovery option for partial failures is available. This option involves marking the disk as bad and reformatting the disk.
When you run the WAAS disk check tool, you will be logged out of the device. The device automatically reboots after it has completed checking the file system. Because this operation results in a reboot, we recommend that you perform this operation after normal business hours.
Copy the script to your WAE device by using the copy ftp disk command.
WAE# copy ftp disk disk_check.sh
Run the script from the CLI, as shown in the following example:
WAE# script execute disk_check.sh
This script will check if there is any file system issue on the attached disks
Activating the script will result in:
Stopping all services. This will log you out.
Perform file system check for few minutes.
and record the result in the following files:
/local1/disk_status.txt - result summary
/local1/disk_check_log.txt - detailed log
If the system doesn't reboot in 10 minutes, please re-login and check the result files.
Please disk_status.txt after reboot for result summary
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...