![]() ![]() Please message the moderators and we'll pull it back in. If you make a post and then can't find it, it might have been snatched away. The spam filter can get a bit ahead of itself. To get flair with your certification level send a picture of your certificate with your Reddit username in the picture to the moderators. If you are an employee, please PM one of the moderators that has a VMware logo for verification instructions and we will add it to yours as well! The VMware logo icon following a username indicates that this user is a VMware employee. Specify your problems/needs, technical requirements, and objectives clearly. When asking for assistance or advice, please give the community sufficient information to work with. When asking for technical support, please specify the specific VMware product(s) and version(s) you are working with. While discussion of virtualization concepts in general is appropriate, requesting technical help for non-VMware products is off-topic. Posts that fail to meet these guidelines may be locked or removed: Vulgarity and hostility towards other users will not be tolerated.ĭon't post brain dumps for certification exams. Want to promote something within the community? Message the mods first with your proposal, and we'll decide if it's too spammy or not.ĭon't be a jerk. Brazen marketing material is also generally unwelcome. within a short period of time will be considered spam. Repeatedly submitting links to the same blog/YouTube channel/etc. Don't submit links to blogspam or other low-quality content. Spammers will be banned this sub will not become a marketing cesspit for vendors. Off-topic posts may be locked or removed. Keep post submissions relevant to VMware. Support requests involving Mac OS on unsupported hardware (not a Mac) or software (VMware Workstation or VMware Player) will be removed, and will result in a ban. ![]() This includes discussion of 'unlocker' or other methods used to violate the Mac OS EULA by running Mac OS on non-Apple hardware. Expect posts facilitating or promoting piracy to be removed. Once the vSphere Alarm has been configured, you can refer to the Github repo for the deployment instructions and further function customizations based on. It is just that the vsphere web-client somehow pulls wrong value and generates warnings based on that value.Have a technical question? Just make a self post!ĭiscussion of piracy methods will not be permitted. To use the example, simply setup a basic vSphere Alarm using the Datastore Disk Usage trigger and setting the value to something that can easily be triggered such as 5 in the example below. In order to verify all of this I logged in with SSH on one of the hosts and verified that the datastore size is indeed ~1.4. If I rescan all storage adapters on the hosts, it will show a correct value of ~1.4TB again but If i click the Refresh button it will revert to 1TB again. When I checked the datastore it had 1TB of space, as if I never increased it. The very next day I've noticed a Datastore usage on disk alarm in the web client. ![]() Originally it had 1TB of storage and from the MSA Array I increased it at 1.4TB, and after that I increased its capacity from the vsphere web client. through the vcenter/vSphere API, meaning that the guest servers disk usage can be checked. The particular datastore in question (MSA_VD005) is located on HP MSA Storage. /main/projects/vmware-alarm-sender-for-nagios/. After I increased it's capacity on 1.4TB the next day it reverted back to 1TB. On the vsphere web client I have a strange problem with one of my datastores as it's displayed capacity is incorrect. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |