SigmaSystemCenter 3.
Copyright (C) NEC Corporation 2003-2012. All rights reserved. Disclaimer of Warranty All the information, text, graphics, links or other items contained within this document is provided by copyright law. All Rights Reserved. No part of this document may be reproduced or transmitted without permission of NEC. NEC may make changes to this document, at any time without notice. NEC assumes no responsibility for errors or omissions in this document.
Contents Preface ................................................................................................................................. 5 How to Use This Manual ....................................................................................................................... 5 Manual Organization ............................................................................................................................. 5 SigmaSystemCenter Manuals ............................................
Appendix A Network Ports and Protocols 1.7.18.Action for Group / Create a Machine to the Group ..................................................................................112 1.7.19.Action for Group / Scalein Delete a Machine From the Group ................................................................112 1.7.20.Action for Group / Delete a Virtual Machine From the Group ..................................................................113 1.7.21.
Preface How to Use This Manual SigmaSystemCenter Data Reference Guide is intended for administrators of SigmaSystemCenter and explains its information of maintenance. This manual is a supplement to SigmaSystemCenter Configuration Guide. Manual Organization Part I Maintenance Information 1 "Error Events and Policy Actions": Describes the list of error events that SigmaSystemCenter can detect, the list of actions of policies, and the default disposals.
Appendix A Network Ports and Protocols SigmaSystemCenter Manuals The manuals of SigmaSystemCenter are configured for the various products and components as follows. In this manual, each of the following manuals is described as "How Manuals Are Called in This Manual." Products or Manuals Components SigmaSystemCenter 3.0 How Manuals Are Called in This Manual SigmaSystemCenter 3.0 First Step Guide SigmaSystemCenter First Step Guide SigmaSystemCenter 3.
The information regarding product summary, installation, configuration, operation and maintenance of SigmaSystemCenter are included in the following four manuals. The purposes of the manuals are as follows. SigmaSystemCenter First Step Guide This manual is intended for users who use SigmaSystemCenter for the first time and explains the product summary, system design methods and operating environment.
Appendix A Network Ports and Protocols Document Conventions In this manual, information that needs attention and references are described as follows: Note: indicates caution notes, and supplementary explanation for functions, operations, and settings. Reference: indicates why and where you should refer to. In addition, this manual uses the following document conventions.
Part I Maintenance Information This part describes the maintenance of SigmaSystemCenter. This part contains the following chapters: • • 1 2 Error Events and Policy Actions ................................................................................11 Logs .........................................................................................................................
1. Error Events and Policy Actions This chapter explains the errors that SigmaSystemCenter can detect and the details of policy actions to which corresponding event handler settings to the assumable errors can be configured. This chapter contains the following sections: • • • • • • • 1.1 1.2 1.3 1.4 1.5 1.6 1.7 Event Monitoring and Policy ..................................................................................... 12 Events SigmaSystemCenter Can Detect .........................................
Appendix A Network Ports and Protocols 1.1. Event Monitoring and Policy SigmaSystemCenter can monitor events and performance of managed machines. It can also change configuration of machines to restore from an event or error and notify a user that an event or error occurred.
1.2. Events SigmaSystemCenter Can Detect Monitoring products and components that SigmaSystemCenter can work with and what they monitor are as follows: Note: A registry path of Windows OS is different according to whether it is x86 OS or x64 OS. The registry path in this section is indicated in the x86 OS format. If you are using x64 OS, substitute "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node" for "HKEY_LOCAL_MACHINE\SOFTWARE.
Appendix A Network Ports and Protocols System Monitor - Performance Monitoring Services System Monitor - Performance Monitoring Services notifies the policy control processing of SigmaSystemCenter when statistics on CPU load factor of a managed machine, a status of utilization, such as disk utilization, or statistics information of multiple machines in a group exceeds the threshold value.
Optimal Placement monitors the value of "Consumed" and "Actually Consumed" in resource pools, and, when it excesses or goes down its thresholds, this function reports the events of resource pool consumption to SigmaSystemCenter policy control. Out-of-Band Management Out-of-Band Management receives PET directly from BMC of managed machines and manages them to detect abnormality and failure in the hardware.
Appendix A Network Ports and Protocols 1.2.1. Events NEC ESMPRO Manager Can Detect The following table shows the error events that NEC ESMPRO Manager can detect. You can check the following error events by specifying "SystemMonitorEvent" in the Report Source box on the Corresponding Event Handler Settings window, and a value that the Source Name in the following table and the event ID are combined, for example, ESMFSSERVICE[0XC00403E8], is displayed in the Event box on the window.
Event Category Hard disk failure CPU load failure CPU degeneracy failure CPU failure Events NEC ESMPRO Manager Can Detect Source Name Event ID Description ASMBENOTIFY 0X00002085 Verify aborted due to I/O error with fixed miscompares ASMBENOTIFY 0X00002090 Recovered error: SMART event received for array ASMBENOTIFY 0X00002091 Recovered error: SMART event received for device ASMBENOTIFY 0X00002094 I/O error aborted Verify, unfixed miscompares ASMBENOTIFY 0X000020AD Device is down.
Appendix A Network Ports and Protocols Event Category Events NEC ESMPRO Manager Can Detect Source Name Event ID Description CPU temperature failure ESMCOMMONSERVICE 0XC0000454 CPU thermal trip event Memory degeneration failure ESMCOMMONSERVICE 0X800002BE Memory Reduce ESMCOMMONSERVICE 0X800002C6 Memory Reduce ESMCOMMONSERVICE 0X80000515 POST memory resize ESMCOMMONSERVICE 0X8000051A POST cache Reduce ESMCOMMONSERVICE 0XC000051C Cache ECC multi ESMCOMMONSERVICE 0XC000044C ECC Multip
Event Category Events NEC ESMPRO Manager Can Detect Source Name Event ID Description ESMDSIKARRAY 0X400403F4 Disk Array Physical Device Rebuild ESMDSIKARRAY 0X400403F5 Disk Array Physical Device Hot Spare ESMDSIKARRAY 0X400403F6 Disk Array Physical Device Ready ESMDSIKARRAY 0X40040406 Disk Array Option report Normal ASMBENOTIFY 0X00002013 Reconstruct completed ASMBENOTIFY 0X0000B02D Array is optimal ESMCPUPERF 0X40000067 CPU Warning Recovered ESMCPUPERF 0X4000006B CPU Warning Reco
Appendix A Network Ports and Protocols 1.2.2. Checking Events that Can Be Detected Through NEC ESMPRO Manager You can refer to events that can be detected through NEC ESMPRO Manager by using the "Save Monitor Event". Perform the following procedure to see the events by reference. Note: The following procedure is for Windows. A document that shows events that can be detected through NEC ESMPRO Agent for Linux is provided individually, so contact our sales representative. 1.
3. Select Save Monitor Event from the Options menu on the Alert Manager setting tool. 4. The dialog box appears. Select the EventLog check box and Agent Events check box, and then click Save.
Appendix A Network Ports and Protocols 5. The system starts writing the monitoring target to a file. The following dialog box is displayed during writing. 6. When the writing process finishes, the dialog box disappears. Writing the monitoring target is now complete. The first line is a header and from the second line, the written file is created in the CSV format. See the event which "Manager" field is YES.
Formula: (the number of Port monitoring target machine units) * 20 [sec] / (the value of Maximum number of parallel processings) < (the value of Maximum time of one time monitoring) If the value of the Maximum number of parallel processings is increased, time to monitor machines at one time becomes short but loads of the management server increase.
Appendix A Network Ports and Protocols Event Category Customized Group Notification VM Server Notification Event ID Event Name Description 10000007 Customized machine notification7 10000008 Customized machine notification8 10000009 Customized machine notification9 1000000A Customized machine notification10 11000001 Customized group notification1 11000002 Customized group notification2 11000003 Customized group notification3 11000004 Customized group notification4 11000005 Customized g
1.2.5. Events the VMware (vCenter Server) Compatible Function Can Detect The events on virtual machines or virtual machine servers that can be detected by working together with VMware (vCenter Server) are as follows. You can check the following error events by specifying "VMwareProvider" in the Report Source box on the Corresponding Event Handler Settings window.
Appendix A Network Ports and Protocols Classification Usage rate of memory on a virtual machine server Event Category Error Description *1 Others Alarm Host CPU Usage on VMS changed from green to yellow The CPU usage rate of the virtual machine server becomes n % or more. (Default value: 75%) CPU load failure Alarm Host CPU Usage on VMS changed from green to red The CPU usage rate of the virtual machine server becomes n % or more.
Classification Event Category Error Description *1 Others Alarm Host Memory Usage on VMS changed from green to gray The memory usage rate of the virtual machine server becomes unknown. Others Alarm Host Memory Usage on VMS changed from green to yellow The memory usage rate of the virtual machine server becomes n % or more.
Appendix A Network Ports and Protocols Classification Usage rate of disk on a Datastore Event Category Error Description *1 Others Alarm Datastore Overallocation on disk on DATASTORE changed from gray to red The allocation rate of the Datastore becomes n % or more. (Default value: 700) Others Alarm Datastore Overallocation on disk on DATASTORE changed from green to gray The allocation rate of the Datastore becomes unknown.
Classification Event Category Error Description *1 Others Alarm Datastore usage on disk on DATASTORE changed from gray to yellow The disk usage rate of the Datastore is less than n %. (Default value: 85) Others Alarm Datastore usage on disk on DATASTORE changed from gray to red The disk usage rate of the Datastore becomes n % or more. (Default value: 85) Others Alarm Datastore usage on disk on DATASTORE changed from green to gray The disk usage rate of the Datastore becomes unknown.
Appendix A Network Ports and Protocols Classification Status of the connection to a network State of heart beat of a virtual machine Power status of a virtual machine Usage rate of CPU on a virtual machine Event Category Error Description *1 Others Storage path redundancy on VMS is degraded Storage redundancy is degraded. Others Network connectivity on VMS is lost Cannot connect to the network. Others Network redundancy on VMS is lost Network redundancy is lost.
Classification Event Category Error Description *1 CPU load failure Alarm Virtual Machine CPU Usage on VM changed from gray to red The CPU usage rate of the virtual machine becomes n % or more. (Default value: 90%) Others Alarm Virtual Machine CPU Usage on VM changed from green to gray The CPU usage rate of the virtual machine becomes unknown. Others Alarm Virtual Machine CPU Usage on VM changed from green to yellow The CPU usage rate of the virtual machine becomes n % or more.
Appendix A Network Ports and Protocols Classification Event Category Error Description *1 Memory degeneration failure Alarm Virtual Machine Memory Usage on VM changed from gray to red The memory usage rate of the virtual machine becomes n % or more. (Default value: 90%) Others Alarm Virtual Machine Memory Usage on VM changed from green to gray The memory usage rate of the virtual machine becomes unknown.
▪ The event of The heart beat value of the virtual machine is less than the threshold value. can be detected when you start a virtual machine. In that case, enable the error event controlling function. For how to configure the function, see Section 4.10.5, "Configuring Policy Property Settings" in SigmaSystemCenter Configuration Guide. ▪ The alarm definitions of virtual machines in Heartbeat status and events of the allocation rate of disk on a datastore are disabled by default.
Appendix A Network Ports and Protocols ▪ If you execute the restart operation of the PVMService and a virtual machine server, the "Hard disk failure" event that has already notified might be notified again. ▪ There is a case where the "Hard disk failure" is notified if a network failure occurs while SigmaSystemCenter is checking the datastore. 1.2.7. Events the Optimized Placement Can Detect The events that the Optimized Placement can detect are as follows.
Event Category Event Event Name Description VM Optimized Placement notification Resource-Pool Info Deasserted Resource Pool Consumption : Info Deasserted The value below its threshold (60% by default) in consumption/actually consumption of resource pool. Note: The "Scaleout Recommendation" and resource pool consumption notification event reports resource deficiency of a group. Configure the recovery process against the event for the group, not for each machine.
Appendix A Network Ports and Protocols Classification Voltage Event Category Prediction: voltage failure Clear Alert: voltage failure recovery Others Event ID Message Description [PET] 0x80010107 Temperature: Upper Non-critical - going low Recovered from the upper warning limit of the temperature. [PET] 0x8001010B Temperature: Upper Non-recoverable going low Recovered from the upper non-recoverable limit of the temperature.
Classification Current FAN Event Category Others Prediction:fan/co oling device failure Event ID Message Description [PET] 0x80020100 Voltage: Lower Non-critical - going high Recovered from the lower warning limit of the voltage. [PET] 0x80020104 Voltage: Lower Non-recoverable going high Recovered from the lower non-recoverable limit of the voltage. [PET] 0x00020107 Voltage: Upper Non-critical - going high Exceeded the upper warning limit of the voltage.
Appendix A Network Ports and Protocols Classification Event Category Clear Alert: fan/cooling device failure recovery Others Event ID Message Description [PET] 0x0004010B Fan(Speed): Upper Non-recoverable going high The number of revolution of FAN exceeded the upper non-recoverable limit. [PET] 0x00040301 Fan(Speed): Monitoring event occurred An event of FAN occurred.
Classification Security Event Category Others Event ID Message Description [PET] 0x00040702 Fan(Speed): Transition to Critical The FAN became the critical level. [PET] 0x00040703 Fan(Speed): Transition to Non-recoverable The FAN became non-recoverable level. [PET] 0x00040B00 Fan(Speed): Redundancy Full The FAN is redundant configuration. [PET] 0x00040B01 Fan(Speed): Redundancy Lost The FAN became not redundant configuration.
Appendix A Network Ports and Protocols Classification Security Violation Event Category Others Event ID Message Description [PET] 0x00056F03 Physical Security(Chassis Intrusion): Processor area Intrusion occurred The cover of CPU area opened. [PET] 0x80056F03 Physical Security(Chassis Intrusion): Processor area Intrusion cleared The cover of CPU area closed.
Classification CPU Event Category Event ID Message Description [PET] 0x00066F03 Platform Security Violation Attempt: Pre-boot Password Violation - network boot password Entered an incorrect network boot password. [PET] 0x00066F04 Platform Security Violation Attempt: Other pre-boot Password Violation Entered an incorrect password. [PET] 0x00066F05 Platform Security Violation Attempt: Out-of-band Access Password Violation OOB access password violation.
Appendix A Network Ports and Protocols Classification Power Supply Event Category Others Event ID Message Description [PET] 0x80076F04 Processor: FRB3/Processor Startup/Initialization failure (CPU didn't start) cleared Recovered from the initialization error. [PET] 0x00076F05 Processor: Configuration Error occurred A CPU configuration error occurred. [PET] 0x80076F05 Processor: Configuration Error cleared Recovered from the CPU configuration error.
Classification Power Unit Event Category Event ID Message Description [PET] 0x00080703 Power Supply: Transition to Non-recoverable The power supply device became non-recoverable. [PET] 0x00080B00 Power Supply: Redundancy Full The power supply device is redundant configuration. [PET] 0x00080B01 Power Supply: Redundancy Lost The power supply device became not redundant configuration.
Appendix A Network Ports and Protocols Classification Cooling Device Event Category Prediction:fan/co oling device failure Event ID Message Description [PET] 0x00090B01 Power Unit: Redundancy Lost The power unit became non-redundant. [PET] 0x00090B02 Power Unit: Redundancy Degraded The power unit became non-redundant but available. [PET] 0x00090B03 Power Unit: Non-Redundant(Suffic ient Resources) The power unit is non-redundant configuration.
Classification Event Category Clear Alert: fan/cooling device failure recovery Others Event ID Message Description [PET] 0x000A0109 Cooling Device: Upper Critical - going high Exceeded the upper critical limit of the cooling device. [PET] 0x000A010B Cooling Device: Upper Non-recoverable going high Exceeded the upper non-recoverable limit of the cooling device. [PET] 0x000A0702 Cooling Device: Transition to Critical The cooling device became the critical level. The liquid might spill.
Appendix A Network Ports and Protocols Classification Memory Event Category Event ID Message Description [PET] 0x000A0B02 Cooling Device: Redundancy Degraded The cooling device is not redundant but available. [PET] 0x000A0B03 Cooling Device: Non-Redundant(Suffic ient Resources) The cooling device is non-redundant configuration. [PET] 0x000A0B05 Cooling Device: Non-Redundant(Insuff icient Resources) The cooling device is non-redundant configuration and unavailable.
Classification Slot Event Category Others Event ID Message Description [PET] 0x000C6F04 Memory: Memory Device Disabled The memory is disabled. [PET] 0x800C6F04 Memory: Memory Device Enabled The memory is enabled. [PET] 0x000C6F05 Memory: Correctable ECC / other correctable memory error logging limit reached 1bit error occurs frequently. [PET] 0x800C6F05 Memory: Correctable ECC have receded. 1bit error was receded. [PET] 0x000C6F06 Memory: Presence detected The memory is implemented.
Appendix A Network Ports and Protocols Classification POST Memory POST Error Event logging System Event Critical Interrupt Event Category Event ID Message Description [PET] 0x800D6F01 Drive Slot(Bay): Drive Recovered Recovered from the failure of the drive device of the slot. Memory degeneration failure [PET] 0x000E0301 POST Memory Resize: Monitoring event occurred Memory resize occurred.
Classification Button/Switch Module/Board Chassis Event Category Others Others Others Event ID Message Description [PET] 0x00136F05 Critical Interrupt: PCI SERR PCI SERR occurred. [PET] 0x00136F06 Critical Interrupt: EISA Fail Safe Timeout EISA Fail Safe Timeout occurred. [PET] 0x00136F07 Critical Interrupt: Bus Correctable Error Bus Correctable Error occurred. [PET] 0x00136F08 Critical Interrupt: Bus Uncorrectable Error Bus Uncorrectable Error occurred.
Appendix A Network Ports and Protocols Classification Chip set Cable Event Category Others Others Event ID Message Description [PET] 0x80180700 Chassis: Transition to Abnormal The chassis became abnormal. [PET] 0x00180701 Chassis: Transition to Non-Critical The chassis became the warning status. [PET] 0x00180702 Chassis: Transition to Critical The chassis became critical. [PET] 0x00180703 Chassis: Transition to Non-recoverable The chassis became non-recoverable.
Classification OS Slot/Connector ACPI Power State Watchdog Timer Event Category Others Others Others Others Event ID Message Description [PET] 0x801B6F01 Cable/Interconnect: Configuration Error cleared Recovered from the Configuration error. [PET] 0x00206F00 OS Stop/Shutdown: Critical stop during OS load / Initialization Stopped during OS initialization. [PET] 0x00206F01 OS Stop/Shutdown: Run-time Critical Stop Stopped while OS is running.
Appendix A Network Ports and Protocols Classification Device ASIC/IC LAN Event Category Others Others Others Event ID Message Description [PET] 0x80236F01 Watchdog Timer: Recover from Hard Reset Recovered from Hard reset by Watchdog Timer. [PET] 0x00236F02 Watchdog Timer: Power Down Executed Power OFF by Watchdog Timer. [PET] 0x80236F02 Watchdog Timer: Recover from Power Down Recovered from Power OFF by Watchdog Timer.
Classification Event Category Event ID Message Description [PET] 0x80296F02 Battery: No Battery Battery not found.
Appendix A Network Ports and Protocols Note: SigmaSystemCenter handles PET as an OOB Management event. PET is a type of SNMP Trap. Even if SigmaSystemCenter receives an OOB Management event corresponding to SNMP Trap, SigmaSystemCenter does not display the event on the Web Console in some cases because such events are filtered by SigmaSystemCenter internally. The following table shows the conditions for discarding SNMP Trap. 1.2.9.
Event Category Event ID Message Description Machine inaccessible error Resources(VM)[Failed] Hyper-V Cluster VM Unavailable A virtual machine is unavailable to the cluster. Resources(VM)[Offline] *1 Hyper-V Cluster VM Resource Offline A virtual machine resource is offline. Machine inaccessible error recovery Resources(VM)[Online] Hyper-V Cluster VM Resource Online A virtual machine resource is online.
Appendix A Network Ports and Protocols Event Category Cluster: Network recovery Event ID Message Description Network[Unavailable] Hyper-V Cluster Network Unavailable A network is unavailable. NetworkInterface[Failed] Hyper-V Cluster Network Interface Failed A network interface failed. NetworkInterface[Unavailable] Hyper-V Cluster Network Interface Unavailable A network interface is unavailable.
1.3. Policy Setting Policy settings are created based on standard policies prepared for each machine type and usage. You can assign different policy settings to each group and model. SigmaSystemCenter specifies a managed machine or a group (model) by using a notified event that is sent when any status change happens, and checks the policy setting assigned to the group (model). If any action against the status change event is set in the policy setting, SigmaSystemCenter executes the action.
Appendix A Network Ports and Protocols 1.4. Configuring Actions Normally, you set an action to each single event; however, you can also set an action to multiple events collectively if you want to execute the same action to all events in the same event category. In addition, you can specify multiple actions to execute and also conditions to execute an action. If you do not set any action to an event, SigmaSystemCenter does not execute any action but outputs the operations log for the event.
If you cancel the execution of an action while the action is being executed, the execution process is aborted and the job ends with an error. In this case, the following actions are not executed and end no matter what execution results are set. The execution result of all actions is displayed as completed only when all the actions are completed. If even one action ends with an error, the result of all actions is ending with an error.
Appendix A Network Ports and Protocols In this case, SigmaSystemCenter executes the event handler settings as follows:
[Example2] Assume that there is an environment where System Monitor - Performance Monitoring Services monitors the load status of a group. If the load exceeds the threshold, SigmaSystemCenter executes Scale Out. This is an example of switching the scripts to notify the user depending on the execution result of the Scale Out. • Type of the managed target: group • Occurred event: group custom report by System Monitor - Performance Monitoring Services • Details of the corresponding event handler settings.
Appendix A Network Ports and Protocols 1.4.2.
1.4.3. Grouping Multiple Events You can select either a single event or all events in the same event category for an event that corresponds to an action to execute. If you select all events, set actions are executed when any of events that are set to the same event category. Note that you cannot set multiple corresponding event handler settings for the same event.
Appendix A Network Ports and Protocols 1.5. About Diagnosis 1.5.1. Diagnosis Function SigmaSystemCenter's diagnosis function enables detailed diagnosis of a failed environment where the Machine inaccessible error occurred. By setting a policy action of the diagnosis function, you can set recovery process to be executed only if the recovery setting is required.
In addition, when checking connection to an OS or access to the shared disk, if a fault is found on the error machine in diagnosis, the diagnosis function diagnoses other machines; however, it targets managed machines that meet the following conditions. For managed machines other than the targets, the diagnosis function does not count on as the number of machines in a group.
Appendix A Network Ports and Protocols Type of failed machine Conditions to cause abnormal end of Notes diagnosis (In the checking order) ESXi Standalone ▪ If connection to an error machine ends with an authority error or is disconnected in SSC. ▪ There are two or more failed machines in one group (other than the error machine).
Type of failed machine Conditions to cause abnormal end of Notes diagnosis (In the checking order) XenServer Machine Slave ▪ Cannot connect to XenServer Pool Master. ▪ Cannot access to the shared disk through XenServer Pool Master. ▪ When a machine cannot connect to Pool Master or access to the disk, the process ends with an error because the diagnosis function cannot control the recovery process.
Appendix A Network Ports and Protocols Receiving the NEC ESMPRO event relevant to the sensor status, sensor diagnosis analyzes the statuses of sensors whose types are the same as the sensor which has sent the triggered event. If any sensor does not respond due to communication failure or hardware failure, sensor diagnosis decides whether it ends normally or abnormally according to the importance of the triggered event.
Note: ▪ Sensor diagnosis targets the power-on machine where HW failure occurred. Therefore, you cannot obtain an accurate result if you execute sensor diagnosis for the power-off machine. ▪ When you executes sensor diagnosis for the machine which the OOB Management is not enabled, sensor diagnosis sets faulted status and ends normally. ▪ The criteria of severity of sensor status are independent from event categories.
Appendix A Network Ports and Protocols Power status result of action The power status changes before and after sensor diagnosis. This action sets faulted status and ends normally. The power status is off before the sensor diagnosis. This action sets faulted status and ends normally. Sensor diagnosis called from Total recover diagnosis explained in Subsection 1.5.
Related Products / Related Hardware Parts Status Name Functionalities NEC ESMPRO Battery / Boot Error / Button/Switch / Cable/Interconnect / Chassis / Chip Set / ClusterLan / ClusterNode / Cooling Device / CpuDegeneracy / CpuLoad / Critical Interrupt / DeadOrAlive / Disk / DiskRecovery / DiskReplace / Drive Slot(Bay) / Entity Presence Information / Event Logging / Fan(Speed) / Management Subsystem Health / Memory / MemoryDegeneration / Module/Board(Missing) / OS Boot / OS Critical Stop / Physical Securit
Appendix A Network Ports and Protocols Hardware Parts Status Corresponding Event Status Name [Summary]Public LAN error ClusterNode Faulted [Source]CLUSTERPRO [ID]0xC00008A4(2212) [Summary]Server down [Source]CLUSTERPRO X [ID]0x40000002(2) [Summary]Server down [Source]EXPRESSCLUSTER X [ID]0x40000002(2) [Summary]Server down CpuDegeneracy Faulted [Source]ESMCommonService [Summary]CPU Module FRB [ID]0xC0000838(2104) Degraded [Source]ESMCommonService [Summary]CPU Reduce [Source]ESMCommonService [Summ
Hardware Parts Status Corresponding Event Status Name [Source]ASMBENotify [ID]0x00002039(8249) [Summary]Scheduled Verify failed to start [Source]ASMBENotify [ID]0x0000204E(8270) [Summary]Verify utility failed to start [Source]ASMBENotify [ID]0x00002059(8281) [Summary]Dedicated spare not functional [Source]ASMBENotify [ID]0x00002085(8325) [Summary]Verify aborted due to I/O error with fixed miscompares [Source]ASMBENotify [ID]0x00002090(8336) [Summary]Recovered error: SMART event received for array [Sourc
Appendix A Network Ports and Protocols Hardware Parts Status Corresponding Event Status Name [Source]ESM Storage Service [ID]0xC00423F8(9208) [Summary]HD:Fatal Not Ready Error [Source]ESM Storage Service [ID]0x800423F7(9207) [Summary]HD:Warning Not Ready Error [Source]ESM Storage Service [ID]0xC00423FA(9210) [Summary]HD:Fatal Medium Error [Source]ESM Storage Service [ID]0x800423F9(9209) [Summary]HD:Warning Medium Error [Source]ESM Storage Service [ID]0xC00423FC(9212) [Summary]HD:Fatal Hardware Error [So
Target Machine Diagnosis for the Target Machine Virtual machine server Executes Subsection 1.5.1, "Diagnosis Function." Checks the following three points: ▪ Whether the target machine can connect to its virtual infrastructure, such as VMware vCenter Server or XenServer PoolMaster.
Appendix A Network Ports and Protocols Note: ▪ When a target machine is a virtual machine server, XenServer slaves cannot recognize access to the shared disk from the target machine. When the number of target disks to diagnose is zero, other virtual machine servers (ESX, standalone ESXi, Xen, and Hyper-V) also cannot recognize the target disks are accessible or not. Therefore, SigmaSystemCenter cannot judge the target machine is Normal using Composite Diagnosis.
1.6. About Standard Policy You can use standard action settings to handle errors for each type or usage of managed machine as standard policies. Contents of policy setting differ according to types of managed machine, such as a physical machine, virtual machine, and virtual machine server, or usage.
Appendix A Network Ports and Protocols Do not delete the System Policy (Manager) or do not change its name. If its name is changed, it will not be automatically applied because it is not recognized as the System Policy (Manager). If the System Policy (Manager) should be deleted by mistake or its name should be changed, it can be restored by restarting the PVMService. It cannot be added from the Add Policy menu. When disabling the System Policy (Manager), disable the monitoring event setting.
Event Name Report Source Event (Default) Event Recovery Event Handler Action State Notification/ E-mail, Event Log Enable Settings Name (Default) CPU load failure SystemMonitorEvent All events in the CPU load failure event category VMwareProvider and Set Faulted Status Machine status / Set faulted status ESMCpuPerf[0x80000065] CPU Error Recovered ESMCpuPerf[0x80000069] CPU Error Recovered (* For compatibility from SigmaSystemCenter 1.
Appendix A Network Ports and Protocols Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) status / Set faulted status AliveMonitor start up machine SystemMonitorEvent All events in the Machine inaccessible error recovery event category Set Ready Status VMwareProvider Enable Machine status / Set ready status AliveMonitor Memory degeneration failure Notification/ E-mail, Event Log SystemMonitorEvent All events in the Memory degenerat
Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) custom group notification 5 SystemMonitorPerf 11000005 no action no action Disable custom machine notification 1 SystemMonitorPerf 10000001 no action no action Disable custom machine notification 10 SystemMonitorPerf 1000000A no action no action Disable custom machine notification 2 SystemMonitorPerf 10000002 no action no action Disable custom machine notification 3 S
Appendix A Network Ports and Protocols 1.6.2. Settings of a Standard Policy (N+1) The following table shows the settings of a Standard Policy (N+1).
Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) SystemMonitorEvent Machine status/ Set faulted status Action for machine/ Replace machine CPU thermal recovery OobManagement Predictive alert : FAN / Cooling device failure OobManagement SystemMonitorEvent * See Subsection 1.6.8 "Settings of HW Predictive Monitoring Events." no action no action Disable * See Subsection 1.6.8 "Settings of HW Predictive Monitoring Events.
Appendix A Network Ports and Protocols Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) SystemMonitorEvent Machine status/ Set faulted status Action for machine/ Replace machine Predictive alert : Coolant leak OobManagement * See Subsection 1.6.8 "Settings of HW Predictive Monitoring Events.
Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) Memory degeneration failure Memory failure Memory Recovery VMS connection state is green VMS connection state is red AliveMonitor [PeriodicalAliveMonitor] TargetUp OobManagement [PET] 0x000E0301 SystemMonitorEvent ESMCOMMONSERVICE[0X 800002BE] ESMCOMMONSERVICE[0X 800002C6] ESMCOMMONSERVICE[0X 80000515] ESMCOMMONSERVICE[0X 8000051A] ESMCOMMONSERVICE[0X C000051C] OobManagement [PET
Appendix A Network Ports and Protocols Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) Alerm Host connection state on VMS changed from gray to red Cluster Node Down HyperVProvider Node[Down] Machine status / Set faulted status Set Faulted Status Notification/ E-mail, Event Log Disable Machine status / Set faulted status Cluster Node Recovery HyperVProvider Node[Up] Set Ready Status Notification/ E-mail, Event Log Disable Machin
Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) custom machine notification 1 SystemMonitorPerf 10000001 no action no action Disable custom machine notification 10 SystemMonitorPerf 1000000A no action no action Disable custom machine notification 2 SystemMonitorPerf 10000002 no action no action Disable custom machine notification 3 SystemMonitorPerf 10000003 no action no action Disable custom machine notification 4
Appendix A Network Ports and Protocols 1.6.3. Settings of a Standard Policy (Virtual Machine) The following table shows the settings of a Standard Policy (Virtual Machine).
Event Name Report Source Event *1 Event Handler Settings Name (Default) Recovery Event Action State (Default) Shortage of Memory VMwareProvider Alarm Virtual Machine Memory Usage on VM changed from gray to red Alarm Virtual Machine Memory Usage on VM changed from green to red Alarm Virtual Machine Memory Usage on VM changed from yellow to red Set Degraded Status Machine status / Set degraded status Disable Shortage of Memory recovery VMwareProvider Alarm Virtual Machine Memory Usage on VM
Appendix A Network Ports and Protocols Event Name (Default) Report Source Event *1 Event Handler Settings Name Recovery Event Action State (Default) *1 A suppressing function is configured to event monitoring. (For the details of the suppressing function, see Subsection 1.1.6, "Failure Recovery With a Policy" in SigmaSystemCenter Configuration Guide.
1.6.4. Settings of a Standard Policy (VM Server), Standard Policy (VM Server Predictive), Standard Policy (VM Server Power save) The following table shows the settings of a Standard Policy (VM Server), a Standard Policy (VM Server Predictive) and a Standard Policy (VM Server Power save).
Appendix A Network Ports and Protocols Event Name Report Source Event (Default) Event Recovery Event Handler Action State Notification/ E-mail, Event Log Enable Settings Name (Default) Machine Down SystemMonitorEvent AliveMonitor ESMDSVNT[0xC0000002] No response from the server Move all running VMs on the VM server Machine status / Set faulted status Action for machine/ Diagnose and Power OFF No response from the machine. Action for VMS / Move all running VMs on the VM server.
In addition to the above events, the HW Predictive event (see Subsection 1.6.8) is provided. ▪ The HW Predictive event is disabled in Standard Policy (VM Server) and Standard Policy (VM Server Power save). ▪ The HW Predictive event is enabled in Standard Policy (VM Server Predictive). (Recovery actions are disabled.) *1 This is a monitoring setting for events of machine down and startup of a virtual machine server available with working together with vCenter Server.
Appendix A Network Ports and Protocols Event Name Report Source Event (Default) Event Handler Recovery Event Settings Action State Name (Default) Machine status / Set faulted status Action for machine/ Diagnose and Power OFF Action for VMS / Move all VMs on the VM server. (Failover) Target Up AliveMonitor The machine access recovered.
1.6.6. Settings of a Standard Policy (VM Server Hyper-V), a Standard Policy (VM Server Hyper-V Predictive), And a Standard Policy (VM Server Hyper-V Power Save) The following table shows the settings of a Standard Policy (VM Server Hyper-V), a Standard Policy (VM Server Hyper-V Predictive), and a Standard Policy (VM Server Hyper-V Power Save).
Appendix A Network Ports and Protocols Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) Alarm Host connection state on VMS changed from red to green VMS connection state is red VMwareProvider Alarm Host connection state on VMS changed from gray to red Alarm Host connection state on VMS changed from green to red Machine status / Set ready status Move all running VMs on the VM server Notification/ E-mail, Event Log Disable Machine statu
Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) In addition to the above events, the HW Predictive event (see Subsection 1.6.8) is provided. ▪ The HW Predictive event is disabled in Standard Policy (VM Server Hyper-V). ▪ The HW Predictive event is enabled in Standard Policy (VM Server Hyper-V Predictive). (Recovery events are disabled.
Appendix A Network Ports and Protocols Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) Datastore Overallocation on disk to green VMwareProvider Alarm Datastore Overallocation on disk on DATASTORE changed from red to green Alarm Datastore Overallocation on disk on DATASTORE changed from yellow to green Alarm Datastore Overallocation on disk on DATASTORE changed from gray to green Notification Notification/ E-mail, Event Log Disable Da
Event Name Report Source Event (Default) Event Recovery Event Handler Action State Settings Name (Default) Cluster Down HyperVProvider Cluster[NotRunning] Notification Notification/ E-mail, Event Log Enable Cluster Up HyperVProvider Cluster[Running] Notification Notification/ E-mail, Event Log Enable * Suppression events of the Policy Property setting window cannot be set on the above events.
Appendix A Network Ports and Protocols Event Name Report Source Event Event Handler (Default) Settings Name (Default) Processor disabled OobManagement [PET] 0x00076F00 [PET] 0x00076F08 SystemMonitorEvent ESMCOMMONSERVICE[0XC0000451] ESMCOMMONSERVICE[0XC0000523] CPU thermal failure OobManagement [PET] 0x00076F01 SystemMonitorEvent ESMCOMMONSERVICE[0XC0000454] Move all running VMs on the VM server CPU thermal recovery OobManagement [PET] 0x80076F01 no action SystemMonitorEvent ESMCOMMONSE
Event Name Report Source Event Event Handler (Default) Settings Name (Default) SystemMonitorEvent ESMCOMMONSERVICE[0XC00000D0] ESMCOMMONSERVICE[0XC00000D2] ESMCOMMONSERVICE[0XC00000D6] ESMCOMMONSERVICE[0XC00000D8] ESMCOMMONSERVICE[0XC00000C8] Predictive alert : Coolant leak OobManagement [PET] 0x000A0702 SystemMonitorEvent ESMCOMMONSERVICE[0XC0000A8C] Clear alert : chassis temperature failure recovery OobManagement [PET] 0x80010102 [PET] 0x80010109 [PET] 0x00010701 SystemMonitorEvent ESMCOMM
Appendix A Network Ports and Protocols Event Name Report Source Event Event Handler (Default) Settings Name (Default) Clear alert : voltage normal recovery Clear alert : FAN / Cooling device normal recovery * OobManagement [PET] 0x80020100 [PET] 0x80020107 [PET] 0x80020301 [PET] 0x00020700 SystemMonitorEvent ESMCOMMONSERVICE[0X400001FC] ESMCOMMONSERVICE[0X40000202] ESMCOMMONSERVICE[0X40000902] ESMCOMMONSERVICE[0X40000931] ESMCOMMONSERVICE[0X40000BAD] ESMCOMMONSERVICE[0X400001FA] SystemMonitorEven
Action for VMS / Move all running VMs on the VM server. (Failover) Action settings that Event Handler Settings Name are "Move all running VMs / Server shutdown" (for Standard Policy (VM Server ESXi), "Move all VMs on the VM server / Server shutdown") are as follows: For policies other than Standard Policy (VM Server ESXi) • Machine status / Set faulted status by sensor diagnosis • Notification/ E-mail, Event Log • Action for VMS / Move all running VMs on the VM server.
Appendix A Network Ports and Protocols Note: ▪ To detect OOB Management events, see Section 3.10, "Preparing for the Use of Out-of-Band (OOB) Management" in SigmaSystemCenter Configuration Guide and perform the procedures from Subsection 3.10.1, "Configuring IP Address of BMC" to Subsection 3.10.3, "Configuring Alert Destination of PET and Alert Level." However, OOB Management events cannot be detected from a managed machine where NEC ESMPRO Agent is working.
1.7. List of Policy Actions In SigmaSystemCenter, you can customize actions for events of specified errors and create a policy. SigmaSystemCenter provides the following actions.
Appendix A Network Ports and Protocols Note: ▪ Policy actions for moving a single virtual machine are abolished with SigmaSystemCenter 2.0. In substitution, policy actions for Power save Virtual Machine server and Load balance Virtual Machine Server are added, If you were using the abolished policy actions before upgrading SigmaSystemCenter, the policy actions are converted to No action.
When receiving notification of an error Event log ID: 502 and any of 530, 531, and 532 Mail message: Received a notification. ("Report Information") When starting process for an error Event log ID: 502 and 540 Mail message: The action ("Process Name") was started. Management ID:"Management ID" When succeeding process for an error Event log ID: 502 and 541 Mail message: The action ("Process Name") has been completed.
Appendix A Network Ports and Protocols Note: ▪ You are notified by SystemPolicy (Manager) only when receiving an event. ▪ Contents of notification by SystemPolicy (Manager) is defined in the following file, stored in the SystemProvisioning installation folder: SystemProvisioning installation folder\conf\PvmCustom.xml 1.7.2. Machine Status / Set Ready Status Configures the Hardware Status of a target machine to "Ready". This action can be executed in parallel with other operations on the same machine. 1.
Note: ▪ To use this function correctly, see Subsection 1.5.2, "Sensor Diagnosis." ▪ You can see the detected sensor alerts at the Sensor tab, which is displayed by clicking Resource - Machine icon - IPMI Information - Sensor. However, sensors with problems might not be detected in the following cases: ▪ You collected sensor information after finishing the sensor diagnosis. ▪ You clicked the Refresh on the Sensor tab after finishing the sensor diagnosis.
Appendix A Network Ports and Protocols 1.7.7. Machine Status / Set Ready Status by Total Recover Diagnosis Diagnoses a target machine comprehensively based on the all statuses relevant to the target machine (status as a virtual machine server, sensor status, and machine status in detail). If this action judges the target machine is Normal, this action set Normal for the hardware status and ends normally.
1.7.12. Action for Machine / Turn off LED Requests a target machine to turn off the LED indicator. This action can be executed in parallel with other operations on the same machine. 1.7.13. Action for Machine / Replace Machine Replaces a target machine with a machine standing by in a pool or shared pool. If SystemProvisioning failed to shut down the target machine, SystemProvisioning executes Power OFF to the machine immediately. The replaced machine is stood by in a group pool. 1.7.14.
Appendix A Network Ports and Protocols Secondly, SystemProvisioning executes ACPI shutdown on the failed machine. If it fails, SystemProvisioning executes Power OFF to the failed machine and completes the process for recovery process to be executed. If it fails the Power OFF process, SystemProvisioning completes the process with Warning output to the Operations log because there is a possibility of succeeding the following recovery processes.
1.7.20. Action for Group / Delete a Virtual Machine From the Group Deletes a running machine (virtual machine) in the corresponding operation group. Completely deletes the machine. If a virtual machine server is being stopped, this action starts up the virtual machine server to delete. If a policy with a power save event is applied for a virtual machine server, the virtual machine server is shut down after the power save event occurs.
Appendix A Network Ports and Protocols The spare virtual machine servers are selected from the ones on which no virtual machine is running and not in failure status or maintenance status. The number of spare machines is the value of "Specify the number of machines to leave powered on even if they have no running VMs in order to respond quickly to load changes. (Power Saving)" in Optimized Placement. This action is enabled only for events detected in a virtual machine server.
In addition, if the target virtual machine server is Pool Master of XenServer and the machine is stopped, SystemProvisioning executes the process of switching Pool Master with other virtual machine server. 1.7.28. Action for VMS / Move all VMs on the VM server. (Failover) Moves all virtual machines on a target virtual machine server to other virtual machine server. As the moving method, Failover is used. This action is only valid for events detected on virtual machine servers.
Appendix A Network Ports and Protocols 1.7.31. Action for VMS / Move all VMs on the VM Server. (Quick Migration, Failover) Moves all virtual machines on a target virtual machine server to another virtual machine server. As the moving method, Quick Migration is used. If Quick Migration fails, Failover is used. This action is only valid for events detected on virtual machine servers.
This action does not execute any operations for virtual machines to which the Optimized Placement Rule is not set. 1.7.35. Action for VMS / Shutdown VM Server(Predictive) Shut down the target virtual machine server. However, if SystemProvisioning action judges that stopping the target virtual machine is likely to cause a problem in management and control of SystemProvisioning, this action is not executed. (For example, a target virtual machine server is Pool Master of XenServer.) 1.7.36.
2. Logs This chapter explains the logs that SigmaSystemCenter outputs. This chapter contains the following sections: • • • 2.1 2.2 2.3 Types of Logs ......................................................................................................... 120 Event Logs .............................................................................................................. 121 List of Log Files .......................................................................................................
Appendix A Network Ports and Protocols 2.1. Types of Logs There are the following logs that SystemProvisioning outputs: Operations Log The operational situation of SystemProvisioning is recorded. You can see the Operations Log on the Operations Log window in the Monitor view. The operations log displayed on this window is stored in the database. If the number of logs exceeds the maximum output number, logs are deleted from the oldest one.
2.2. Event Logs This section provides the lists of Event logs of SystemProvisioning are related to the operation in SigmaSystemCenter. Reference: For the Event logs of System Monitor - Performance Monitoring Services, see Section 9.1, "The Event Log" in System Monitor - Performance Monitoring Services User’s Guide.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 150 Transaction log of configuration database exceeded file size("file size"). (FileName:"file name") Information Transaction log expands. The transaction log might degrades the system performance use almost all the disk space. Stop SystemProvisioning and shrink the transaction log. 502 *1 Received a notification.
Event Description Type Meanings Solution 502 *1 The action ("information") has been canceled. Management ID:"Management ID" Information An action of the policy that contains "Notification/ E-mail, Event Log" is canceled. "Information": Information of the action "Management ID": The management number of the action Nothing 510 An event was detected. Target is "Target" Event is "Event Message" ------------------------------------* Additional information. (see the table below this table.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 530 Received a notification. ("Event Message" : "Target") ------------------------------------* Additional information. (see the table below this table.) Information Information detection, such as normalization set to be monitored in a policy, occurred at the target machine. Nothing 531 Received a notification. ("Event Message" : "Target") ------------------------------------* Additional information.
Event Description Type Meanings Solution 541 The action ("Infomation") has been completed.Management ID:"Management ID" ------------------------------------* Additional information. (see the table below this table.) Information An action as an autonomous control ends successfully. "Information": information of the action "Management ID": Management ID of the action Nothing 542 The action ("Infomation") was terminated because an error occurred.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 2023 Aborted the action starting up the machine. Management ID:"Management ID" Machine to be started up.("machine name") Warning Failed to start a machine. The process of starting the machine has failed. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 2024 Canceled the action starting up the machine. Management ID:"Management ID" Machine to be started up.
Event Description Type Meanings Solution 2033 Started the action adding the machine to the group. Management ID:"Management ID" The machine which is waiting to the pool of a group.("machine name") The group which works a machine.("group name") Information Adds a machine to a group and start the machine. Nothing 2034 Completed the action adding the machine to the group. Management ID:"Management ID" The machine which is waiting to the pool of a group.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution Completed the action deleting substance of the virtual machine from the group. Management ID:"Management ID" Information Completed a process of deleting a machine (virtual machine) running in a group from the group and deleting the resource. Nothing Aborted the action removing a running machine from the group.
Event Description Type Meanings Solution 2044 Aborted the action replacing the specified machine to standby machine. Management ID:"Management ID" Source machine.("machine name") Warning Failed to replace a machine running in a group with a stand by machine. Replacing a machine running in a group with a stand by machine has failed. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 2054 Started the action creating a virtual machine and adding it to the group. Management ID:"Management ID" VM to create("machine name") The group which works a machine("group name") The machine definition of VM to create("host name") Information Creates a machine in a group, Nothing 2055 Completed the action creating a virtual machine and adding it to the group.
Event Description Type Meanings Solution 2066 Started the action Move/Failover VMs on the specified VM Server. Management ID:"Management ID" Source VM Server.("machine name") Migration/QuickMigration.("True" or "False") Move. ("True" or "False") Failover. ("True" or "False") Information Execute Move or Failover a virtual machine on a virtual machine server. Nothing 2067 Completed the action Move/Failover VMs on the specified VM Server. Management ID:"Management ID" Source VM Server.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 2076 Aborted the action distributing software to all machines in the group. Management ID:"Management ID" Group to distribute a software.("group name") Warning Failed to distribute software to all machines in a group. Distributing software to all machines in a group has failed. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again.
Event Description Type Meanings Solution 2088 Aborted the action Power on the machine. Management ID:"Management ID" Machine to be power on.("machine name") Warning Failed to power ON a machine. A process of powering ON the machine has failed. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 2089 Canceled the action Power on the machine. Management ID:"Management ID" Machine to be power on.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 2098 Started the action Diagnose the machine. Management ID:"Management ID" Machine to be Investigated.("machine name") Information Diagnoses a machine. Nothing 2099 Completed the action Diagnose the machine. Management ID:"Management ID" Information Completed diagnosis. Nothing 2100 Aborted the action Diagnose the machine. Management ID:"Management ID" Warning Failed to diagnose a machine.
Event Description Type Meanings Solution 2108 Aborted the action Power cycle the machine. Management ID:"Management ID" Machine to be powercycled.("machine name") Warning Power cycle of the machine is aborted. A process of Power cycle of the machine has failed. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 2109 Canceled the action Power cycle the machine. Management ID:"Management ID" Machine to be powercycled.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 2118 Started the action Turn on the LED of machine. Management ID:"Management ID" Machine to turn on LED.("machine name") Information Turning on the LED of the machine is started. Nothing 2119 Completed the action Turn on the LED of machine. Management ID:"Management ID" Machine to turn on LED.("machine name") Information Turning on the LED of the machine is completed.
Event Description Type Meanings Solution 2129 Canceled the action Execute Load Balancing for VM Server. ID:"Management ID" Target VM Server.("machine name") Information Load balancing for VM Server is canceled. Nothing 2130 Started the action Execute Power Saving for VM Server ID:"Management ID" Target VM Server.("machine name") Information Power saving for VM Server is started. Nothing 2131 Completed the action Execute Power Saving for VM Server ID:"Management ID" Target VM Server.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 2140 Aborted the action Composite diagnosis and setting ready status ID:"Management ID" Machine to be diagnosed.("machine name") Diagnosis result.(False) Warning Recover diagnosis is failed. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 2141 Canceled the action Composite diagnosis and setting ready status ID:"Management ID" Machine to be diagnosed.
Event Description Type Meanings Solution 2502 Software ("software name") has been distributed to machine ("machine name"). Information Completed distributing software to a machine. Nothing 2652 VLAN ("VLAN name","port name") of switch ("switch name") could not be created. Error Failed to create a VLAN of a switch. Creating a VLAN of a switch has failed. Check the cause in the log, remove the cause, and execute the process again.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 2702 Startup for VM Server ("machine name") failed. ID:"Management ID" Warning Starting up a VM Server for Optimized Placement or the action of Refilling reserved VM Server failed. Check the cause in the SystemProvisioning log, remove the cause. 2703 Shutdown for VM Server ("machine name") was started.
Event Description Type Meanings Solution 2721 *3 ▪ There is no suitable VM server as migration target. ID:"Management ID" ▪ Load balancing is skipped because the master ("machine name") is not active. Warning Warning of the action of Load Balancing for VM Server. Check the cause in the SystemProvisioning log, remove the cause. 2722 *3 Information Information of the action of Power Saving for VM Server.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 2802 Failed to execute "Migrate Type" the virtual machine("Machine Name"). Information Failed to migrate the virtual machine. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again 2901 Failed to create the virtual machine. The request for creating the virtual machine failed. Cause:{0} Error Failed to create the virtual machine.
Event Description Type Meanings Solution 3011 Aborted the action Register manager. Warning Aborted the action Register manager. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 3012 Started the action Add the virtual machine server. Information Started the action Add the virtual machine server. Nothing 3013 Completed the action Add the virtual machine server. Information Completed the action Add the virtual machine server.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3026 Canceled the action Collect all data. Information Canceled the action Collect all data. Nothing 3027 Aborted the action Collect all data. Warning Aborted the action Collect all data. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 3028 Started the action Collect data for group. Information Started the action Collect data for group.
Event Description Type Meanings Solution 3043 Aborted the action Collect the scenario. Warning Aborted the action Collect the scenario. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 3044 Started the action Collect data for storage. Information Started the action Collect data for storage. Nothing 3045 Completed the action Collect data for storage. Information Completed the action Collect data for storage.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3058 Canceled the action Connect to the virtual machine server. Information Canceled the action Connect to the virtual machine server. Nothing 3059 Aborted the action Connect to the virtual machine server. Warning Aborted the action Connect to the virtual machine server. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again.
Event Description Type Meanings Solution 3074 Canceled the action Create the virtual machine without OS. Information Canceled the action Create the virtual machine without OS. Nothing 3075 Aborted the action Create the virtual machine without OS. Warning Aborted the action Create the virtual machine without OS. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 3076 Started the action Create the load balancer group.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3089 Completed the action Create the VLAN into specified switch. Information Completed the action Create the VLAN into specified switch. Nothing 3090 Canceled the action Create the VLAN into specified switch. Information Canceled the action Create the VLAN into specified switch. Nothing 3091 Aborted the action Create the VLAN into specified switch.
Event Description Type Meanings Solution 3106 Canceled the action Delete VLAN. Information Canceled the action Delete VLAN. Nothing 3107 Aborted the action Delete VLAN. Warning Aborted the action Delete VLAN. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3121 Completed the action Delete account Information Completed the action Delete account Nothing 3122 Canceled the action Delete account Information Canceled the action Delete account Nothing 3123 Aborted the action Delete account Warning Aborted the action Delete account Check the cause in the SystemProvisioning log, remove the cause, and execute the process again.
Event Description Type Meanings Solution 3138 Canceled the action Delete the virtual machine server. Information Canceled the action Delete the virtual machine server. Nothing 3139 Aborted the action Delete the virtual machine server. Warning Aborted the action Delete the virtual machine server. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 3140 Started the action Delete the VLAN from switch.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3152 Started the action Disconnect from the virtual machine server. Information Started the action Disconnect from the virtual machine server. Nothing 3153 Completed the action Disconnect from the virtual machine server. Information Completed the action Disconnect from the virtual machine server. Nothing 3154 Canceled the action Disconnect from the virtual machine server.
Event Description Type Meanings Solution 3168 Started the action Turn off LED request Information Started the action Turn off LED request Nothing 3169 Completed the action Turn off LED request Information Completed the action Turn off LED request Nothing 3170 Canceled the action Turn off LED request Information Canceled the action Turn off LED request Nothing 3171 Aborted the action Turn off LED request Warning Aborted the action Turn off LED request Check the cause in the SystemProv
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3185 Completed the action Modify the load balancer group. Information Completed the action Modify the load balancer group. Nothing 3186 Canceled the action Modify the load balancer group. Information Canceled the action Modify the load balancer group. Nothing 3187 Aborted the action Modify the load balancer group. Warning Aborted the action Modify the load balancer group.
Event Description Type Meanings Solution 3201 Completed the action Moving the virtual machine server. Information Completed the action Moving the virtual machine server. Nothing 3202 Canceled the action Moving the virtual machine server. Information Canceled the action Moving the virtual machine server. Nothing 3203 Aborted the action Moving the virtual machine server. Warning Aborted the action Moving the virtual machine server.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3215 Aborted the action Collect specified disk array information. Warning Aborted the action Collect specified disk array information. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 3216 Started the action Refresh the machine information. Information Started the action Refresh the machine information.
Event Description Type Meanings Solution 3229 Completed the action Add a port to VLAN. Information Completed the action Add a port to VLAN. Nothing 3230 Canceled the action Add a port to VLAN. Information Canceled the action Add a port to VLAN. Nothing 3231 Aborted the action Add a port to VLAN. Warning Aborted the action Add a port to VLAN. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3244 Started the action Scan datastore Information Started the action Scan datastore Nothing 3245 Completed the action Scan datastore Information Completed the action Scan datastore Nothing 3246 Canceled the action Scan datastore Information Canceled the action Scan datastore Nothing 3247 Aborted the action Scan datastore Warning Aborted the action Scan datastore Check the cause in the SystemProvisioning
Event Description Type Meanings Solution 3259 Aborted the action Register VLAN to the machine. Warning Aborted the action Register VLAN to the machine. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again. 3260 Started the action Set the faulted status to machine. Information Started the action Set the faulted status to machine. Nothing 3261 Completed the action Set the faulted status to machine.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3273 Completed the action Set maintenance status of the machine. Information Completed the action Set maintenance status of the machine. Nothing 3274 Canceled the action Set maintenance status of the machine. Information Canceled the action Set maintenance status of the machine. Nothing 3275 Aborted the action Set maintenance status of the machine.
Event Description Type Meanings Solution 3287 Aborted the action Unbind the disk volume. Warning Aborted the action Unbind the disk volume. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again.
Appendix A Network Ports and Protocols Event Description Type Meanings Solution 3301 Completed the action Notify group edit to DPM. Information Completed the action to notify DPM to edit groups. Nothing 3302 Canceled the action Notify group edit to DPM. Information Canceled the action to notify DPM to edit groups. Nothing 3303 Aborted the action Notify group edit to DPM. Warning Aborted the action to notify DPM to edit groups.
Event Description Type Meanings Solution 3314 Canceled the action Notify the group registration information on a machine to DPM. Information Canceled the action to notify DPM the registered information of the machine. Nothing 3315 Aborted the action Notify the group registration information on a machine to DPM. Warning Aborted the action to notify DPM the registered information of the machine. Check the cause in the SystemProvisioning log, remove the cause, and execute the process again.
Appendix A Network Ports and Protocols E.g.) Output message for event ID：541 The action (SetFaultedStatus) has been completed. Management ID:00049-01 -----------------------------[EventNumber] RE00144 [EventType] Information [EventCategory] TargetDown [EventSource] VC[https://192.168.10.220:50443/sdk] DataCenter[dataCenterB] ESX[192.168.220.
Additional information name Description Event ID: Event ID: 51X, 52X 53X, 54X [EventNumber] Number of the notified event Yes Yes [EventType] Type of the notified event (any of "Information", "Warning", or "Error") Yes Yes [EventCategory] Category of the notified event Yes Yes [EventSource] Source of the notified event Yes Yes [Provider] Provider of the notified event Yes Yes [Provider(ID)] Provider (ID) of the notified event Yes Yes [Event] Information identifies the notified
Appendix A Network Ports and Protocols Additional information name Description Event ID: Event ID: 51X, 52X 53X, 54X other(x):(yyy) Other information for action execution x indicates the order if multiple machines exist. yyy is a parameter name in the action sequence. Yes (yyy) is zzz Explanation of yyy included in the action information key. Yes 2.2.2.
2.3. List of Log Files This section gives you lists of log files that each component of SigmaSystemCenter outputs. To the log files, maximum size is set and SigmaSystemCenter manages the files by generation management. 2.3.1. Logs of SystemProvisioning The logs SystemProvisioning outputs are as follows: SystemProvisioning Folder SystemProvisioning installation folder\log\ (Default installation folder: C:\Program Files\NEC\PVM\log) Files ActionJob.log ActionSequence.log AliveMonitor.log CacheManager.
Appendix A Network Ports and Protocols PvmNetApp.log PvmNetvisorpro.log PvmPimIpmi.log PvmPimIpmi_Rmcp.log PVMReport.log PvmStorage.log PvmSwitchBlade.log PvmSymmetrix.log pvmutl.log ResourceEventList.log ResourceEventListener.log ResourceEventSender.log rm_pfmAPI.log rm_pfmAPI_old.log SLBProvider.log ssc.log ssc-old.log SystemEvent.log Usual.log UniversalConnector.log UniversalConnectorDefect.log VMwareProvider.log VMwareProviderInfo.log VMwareProviderEsxEvent.log VMwareProviderEvent.log VncClient.
Web-GUI.log.1 and the new Web-GUI.log is created. (If Web-GUI.log.1 already exists, it is deleted.) Supplement You can check the log files with Text Editor.
Appendix A Network Ports and Protocols 2.3.2. Logs of DPM The logs DPM outputs are as follows: DPM Server The logs output in a DPM Server installed machine are as follows: Folder DPM Server installation folder\Log\ ▪ For x86 OS machines (Default installation folder: C:\Program Files\NEC\DeploymentManager\Log) ▪ For x64 OS machines (Default folder: C:\Program Files (x86)\NEC\DeploymentManager\Log) Files apiserv.csv apitrace.log bkressvc.csv DepInit.csv depssvc.csv DIBPkgMake.csv ftsvc.csv pmdb.
(x86)\NEC\DeploymentManager\Datafile\ LogFile\SnrReport) Files Scenario.rpt Contents Result of scenario execution Recording There is no limit for its file size. You can delete the file on the DPM Web Console. (For deleting procedure, see Subsection 4.5.2, "Delete Log" in DeploymentManager Reference Guide.
Appendix A Network Ports and Protocols Recording Method Each file is saved in its current date file. Each file has no limit for its file size. Current date files cannot be deleted if the DPM services are running, but the past date files can be deleted manually. When 30 days pass after the create date, the files are automatically deleted.
(Default foler: C:\WINDOWS) Files Inst_Dpm_Db.log Inst_Dpm_Ports.log Inst_DPM_Mng.log Inst_Dpm_Jre.log Inst_DPM_Win_Cli.log Contents Installation logs of DPM Recording Each file has no limit for its file size. Inst_Dpm_Db.log and Inst_Dpm_Jre.log are overwritten every time DPM Server is installed, so their file sizes are not increased after installation of DPM Server. The Inst_Dpm_Db.log and Inst_Dpm_Jre.
Appendix A Network Ports and Protocols Folder %SystemRoot%\DeploymentManager\JSLog (Default folder: C:\WINDOWS\DeploymentManager\JSLog) Files CliSelfJSLog_YYYYMMDD.csv (YYYYMMDD: date) Contents Audit log (Internal working of DPM Client) Recording Each file has no limit for its file size. Current date files cannot be deleted if the DPM services are running, but the past date files can be deleted manually. When 30 days pass after the create date, the files are automatically deleted.
(Default folder: C:¥Program Files (x86)¥NEC¥DeploymentManager\Log) Files DPM_Trace1.csv Contents Audit log (Operation by a user / internal action in DPM Command Line) Recording The maximum size of DPM_Trace1.csv is 10 MB. The file is managed up to five generations. (If DPM_Trace1.csv exceeds the maximum size, the file is renamed to "DPM_Trace2.csv." Then, other "DPM_Trace[n].csv" files are also renamed to "DPM_Trace[n+1].csv " and "DPM_Trace5.csv" is deleted.) Files can be deleted manually.
Appendix A Network Ports and Protocols Note: If you are using x64 OS, substitute "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node" for "HKEY_LOCAL_MACHINE\SOFTWARE." Logs that the main Manager unit outputs • Statistical information files Folder The esmpro directory in the directory that the registry [HKEY_LOCAL_MACHINE\SOFTWARE\NEC\NVBASE] WorkDir locates Files Files with a name of a server name with .dat or .
Action of If a Size Reaches the Maximum Capacity Until What Generation the Outputs a maximum capacity of 5 Mbyte log in one file at one auto discovery process. If the output exceeds the 5 Mbyte, create a new file by adding "YY" of the file name part to output the log. If the number of log files exceeds 10, the oldest log file is overwritten. Five generation Files Are Managed If Logs Are Increasing in Operation Increases each time an auto discovery process is executed.
Appendix A Network Ports and Protocols If Logs Are Increasing in Increases. Operation If Capacity Can Be Limited No If There Is No Problem If No problem / Unnecessary You Delete Files Periodically / If You Delete Them, If You Need to Create Files With the Same Names If You Can Refer to Files (If So, If You Can Check Them Directly) Yes (Text Editor) However, the architecture is withheld as the logs are the internal logs.
Contents Events of communication with the management server and the operation the operator executes. Use Application log Maximum Capacity 2000 lines (by default) Action of If a Size Reaches Renames the file "hislog.bak" to create a new "hislog.txt". the Maximum Capacity Until What Generation the Two generation (hislog.txt、hislog.bak) Files Are Managed If Logs Are Increasing in Increases up to the maximum capacity.
Appendix A Network Ports and Protocols If You Can Refer to Files (If So, If You Can Check Them Directly) • Yes (Text Editor) However, the architecture is withheld as the logs are the internal logs. Console log Folder C:\Program Files\ESMPRO\ESMWEB\wbserver\webapps\esmpro\ WEB-INF\service Files xx.txt xx: Server ID Contents Display data of the Remote Console. Use Console log Maximum Capacity 64 KB (by default) Action of If a Size Reaches Renames the file xx.bak to create a new xx.txt.
• Database log Folder C:\Program Files\ESMPRO\ESMWEB\wbserver\webapps\esmpro\W EB-INF\service Files rmmanager.log Contents Stores execution status of ExpressUpdate internal database. Use Failure analysis Maximum Capacity 3 MB Action of If a Size Reaches Deletes the rmmanager.log and creates a new rmmanager.log the Maximum Capacity Until What Generation the One generation (rmmanager.log) Files Are Managed If Logs Are Increasing in Increases up to the maximum capacity of 3 MB.
Appendix A Network Ports and Protocols If Capacity Can Be Limited No If There Is No Problem If There is a problem with deleting files. / Unnecessary You Delete Files Periodically / If You Delete Them, If You Need to Create Files With the Same Names If You Can Refer to Files Yes (Text Editor) (If So, If You Can Check Them Directly) • Axis2 log Folder C:\Program Files\ESMPRO\ESMWEB\wbserver\webapps\esmpro\W EB-INF\service Files axis2.
Logs that the AlertManager unit outputs The following files are the examples that you installed NEC ESMPRO Manager first in the default installation folder in the C drive. Note: If NEC ESMPRO Agent is installed first, the default installation folder is C:\ESM\AlertMan. (If NEC ESMPRO Manager is installed first, the default installation folder is C:\ProgramFiles\ESMPRO\AlertMan.) Folder C:\ProgramFiles\ESMPRO\AlertMan\Work\ Files AMVSCKR.
Appendix A Network Ports and Protocols Until What Generation the Files One generation Are Managed If Logs Are Increasing in No: The file does not increase. Operation If Capacity Can Be Limited No If There Is No Problem If You No / No: No need for an empty file.
Folder C:\ProgramFiles\ESMPRO\NVWORK\AMWORK\SCK\ Files AMVSCKR.LOG Contents Internal logs of TCO/IP alert receiving Use Failure analysis Maximum Capacity 2000 Kbytes Action of If a Size Reaches the Information is updated from the oldest one Maximum Capacity Until What Generation the Files One generation Are Managed If Logs Are Increasing in Yes: If AlertManager receives TCP/IP information.
Appendices • • • • • • Appendix A Network Ports and Protocols ................................................................................ 189 Appendix B Transferring the Configuration Database ............................................................. 205 Appendix C How to Estimate Database Usage ....................................................................... 215 Appendix D Types of Action Sequence ...................................................................................
Appendix A Network Protocols Ports and Components in SigmaSystemCenter are configured to use the following network ports by default. This appendix provides the information of network ports and protocols. SystemProvisioning Item Execution File Port Proto Direc Name No. col tion Auto matic HTTP > DPM Server ICMP > < Managed machine DPM Server Connecting Target Port Execution File No. Name 80 Web service (IIS) Alive Monitoring (Ping) \Program Files\NEC\PVM\ bin\PVMService Proc.
Appendix A Network Ports and Protocols Item Execution File Port Proto Direc Name No. col tion \WINDOWS\Sys tem32\snmptrap .exe 162 UDP (SNM P Trap) 162 < Connecting Target BMC Port Execution File No. Name Auto matic *1 Used by connection from System Monitor - Performance Monitoring Services and SystemProvisioning modules, including the Web Console and pvmutl. *2 To restrict ports, note the points on Microsoft KB300083 and KB154596.
DeploymentManager Item DPM Server *9 Execution File Port Proto Direc Connecting Port Execution File Name *1 No. col tion Target No. Name Power ON \Program Files\NEC\Depl oymentManager \magicsend.exe Auto matic UDP > Managed machine *3 5561 Shutdown \Program Files\NEC\Depl oymentManager \apiserv.exe \Program Files\NEC\Depl oymentManager \schwatch.exe Auto matic TCP > Managed machine 56010 Network boot *4 DHCP server or \Program Files\NEC\Depl oymentManager \pxesvc.
Appendix A Network Ports and Protocols Item Execution File Port Proto Direc Connecting Port Execution File Name *1 No. col tion Target No. Name \Program Files\NEC\Depl oymentManager \bkressvc.exe 56022 TCP < Managed machine 56022 OS installation by disk duplication *7 \Program Files\NEC\Depl oymentManager \ftsvc.exe 56023 TCP < Managed machine Auto matic Backup *8 \Program Files\NEC\Depl oymentManager \ftsvc.
Item Execution File Port Proto Direc Connecting Port Execution File Name *1 No. col tion Target No. Name \Program Files\NEC\Depl oymentManager \rupdssvc.exe Auto matic UDP > Managed machine 56001 ▪ For a Windows machine \WINDOWS\sys tem32\rupdsvc. exe *2 ▪ For a Linux machine /opt/dpmclient/a gent/bin/Depagt d \Program Files\NEC\Depl oymentManager \rupdssvc.exe 56028 TCP < Managed machine Auto matic ▪ Only for a Windows machine \WINDOWS\sys tem32\rupdsvc.
Appendix A Network Ports and Protocols Item Execution File Port Proto Direc Connecting Port Execution File Name *1 No. col tion Target No. Name Connection with Image Builder (Remote Console) \Program Files\NEC\Depl oymentManager \ftsvc.exe 56023 TCP < Image Builder (Remote Console) Auto matic \Program Files\NEC\Depl oymentManager \DIBuilde.
Reference: To use a managed machine as a master machine or a master VM and join it to the domain, the port of domain network must be open. For details, see Subsection 1.1.1, " Notes for Environment Setup When Executing OS Installation by Disk Duplication" and "For General Virtual Environment" in Subsection 1.2.1, "About System Configuration" in SigmaSystemCenter Notes and Trouble Shooting Reference Guide.
Appendix A Network Ports and Protocols NEC ESMPRO Manager Item Execution File Port Protoc Direc Connecting Port Execution File Name No. ol tion Target No. Name Server configuration/ Server Monitoring (SNMP) \Program Files\NEC\SMM \ESMBASE\bin\ nvbase.exe Auto matic UDP > < NEC ESMPRO Agent 161 Alive Monitoring (Ping) ¥Program Files¥NEC¥SM M¥NVBASE¥bin ¥nvbase.exe ICMP > Managed machine Manager Report (SNMP) \Program Files\NEC\SMM \ESMBASE\bin\ nvbase.
Ack Transmission for Manager Report ¥Program Files¥NEC¥SM M¥NVBASE¥bin ¥esmasvnt.exe Auto matic UDP > EM card 5002 *3 *1 This value can be changed by either of the following procedures: ▪ From Windows GUI, click [Tools] - [Report Settings] on AlertViewer to open Alert Manager, click [Setting] - [Base Setting] - [Receive] tab, then click Configure button. ▪ From Web GUI, click [TCP/IP Report Settings] on the AlertViewer. *2 The value can be changed only from NEC ESMPRO Manager's Windows GUI.
Appendix A Network Ports and Protocols System Monitor - Performance Monitoring Services Item Monitored machines Execution File Port Execution No.
Adding ICMP Echo Reply to the Exception List of Windows Server 2008 Firewall Windows Server 2008 does not receive ICMP Echo Reply by default. Windows Server 2008 Firewall blocks the connection. To use Ping monitoring of alive monitoring function on Windows Server 2008, perform the following procedure to add ICMP Echo Reply to the Firewall exception list. 1. Click Start, and click Administrative Tools to open Windows Firewall with Advanced Security.
Appendix A Network Ports and Protocols 2. Select Inbound Rules in the left pane, click New Rule… in the right pain. 3. Select Custom, and click Next.
4. Enter %ProgramFiles%\NEC\PVM\bin\PVMServiceProc.exe, and click Next. 5. Select ICMPv4 in Protocol type, and click Next.
Appendix A Network Ports and Protocols 6. Click Next. 7. Click Next.
8. Click Next. 9. Enter an arbitrary name in the Name box, and click Finish.
Appendix A Network Ports and Protocols 10. Confirm that the setting is added to the Inbound Rules.
Appendix B Transferring the Configuration Database Although the configuration database is created on a management server when SystemProvisioning is installed, SQL Server 2008 R2 configured on a remote server on the network also can be used.
Appendix B Transferring the Configuration Database 2. Run the downloaded SQLEXPR.EXE and proceed with the setup according to the instructions on the screen. 3. The Instance Configuration dialog box appears. Select Named instance, and enter SSCCMDB in the text box. 4. Server Configuration dialog box appears. Select NT AUTHORITY\NETWORK SERVICE for the account name of SQL Server Database Engine service.
5. Database Engine Configuration dialog box appears. Select Windows authentication mode. After this, follow the instructions that appear on the screen to complete the setup. 3. Validating the network connection Because SQL Server 2008 R2 Express permits only the local client connection by default, you need to enable the network connection. In addition, SQL Server Browser must be started and Firewall exceptions must be created. Reference: Refer to the following site for more details. http://support.
Appendix B Transferring the Configuration Database E.g.1) > sqlcmd -E -S (local)\SSCCMDB -Q "create database pvminf" E.g.2) > sqlcmd -E -S (local)\SSCCMDB 1> create database pvminf 2> go 5. Restarting the service Click the Start menu, and click Control Panel. From Control Panel, double-click Administrative Tools. From Administrative Tools, and double-click Services to start the Services Snap-in on the SERVER1. Right-click the following service and click Restart.
Note: Replace the following data with the Login Name part: Domain Name\the computer name of the management server$. E.g.) An input example for the case of domain Domain name: Domain The computer name of the management server: SSC_Management_Server > sqlcmd –E –S (local)\SSCCMDB 1> CREATE LOGIN [Domain\SSC_Management_Server$] FROM WINDOWS WITH DEFAULT_DATABASE=[pvminf] 2> go 1> EXEC master..sp_addsrvrolemember @loginame = N'Domain\SSC_Management_Server$', @rolename = N'sysadmin' 2> go 1> exit 8.
Appendix B Transferring the Configuration Database 3. Enter values in the Host name and Instance name boxes, and select Use Windows authentication login. Click Save. 4. Click the Start menu, and click Control Panel. From Control Panel, double-click Administrative Tools. From Administrative Tools, and double-click Services to start the Services Snap-in. 5. Right-click PVMService and click Restart. Transferring the configuration database using Windows authentication login is now complete.
Using SQL Authentication Login Perform the following procedures to transfer the configuration database using the SQL authentication login. 1. Backing up SystemProvisioning Back up SystemProvisioning. For the procedure, see Subsection 10.2.1, "Backing up SystemProvisioning" in SigmaSystemCenter Configuration Guide. Note: Set the name of the backup file as "backup.dat". 2. Creating Instance Setup the SQL Server 2008 R2 Express on the SERVER1. 1.
Appendix B Transferring the Configuration Database 4. Server Configuration dialog box appears. Select NT AUTHORITY\NETWORK SERVICE for the account name of SQL Server Database Engine service. 5. Database Engine Configuration dialog box appears. Select Mixed Mode (SQL Server authentication and Windows authentication). Enter the sa logon password in the Enter password box and the Confirm password box. Note: The administrator determines the password.
After this, follow the instructions that appear on the screen to complete the setup. 3. Validating the network connection As SQL Server 2008 R2 Express permits only the local client connection by default, you need to enable the network connection. In addition, SQL Server Browser must be started and Firewall exceptions must be created. Reference: Refer to the following site for more details. http://support.microsoft.com/kb/914277/en-us 4.
Appendix B Transferring the Configuration Database E.g.2) > sqlcmd -E -S (local)\SSCCMDB 1> restore database pvminf from disk = ‘C:\temp\backup.dat’ with replace 2> go 7. Environment settings Configure the environment settings and restart the PVMService. 1. Start SystemProvisioning Installation Folder\bin\PvmConfig.exe on the management server. 2. The Environment Setting dialog box appears. 3. Enter values in the Host name and Instance name boxes, and select Use SQL authentication login.
Appendix C How to Estimate Database Usage SystemProvisioning, System Monitor - Performance Monitoring Services and DeploymentManager use the database in SigmaSystemCenter. Instructions on how to estimate the database usage are provided below. SystemProvisioning Estimates of disk capacities are described below according to the machine types. Physical machines About 4.1 KB is used for management of a blade chassis and a blade server. Use the following information as a guide of individual calculation.
Appendix C How to Estimate Database Usage Virtual machines vCenter Server or ESX must be built to manage virtual machines. About 9.0 KB is used for management of a virtual machine. Use the following information as a guide of individual calculation. vCenter Server 0.5 KB / unit DataCenter 0.6 KB / unit ESX 4.0 KB / unit virtual machine 3.3 KB / unit template 0.6 KB / unit E.g.
Operations log Operations logs are recorded in the SystemProvisioning database. An operations log is composed of two kinds of information: logs and events which are the source of the logs. Usually, multiple logs are registered for one event. Events can be recorded up to one third of the maximum amount of log records. Use the following information as a guide of capacity calculation. • 0.6 KB is used for one record of operations log. • 2.8 / 3 KB is used for one event.
Appendix C How to Estimate Database Usage System Monitor - Performance Monitoring Services System Monitor - Performance Monitoring Services collects performance data and accumulates them in the database. Depending on operation forms, the database might exceed the maximum capacity of SQL Server. For example, the maximum capacity of SQL Server 2008 R2 Express is 10 GB. There are two ways to avoid the above case: 1. Upgrade SQL Server 2008 R2 Express to SQL Server 2008. 2.
DeploymentManager SQL Server 2008 R2 SP1 Express requires about 711 MB disk spaces. DPM Server installation requires 256 MB databace spaces. A rough estimate of database capacity necessary for future increases can be made according to the following formula. Necessary disk capacity = The number of registered computers * 10 KB + The number of registered packages * 3 KB + The number of registered computers * 0.15 KB * The number of registered packages E.g.
Appendix D Types of Action Sequence The following table shows action sequences. NO. Action Sequence Names Corresponding Functions machine Physical Virtual Machine Machine configuration change 1 ChangeServerGroup Change Machine Usage (Physical Machine) Changes a machine running in the specified group to another usage (move to another group).
Appendix D Types of Action Sequence NO. Action Sequence Names Corresponding Functions machine Physical Virtual Machine Machine configuration change 13 MoveFromPoolToGroup Activating Machine / Allocate Machine (Physical Machine) Activating Machine / Scale Out (Physical Machine) Activating Machine / Allocate Machine (Virtual Machine) Activating Machine / Scale Out (Virtual Machine) Activates a machine in the pool of the group to run in the group.
NO. Action Sequence Names Corresponding Functions machine Physical Virtual Machine Machine configuration change 25 PowerCycleMachine Power Operation to machine / Power Cycle Powers off and then Power on a running machine. A *4 N 26 AcpiShutdownMachine Power Operation to machine / ACPI Shutdown Executes ACPI shutdown on a running machine. A *4,5 N 27 DumpMachine Dump Machine Sends dump demand to a machine. A *4,5 N 28 LedTurnOnMachine Sends LED on demand to a running machine.
Appendix E Revision History Second Edition (January 2012) Revised adding descriptions about enhancements in Update 1. Added description regarding the vSphere 5.0 supports. Chapter 1 1.2.5. Events the VMware (vCenter Server) Compatible Function Can Detect 1.2.6. Events the VMware (ESXi) Compatible Function Can Detect Added description regarding the newly featured resource pool monitoring Chapter 1 1.2. Events SigmaSystemCenter Can Detect 1.2.7. Events the Optimized Placement Can Detect 1.6.4.
Appendix F License Information This product includes certain open source software. Details of individual licenses are provided on the SigmaSystemCenter DVD \doc\OSS directory. Please contact us in order to obtain the source code of software that is distributed under the LGPL. ▪ PXE Software Copyright (C) 1997 - 2000 Intel Corporation. ▪ This product contains JRE (Java Runtime Environment) which is distributed by Oracle Corporation without charge.
