eBGP Mesh - failure of redundancy

Similar Questions

• Status of Volume failure redundancy mirrored after each reboot with Windows 7 Ultimate edition.

  I have 2 x 2 TB hard drives that I put as dynamic disks and mirrored Volumes (software through Windows 7). There are data on the disks and when I created first the mirror and he finished re-synchronization status has been set to healthy. Now after restarting the computer the disks come with a warning in management records indicating the failure of redundancy. I can reactivate the disk and it synchronizes and back healthy (which takes all day) but after a reboot it says has a failure of redundancy again.

  Have not been able to find something that helps or stops this from happening.

  I just changed 1 TB for windows changed 2 TB disks numbers of himself...

• Readers uncertified casting flaws

  Hello

  We have a number of blades Dell Perc h700 and h710 Perc cards running.

  Most of them is running 840 Samsung pro SSDS and disks SSD Samsung 830 - these discs work perfectly well and we show him simply as "uncertified" and table is Non-critical", this does not lead to problems.

  Now, we just installed some servers with the last crucial 960GB SSD drives and again all this works very well, but every time to start the machines it is update errors in the log of the CMC:

  • 12 changed in a State Server status critical from a normal or a warning state.
  • Failure detected on drive 0 in the drive Bay 1
  • Failure detected on disk 1 in the drive Bay 1.

  Does anyone have any idea why this might be happening?
  

  Here are the omreports:
  

  ---
  

  root@zeus # omreport storage vdisk
  List of Virtual Disks in the System
  
  Controller PERC H710 Mini (Embedded)
  ID                        : 0
  Status                    : Ok
  Name                      : Zeus
  State                     : Ready
  Hot Spare Policy violated : Not Assigned
  Encrypted                 : Not Applicable
  Layout                    : RAID-1
  Size                      : 850.00 GB (912680550400 bytes)
  Device Name               : /dev/sda
  Bus Protocol              : SATA
  Media                     : SSD
  Read Policy               : Adaptive Read Ahead
  Write Policy              : Write Back
  Cache Policy              : Not Applicable
  Stripe Element Size       : 64 KB
  Disk Cache Policy         : Enabled
  
  root@zeus # omreport storage pdisk controller=0
  List of Physical Disks on Controller PERC H710 Mini (Embedded)
  
  Controller PERC H710 Mini (Embedded)
  ID                        : 0:0
  Status                    : Non-Critical
  Name                      : Physical Disk 0:0
  State                     : Online
  Power Status              : Not Applicable
  Bus Protocol              : SATA
  Media                     : SSD
  Device Life Remaining     : Not Applicable
  Failure Predicted         : No
  Revision                  : MU02
  Driver Version            : Not Applicable
  Model Number              : Not Applicable
  Certified                 : No
  Encryption Capable        : Yes
  Encrypted                 : No
  Progress                  : Not Applicable
  Mirror Set ID             : Not Applicable
  Capacity                  : 893.75 GB (959656755200 bytes)
  Used RAID Disk Space      : 850.00 GB (912680550400 bytes)
  Available RAID Disk Space : 43.75 GB (46976204800 bytes)
  Hot Spare                 : No
  Vendor ID                 : ATA
  Product ID                : Crucial_CT960M500SSD1
  Serial No.                : 1311092FA641
  Part Number               : Not Available
  Negotiated Speed          : 6.00 Gbps
  Capable Speed             : 6.00 Gbps
  Device Write Cache        : Not Applicable
  Manufacture Day           : Not Available
  Manufacture Week          : Not Available
  Manufacture Year          : Not Available
  SAS Address               : 4433221104000000
  
  ID                        : 0:1
  Status                    : Non-Critical
  Name                      : Physical Disk 0:1
  State                     : Online
  Power Status              : Not Applicable
  Bus Protocol              : SATA
  Media                     : SSD
  Device Life Remaining     : Not Applicable
  Failure Predicted         : No
  Revision                  : MU02
  Driver Version            : Not Applicable
  Model Number              : Not Applicable
  Certified                 : No
  Encryption Capable        : Yes
  Encrypted                 : No
  Progress                  : Not Applicable
  Mirror Set ID             : Not Applicable
  Capacity                  : 893.75 GB (959656755200 bytes)
  Used RAID Disk Space      : 850.00 GB (912680550400 bytes)
  Available RAID Disk Space : 43.75 GB (46976204800 bytes)
  Hot Spare                 : No
  Vendor ID                 : ATA
  Product ID                : Crucial_CT960M500SSD1
  Serial No.                : 1311092FA619
  Part Number               : Not Available
  Negotiated Speed          : 6.00 Gbps
  Capable Speed             : 6.00 Gbps
  Device Write Cache        : Not Applicable
  Manufacture Day           : Not Available
  Manufacture Week          : Not Available
  Manufacture Year          : Not Available
  SAS Address               : 4433221105000000
  
  root@zeus # omreport storage controller
   Controller  PERC H710 Mini (Embedded)
  
  Controllers
  ID                                            : 0
  Status                                        : Ok
  Name                                          : PERC H710 Mini
  Slot ID                                       : Embedded
  State                                         : Ready
  Firmware Version                              : 21.2.0-0007
  Latest Available Firmware Version             : Not Applicable
  Driver Version                                : 06.504.01.00-rh1
  Minimum Required Driver Version               : Not Applicable
  Storport Driver Version                       : Not Applicable
  Minimum Required Storport Driver Version      : Not Applicable
  Number of Connectors                          : 1
  Rebuild Rate                                  : 30%
  BGI Rate                                      : 30%
  Check Consistency Rate                        : 30%
  Reconstruct Rate                              : 30%
  Alarm State                                   : Not Applicable
  Cluster Mode                                  : Not Applicable
  SCSI Initiator ID                             : Not Applicable
  Cache Memory Size                             : 512 MB
  Patrol Read Mode                              : Auto
  Patrol Read State                             : Stopped
  Patrol Read Rate                              : 30%
  Patrol Read Iterations                        : 9
  Abort Check Consistency on Error              : Disabled
  Allow Revertible Hot Spare and Replace Member : Enabled
  Load Balance                                  : Not Applicable
  Auto Replace Member on Predictive Failure     : Disabled
  Redundant Path view                           : Not Applicable
  CacheCade Capable                             : Yes
  Persistent Hot Spare                          : Disabled
  Encryption Capable                            : Yes
  Encryption Key Present                        : No
  Encryption Mode                               : None
  Preserved Cache                               : No
  Spin Down Unconfigured Drives                 : Disabled
  Spin Down Hot Spares                          : Disabled
  Spin Down Configured Drives                   : Disabled
  Automatic Disk Power Saving (Idle C)          : Disabled
  Time Interval for Spin Down (in Minutes)      : Not Applicable
  Start Time (HH:MM)                            : Not Applicable
  

  ---
  

  The error has been a Dell uncertified drive.  The player will operate normally, but the shift of the firmware will return the error.

  Kind regards

• State of the controller H710P degraded, but pdisks and vdisks are OK

  Hi, I have several PowerEdge servers R720 with Mini H710P (embedded) controllers and PERC H710P who have problems. Omreport, the controller is in a non-critical State and a degraded state:

  Controller of
  ID: 1
  Status: No reviews
  Name: PERC adapter H710P
  Location ID: PCI Slot 2
  State: degraded
  Firmware version: 21.3.0 - 0009
  Minimum Firmware Version: 21.3.1 - 0001
  Driver version: 06.806.08.00 - rh3
  The minimum required driver version: not Applicable
  The Storport driver version: not Applicable
  Minimum required: Version of the Storport driver: not Applicable
  Number of connectors: 2
  Regeneration rate: 30%
  BGI rate: 30%
  Consistency check rate: 30%
  Rebuild rate: 30%
  Alarm status: not applicable
  Cluster mode: not Applicable
  SCSI initiator ID: not Applicable
  Cache memory size: 1024 MB
  Patrol read mode: Auto
  Patrol read status: stopped
  Patrol read rate: 30%
  Read the iterations of patrol: 42
  Give up control of consistency error: disabled
  Enable reversible hot spare and replace the: enabled
  Load Balancing: not Applicable
  Auto Member Replace on Predictive Failure: disabled
  Redundant path view: not Applicable
  CacheCade Capable: Yes
  Persistent backup: disabled
  Encryption Capable: Yes
  Currently key encryption: No.
  Encryption mode: no
  Preserved cache: not Applicable
  Spin down drives unconfigured: disabled
  Turn down hot spares: disabled
  Spin down drives configured: disabled
  Automatic disk Power Saving (Idle_c): disabled
  Start time (hh: mm): not Applicable
  Time interval of rotating upward (in hours): not Applicable

  Vdisk is OK:

  Controller PERC H710P adapter (Slot 2)
  ID: 0
  Status: Ok
  Name: Virtual disk 0
  Status: ready
  Hot violated political alternatives: not
  Encrypted: No.
  Layout: RAID-5
  Size: 3 350,25 GB (3597303545856 bytes)
  T10 Protection Information status: No.
  Liquid state of Cache associated with: not Applicable
  Name of the device: / dev/sdc
  Bus protocol: SAS
  Media: HDD
  Political reading: Adaptive Read Ahead
  Political writing: write back
  The cache policy: not Applicable
  Stripe Element Size: 64 KB
  The strategy of Disk Cache: disabled

  And so are the physical disks (output truncated, there are many records!):

  ID: 0:2:7
  Status: Ok
  Name: Physical disk 0:2:7
  Status: ready
  Supply status: leader
  Bus protocol: SAS
  Media: HDD
  Part of the Cache Pool: not Applicable
  Remaining nominal write Endurance: not applicable
  Predicted failure: No.
  Review: LS0A
  Driver version: not Applicable
  Model number: not Applicable
  T10 IP Capable: No.
  Certified: Yes
  Encryption Capable: No.
  Encrypted: Not Applicable
  Progress: Not Applicable
  Mirror Set ID: Non Applicable
  Capacity: 558,38 GB (599550590976 bytes)
  RAID disk space used: 558,38 GB (599550590976 bytes)
  Space disk RAID: 0.00 GB (0 bytes)
  Hot spare: dedicated
  Vendor ID: Dell (TM)
  Product ID: ST600MM0006
  Serial number: S0M4EMF4
  Part No.: CN07YX587262251B0119A02
  Negotiated speed: 6,00 Gbps
  Measuring speed: 6,00 Gbps
  PCIe negotiated link width: not Applicable
  PCIe Maximum link width: not Applicable
  Sector size: 512 b
  The device's write cache: not Applicable
  Date of manufacture: 03
  Week of manufacture: 02
  Manufacturing year: 2015
  SAS address: 5000C5007F103929
  Form factor: not available
  Void Publisher: not available

  I had found a previous thread which suggested updating the firmware, but I can't find a more recent version of the firmware for controllers (embedded or extra).

  If it makes a difference, all servers running RHEL 6.6 (Santiago)

  Lachlandehaas,

  I think you are right in assuming that the problem is caused by the firmware being obsolete. The firmware is actually a few updates behind. You can find the latest version of the update here. Updated the fw on the controller and let me know if the VD shows ONLINE later.

  Let me know what you see

• RAID Controller degraded by the Firmware version

  Hi all

  My security system is sending me alert because my RAID controllers being day. RAID controllers are fine, but the State is deteriorating because of the "latest Firmware Version available" which means I can't properly control if something really bad happens.

  Is it possible to disable the alert or lower the minimum version expected? I just can't reboot all my servers just for an update of the RAID firmware.

  My security system expects a status: Ok

  Thank you very much in advance!

  Greg

  Below the output omreport:

  omreport storage controller $
  Controller PERC H700 integrated (Embedded)

  Controllers of
  ID                                            : 0
  Status: No reviews
  Name: PERC H700 integrated
  Location ID: shipped
  State: degraded
  Firmware version: 12.10.1 - 0001
  Latest Version of the Firmware available: 12.10.4 - 0001
  Driver version: 00.00.06.14 - kh1
  The minimum required driver version: not Applicable
  The Storport driver version: not Applicable
  Minimum required: Version of the Storport driver: not Applicable
  Number of connectors: 2
  Regeneration rate: 30%
  BGI Rate                                      : 30%
  Consistency check rate: 30%
  Rebuild rate: 30%
  Alarm status: not applicable
  Cluster mode: not Applicable
  SCSI initiator ID: not Applicable
  Cache memory size: 512 MB
  Patrol read mode: manual
  Patrol read status: stopped
  Patrol read rate: 30%
  Read the iterations of patrol: 2
  Give up control of consistency error: disabled
  Enable reversible hot spare and replace the: enabled
  Load Balancing: not Applicable
  Auto Member Replace on Predictive Failure: disabled
  Redundant path view: not Applicable
  Able CacheCade: Non Applicable
  Persistent backup: disabled
  Encryption Capable: Yes
  Currently key encryption: No.
  Encryption mode: no
  Preserved cache: No.
  Spin down drives unconfigured: disabled
  Turn down hot spares: disabled
  Centrifuge the configured drives: not Applicable
  Automatic disk Power Saving (idle C): not Applicable

  Thanks again!

  gcharot

  Is it possible to update the firmware without system reboot? I am running CentOS 5 and 6

  No, you can update the firmware without a reboot, but the update will be based in the controller cache until a reset is performed. So yes, you can perform the update without reboot, but it will not take effect until you perform a reboot.

  Thank you

• grid below 11 GR 2 helps the installation required

  Mr President
  
  I have some problem.do don't know don't not how to solve?
  
  I need to install the Advanced installation grid infrastructure.
  Scenario and question:
  
  I have a raw(74GB) under the DSO on 192.168.1.13.but how to implement cluster is not under OCFS2, what to do (under OEL5.4)?
  
  and in another machine (with ip 192.168.1.30) I want to load 11 GR 2 grid as well as 11 GR 2 db but how would you describe the disk to ASM-ocfs2 cluster? I had an a partition/dev/sda3 as LVM with two partion mounted /ASM1 and /ASM2 empty ext3 in this machine.what do?
  
  concerning

  I guess this will help - http://blog.ronnyegner-consulting.de/2009/09/14/oracle-11g-release-2-install-guide-%e2%80%93-grid-infrastructure-installation/
  -http://husnusensoy.wordpress.com/2009/10/30/how-to-install-oracle-11g-release-2-on-oel-5-4-on-virtualbox-installing-grid-infrastructure/

  To identify storage needs for the use of Automatic Storage Management, you must determine the number of devices and the amount of free space on the drive you need. To perform this task:
  1. determine if you want to use Automatic Storage Management for Oracle database files, recovery of files or both.
  Note:
  You don't have to use the same storage mechanism for Oracle database and file recovery files. You can use a file system for one type of Automatic Storage Management and file for each other.
  If you choose to enable automatic backups and you don't have a system of shared files available, you must choose Automatic Storage Management for the storage of files recovery.
  If you plan to activate backups automated installation, then you can Automatic Storage Management as storage of file recovery mechanism by specifying a group of Automatic Storage Management disk for fast recovery area. Depending on how you choose to create a database during installation, you have the following options:
  o If you select an installation method that runs Oracle Automatic Storage Management Configuration Wizard in interactive mode, you can decide if you want to use the same disk group Automatic Storage Management for data files and recovery files, or you can choose to use groups of different record for each file type. Ideally, you should create separate Automatic Storage Management disk groups for the data files and recovery files.
  The choice is available if you are using Oracle Database Configuration Wizard after the installation to create a database.
  o If you select a type of installation that works Automatic Storage Management Assistant de Configuration Oracle silent mode or in answer file mode, then you must use the same disk group Automatic Storage Management for data files and recovery files.
  2. choose the level of redundancy of automatic storage management you want to use for each Automatic Storage Management disk group that you create.
  The level of redundancy you choose for the Automatic Storage Management disk group determines how Automatic Storage Management reflects the disk group files and determines the number of disks and the amount of disk space you need, as follows:
  o external redundancy
  This option does not Automatic Storage Management reflect the content of the disk group. Oracle recommends that you select this redundancy when the disk group contains devices, such as the RAID devices, which protect their own data or when the database does not require uninterrupted access to data.
  o Normal dismissal
  To optimize performance and reliability in a group of disks in normal redundancy, Automatic Storage Management uses two-way mirroring for three-way mirroring for the default control files and data files. In addition, you can choose the features of mirroring for individual files in a disk group. You can also use the bidirectional or not mirror mirrored.
  A normal redundancy disk group requires a minimum of two groups of failure (or two drive devices) If you use two-way mirroring. Effective space in a disk of normal redundancy group is half of the sum of the space in all of its features.
  For most installations, Oracle recommends to use normal redundancy disk groups.
  o high redundancy
  The contents of the disk group is three lanes in reverse by default. To create a disk with high redundancy group, you must specify at least three groups of failure (a minimum of 3 devices).
  Although disk groups high redundancy offer a high level of data protection, you must take into account the higher cost of additional storage devices before you decide to use this level of redundancy.
  3. determine the total amount of disk space you need for database files and recovery files.
  If an Automatic Storage Management instance is already running on the system, you can use an existing disk group to meet these needs of storage. If necessary, you can add disks to a group of existing installation drive.
  Use the following table to determine the minimum number of disks and space of minimum disc required for installation:
  The two Types of files the files number Minimum level of redundancy of records data files recovery
  External 1 GB GB 5.4 GB 3.6 1.8
  Normal 2 3.6 GB GB 7.2 10.8 GB
  High 3 5.4 GB GB 10.8 16.2 GB

  4. If necessary, identify the groups of failure for devices of Automatic Storage Management disk group.
  If you plan to use a normal or high redundancy disk group, you can further protect the database against hardware failures by combining a set of disk devices in a custom group failure. By default, each unit includes its failure. However, if two drive devices in a group of normal redundancy disks are attached to the same SCSI controller, then the disk group would become unavailable if the controller fails. The controller in this example is a single point of failure.
  To avoid failures of this type, you can use two controllers SCSI, each with two discs and define a group of failure for the drives attached to each controller. This configuration would allow the disk group to tolerate the failure of a SCSI controller.
  Note:
  If you set custom failure groups, you must specify a normal minimum of two groups of failure for redundancy disk groups and three groups failed for disk groups high redundancy.
  5. If you are sure that a suitable disk group does not exist on the system, then install or identify the drive devices appropriate to add a new disk group. Apply the following guidelines when identifying the appropriate drive devices:
  o disc devices must belong to the user who performs the installation of the grid.
  o all devices in an Automatic Storage Management disk group must be the same size and have the same performance characteristics.
  o do not specify several partitions on a single physical disk as a disk device group. Automatic Storage Management expects that each device group on a separate physical disk drive.
  o Oracle does not recommend the use of a logical volume as a device of automatic storage management, because the logical volume is able to hide the physical disk architecture that prevents Automatic Storage Management of I/O optimization across physical devices.

• Redundancy of the Normal ASM - three stores, three groups of failure

  Hello

  I have a question about groups of failure in ASM. I have an ASM diskgroup with normal redundancy and records of three different preparations. Each storage disks are in separate groups of failure (see screen below). I know what ASM allocates to a point as it allocates a copy of copy and the primary mirror and mirror copy is placed on a different disk that is part of a group of different failure. And it is understood for the configuration with two storage (or controllers) and two different groups of failure. But what with configuration where are three storages and failure groups? My question is: If I failed three groups if new extensions are allocated are mirrored are placed on the other two discs are it is a part of a group of different failure? Or maybe this kind of configuration (with three groups of normal redundancy ASM failure) is not supported?

  

  I know what ASM allocates to a point as it allocates a copy of copy and the primary mirror and mirror copy is placed on a different disk that is part of a group of different failure. And it is understood for the configuration with two storage (or controllers) and two different groups of failure. But what with configuration where are three storages and failure groups? My question is: if I have three groups of failure, if new extensions are allocated are mirrored are placed on the other two discs are it is a part of a group of different failure? Or maybe this kind of configuration (with three groups of normal redundancy ASM failure) is not supported?

  No matter how much you failgroup. Normal redundancy requires at least 2 Failgroup.

  Oracle will allocate primary measure in a failgroup and place the mirror of the scopes in an another failgroup.

  The order does not matter since you always have a copy in a different failgroup.

  See example below (d = data extended)

  FG1 |   FG2 | FG3

  ========|===============|=========
  

  d1      |   d1_copy:

  |   d2          | d2_copy

  d3_copy |               | d3

  When you create a Diskgroup without specifying the failgroup, Oracle will automatically create a failgroup to each diskgroup. So, if you create a normal with normal redundancy Diskgroup and ASMDISK 10, ASM will create 10 failgroups.

  You have 3 warehouses and 3 Failgroup

  If you loss storage (h/f) ASM will tolerate because you measure mirror in any other failgroup (h, l, square).

  If you loss both storage (h/f) or two different storage disk/controller at the same time ASM will not tolerate. (Need to restore a backup database)

  Your point of failure: you must make sure that the two storages/controllers/disks will still be available.

  If your concern is: can I have a situation where two storage can do fail (or cut) at the same time. Then, you need high redundancy, because this configuration will tolerate you two storages loss (h/f) at the same time and Diskgroup will remain active.

• Cannot boot from recovery CD - error: PXE - E61: Media test failure

  Recovery CD (Windows XP home Edition) cannot start the Toshiba satellite A40 Model # PSA40E-0EWDE-AR (SA40-261), whenever I try to Boot From recovery cd I get this error:

  PXE - E61: Media test failure, check cable of
  PXE - M0F: Exit Intel Boot Agent.

  but when I boot from any other cd (windows ME, WIN 2 K, WIN XP Pro...) everything is ok.
  Any clue? Help me please
  Thank you
  Mesha

  Hello

  It seems that the player is unable to boot from the recovery CD and the switch to boot from LAN.
  The error PXE - E61 message because the LAN cable was not connected and the laptop is not able to find a source of network boot

  I think you should check the recovery CD and perhaps you will need a new

• 2012 server redundancy

  Hmmm, I'm a little confused that I don't see any option for this post in forum windows server 2012.

  In any case, I have a few questions about creating a backup for an all-in-one server. The server has active directory, DNS, file server, and everything on it. I am trying to create a configuration of redundancy in case of failure. While I was reading on the failover clusters and this seems to be what I need to do. I'm just a little confused.
  When I create a cluster and add servers to it, what happens exactly? For the simplest case instance, I have the main server with all the data. Now, I bring to another machine with nothing on it. I have install windows server 2012 on it and add, as well as the other computer in a cluster. The main server data automatically copied on all servers that are part of this group? At this point if a server goes down the other to take over?
  Any help is greatly appreciated.
  FlipFlop

  In the Windows Server forum:
  http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer.

• Data backup (cyclic redundancy check) error 0 x 80070017

  does not end ox80070017 of error (cyclic redundancy check) backup data?

  Hello

  When you try to save on?

  You should not save it to your hard drive, because in the event of a disk failure hard, all your data is lost.

  And you perform backups to your recovery partition; This is to reinstall the operating system.

  Backups must be performed on a DVD or an external hard drive; preferably an external hard drive.

  This can help you:

  "How to back up your data.

  http://www.wintuts.com/how-to-backup-your-data

  "Back up and restore: frequently asked questions.

  http://Windows.Microsoft.com/en-us/Windows-Vista/back-up-and-restore-frequently-asked-questions

  See you soon.

• Problems of redundancy PowerConnect 7048

  Hello! I recently put in place a network I have a problem with and need someone to go through my configs of switch and tell me if they see something that I did wrong.

  The network consists of a blade M1000 - filled completely, Equalogic 2, 2 Powerconnect 7048 and 2 Powerconnect 8024-K (inside of the blade). I have everything configured for redundancy. Each server blade has 4 NIC, two are for iSCSI traffic and the other 2 are for virtual machine network traffic.

  The 7048 are stacked. I got everything is configured so I can unplug all four NICS (one at a time) on a blade, and the server will remain connected to storage and the network of the VM. I can also 2 (one at a time) 8024 switch K to shoot, and servers will be connected for the storage and the network of the VM. However, when I unplug one of the 7048 s 2, or the other, I lose the storage and access to the VM network, these all the network goes down. There is a lag configured for the uplink of the 7048 to a Meraki switch, so I should be able to always pass traffic, but the network is down.

  Attached are the configs of switch and a Visio diagram, I hope that someone can choose the problem immediately. My goal is a total redundancy, so when I lose a 7048 network remains standing. Thanks in advance!

  I try to activate the transfer non-stop on the battery and test it again. Nonstop forwarding allows transfer of battery units plan to continue to transmit packets while the control and management of aircraft restart after a power failure, hardware failure or the software on the management of battery unit.

  Console (config) #nsf

• Licenses for Windows 7 Pro on a redundant "Server"

  I support for a local dental practice (~ 12 workstations) and, recently, their waiter, who was 10 years old dies and we moved on to a more recent machine. Because of the dental software they use, there are restrictions on this operating system, they can use. Therefore, because it is not in a domain configuration, we ran Windows 7 Pro on all machines. In order to avoid the 2-3 days of chaos, if the server is down, I want to put up with a redundant server (same hardware, same o/s, same configuration, always enabled for database backups can be loaded on it).

  • Is it possible to run this server in the license limit without buying an additional license of W7?

  I am aware that there are other ways around this problem. However, given that this will be a server that can be installed immediately in case of failure of the system on the primary server, I want to avoid potential problems when you connect to this hot spare in their network.

  All advice is appreciated.

  Best regards

  Basically, what you create is a backup domain controller. Which version of Windows Server is currently on the machine?

  You could create configure Windows Server as a member server, if the PDC fails, users can still access the network and services on the backup authentication log ons member server.

• I presume that the motherboard is the cause of the failure of the video card on my alienware aurora desktop. Where can I buy a motherboard for this system?

  HI: Blues ray and dvd drives work. I checked the raid drives, test of redundancy having failed, too bad sectors. I presume that the motherboard is defective in this case for the video card failure. I see some white corrosion around the battery from the motherboard. I put other work disk drives into the slots on the drive. Where can I buy or upgrade the motherboard for this system? Thank you.

  The network cable is not shining, which confirms that the motherboard does not work.

• Map system PS1 PG failure of voltage is outside the range

  System model PowerEdge R720

  Revision of the system I have
  BIOS version
  1.6.0
  Firmware version
  1.40.40 (build 17)
  The lifecycle controller firmware
  1.1.5.165
  Version of the Firmware IDSDM
  N/A

   

   

  JOURNAL OF THE IDRAC

  Map system PS1 PG failure of voltage is outside the range.

  The food temperature 1 is outside the range.
  Power supply 1: status = 0x200c, IOUT = 0 x 0, VOUT = 0 x 0, TEMP = 0xc0, FAN = 0 0 x, ENTRANCE = 0 x 30
  Power supply 1 is operating normally.

  Tensions

  System Board PS1 PG Fail

  power configuration ,

  No redundant Reduncancy

  primary 1st turn on hot spare

  Thus,.

  -7/24 job server, can I fix this without stopping.

  -Power to POWER block? What should be the configuration of redundancy?

  Kind regards.

  NikolaTesla,

  If the power supply is switchable redundant power supplies hot, you can remove and replace the PS1 while the server is online.

  I suggest also, as best as possible, to plan downtime, update the current server.

  I see you're a few updates on BIOS, iDrac, as well as the lifecycle controller. Now with the BIOS and iDrac being 4 updates back, I suggest clicking on 'Other Versions' on these pages and updates up to current walk.

  Let me know if it helps.

• How moving to redundant ESP on ASR1006?

  It seems that you can failover to the redundant RP by the command "redundancy force-passage to the.

  But what of the ESP?

  How can I switchoever to redundant ESP without waiting on the active blade failure occur?

  I went through several guides configuration, but all they talk about is high availability for SSO and routing protocols.

  Have you tried the command "redundancy force-crossing the fp.

  CARRR01 #sh pla

  Chassis type: ASR1006

  State of Type slot Insert (back)

  --------- ------------------- --------------------- -----------------

  0 ASR1000-SIP10 ok 2w0d

  SPA-5X1GE-V2 0/0 2w0d ok

  1 ASR1000-SIP10 ok 2w0d

  R0 ASR1000-RP2 ok, active 2w0d

  F0 ASR1000-ESP10 ok, active 2w0d

  F1 ASR1000-ESP10 ok, 2w0d eve

  Failure of P0 ASR1006-PWR-AC ch, 2w0d

  P1 ASR1006-PWR-AC 2w0d ok

  Slot CPLD Firmware Version Version

  --------- ------------------- ---------------------------------------

  0 09111601 12.2 XNC (33r)

  1 07091401 12.2 (33r) XN2

  R0 SECOND 10021901 12.2 (33r)

  F0 XNC 07091401 12.2 (33r)

  F1 XNC 07091401 12.2 (33r)

  CARRR01 #red

  CARRR01 #redundancy fo

  CARRR01 #redundancy force-passage?

  fp FP Execute failover

  CARRR01 #redundancy force-crossing the fp

  CARRR01 #redundancy force-crossing the fp?

  CARRR01 #redundancy force-crossing the fp

  Moving forward with transition to the standby FP? [confirm]

  CARRR01 #.

  * 15 sep 03:26:19.147: PARM-6-FP_SB_RELOAD_REQ %: R0/0: Secretariats: reload ensures FP: initiated by passage in the public Service message

  * 15 sep 03:26:19.150: % IOSXE_OIR-6-OFFLINECARD: map (fp) offline in location F0

  * 15 sep 03:26:19.463: PARM-6-FP_HA_STATUS %: R0/0: Secretariats: F1 redundancy State is Active

  CARRR01 #sh platform

  Chassis type: ASR1006

  State of Type slot Insert (back)

  --------- ------------------- --------------------- -----------------

  0 ASR1000-SIP10 ok 2w0d

  SPA-5X1GE-V2 0/0 2w0d ok

  1 ASR1000-SIP10 ok 2w0d

  R0 ASR1000-RP2 ok, active 2w0d

  2w0d start F0 ASR1000-ESP10

  F1 ASR1000-ESP10 ok, active 2w0d

  Failure of P0 ASR1006-PWR-AC ch, 2w0d

  P1 ASR1006-PWR-AC 2w0d ok

  Slot CPLD Firmware Version Version

  --------- ------------------- ---------------------------------------

  0 09111601 12.2 XNC (33r)

  1 07091401 12.2 (33r) XN2

  R0 SECOND 10021901 12.2 (33r)

  F0 XNC 07091401 12.2 (33r)

  F1 XNC 07091401 12.2 (33r)

  * 15 sep 03:27:20.681: % IOSXE_OIR-6-ONLINECARD: online in the F0 slot (fp) map

  CARRR01 #sh platform

  Chassis type: ASR1006

  State of Type slot Insert (back)

  --------- ------------------- --------------------- -----------------

  0 ASR1000-SIP10 ok 2w0d

  SPA-5X1GE-V2 0/0 2w0d ok

  1 ASR1000-SIP10 ok 2w0d

  R0 ASR1000-RP2 ok, active 2w0d

  F0 ASR1000-ESP10 init, 2w0d eve

  F1 ASR1000-ESP10 ok, active 2w0d

  Failure of P0 ASR1006-PWR-AC ch, 2w0d

  P1 ASR1006-PWR-AC 2w0d ok

  Slot CPLD Firmware Version Version

  --------- ------------------- ---------------------------------------

  0 09111601 12.2 XNC (33r)

  1 07091401 12.2 (33r) XN2

  R0 SECOND 10021901 12.2 (33r)

  F0 XNC 07091401 12.2 (33r)

  F1 XNC 07091401 12.2 (33r)

  * 15 sep 03:27:40.740: % CPPHA-7-START: F0: cpp_ha: CPP 0 prepare image/tmp/sw/fp/0/0/fp/mount/usr/CPC/bin/FAQ-ucode-esp10

  * 15 sep 03:27:41.211: % CPPHA-7-START: F0: cpp_ha: RPC starting 0 init image/tmp/sw/fp/0/0/fp/mount/usr/CPC/bin/FAQ-ucode-esp10

  * 15 sep 03:27:46.492: % CPPHA-7-START: F0: cpp_ha: CPP 0 runs init image/tmp/sw/fp/0/0/fp/mount/usr/CPC/bin/FAQ-ucode-esp10

  * 15 sep 03:27:46.763: % CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization complete

  * 15 sep 03:27:48.175: % IOSXE-6-PLATFORM: F0: cpp_cp: CPP_PFILTER_EA_EVENT__API_CALL__REGISTER process

  * 15 sep 03:27:51.358: PARM-6-FP_HA_STATUS %: R0/0: Secretariats: State of redundancy F0 is worm watch | in IOS

  CARRR01 #sh platform

  Chassis type: ASR1006

  State of Type slot Insert (back)

  --------- ------------------- --------------------- -----------------

  0 ASR1000-SIP10 ok 2w0d

  SPA-5X1GE-V2 0/0 2w0d ok

  1 ASR1000-SIP10 ok 2w0d

  R0 ASR1000-RP2 ok, active 2w0d

  F0 ASR1000-ESP10 ok, 2w0d eve

  F1 ASR1000-ESP10 ok, active 2w0d

  Failure of P0 ASR1006-PWR-AC ch, 2w0d

  P1 ASR1006-PWR-AC 2w0d ok

  Slot CPLD Firmware Version Version

  --------- ------------------- ---------------------------------------

  0 09111601 12.2 XNC (33r)

  1 07091401 12.2 (33r) XN2

  R0 SECOND 10021901 12.2 (33r)

  F0 XNC 07091401 12.2 (33r)

  F1 XNC 07091401 12.2 (33r)