Maintenance Mode Questions

Hi All,
I have SCOM 2012 SP1 CU5 and have few questions on Maintenance Mode (MM).
1) I put my 800 agents in MM for 300 minutes and they get into "Not Monitored" state. When I pull all these 800 agents out of MM together they remain in "Not Monitored" state for about 2 to 3 hours. They get into healthy state slowly
during these 3 hours. Is this expected? Shouldn't they all get healthy quickly? Is the number of agents slows the process and so they take time to get into Healthy State?
2) When I pull my agents out of MM and after they get healthy, I get flood of alerts for them like Health service heartbeat failure, failed to connect to computer., low free disk space, etc. Why is this so as they were in MM and not healthy?
3) When the servers come out of MM, will all the workflows (rules and monitors) run again and generate alerts? even if their alerts (previously created) are already Active in SCOM ?
4) While rebooting the SCOM servers during maintenance activity, what should be the sequence among Management Servers, DB server, DW Server, Reporting Server, Gateway Servers, Web console servers ?
Thanks, S K Agrawal

1) For agent "not monitor" after MM, Try to restarting the System Center Management Health service on the agent-managed computer
2) For What to do for a not monitored state, you can refer below link
http://technet.microsoft.com/en-us/library/hh212723.aspx
3) Yes, after server come out from maintenance mode, it will generate alerts and work normal.
4) Sequence will be DB server, DW Server, Management server, Reporting server, Gateway server, web console Server.
Also you can refer below link for more info.
http://support.microsoft.com/kb/2704170/en-us
http://support.microsoft.com/kb/942866/en-us
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Similar Messages

Warning: The system has not been taken off maintenance mode completely

After I enabled Maintenance mode using adadmin, I ran Compile Flexfields. Then I disabled Maintenance mode. But, on the 11i login page, I keep getting a warning message:
Warning
The system has not been taken off maintenance mode completely. Please contact your System Administrator.
I am sure I disabled the Maintenance mode in adadmin. Why I still get the warning? How to fix it? Thanks a lot.

Thanks a lot. That is the fix.
One more question. After I ran "Compile Flexfields", I got
Number of successful descriptive flex compilations : 7520
Number of failed descriptive flex compilations : 1
How can I find the failed description flex? The log does not give info on this. And, how to fix it?
Thanks a lot for your help.

Redirect users to page when we take system in maintenance mode.

I would like to redirect users to page when we take system in maintenance mode. We are on 12.1.3 application. please provide me document which have these details

Please see old threads which discuss the same topic.
http://forums.oracle.com/forums/search.jspa?threadID=&q=Redirect+AND+Maintenance&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
http://forums.oracle.com/forums/search.jspa?threadID=&q=Maintenance+AND+Message&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
http://forums.oracle.com/forums/search.jspa?threadID=&q=Outage+AND+Maintenance&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Please search the forum before posting similar questions.
Thanks,
Hussein

SQL Query for maintenance mode in SCOM

Hi all
I was wondering if I can find a query about this request:
- Found all the Servers that were restart without the maintenance mode were actived ?
It's to make a Report To include in Reporting Services.
sorry for my English :)
Thank you very much and have a good day

Your question seems related to SCOM. SCOM may use SQL Server, but to answer the question, I guess one needs to know SCOM, so maybe you should try a forum for that product? I found
http://social.technet.microsoft.com/Forums/systemcenter/en-US/home?forum=operationsmanagergeneral
Erland Sommarskog, SQL Server MVP, [email protected]

Maintenance Mode For One Monitor

Is it possible to place one monitor in maintenance mode? Not the entire computer or object, but just that one monitor? I don't want other monitors for that object to be silenced though.

Hi,
A Windows Schedule task,
http://technet.microsoft.com/en-us/library/cc748993.aspx
Please read this one:
Management Pack for the SCOM 2012 Maintenance Mode Scheduler
http://blog.tyang.org/2014/05/22/management-pack-scom-2012-maintenance-mode-scheduler/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

"Cluster maintenance mode" script to keep cluster names in MM when nodes are placed in MM

Hello All,
Thanks in advance,
is there any script to keep the cluster names in Maintenance Mode when nodes are placed in Maintenance Mode
Best Regards...
Nikhil GS

You can refer below link
http://blogs.msdn.com/b/mariussutara/archive/2008/09/05/cluster-and-maintenance-mode.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

SCOM 2012 Maintenance Mode PowerShell Script Problems

I've seen other questions about this topic before, but none of them seem to address my specific problem, so I am starting a new thread.
I am writing a script to put a single server (not a group) into maintenance mode.   Here is the command that it ultimately tries to call:
Start-SCOMMaintenanceMode-Instance$Instance-EndTime$EndTime-Reason$Reason-Comment$Comment
So an exmaple would look like this:
Start-SCOMMaintenanceMode -Instance "$Instance -EndTime "02/03/2014 15:26:00" -Reason "PlannedOther" -Comment "Testing Maintenance Mode"
When my script tries to run this command, this is the error message that I get:
Start-SCOMMaintenanceMode : Start time must be before end time for maintenance mode.
Parameter name: startTime
At C:\users\x036036\Desktop\Start-SCOMMaintenanceModeForServer.ps1:143 char:21
+                     Start-SCOMMaintenanceMode -Instance $Instance -EndTime $EndT ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Microsoft.Syste...anceModeCommand:StartSCMaintenanceModeCommand) [Start-SCOMMaintenance
   Mode], ArgumentOutOfRangeException
    + FullyQualifiedErrorId : ExecutionError,Microsoft.SystemCenter.OperationsManagerV10.Commands.StartSCMaintenanceModeCommand
I've tried to look at Start-SCOMMaintenanceMode help online, but I don't see that "startTime" is a parameter. So what is this error message talking about? What am I missing?

Thanks for your help.   I didn't see your response until just now, but I have been playing around with this all since my last response.   I got it to work. I wish I could pinpoint what exactly I changed to get it to work, but I
feel like I've been changing so much stuff that I'm not sure any more.
Just in case anyone finds it useful, here is the code.
[CmdletBinding(SupportsShouldProcess=$true)]
param
[Parameter(Mandatory=$True,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='What is the server you want to put in Maintenance Mode?')]
[Alias("Server")]
[string[]]$ServerName,
[Parameter(Mandatory=$True,
ValueFromPipeline=$false,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Specifies the time the maintenance will end. The minimum amount of time a resource can be in maintenance mode is 5 minutes. This is a required parameter. Format is 1/29/2014 8:59:26 AM')]
[Datetime]$end,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='PlannedOther, UnplannedOther, PlannedHardwareMaintenance, UnplannedHardwareMaintenance, PlannedHardwareInstallation, UnplannedHardwareInstallation, PlannedOperatingSystemReconfiguration, UnplannedOperatingSystemReconfiguration, PlannedApplicationMaintenance, ApplicationInstallation, ApplicationUnresponsive, ApplicationUnstable, SecurityIssue, LossOfNetworkConnectivity')]
[string]$Reason,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Allows you to type a comment about the maintenance activity.')]
[string]$Comment,
[switch]$EventLog
set-strictmode -version latest
#$start=Get-Date
#$currentlog = $start.ToString()
Write-Verbose "Starting $($myinvocation.mycommand)"
Write-Verbose "Ready to put ServerName $ServerName in Maintenance Mode"
Function Start-SCOMMaintenanceModeForServer
[CmdletBinding(SupportsShouldProcess=$true)]
param
[Parameter(Mandatory=$True,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='What is the server you want to put in Maintenance Mode?')]
[Alias("Server")]
[string[]]$ServerName,
[Parameter(Mandatory=$True,
ValueFromPipeline=$false,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Specifies the time the maintenance will end. The minimum amount of time a resource can be in maintenance mode is 5 minutes. This is a required parameter. Format is 1/29/2014 8:59:26 AM')]
[Datetime]$end,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='PlannedOther, UnplannedOther, PlannedHardwareMaintenance, UnplannedHardwareMaintenance, PlannedHardwareInstallation, UnplannedHardwareInstallation, PlannedOperatingSystemReconfiguration, UnplannedOperatingSystemReconfiguration, PlannedApplicationMaintenance, ApplicationInstallation, ApplicationUnresponsive, ApplicationUnstable, SecurityIssue, LossOfNetworkConnectivity')]
[string]$Reason,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Allows you to type a comment about the maintenance activity.')]
[string]$Comment,
[switch]$EventLog
Begin
Write-Verbose "Starting Function Start-SCOMMaintenanceModeForServer"
#Check for minumum Maintenance mode period of 5 mins.
$start = Get-Date
$5MinFromNowTime = $start.AddMinutes(5)
#$end = [datetime]$end
$end = $end.AddSeconds(5)
if($end -lt $5MinFromNowTime)
Write-Error "The time span for the maintenance mode should be at least 5 minutes." -ErrorAction Stop
Write-Verbose "Following server will be put in Maintenance Mode: $ServerName"
$MSs = Get-SCOMManagementServer
} #End Begin
Process
Write-Verbose "Checking if server $ServerName is a Management Server"
#Write-Verbose ($MSs | Select DisplayName)
if(($MSs | Select DisplayName) -eq $ServerName)
Write-Verbose "We don't want to put a Management Server in Maintenance Mode. Skipping"
else
Write-Verbose "Let's put server $ServerName in Maintenance Mode"
$Instance = Get-SCOMClassInstance -Name $ServerName
if ($PSCmdlet.ShouldProcess("Putting $ServerName in Maintenance Mode until $($end).") )
Write-Verbose ("Start-SCOMMaintenanceMode -Instance " + $Instance + " -EndTime " + $end + " -Reason " + $Reason + " -Comment " + $Comment)
Start-SCOMMaintenanceMode -Instance $Instance -end $end -Reason $Reason -Comment $Comment
}#End of whatif
}#End of else
if ($PSBoundParameters['EventLog'])
write-eventlog -LogName "Operations Manager" -Source "OpsMgr SDK Service" -EventID 999 -message "The following Objects are put into in Maintenance Mode until $($end) : $($ServerName)"
}#End if
} #End Process
End
Write-Verbose "Finished Function Start-SCOMMaintenanceModeForServer Function"
#Main
try
if ($PSBoundParameters['EventLog'])
write-eventlog -LogName "Operations Manager" -Source "OpsMgr SDK Service" -EventID 998 -message "The $($myinvocation.mycommand) is used to put Objects in Maintenance Mode"
Write-Verbose "Checking if OperationsManager Module is loaded"
#Check if OperationsManager Module is loaded.
if(!(Get-Module OperationsManager))
Write-Verbose "Importing OperationsManager Module"
Import-Module OperationsManager -ErrorAction Stop
Write-Verbose "Checking for OM2012 environment"
#Check if OM2012 is being used.
if(!(Get-Module OperationsManager).Description -eq "Operations Manager OperationsManagerV10 Module")
Write-Error "This script is only for OM2012"
#Call Function
if ($PSBoundParameters['EventLog'])
Start-SCOMMaintenanceModeForServer -ServerName $ServerName -end $end -Reason $Reason -Comment $Comment -EventLog
else
Start-SCOMMaintenanceModeForServer -ServerName $ServerName -end $end -Reason $Reason -Comment $Comment
} #End Try
catch [System.IO.FileNotFoundException]
"OperationsManager Module not found"
$_.Exception.Message
catch
Write-Warning "Oops something went wrong"
$_.Exception.Message
$end=Get-Date
Write-Debug ("Total processing time {0}" -f ($end-$start).ToString())
Write-Verbose "Ending $($myinvocation.mycommand)"
There is one remaining problem with this script.   It does not correctly check to see if something is a management server. We have two management servers. These are the applicable lines, which I still haven't gotten to work yet. First, this retrieves
the list of my Management servers:
$MSs=Get-SCOMManagementServer
Next, these lines are supposed to check if the server I specified is a management server:
if(($MSs | Select DisplayName) -eq $ServerName)
Write-Verbose "We don't want to put a Management Server in Maintenance Mode. Skipping"
Thanks to the Intellisense pop-up deal, I can see that $MSs does get my two management servers. And I can clearly see that there is a DisplayName column. And I can also see that the $ServerName does match what I put in my command line.   But it doesn't
seem to catch them if they are actually equal to each other. I don't know if it's because there's two Management Servers, and it doesn't know how to compare like that? Any idea? Is there some sort of loop I need to write so that it compares is to the DisplayName
for EACH Management Server it finds? Any help would be greatly appreciated.

Another SCOM Maintenance Mode query/advice...

Hi,
Just looking some advice on setting SCOM Maintenance Mode (using SCOM/SCO 2012R2)...
I want to be able to set a server entirely into MaintMode, ie similar to choosing "Selected object AND ALL their contained objects" from SCOM console.
I had asked similar question back in SCOM 2007/Opalis days, but the solution then (placing server and health server watchers separately into maintenance as per Anders blog http://contoso.se/blog/?p=2164 I'm not sure is appropriate now as I believe MaintMode
is handled differently in 2012.
I have seen some pretty complex solutions where using custom built DBs to hold MaintMode status etc. Was hoping theres a neater/simpler soultion using the Orchestrator Activities these days.
If not possible using Native Orchestrator then the fallback would be to try use powershell commandlet. Looking at the Commandlet Examples if I used the following example solution, will that effectively put the server object (and all contained objects
into maintenance which is what I'm trying to achieve.
Windows PowerShell
PS C:\> $Instance = Get-SCOMClassInstance -Name "Server01.Contoso.com"
PS C:\> $Time = ((Get-Date).AddMinutes(10))
PS C:\> Start-SCOMMaintenanceMode -Instance $Instance -EndTime $Time -Comment "Applyin
Any advice to this recurring pain point of SCOM much appreciated.
PS. Not sure if this post is better placed here or in SCOM/Powershell forum so can move if necessary...

Hi Michael,
thanks for your reply confirming the powershell command will work.
I have actually just tried using the native Start Maintenance Mode Activity which actually seems to do as required - if the monitor selected is the relevant <servername> : Microsoft.Windows.Computer: <servername> object then it seems to put the
entire server into maintenance. I tested against a server which happened to also host SQL role, so when I placed in Maint via the runbook I then stopped the SQL service and no alerts generated from SQL MP and I could see the spanner Icon against
the server in relevant SQL node views aswell.
I had though maybe that only windows MP stuff might be supressed - so again when I came across all the very complex solutions to apply Maint mode properly I wasnt sure if it was still relevant in 2012 (even though some of those solutions indicated for use
on SCOM/SCO 2012?)
Anyway if the simple solution work - as it appears to do so, then I'll run with that - unless someone can tell me why not?...
Cheers

Put servers in Maintenance Mode in SCOM 2012

Hi,
When we put a server in maintenance mode in SCOM 2012 it asks for only the end time. How can we specify the start time for maintenance mode.
Thanks

You can specify the start time for maintenance mode by schedule Maintenance mode.
For how to create schedule for maintenance mode, you can refer below link
http://support.microsoft.com/kb/2704170/en-us
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical

SCOM 2012 - Use Powershell to put specific server and contained objects into Maintenance Mode

I am still trying to develop what I thought was going to be an easy script, to put a specific server and all it's contained objects into maintenance mode in SCOM 2012.   Not a group, but just one specific server and all it's stuff.
My script to START maintenance mode has two parameters:
1. The FQDN. So for example: server1.contoso.com
2. The amount of minutes to put into maintenance mode
Then it does the following to START maintenance mode:
Import-Module OperationsManager
$Instance = Get-SCOMClassInstance -Name $FQDN
If ($Instance)
$newEnd = ((Get-Date).AddMinutes($minutes))
Start-SCOMMaintenanceMode -Instance $Instance -end $newEnd -Reason "PlannedOther" -Comment "Comments here"
This seems to work from what I can tell. I know that when you schedule maintenance mode manually in SCOM, there is an option to apply to "Selected objects and all their contained objects". I do not know if that is occurring based on
my code above.   But I think that is what I want to happen.   I just want all monitoring and alerting for the specified server to stop.   So if you think I need to change the above code so that it gets all the "contained
objects" please let me know.
The second part, which I know for a fact isn't fully working, is intended to stop maintenance mode for a server.
My script to STOP maintenance mode has only one parameter:
1. The FQDN. So for example: server1.contoso.com
Then it does the following to STOP maintenance mode:
Import-Module OperationsManager
$Instance = Get-SCOMClassInstance -Name $FQDN
If ($Instance)
$MMEntry = Get-SCOMMaintenanceMode -Instance $Instance
If ($MMentry)
#basically sends an end time of 1 minute from when the script is run
$newEnd = ((Get-Date).AddMinutes(1))
Set-SCOMMaintenanceMode -MaintenanceModeEntry $MMEntry -EndTime $NewEnd -Comment "Removing from Maintenance Mode"
This part does seem to work partially.   It does remove the server from maintenance mode. However, I suspect that it's not removing all the "contained objects" from maintenance mode because when I run the script to stop maintenance
mode on a server, the little maintenance mode icon in SCOM does go away but the overall light for the server stays set to "Not Monitored".   It never turns back to the green checkbox and says "Healthy".   When I start
and stop maintenance mode manually I can see that the green Healthy checkbox comes back. But when I try to run my above code to do it via script, it stays at "Not Monitored" instead.
Can someone help me out here? Looking for answers to two questions:
1. Does my Start maintenance mode code look ok? Will that put a server and all it's contained objects into maintenance mode?
2. What do I need to hadd to my Stop maintenance mode code, so that it correctly stops maintenance mode on the server and all its objects and everything starts to be monitored again?
Thanks in advance! Please let me know if you need any more information in order to be able to help me!

Hello, thanks for your response. Unfortunately, it does not appear that the link you provided works.
As far as not including "selected objects and all their contained objects" I am wondering if there is a way for me to tell for sure. One thing I found was that if I run this script and put the server into maintenance mode, then I go into
SCOM and click on Edit Maintenance Mode for that server, it shows me the details.   It has some comment, and my selected reason, based on the code I posted above.   It also DOES have "selected objects and all their contained objects"
selected at top. So it seems to me like it is working correctly, and does contain all the objects.   If you think that 'Edit' screen would be inaccurate for some reason, please let me know. Or if you know of a way for me to check and
confirm, please let me know that as well.
As for REMOVING it from maintenance mode, I did eventually find a line of code that I think works. Here's what my code looks like now:
Import-Module OperationsManager
$Instance = Get-SCOMClassInstance -Name $FQDN
If ($Instance)
$MMEntry = Get-SCOMMaintenanceMode -Instance $Instance If ($MMentry)
$Instance.StopMaintenanceMode([DateTime]::Now.ToUniversalTime(),[Microsoft.EnterpriseManagement.Common.TraversalDepth]::Recursive);
When I use the above code to STOP maintenance mode, the green checkmark does reappear for the server, and everything seems to be being monitored again.   Unlike before, where the maintenance mode icon would go away, but it would never change back
to saying 'Monitored' again. So I think that changing that one line to stop maintenance mode seems to have done the trick.
So I guess my last concern now is just putting in maintenance mode initially, as I was talking about above. If you still think the 'Edit Maintenance Mode' screen is not a good indicator of what my code does, please let me know.

Maintenance Mode Switch for APEX

Is there any way that I can throw an switch in APEX and have it allow users who are currently logged in to finish their sessions (maybe displaying an alert message at the top of their pages asking them to finish what they are doing quickly and logout) but display a message denying new users the ability to login and use APEX. What I am after is a way to gracefully clear users off of my app server so I can take it down without giving a grand maul das boot to active users. Kind of the "The store is now closing, please take your final purchases to the registers at this time." type of announcement. Lock the front doors but let people who are already inside finish their business type of result. If this does not exist, it would be a nice feature to have at the internal workspace control level.

Hi,
A Windows Schedule task,
http://technet.microsoft.com/en-us/library/cc748993.aspx
Please read this one:
Management Pack for the SCOM 2012 Maintenance Mode Scheduler
http://blog.tyang.org/2014/05/22/management-pack-scom-2012-maintenance-mode-scheduler/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Looking for a Powershell Script which can put the scom servers in maintenance mode

Looking for a Powershell Script which can put the scom servers in maintenance mode so that SCOM should not send an alert during planned task.
Rahul

1. Provide list of servers line-by-line in C:\ServerList.txt, make sure you provide limited no. of servers, do not exceed 20 - 25 per batch
2. Save the script with suitable name (test.ps1)
3. Open PowerShell cmd prompt
4. Script accepts 3 params - TimeInMinutes, Reason and Comment
**** Please note, this script will work for SCOM 2012 R2
param([int32]$TimeMin, [string]$Reason, [string]$Comment)
try
$api = new-object -comObject 'MOM.ScriptAPI'
Import-Module operationsmanager
New-SCOMManagementGroupConnection
$Servers = Get-Content "C:\ServerList.txt"
$Time = (Get-Date).Addminutes($TimeMin)
Foreach ($Server in $Servers)
#Get Computer instance
$ComputerClass = Get-SCOMClass -Name Microsoft.Windows.Computer
$ComputerClassInstance = Get-SCOMClassInstance -Class $ComputerClass | Where {$_.DisplayName -eq $Server}
If ($ComputerClassInstance -ne $Null)
$HealthServiceWatcherClass = Get-SCOMClass -name:Microsoft.SystemCenter.HealthServiceWatcher
#Get Health Service Watcher Class instance of the server
$HSWClass = Get-SCOMClass -Name Microsoft.SystemCenter.HealthServiceWatcher
$HSWClassIns = Get-SCOMClassInstance -Class $HSWClass | Where {$_.DisplayName -eq $Server}
#Starting the maintenance mode
Start-SCOMMaintenanceMode -Instance $HSWClassIns -EndTime $Time -Reason $Reason -Comment $Comment
Start-SCOMMaintenanceMode -Instance $ComputerClassInstance -EndTime $Time -Reason $Reason -Comment $Comment
Write-Host "Health Service Watcher and Agent server "$Server " kept in maintenance mode" -foregroundcolor "green"
$api.LogScriptEvent('MaintenanceModeScript.ps1', 200, 0, "$Server kept in maintenance mode for $TimeMin minutes")
Else
Write-Host $Server" not found " -foregroundcolor "red"
$api.LogScriptEvent('MaintenanceModeScript.ps1', 201, 1, "$Server could not be found in domain")
Catch [system.exception]
$api.LogScriptEvent('MaintenanceModeScript.ps1', 201, 1, $_.Exception.Message)
Faizan

5508-HA standby in Maintenance mode

My standby controller is in maintenance mode. Other post say to simply reboot the standby but I'm worried about doing this during business hours. Say I did reboot it during business hours, would it affect the active controller? All redundancy links are connected.
(Cisco Controller) >show redundancy sum
Redundancy Mode = SSO ENABLED
Local State = MAINTENANCE
Peer State = UNKNOWN - Communication Down
Unit = Secondary - HA SKU
Unit ID = 00:06:F6:DC:17:00
Redundancy State = Non Redundant
Mobility MAC = 68:EF:BD:8E:61:E0
Maintenance Mode = Enabled
Maintenance cause= Negotiation Timeout

No it won't affect the active controller:
While booting, the WLCs will negotiate the HA role as per the configuration done. Once the role is determined, the configuration is synced from the Active WLC to the Standby WLC via the Redundant Port. Initially WLC is configured, as Secondary will report XML mismatch and will download the configuration from Active and reboot again. During the next reboot after role determination, it will validate the configuration again, report no XML mismatch, and process further in order to establish itself as the Standby WLC
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.pdf
https://supportforums.cisco.com/discussion/11758901/ask-expert-high-availability-wireless-lan-controller-wlc

Cairo-dock starts in "maintenance mode"

Hi,
I've recently upgraded the cairo-dock, but since then it starts along with the <maintenance mode window>... When I try to close it, it reappears until the wifi connection settles down. I suspect that weather-dock is making troubles when it does not have connection to the internet.
I've looked through the cairo-dock options, and it has an option to force maintenance mode, but it does not have one to force disabling it unfortunately.
Anyone has any idea how to get rid of this?

probably an issue with your configuration. had this once, deleted my .config/cairo-doc ( at least i think thats where it was) folder and it worked again - with default settings.

OM2012 – Putting a Monitor in maintenance mode

Hi there,
I need to write a powershell script to put a Monitor in Maintenance mode. This is easily doable manually on the console whenever an alert comes up by putting the alert in Maintenance Mode.
So far I managed to make my script to put the class of the Monitor into maintenance, as per bellow
i.e. if the monitor is “Total CPU Utilization Percentage”, it would put Microsoft Windows Server 2012 R2 Datacenter in maintenance mode for the computer $ComputerName.
$ComputerName = Read-Host “Enter computer name”
$MonitorName = “Total CPU Utilization Percentage”
$Monitors=Get-SCOMMonitor -ComputerName $strComputerName | where {$_.DisplayName -eq $MonitorName}
$Time = ((Get-Date).AddMinutes(6))
foreach ($Monitor in $Monitors) {
$Instance = Get-SCOMclass -name $Monitor.target.identifier.path | Get-SCOMClassInstance #| where {$_.Path -eq $ComputerName}
Start-SCOMMaintenanceMode -Instance $Instance -EndTime $Time -Comment: “Server maintenance”
I can’t figure our how to simply put “Total CPU Utilization Percentage” (or any other Monitor) in maintenance mode
Thanks for your help !

Yes, use the "Start Maintenance Mode" Activtiy of the Integration Pack for OpsMgr.
www.sc-orchestrator.eu ,
Blog sc-orchestrator.eu

Maintenance Mode Questions

Similar Messages

Maybe you are looking for