Eventually, we all have an accident or get hacked. And when we do, backups are often the only way to recover. Backups are cheap and easy; make sure you are backing up all of your personal information (such as family photos) on a regular basis.
Monthly Archives: December 2016
Ransomware
This post was originally published on this site
Ransomware is a special type of malware. Once it infected your computer, it encrypts all of your files and demands you pay a ransome if you want your files back. Be suspicious of any emails trying to trick you into opening infected attachments or click on malicious links, common sense is your best defense. In addition. backups are often the only way you can recover from ransomware.
Vmware ESX 5.5 cannot see Lun on HP P2000 Storage System
This post was originally published on this site
hi folks,
we have deployed vsphere 5.5 that includes 2 HP DL380G7 Servers and HP MSA P2000 Storage as our SAN. it worked fine for about 1 year but yesterday we had a power failure. there are 2 LUNs created and mapped to hosts. Lun 11 is accessible and working perfect. but hosts in cluster cannot see the LUN number 21. however if i try to directly connect to esx Servers using vmware vsphere client and add storage, i can see the storage and i can add it. the problems is why i cannot see Disk inside Vcenter. and why when i try to add it directly inside client (connected to ESX and not vmware Vcenter) it asks for format and wipe of all data. even inside Vcenter i can see Path and devices are working fine and can see the space and Partition format assigned to disk. there are some errors inside vmkernel which i add below.
2016-12-28T11:57:31.704Z cpu16:35861 opID=cbd8c8a1)VC: 2064: Refresh open volume time 1 msec
2016-12-28T11:57:31.858Z cpu10:34074 opID=89cd1ef9)World: 14296: VC opID hostd-8f35 maps to vmkernel opID 89cd1ef9
2016-12-28T11:57:39.220Z cpu14:33444)lpfc: lpfc_rportStats:3778: 0:(0) Compression log for fcp target 0, path is ok, TMGMT: abts=0, tgt_rst=1, lun_rst=0
2016-12-28T11:57:40.016Z cpu15:34075)World: 14296: VC opID hostd-90f1 maps to vmkernel opID 97d2fbe2
2016-12-28T11:58:00.010Z cpu7:34437)World: 14296: VC opID hostd-2138 maps to vmkernel opID 34571439
2016-12-28T11:58:06.793Z cpu7:64688)WARNING: NMP: nmp_IssueCommandToDevice:3488: I/O could not be issued to device “naa.600c0ff000142c3a4d129e5701000000” due to Not found
2016-12-28T11:58:06.793Z cpu7:64688)WARNING: NMP: nmp_DeviceRetryCommand:133: Device “naa.600c0ff000142c3a4d129e5701000000”: awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.
2016-12-28T11:58:06.793Z cpu7:64688)WARNING: NMP: nmp_DeviceStartLoop:723: NMP Device “naa.600c0ff000142c3a4d129e5701000000” is blocked. Not starting I/O from device.
2016-12-28T11:58:07.708Z cpu6:34789)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:07.708Z cpu11:63301)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:07.708Z cpu12:33480)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device “naa.600c0ff000142c3a4d129e5701000000” – issuing command 0x412e835bd200
2016-12-28T11:58:07.708Z cpu12:33480)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device “naa.600c0ff000142c3a4d129e5701000000” – failed to issue command due to Not found (APD), try again…
2016-12-28T11:58:07.708Z cpu12:33480)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device “naa.600c0ff000142c3a4d129e5701000000”: awaiting fast path state update…
2016-12-28T11:58:08.708Z cpu6:35827)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:08.708Z cpu8:63245)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:08.708Z cpu19:64603)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device “naa.600c0ff000142c3a4d129e5701000000” – issuing command 0x412e835bd200
2016-12-28T11:58:08.708Z cpu19:64603)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device “naa.600c0ff000142c3a4d129e5701000000” – failed to issue command due to Not found (APD), try again…
2016-12-28T11:58:08.708Z cpu19:64603)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device “naa.600c0ff000142c3a4d129e5701000000”: awaiting fast path state update…
2016-12-28T11:58:09.708Z cpu6:35830)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:09.708Z cpu17:61464)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:10.708Z cpu6:32800)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:10.708Z cpu22:60638)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:11.708Z cpu6:35830)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:11.708Z cpu5:59848)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:12.708Z cpu6:34789)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:12.708Z cpu16:64462)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:13.708Z cpu6:33663)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:13.708Z cpu3:32998)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:14.708Z cpu6:34789)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:14.708Z cpu10:64065)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:15.708Z cpu6:35837)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:15.708Z cpu4:63301)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:16.708Z cpu6:35830)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:16.708Z cpu0:63245)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:17.708Z cpu6:32800)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:17.708Z cpu12:61464)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:18.708Z cpu6:35836)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:18.708Z cpu22:60638)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
2016-12-28T11:58:19.708Z cpu6:34789)lpfc: lpfc_scsi_cmd_iocb_cmpl:2157: 0:(0):3271: FCP cmd xa3 failed <0/21> sid x010300, did x010000, oxid xffff SCSI Chk Cond – Not Ready: Data(x2:x2:x4:x3)
2016-12-28T11:58:19.708Z cpu5:59848)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:690: Path “vmhba2:C0:T0:L21” determined to be in unexpected NOT READY state when probed (0x2/0x4/0x3).
Kids and Family Members
This post was originally published on this site
If you have children visiting or staying with family members (such as grandparents), make sure the family members know your rules concerning technology that your kids must follow. Just because your kids leave the house does not mean the rules about what they can do online change.
Forwarding Emails
This post was originally published on this site
When you forward an email to others or copy new people to an email thread, review all the content in the entire email and make sure the information contained in it is suitable for everyone. It is very easy to forward emails to others, not realizing there is highly sensitive information in the bottom of the email that people should not have access to.
Secure Your Home Wi-Fi Network
This post was originally published on this site
Be aware of all the devices connected to your home network, including baby monitors, gaming consoles, TVs, appliances or even your car. Ensure all those devices are protected by a strong password and/or are running the latest version of their operating system.
Detecting Fraud
Invalid CPU allocation for high latency Sensitive VM
This post was originally published on this site
cpu98:20280380)WARNING: Sched: 1677: Group host/user: Invalid CPU allocation for high latency Sensitive VM vmm0:xvuyehj. reserve CPU fully (current min: 0)
2016-12-07T12:05:11.896Z cpu124:33133)WARNING: CpuMetrics: 1268: insufficient CPU entitlement for group 37785920 vm.20006086 demand= 32134 MHz, entitlement= 31532 MHz
there is a VM which is of SAP HANA alloated with 1tb ram , which hangs quite frequently and reboots itself
these are some snips from vmkernel where am unable to interpret or get any information in regards to the message above , has anyone come across this
What is Malware
This post was originally published on this site
Malware is software–a computer program–used to perform malicious actions. In fact, the term malware is a combination of the words malicious and software. Cyber criminals install malware on your computers or devices to gain control over them or gain access to what they contain. Once installed, these attackers can use malware to spy on your online activities, steal your passwords and files, or use your system to attack others.