funksoul's Posts

Hi, I had to create a vROps custom group of VMs based on port group connectivity information but was not able to do it with vSS(vSphere Standard Switch). Because vROps supports objects, metrics... See more...
Hi, I had to create a vROps custom group of VMs based on port group connectivity information but was not able to do it with vSS(vSphere Standard Switch). Because vROps supports objects, metrics, relationships for vDS only and not for vSS, I tried to use vSphere Tags as a workaround. After create tag category > create tags of each port group names > assigned tags to VMs in vCenter, I was able to create vROps custom group by vSS port group connectivity. p.s. PowerCLI script which automates vCenter-side steps of this workaround was attached
I used ko_KR.UTF-8 for Korean language. Though I did not try other locales, UTF-8 encodings might work if one can see localized strings in vROps Web UI.
Hi, In vROps 6.6.1, outbound plug-ins do not send localized contents by default. But they will send localized contents if the vmware-vcops service is running in specific locale. To configure... See more...
Hi, In vROps 6.6.1, outbound plug-ins do not send localized contents by default. But they will send localized contents if the vmware-vcops service is running in specific locale. To configure a locale of vmware-vcops service In vROps VA, add $LANG environment variable to /etc/profile.d/vcops.sh.     # echo "export LANG=[your locale name here]" >> /etc/profile.d/vcops.sh     (*restart required) I don't know if it's supported but worked like a champ for me. Thank you.
Hi, bjohn If the situation that was raised thru an alert(symptoms in vR Ops) no longer exists, the alert get cancelled automatically. Though there are alerts that can be cancelled by pressing... See more...
Hi, bjohn If the situation that was raised thru an alert(symptoms in vR Ops) no longer exists, the alert get cancelled automatically. Though there are alerts that can be cancelled by pressing the cancel alert button, performance metric based alerts cannot be cancelled by this way because the metrics are refreshed on each collection interval. They only get cancelled by the system if the symptoms are resolved. So if you want to control an alert: 1. Review the alert definition with related symptoms and 2. [Modify the alert definition] or [adjust the symptoms thresold in the policy] Regards, Ho-Sung.
Hi, bjohn There are many ways to clear that alert.. for example, - Make the recompose task routine so that vR Ops can learn the behavior and create a new alert definition that adds a dy... See more...
Hi, bjohn There are many ways to clear that alert.. for example, - Make the recompose task routine so that vR Ops can learn the behavior and create a new alert definition that adds a dynamic threshold criteria to the original alert. - Put the VMs into maintenance mode in vR Ops while the recompose task is in progress. (metrics are not collected and no alert fires when an object is in maintenance mode) - Push the snooze button to make the alert go into sleep 9999999999 minutes. (just a joke but it will do the work anyway) Regards, Ho-Sung.
Hi, bjohn. In vR Ops, alerts are always fired if conditions are met. That means you cannot just clear alerts without resolving the alert conditions. In your case, you can review the alert de... See more...
Hi, bjohn. In vR Ops, alerts are always fired if conditions are met. That means you cannot just clear alerts without resolving the alert conditions. In your case, you can review the alert definition and change the symptom threshold or disable the alert for group of objects from the policy. Regards, Ho-Sung.
Hi TheVMinator. AFAIK, you can assume that a vNIC instance 4000 is a 'Network Adapter 1' in most cases. So if you do not care for few exceptions, you will be able to get the result by using e... See more...
Hi TheVMinator. AFAIK, you can assume that a vNIC instance 4000 is a 'Network Adapter 1' in most cases. So if you do not care for few exceptions, you will be able to get the result by using existing metric 'Network I/O|4000|Usage Rate (KBps)' and don't have to create a SM. * There are plenty of metrics for VM Network usage so you may not need the SMs if there's no need of very complex/specific metrics.   But for sure, you can create a SM if the metric you want does not exist. Regards, Ho-Sung.
Hi, rgcda. > Are you saying that I need to create new symptom definitions that I want to assign to development machines and then enable them in this specific policy in the Override Alert / S... See more...
Hi, rgcda. > Are you saying that I need to create new symptom definitions that I want to assign to development machines and then enable them in this specific policy in the Override Alert / Symptom Definitions? When you define a symptom that triggers over 95% of disk space usage, the default threshold value of the symptom will be 95. But if you want different threshold value of 99% for your development machines group with the same symptom definition, you don't have to define another duplicated symptom but just override(modify) the threshold value of original symptom to 99 in the policy edit screen. In other words, single symptom definition can have different threshold values in each policy. > Also for alert notifications would I have to create a new alert definition and enable it in is this specific policy? Nope, you do not have to create a new alert in this case. If a symptom threshold value changes via policy override, alerts which have that symptom will fire at different threshold value accordingly. > If I would have different symptom definitions for the same object are you saying I have to make the change in the KB you mentioned?     For instance if I want the C drive to be a critical alarm when it reaches 95% on this machine and a critical when it reached 99% on a different machine. Nope, as you see in the above example, applying different threshold value to each machine can be done regardless of the metric you use is instanced or not. The KB is about treating a metric that has many instances for a machine and you may need it for disk space usage. Regards, Ho-Sung.
Hi, rgcda. The attribute packages from vC Ops 5 merged as a part of the policy in vR Ops 6. To illustrate a general procedure, in vR Ops 6 you would go through these steps to set different ... See more...
Hi, rgcda. The attribute packages from vC Ops 5 merged as a part of the policy in vR Ops 6. To illustrate a general procedure, in vR Ops 6 you would go through these steps to set different threshold values to different groups of machines: 1. From 'Content > Symptom Definitions' menu, define symptoms using metrics for monitoring disk usage. (e.g. guestfilesystem|percentage)    You can set thresholds like 85% = WARNING, 90% = IMMEDIATE, 95% = CRITICAL as a baseline for all machines. 2. From 'Content > Alert Definitions' menu, define an alert using symptoms you defined above. 3. From Environment menu, create a group that has the development machines in it. 4. From 'Administration > Policies' menu, create a new policy based on your default policy and override symptom threshold value (like 99% = CRITICAL) and assign the policy to the group you created. 5. From 'Content > Notifications' menu, define a notification rule if you need to receive an e-mail or something on the alert you defined. * Unlike Memory usage metrics (for example), a machine can have many disk drives that results to many instances of a same metric. (such as disk space usage for C:, D:, E:)    So when you define a symptom using these metrics, you should set an 'instanced' property for it. (KB 2108273 : http://kb.vmware.com/kb/2108273) Regards, Ho-Sung.
Hi, folks. I wanted to model Hyperic Service (InetAddress Ping, HTTP,.. etc) to independent vR Ops resource so added configuration parameter to hyperic.properties file like this:     serviceT... See more...
Hi, folks. I wanted to model Hyperic Service (InetAddress Ping, HTTP,.. etc) to independent vR Ops resource so added configuration parameter to hyperic.properties file like this:     serviceTypesForIndependentServices=HTTP Though it is described in the documentation (vRealize Operations Manager 6.0.1 Documentation Center) but looks like not working as expected. Does anyone have experience on this issue? Any hint will be appreciated. vR Ops version is 6.0.1 and Hyperic adapter version is 6.0.2470875 Regards, Ho-Sung
Yeap. An array(storage) CIM provider should be added to the vCenter Server first via VASA providers registration and the vCenter Server should be added to the vR Ops MPSD Adpater instance. If... See more...
Yeap. An array(storage) CIM provider should be added to the vCenter Server first via VASA providers registration and the vCenter Server should be added to the vR Ops MPSD Adpater instance. If you add the vCenter Server to the vR Ops MPSD Adapter instance successfully, "Add Fabric Server" button is activated in the MPSD Adapter Settings page and you can add a fabric(switch) CIM provider like DCNM. AFAIK there's no way to add a fabric CIM provider in the vCenter Server. Regards, Ho-Sung.
Hi, GSS344 I used to configure a SCOM adapter with vC Ops 5.x and it worked fine. vR Ops 6.x has the same SCOM adapter so it will work, too. * BTW, You will need vR Ops enterprise licenses... See more...
Hi, GSS344 I used to configure a SCOM adapter with vC Ops 5.x and it worked fine. vR Ops 6.x has the same SCOM adapter so it will work, too. * BTW, You will need vR Ops enterprise licenses for the adapter. Regards, Ho-Sung
Hi, Gabrie. Seems that you already added the VC to the MPSD instance and registered VASA providers to the VC. Then the next step is to register fabric servers to the vR Ops MPSD instance. ... See more...
Hi, Gabrie. Seems that you already added the VC to the MPSD instance and registered VASA providers to the VC. Then the next step is to register fabric servers to the vR Ops MPSD instance. If DCNM supports SMI-S and provides CIM fabric or switch profile, all you need might be the ip/username/password of DCNM's SMI-S provider when register it to the vR Ops MPSD instance. * A fabric server means a SAN device such as a switch that provides CIM fabric or switch profile via SMI-S. * The MPSD adapter logs will give you useful hints when you encounter any problem. Regards, Ho-Sung.
Um, I did not installed vRA in my environment and do not need to monitor vSphere SSO right now. So I can not understand why you're not recommending leaving them not being integrated to vR Ops. ... See more...
Um, I did not installed vRA in my environment and do not need to monitor vSphere SSO right now. So I can not understand why you're not recommending leaving them not being integrated to vR Ops. Actually, I don't know what to do with the .jar file now because I upgraded my Hyperic MP instance only with the .pak file. Should the .jar file get installed to some location for the Hyperic MP instance itself work correctly when there's no integration of vRA and SSO to Hyperic? I don't want waste your time if there's any document or clear information that I can access for this topic. Thank you. Ho-Sung.
Hi, Brian. Sorry I did not know that you're such an expert to this subject :smileyblush: [:blush:] I was impressed at the new policy system that incorporates symptoms and alerts in the vR Ops... See more...
Hi, Brian. Sorry I did not know that you're such an expert to this subject :smileyblush: [:blush:] I was impressed at the new policy system that incorporates symptoms and alerts in the vR Ops 6 and I felt that it's the perfect solution for the policy part of "policy based automation". But for the automation part, I was disappointed a bit because oob python action is manual, limited and it looked difficult to customize. So as of now, I think vCO integration will be the best choice for these reasons: - has huge extensibility that covers different domains - all the automated actions are triggered from the alerts in the vR Ops - it is an out-of-the-vmware-box solution For the risks of automated remediation, what about integrating remediation procedure with organization's approval process? Such as vR Ops(fire an alert) -> REST(remediation approval/audit) -> vCO(trigger an automated workflow) Regards, Ho-Sung
Sounds like that I don't need that .jar file if I would not implement vRA or SSO integration. Am I understanding right?
Hi, I upgraded Hyperic MP to the new version and confirmed that the relationships are re-established as expected. Thank you very much for the quick fix. BTW, do you know what is the hyperi... See more...
Hi, I upgraded Hyperic MP to the new version and confirmed that the relationships are re-established as expected. Thank you very much for the quick fix. BTW, do you know what is the hyperic-common-model-1.0.jar file? It's included in the updated Hyperic MP distribution package with .pak file. Regards, Ho-Sung.
Hi, Brian. Yes vR Ops 6 has some builtin actions out of the box but they are manual actions and do not provide automation. To build an automated infrastructure, you should integrate vR Ops to... See more...
Hi, Brian. Yes vR Ops 6 has some builtin actions out of the box but they are manual actions and do not provide automation. To build an automated infrastructure, you should integrate vR Ops to an existing automation framework such as vCO. There is a 'vCO Remediation Workflow Package for vR Ops' that utilizes vR Ops SNMP Trap Plug-In. (Cloud Management Marketplace | Solution Exchange) Or you can use a 'REST Plug-In for vRealize Operations Manager Outbound Alerts' if you own a REST-enabled automation framework. (http://pubs.vmware.com/vrealizeoperationsmanager-6/topic/com.vmware.ICbase/PDF/vrealize-operations-manager-60-cust-admin… / p.120) Regards, Ho-Sung.
Very glad to hear the good news. Thank you Boris_Erblat, I will be waiting for the update :smileygrin: Regards, Ho-Sung
Hi, folks. VMs has Datastores as their child object in the vCenter Adapter. But after config a Hyperic adatper instance, such relationships are lost. For example, - Before the problem : V... See more...
Hi, folks. VMs has Datastores as their child object in the vCenter Adapter. But after config a Hyperic adatper instance, such relationships are lost. For example, - Before the problem : VM(vCenter Adapter) - Datastore(vCenter Adapter) - After the problem : VM(vCenter Adapter) - OS(Hyperic Adapter) - What I expected : VM(vCenter Adapter) - OS(Hyperic Adapter) and Datastore(vCenter Adapter) = vC Ops 5.8.x way Did anyone experience this problem? Regards, Ho-Sung