제2의 비엔지니어 인생관을 꿈꾸며

Posted
Filed under Study

https://social.technet.microsoft.com/Forums/

https://chinnychukwudozie.com/


Cluster network name resource ‘Cluster Name’ failed registration of one or more associated DNS name(s) for the following reason:
The handle is invalid. Select your cluster name on the top left pane of the Failover Cluster Manager.

The error was obviously related to DNS in some way. I still couldn’t figure out the cause though. After digging around for a while, I came up with the following steps that have so far helped me resolve the problem.

Open the Failover Cluster Manager Console.

In the center panel, go down to “Cluster Core Resources”.

Right-click your Cluster name and select the “More actions” drop down option.

I selected the “Simulate Failure” option.

After the Cluster Object goes offline, right-click the Cluster Name again, “More actions” and select “Repair”.

Still the DNS status was still “Invalid” .
For a second time, I went ahead and did a right-click on the Cluster name object again.

This time I selected the “Take Offline” option.

After the Cluster Object went offline, I did a right-click on the Cluster Name, “More actions” and selected the “Repair” option.

This time, the DNS status changed to “OK” after the Cluster name “Repair” action.

사용자 삽입 이미지

MSCS 환경에서 언제부터인가 DNS 등록실패 이벤트가 발생하고 클러스터 서버이름에서는 DNS 핸들 오류로 실시간 마이그레이션이 되지 않는 상황이 발생하였었습니다. 커버로스 인증도 안된다고 하고 윈도우가 깨졌나 싶은 이상한 상황이였습니다.

클러스터 네트워크 이름 리소스 '클러스터 이름'이(가) 이 노드에서 네트워크 이름을 사용하도록 설정하는 동안 오류가 발생했습니다. 오류의 원인:
 'Unable to obtain a logon token'.

 오류 코드는 '1326'입니다.

 네트워크 이름 리소스를 오프라인 상태로 만들었다가 다시 온라인 상태로 설정하여 다시 시도할 수 있습니다.

이벤트 1228 오류도 발생하고

다음과 같은 이유로 클러스터 네트워크 이름 리소스 '클러스터 이름'이(가) 하나 이상의 연결된 DNS 이름을 등록하지 못했습니다.
핸들이 잘못되었습니다.

종속 IP 주소 리소스와 연결된 네트워크 어댑터가 하나 이상의 DNS 서버에 액세스하도록 구성되어 있는지 확인하십시오.

이벤트 1196 도 발생하게 됩니다.

클러스터 코어 리소스의 서버이름의 네트워크 리소스를 오프라인 시켜놓구 추가작업에서 복구를 진행하면 이벤트 오류가 발생되던게 멈추고 클러스터 노드이동 작업을 문제없이 진행할수가 있습니다.

2017/01/15 04:09 2017/01/15 04:09
Posted
Filed under Study

Get-Cluster -Name HVCLUSTER.domain.local | select ClusterFunctionalLevel

Windows server 2012 R2 에서는 레벨이 8입니다. Windows Server 2016 및 Hyper-V Server 2016 Core 를 설치하고 나서 2012 R2 클러스터 그룹에 가입이 되지만 가입되는 동시에 클러스터 관리도구가 2012 R2에서는 버젼문제로 접근할수 없게됩니다. 그러면 2016이나 Windows 10 RSAT로 클러스터관리도구를 사용해야되며  기존 2012 R2 노드들은 드레이닝으로 각 가상화 컴퓨터들을 다른노드로 이전하고 노드삭제하고 2016 설치하고 재가입 시키는 수순으로 진행하면 별무리가 없습니다.
전부 2016으로 설치가 완료되고 클러스터 그룹에 가입이 완료되면 클러스터 레벨을 업그레이드 시켜줍니다.

Get-Cluster -Name HVCLUSTER.domain.local | update-ClusterFunctionalLevel
레벨수준이 8에서 9로 업그레이드가 완료됩니다.

사용자 삽입 이미지

업그레이드가 완료되면 2012에서 보이지 않던 클러스터 인프라 리소스가 추가된것을 확인할수가 있습니다.



2017/01/09 09:23 2017/01/09 09:23
Posted
Filed under Study


https://blogs.technet.microsoft.com/askpfeplat/2012/12/09/why-adding-hyper-v-replica-connection-broker-fails-in-failover-cluster-manager/
사용자 삽입 이미지

MSCS 환경에서 복제본 브로커 등록할때 실패가 떨어지는 경우가 간혹 있습니다.
사용자 삽입 이미지

수동으로 복제본 브로커 컴퓨터 개체를 만들고 속성에 보안탭에 MSCS 클러스터 컴퓨터 개체를 등록해주고 풀권한을 주고 확인을 주면 해결이 됩니다.
사용자 삽입 이미지
이방법은 복제본 브로커 등록 실패뿐만이 아니고 MSSQL 사전설치 DTC 구성시에도 등록실패가 발생하는 경우도 간혹 있습니다. 이와 같은 방법으로 클러스터 컴퓨터 개체의 권한을 등록시켜줘서 자동으로 업데이트 되게 하는 방법이 있습니다.
위에 링크에는 두번째 방법  특정권한을 위임해주는 방법도 존재합니다만 전 첫번째 옵션 방법이 단번에 해결되어서 두번째 방법까지 쓸 경우가 없었습니다.
2017/01/08 04:02 2017/01/08 04:02
Posted
Filed under Study
USE master
GO
IF OBJECT_ID ('sp_hexadecimal') IS NOT NULL
  DROP PROCEDURE sp_hexadecimal
GO
CREATE PROCEDURE sp_hexadecimal
    @binvalue varbinary(256),
    @hexvalue varchar (514) OUTPUT
AS
DECLARE @charvalue varchar (514)
DECLARE @i int
DECLARE @length int
DECLARE @hexstring char(16)
SELECT @charvalue = '0x'
SELECT @i = 1
SELECT @length = DATALENGTH (@binvalue)
SELECT @hexstring = '0123456789ABCDEF'
WHILE (@i <= @length)
BEGIN
  DECLARE @tempint int
  DECLARE @firstint int
  DECLARE @secondint int
  SELECT @tempint = CONVERT(int, SUBSTRING(@binvalue,@i,1))
  SELECT @firstint = FLOOR(@tempint/16)
  SELECT @secondint = @tempint - (@firstint*16)
  SELECT @charvalue = @charvalue +
    SUBSTRING(@hexstring, @firstint+1, 1) +
    SUBSTRING(@hexstring, @secondint+1, 1)
  SELECT @i = @i + 1
END

SELECT @hexvalue = @charvalue
GO

IF OBJECT_ID ('sp_help_revlogin') IS NOT NULL
  DROP PROCEDURE sp_help_revlogin
GO
CREATE PROCEDURE sp_help_revlogin @login_name sysname = NULL AS
DECLARE @name sysname
DECLARE @type varchar (1)
DECLARE @hasaccess int
DECLARE @denylogin int
DECLARE @is_disabled int
DECLARE @PWD_varbinary  varbinary (256)
DECLARE @PWD_string  varchar (514)
DECLARE @SID_varbinary varbinary (85)
DECLARE @SID_string varchar (514)
DECLARE @tmpstr  varchar (1024)
DECLARE @is_policy_checked varchar (3)
DECLARE @is_expiration_checked varchar (3)

DECLARE @defaultdb sysname

IF (@login_name IS NULL)
  DECLARE login_curs CURSOR FOR

      SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
      ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name <> 'sa'
ELSE
  DECLARE login_curs CURSOR FOR


      SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
      ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name = @login_name
OPEN login_curs

FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin
IF (@@fetch_status = -1)
BEGIN
  PRINT 'No login(s) found.'
  CLOSE login_curs
  DEALLOCATE login_curs
  RETURN -1
END
SET @tmpstr = '/* sp_help_revlogin script '
PRINT @tmpstr
SET @tmpstr = '** Generated ' + CONVERT (varchar, GETDATE()) + ' on ' + @@SERVERNAME + ' */'
PRINT @tmpstr
PRINT ''
WHILE (@@fetch_status <> -1)
BEGIN
  IF (@@fetch_status <> -2)
  BEGIN
    PRINT ''
    SET @tmpstr = '-- Login: ' + @name
    PRINT @tmpstr
    IF (@type IN ( 'G', 'U'))
    BEGIN -- NT authenticated account/group

      SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' FROM WINDOWS WITH DEFAULT_DATABASE = [' + @defaultdb + ']'
    END
    ELSE BEGIN -- SQL Server authentication
        -- obtain password and sid
            SET @PWD_varbinary = CAST( LOGINPROPERTY( @name, 'PasswordHash' ) AS varbinary (256) )
        EXEC sp_hexadecimal @PWD_varbinary, @PWD_string OUT
        EXEC sp_hexadecimal @SID_varbinary,@SID_string OUT

        -- obtain password policy state
        SELECT @is_policy_checked = CASE is_policy_checked WHEN 1 THEN 'ON' WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name = @name
        SELECT @is_expiration_checked = CASE is_expiration_checked WHEN 1 THEN 'ON' WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name = @name

            SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' WITH PASSWORD = ' + @PWD_string + ' HASHED, SID = ' + @SID_string + ', DEFAULT_DATABASE = [' + @defaultdb + ']'

        IF ( @is_policy_checked IS NOT NULL )
        BEGIN
          SET @tmpstr = @tmpstr + ', CHECK_POLICY = ' + @is_policy_checked
        END
        IF ( @is_expiration_checked IS NOT NULL )
        BEGIN
          SET @tmpstr = @tmpstr + ', CHECK_EXPIRATION = ' + @is_expiration_checked
        END
    END
    IF (@denylogin = 1)
    BEGIN -- login is denied access
      SET @tmpstr = @tmpstr + '; DENY CONNECT SQL TO ' + QUOTENAME( @name )
    END
    ELSE IF (@hasaccess = 0)
    BEGIN -- login exists but does not have access
      SET @tmpstr = @tmpstr + '; REVOKE CONNECT SQL TO ' + QUOTENAME( @name )
    END
    IF (@is_disabled = 1)
    BEGIN -- login is disabled
      SET @tmpstr = @tmpstr + '; ALTER LOGIN ' + QUOTENAME( @name ) + ' DISABLE'
    END
    PRINT @tmpstr
  END

  FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin
   END
CLOSE login_curs
DEALLOCATE login_curs
RETURN 0
GO

다음단계 master db 에서 쿼리창 열고
EXEC sp_help_revlogin
을 실행시키면 각계정마다 아래와 같이 출력이 됩니다.
CREATE LOGIN [Test] WITH PASSWORD = '', SID = 0x90FD605DCEFAE14FAB4D5EB0BBA1AECC, DEFAULT_DATABASE = [master], CHECK_POLICY = ON, CHECK_EXPIRATION = OFF

필자가 해본결과로는 조금 틀리게 나오는데 MSSQL버젼때문인지는 몰라도
-- Login: testuser
CREATE LOGIN [testuser] WITH PASSWORD = 0x020022FB4795F3FE36F30074E97A9F2C8A37775119EEDF6E29AF05D3B8E2C7959EB7190
D8DF8A57826541AF213ACAFB1B0BEE4A475568D4DFE5DA626C1451D6D09B08F9E3E8F HASHED, SID = 0x2086C2394C37AE4D9A175731783AFE77, DEFAULT_DATABASE = [testDB], CHECK_POLICY = OFF, CHECK_EXPIRATION = OFF
암호해쉬 와 정책 및 만료체크를 사용안함으로 추가가 되었습니다. 아마도 기본값이 암호 및 정책이 되어 있으면 복원하자마자 잠김상태가 되는거기때문에 이렇게 다르게 나오나봅니다.

2016/12/27 16:20 2016/12/27 16:20
Posted
Filed under Study
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033250

Purpose

In the majority of environments, you must not change VMware High Availability (HA) default settings. However, depending on your specific environment, you must modify some HA options.

This article describes the different configuration options available and how to apply them.

Resolution

Note: Not all configuration variables work in all versions of vCenter Server. As new variables are introduced in newer releases, they remain throughout later versions.

Applying a VMware HA customization

Using the vSphere Web Client

  1. Log in to VMware vSphere Web Client.
  2. Go to Home > vCenter > Clusters.
  3. Under Object, click on the cluster you want to modify.
  4. Click Manage.
  5. Click vSphere HA.
  6. Click Edit.
  7. Click Advanced Options.
  8. Click Add and enter in Option and Value fields as appropriate (see below).
  9. Deselect Turn ON vSphere HA.
  10. Click OK.
  11. Wait for HA to unconfigure, click Edit and check Turn ON vSphere HA.
  12. Click OK and wait for the cluster to reconfigure.
Using the vSphere Client
  1. Log in to vCenter Server with vSphere Client as an administrator.
  2. Right-click the Cluster in the Inventory and click Edit Settings.
  3. Click VMware HA.
  4. Click Advanced Options.
  5. Enter Option and Value fields as appropriate (see below).
  6. Click OK.
  7. Click OK again.
  8. Wait for the Reconfigure Cluster task to complete and right-click the Cluster again from the Inventory.
  9. Click Properties.
  10. Disable VMware HA and wait for the Reconfiguration Cluster task(s) to complete.
  11. Right-click the cluster and Enable VMware HA to have the settings take effect.

    Note: See below if reconfiguration of the hosts is necessary.

There are three types of HA advanced options and each is set in a different way.

  • vCenter Server options (VC) -- these options are configured at the vCenter Server level and apply to all HA clusters unless overridden by cluster-specific options in cases where such options exist. If the vCenter Server options are configured using the vCenter Server options manager, a vCenter Server restart may not be required -- see the specific options for details. But if these options are configured by adding the option string to the vpxd.cfg file (as a child of the config/vpxd/das tag), a restart is required.
  • Cluster options (cluster) -- these options are configured for an individual cluster and if they impact the behavior of the HA Agent (FDM), they apply to all instances of FDM in that cluster. These options are configured by using the HA cluster-level advanced options mechanism, either via the UI or the API. Options with names starting with "das.config." can also be applied using the "fdm options" mechanism below, but this is not recommended because the options should be equally applied to all FDM instances.
  • fdm options (fdm) -- these options are configured for an individual FDM instance on a host. They are configured by adding the option to the/etc/opt/vmware/fdm/fdm.cfg file of the host as a child of the config/fdm tag. Options set in this way are lost when fdm is uninstalled (for example if the host is removed from vCenter Server and then re-added) or if the host is managed by Auto Deploy and is rebooted.

Common Options

Version

Name

Description

Reconfiguration

Type of Option

Cluster Configuration

5.0, 5.1, 5.5

das.allowNetworkX

Allows you to specify the specific management networks used by HA, where X is a number between 0 and 9. For example if you set a value to ʺManagement Networkʺ, only the networks associated with port groups having this name are used. Ensure that all hosts are configured with the named port group and the networks are compatible. In 5.5, this option is ignored if vSAN is enabled for the cluster.

Yes. Reconfigure HA on all hosts to have the specification take effect.

Cluster

5.0, 5.1, 5.5

das.ignoreRedundantNetWarning

HA will report a config issue on a host if the host is not configured with redundant networks for the networks used by HA. Prior to 5.5, HA only uses management networks, while in 5.5, if vSAN is enabled, HA will use the networks configured for vSAN. Valid values are true/false. Set to true to suppress the config issue. False is assumed if the option is not set. 

Yes. Reconfigure HA on a host to have the config issue for that host cleared.

Cluster

5.0, 5.1, 5.5, 6.0

das.heartbeatDsPerHost

HA chooses by default 2 heartbeat datastores for each host in an HA cluster. This option can be used to increase the number to a value in the range of 2 to 5 inclusive.

Yes. Reconfigure HA on all hosts in the cluster.

Cluster

5.0, 5.1, 5.5, 6.0

das.ignoreInsufficientHbDatastore

HA will report a host config issue if it was not able to select the required number of datastores for a host given by das.heartbeatDsPerHost. Set this option to true to suppress this warning, and false to enable it. A value of false is assumed if the option is not set.

Yes. Reconfigure HA on all hosts in the cluster.

Cluster

5.0, 5.1, 5.5

das.includeFTcomplianceChecks

Whether to check the cluster for compliance with Fault Tolerance as part of the cluster profile compliance check. Set this option to false if you don't plan to use FT in the cluster. A value of true enables the checks. If unset, a value of true is assumed.

No

Cluster

5.5 U3 vpxd.das.fdmWaitForUpdatesTimeoutSec Timeout period for which HA waits for a response from the FDM master node.

Note:  This setting needs to be applied from the vCenter Server Advanced Settings.  For more information. see the Configure Advanced Settings in the vSphere Web Client section of the vCenter Server and Host Management guide.
Yes,  vCenter Server needs to be restarted. VC

Admission Control

5.0, 5.1, 5.5

das.vmMemoryMinMB

Value in MB to use for the memory reservation of a virtual machine if no non-zero memory reservation is set by a user. 0 is assumed if the option is not set.

No

Cluster

5.0, 5.1, 5.5

das.vmCpuMinMHz

Value in MHz to use for the CPU reservation of a virtual machine if no non-zero CPU reservation are set by a user. 32 is assumed if the option is not set.

No

Cluster

5.0, 5.1, 5.5, 6.0

das.slotCpuInMHz

Maximum value in MHz to use for CPU component of the slot size. No limit is imposed if the option is not set. In 5.1, the CPU component of the slot size can be exactly specified in the UI and the API (see the vim.cluster.slotPolicy object). Note that this option and the UI/API behave differently -- this option sets a max while the UI/API sets the exact value. If a slot policy is defined and this option is specified, the value specified by this option is ignored.

No

Cluster

5.0, 5.1, 5.5, 6.0

das.slotMemInMB

Maximum value in MB to use for memory component of the slot size. No limit is imposed if the option is not set. In 5.1, the memory component of the slot size can be exactly specified in the UI and the API (see the vim.cluster.slotPolicy object). Note that this option and the UI/API behave differently -- this option sets a max while the UI/API sets the exact value. If a slot policy is defined and this option is specified, the value specified by this option is ignored.

No

Cluster

6.0 das.config.fdm.memreservationmb  By default vSphere HA agents run with a configured memory limit of 250 MB. A host might not allow this reservation if it runs out of reservable capacity. You can use this advanced option to lower the memory limit to avoid this issue. Only integers greater than 100, which is the minimum value, can be specified. Conversely, to prevent problems during master agent elections in a large cluster (containing 6,000 to 8,000 VMs) you should raise this limit to 325 MB.

Note: Once this limit is changed, for all hosts in the cluster you must run the Reconfigure HA task. Also, when a new host is added to the cluster or an existing host is rebooted, this task should be performed on those hosts in order to update this memory setting.
No Cluster

Restarting virtual machines

5.0, 5.1, 5.5

das.maxvmrestartcount

The maximum number of times an FDM master will try to restart a virtual machine before giving up. Five attempts are made if this option is unset. This limit only applies if the time since the first restart attempt was made is less than das.maxvmrestartperiod. Note that FT secondary virtual machine restarts are governed by the separate parameter, das.maxftvmrestartcount.
Warning: Setting this value to a very high number creates a large amount of extra logging which can have an impact on your system log directories.

No

Cluster

5.0, 5.1, 5.5

das.maxvmrestartperiod

The maximum amount of time (in seconds) during which a FDM master will attempt to restart a virtual machine after the first restart attempt failed. The time is measured from when the FDM master first tried to restart the virtual machine. This time limit takes precedence over das.maxvmrestartcount. No time limit is imposed if this option is unset.

No

Cluster

5.0, 5.1, 5.5

das.maxftvmrestartcount

The maximum number of times an FDM master will try to start a secondary virtual machine for an FT virtual machine pair before giving up. Five attempts are made if this option is unset.
Warning: Setting this value to a very high number creates a large amount of extra logging which can have an impact on your system log directories

No

Cluster

5.0U1, 5.1, 5.5

das.maskCleanShutdownEnabled

When a virtual machine powers off and its home datastore is not accessible, HA cannot determine whether the virtual machine should be restarted. So, it must make a decision. If this option is set to false, the responding FDM master will assume the virtual machine should not be restarted, while if this option is set to true, the responding FDM will assume the virtual machine should be restarted. If the option is unset in 5.0U1, a value of false is assumed, whereas in ESXi 5.1 and later, a value of true is assumed.

No

Cluster

5.5, 6.0 das.respectVmVmAntiAffinityRules Respect vm-vm anti-affinity rules when restarting virtual machines after a failure. The valid values are "false" (default) and "true" No Cluster
6.0 das.maxresets The maximum number of reset attempts made by VMCP. If a reset operation on a virtual machine affected by an APD situation fails, VMCP retries the reset this many times before giving up. No Cluster
6.0 das.maxterminates The maximum number of retries made by VMCP for virtual machine termination. No Cluster
6.0 das.terminateretryintervalsec If VMCP fails to terminate a virtual machine, this is the number of seconds the system waits before it retries a terminate attempt. No Cluster
6.0 das.reregisterRestartDisabledVMs
When vSphere HA is disabled on a specific virtual machine this option
ensures that the virtual machine is registered on another host after a
failure. This allows you to power-on that virtual machine without
needing to re-register it manually.
Note: When this option is used, vSphere HA does not
power on the virtual machine, but only registers it.
No Cluster

Isolation Response

5.0, 5.1, 5.5, 6.0

das.isolationAddressX

IP addresses an FDM agent uses to check for isolation when no agent network traffic is observed on the network(*) used by HA, where X = 0-9. HA will use the default management-network gateway as an isolation address by default plus those specified by this advanced option as additional addresses to check. We recommend adding an isolation address for each management network used by HA.(*) Prior to 5.5, HA uses only the management network, but in 5.5 when vSAN is also enabled on the cluster, HA will use the vSAN network for inter-agent communication.

No

Cluster

5.0, 5.1, 5.5, 6.0

das.useDefaultIsolationAddress

Whether the default isolation address (gateway of management network) should be used when determining if a host is network isolated. Valid values are true/false. By default, the management network default gateway is used. If the default gateway is a non-pingable address, set the “das.isolationaddressX” to a pingable address and disable the usage of the default gateway by setting this option to “false”.

No

Cluster

5.1, 5.5, 6.0

das.config.fdm.isolationPolicyDelaySec

The number of seconds an FDM agent waits before executing the isolation policy once it has determined that the host is isolated. The minimum value is 30. If set to a value less than 30, the delay is 30 seconds.

No

Cluster

5.0, 5.1, 5.5, 6.0

das.isolationShutdownTimeout

The number of seconds an FDM waits for a virtual machine to power off after initiating a guest shutdown before the FDM issues a power off. If the option is unset, 300s is used.

No

Cluster

6.0 das.config.fdm.reportfailoverfailevent When set to 1, enables generation of a detailed per-VM event when an attempt by vSphere HA to restart a virtual machine is unsuccessful. Default value is 0. In versions earlier than vSphere 6.0, this event is generated by default. No Cluster

Virtual machine/App Monitoring

5.0, 5.1, 5.5, 6.0

das.iostatsInterval

If an FDM detects that a sufficient number of VMtools heartbeats are missing to trigger a virtual machine's configured virtual machine/App monitoring policy, the FDM checks if any I/O have been issued in the last ioStatsInterval, and will only reset the virtual machine if no I/O occurred in this interval. Values of 0 or greater are valid. 120s is assumed if the option is unset.

No

Cluster

Fault Tolerance

5.0, 5.1, 5.5

das.maxFtVmsPerHost

Specifies the number of Fault Tolerance virtual machines that can be run on a host at one time. If unset, a value of 4 is used. A value of -1 or 0 disables the limit. The limit is enforced by vCenter Server when executing user initiated power ons and vmotions, and by DRS when doing initial placement and load balancing. HA does not enforce this limit to maximize uptime. DRS does not correct any violations of this limit.

No

Cluster

Logging

5.0, 5.1, 5.5

das.config.log.maxFileNum

Controls the number of FDM log-file rotations retained by the FDM file-based logger. The file-based logger is used by default only by the FDM when running on ESX versions earlier than ESX 5.0. If you wish to change the number of log-file rotations maintained for a pre ESX 5.0 host, set this option to the desired number of log files. For ESX 5.0 and later hosts, the FDM logs to syslog by default and so you need to use the syslog configuration mechanism to change the amount of retained logging history. However, it is possible to enable the file-based logger for ESXi 5.0 and later hosts hosts also. To do so, set this option to a valid value. If you are using vSphere 5.0 Update 1 or later, you must also set the option das.config.log.outputToFiles to true. For all ESX versions, setting the option das.config.log.maxFileNum to 1 will disable the log-file rotations. The location of log files can be changed using the option das.config.log.directory.

Yes

Cluster

5.0, 5.1, 5.5

das.config.log.maxFileSize

Controls the size of each log file written out by the FDM file-based logger. Files are 1 MB in size unless this option is specified. This option is used in conjunction with das.config.log.maxFileNum to control the log history.

Yes

Cluster

5.0, 5.1, 5.5

das.config.log.level

Controls the amount of information recorded in the logs based on severity levels None, Warning, Info, Verbose, and Trivia.

Yes

Cluster

 

2016/12/10 00:36 2016/12/10 00:36