How to Enable SNMP on VMware ESXi 6.5 with esxcli

To enable SNMP on a VMware ESXi 6.5 host, connect to it with your favorite SSH client (I use PuTTY) and run the following commands:

esxcli system snmp set --communities public
esxcli system snmp set --enable true
esxcli network firewall ruleset set --ruleset-id snmp --allowed-all true
esxcli network firewall ruleset set --ruleset-id snmp --enabled true
/etc/init.d/snmpd restart

What each step does:

  • Sets the SNMP community string (replace public with your own).
  • Enables the SNMP agent.
  • Allows all IPs through the ESXi firewall’s SNMP ruleset, then enables that ruleset.
  • Restarts the SNMP service so the changes take effect.

If you copy these commands, make sure the options begin with two hyphens (--), not a single dash. Related: enabling SNMP on a Raspberry Pi.

Fix Schannel Fatal Alert 40 and 70 Errors (FipsAlgorithmPolicy)

Windows was logging Schannel fatal alert 40 and fatal alert 70 errors. This turned out to be related to the System cryptography: Use FIPS compliant algorithms Group Policy setting, even though that policy was disabled.

The Cause

Microsoft’s documentation says this GPO controls the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy

On the affected machine, that value was still set to 1 (FIPS mode on), despite the policy being disabled.

The Fix

I created a GPO at the workstation level with a registry preference (action: Update/Replace) on HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa that sets FipsAlgorithmPolicy to 0. After the next reboot, the machine stopped generating the Schannel errors.

Related: disabling SSL 3.0 in the SCHANNEL registry settings on IIS.

Default Usernames and Passwords for SAN, Storage and Virtualization Gear (EMC, VMware, Cisco, HP, Pure)

Here is a reference list of factory default usernames and passwords for SAN, storage, server and virtualization products from EMC, HP, Cisco, Pure Storage, VMware, Trend Micro, IBM, Citrix and others. These are the vendor-documented defaults for first login. Change them as soon as a device or appliance is deployed.

EMC Secure Remote Support (ESRS) Axeda Policy Manager Server:

Username: admin
Password: EMCPMAdm7n
EMC VNXe Unisphere (EMC VNXe Series Quick Start Guide, step 4):

Username: admin
Password: Password123#
EMC vVNX Unisphere:

Username: admin
Password: Password123#
NB You must change the administrator password during this first login.
EMC CloudArray Appliance:

Username: admin
Password: password
NB Upon first login you are prompted to change the password.
EMC CloudBoost Virtual Appliance:
https://:4444

Username: local\admin
Password: password
NB You must immediately change the admin password.
$ password
EMC Ionix Unified Infrastructure Manager/Provisioning (UIM/P):

Username: sysadmin
Password: sysadmin
EMC VNX Monitoring and Reporting:

Username: admin
Password: changeme
EMC RecoverPoint:

Username: admin
Password: admin
Username: boxmgmt
Password: boxmgmt
Username: security-admin
Password: security-admin
EMC XtremIO:

XtremIO Management Server (XMS)

Username: xmsadmin
password: 123456 (prior to v2.4)
password: Xtrem10 (v2.4+)
XtremIO Management Secure Upload

Username: xmsupload
Password: xmsupload
XtremIO Management Command Line Interface (XMCLI)

Username: tech
password: 123456 (prior to v2.4)
password: X10Tech! (v2.4+)
XtremIO Management Command Line Interface (XMCLI)

Username: admin
password: 123456 (prior to v2.4)
password: Xtrem10 (v2.4+)
XtremIO Graphical User Interface (XtremIO GUI)

Username: tech
password: 123456 (prior to v2.4)
password: X10Tech! (v2.4+)
XtremIO Graphical User Interface (XtremIO GUI)

Username: admin
password: 123456 (prior to v2.4)
password: Xtrem10 (v2.4+)
XtremIO Easy Installation Wizard (on storage controllers / nodes)

Username: xinstall
Password: xiofast1
XtremIO Easy Installation Wizard (on XMS)

Username: xinstall
Password: xiofast1
Basic Input/Output System (BIOS) for storage controllers / nodes

Password: emcbios
Basic Input/Output System (BIOS) for XMS

Password: emcbios
EMC ViPR Controller :
http://ViPR_virtual_ip (the ViPR public virtual IP address, also known as the network.vip)

Username: root
Password: ChangeMe
EMC ViPR Controller Reporting vApp:
http://:58080/APG/

Username: admin
Password: changeme
EMC Solutions Integration Service:
https://:5480

Username: root
Password: emc
EMC VSI for VMware vSphere Web Client:
https://:8443/vsi_usm/

Username: admin
Password: ChangeMe

Note:
After the Solutions Integration Service password is changed, it cannot be modified.
If the password is lost, you must redeploy the Solutions Integration Service and use the default login ID and password to log in.

EMC Avamar Backup Service

username: admin
password: changeme
openSSH key
ssh-agent bash
ssh-add ~admin/.ssh/admin_key
Password: P3t3rPan

Pure Storage Arrays

Username: pureuser
Password: pureuser
Cisco Integrated Management Controller (IMC) / CIMC / BMC:

Username: admin
Password: password
Cisco UCS Director:

Username: admin
Password: admin
Username: shelladmin
Password: changeme
Hewlett Packard P2000 StorageWorks MSA Array Systems:

Username: admin
Password: !admin (exclamation mark ! before admin)
Username: manage
Password: !manage (exclamation mark ! before manage)
IBM Security Access Manager Virtual Appliance:
Username: admin
Password: admin
VCE Vision:

Username: admin
Password: 7j@m4Qd+1L
Username: root
Password: V1rtu@1c3!
VMware vSphere Management Assistant (vMA):

Username: vi-admin
Password: vmware
VMware Data Recovery (VDR):

Username: root
Password: vmw@re (make sure you enter @ as Shift-2 as in US keyboard layout)
VMware vCenter Hyperic Server:
https://Server_Name_or_IP:5480/

Username: root
Password: hqadmin
https://Server_Name_or_IP:7080/

Username: hqadmin
Password: hqadmin
VMware vCenter Chargeback:
https://Server_Name_or_IP:8080/cbmui

Username: root
Password: vmware
VMware vCenter Server Appliance (VCSA) 5.5:
https://Server_Name_or_IP:5480

Username: root
Password: vmware
VMware vCenter Operations Manager (vCOPS):

Console access:

Username: root
Password: vmware
Manager:
https://Server_Name_or_IP

Username: admin
Password: admin
Administrator Panel:
https://Server_Name_or_IP/admin

Username: admin
Password: admin
Custom UI User Interface:
https://Server_Name_or_IP/vcops-custom

Username: admin
Password: admin
VMware vCenter Support Assistant:
http://Server_Name_or_IP

Username: root
Password: vmware
VMware vCenter / vRealize Infrastructure Navigator:
https://Server_Name_or_IP:5480

Username: root
Password: specified during OVA deployment
VMware ThinApp Factory:

Username: admin
Password: blank (no password)
VMware vSphere vCloud Director Appliance:

Username: root
Password: vmware
VMware vCenter Orchestrator :
https://Server_Name_or_IP:8281/vco – VMware vCenter Orchestrator
https://Server_Name_or_IP:8283 – VMware vCenter Orchestrator Configuration

Username: vmware
Password: vmware
VMware vCloud Connector Server (VCC) / Node (VCN):
https://Server_Name_or_IP:5480

Username: admin
Password: vmware
Username: root
Password: vmware
VMware vSphere Data Protection Appliance:

Username: root
Password: changeme
VMware HealthAnalyzer:

Username: root
Password: vmware
VMware vShield Manager:
https://Server_Name_or_IP

Username: admin
Password: default
type enable to enter Privileged Mode, password is ‘default’ as well
Teradici PCoIP Management Console:

The default password is blank
Trend Micro Deep Security Virtual Appliance (DS VA):

Login: dsva
password: dsva
Citrix Merchandising Server Administrator Console:

User name: root
password: C1trix321
VMTurbo Operations Manager:

User name: administrator
password: administrator
If DHCP is not enabled, configure a static address by logging in with these credentials:
User name: ipsetup
password: ipsetup
Console access:
User name: root
password: vmturbo

How to Install the Check_MK Agent on Red Hat / CentOS 6 Linux

Here are the simple steps to install the Check_MK agent on a Red Hat (or CentOS) 6.x Linux server. Replace %checkmkurl% with the address of your Check_MK server.

1. Install xinetd and Add the Agent Service

Save the Check_MK xinetd config file as /tmp/xinetd.conf, then:

yum -y install xinetd
cd /tmp
cp xinetd.conf /etc/xinetd.d/check_mk

2. Download and Install the Agent

wget http://%checkmkurl%/check_mk/agents/check_mk_agent.linux
cp check_mk_agent.linux check_mk_agent
chmod 776 check_mk_agent
cp /tmp/check_mk_agent /usr/bin/check_mk_agent

3. Add the Inventory Plugin

mkdir /usr/lib/check_mk_agent
mkdir /usr/lib/check_mk_agent/plugins
cd /usr/lib/check_mk_agent/plugins
wget http://%checkmkurl%/check_mk/agents/plugins/mk_inventory.linux
cp mk_inventory.linux mk_inventory.sh
chmod 776 mk_inventory.sh

4. Restart xinetd

/etc/init.d/xinetd restart

Running Debian? See installing the Check_MK agent on Debian Linux.

Check_MK Agent xinetd Configuration File (/etc/xinetd.d/check_mk)

This is the xinetd configuration for the Check_MK Linux agent. Save it as /etc/xinetd.d/check_mk. It runs the agent on TCP port 6556 whenever your monitoring server connects. Before you use it, replace %YOUR IP ADDRESSES HERE!!!% on the only_from line with the IP address(es) of your monitoring server, so no one else can query the agent.

For the full install steps, see installing the Check_MK agent on Red Hat Linux.

# This file is part of Check_MK (GNU General Public License v2).
# Copyright Mathias Kettner 2014. The official homepage is at http://mathias-kettner.de/check_mk.

service check_mk
{
type = UNLISTED
port = 6556
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/bin/check_mk_agent

# If you use fully redundant monitoring and poll the client
# from more then one monitoring servers in parallel you might
# want to use the agent cache wrapper:
#server = /usr/bin/check_mk_caching_agent

# configure the IP address(es) of your Nagios server here:
only_from = 127.0.0.1 %YOUR IP ADDRESSES HERE!!!%

# Don't be too verbose. Don't log every check. This might be
# commented out for debugging. If this option is commented out
# the default options will be used for this service.
log_on_success =

disable = no
}

Teaching Coding in a Fiji Village: A Proposal to Reverse the Brain Drain

Hi, my name is Harlan Stanley, and I have a project in mind that I’d like to talk to you about.

My family has ties to Fiji. We visit home regularly, though not as often as we’d like, and we hope to move there permanently. When we do, I want to share my knowledge of technology and my skill set. I don’t have a lot of financial resources, but I do have an idea.

The Challenge: Few Jobs, Fewer Skilled Workers

Fiji has very few jobs and even fewer skilled workers. The economic situation is poor at best, and no one really knows whether it’s getting better.

Life in the Village

Traditionally, most Fijians grow up in a very rural environment. We’ll call it “the Village.”

In the Village you live with your mom and dad, or a relative who cares for you. You attend primary school, and you might go on to secondary school (high school). Depending on your studies, your finances, or whether you can find a job, you go on to college or a technical institute, or you go to work for a resort. Those who can’t find jobs end up depending on government assistance or on the street. Others return to the Village to become farmers or fishermen, or to work at a resort.

For a land celebrated all over the world as “paradise,” the outlook for most of these occupations is pretty dismal. You’ll probably make about one US dollar per hour. Yes, that’s right: $1.00 per hour, if that. The average salary for a government employee is about $7,000 USD.

The Real Problem: Brain Drain

Education itself isn’t the problem. It’s someone’s future. Once people become educated, they see the light: they become doctors, teachers, mechanics, plumbers, even lawyers. But why would any of these professionals stay in the Village? There’s no future for them there. Only primary school teachers, fishermen and farmers can make a living in the Village.

So we have a brain drain. How can we fix it?

The Idea: Bring Technology Careers to the Village

We could introduce a new field: technology. Computer programming, application development, database management and other careers that don’t depend on location would let someone earn a decent wage while staying in the Village.

Start with the Kids

I propose we start with the children. Kids have an insatiable thirst for knowledge. They want to know how things work, why they work, and how to break them, and they pick up a new “language” easily. Let’s introduce Village kids to programming, any programming, and teach them a marketable skill. Instead of depending on a local marketplace, they could work remotely and sell their skills to the world.

Picture a 10-year program. We start teaching kids at around 7 to 10 years old how to type, then work them into basic programming, database management, networking and IT management.

The Computer Lab

We would build a small, solar-powered computer lab with an internet connection and a backup generator, and set up three levels of classes:

  1. Typing and basic computer skills.
  2. An introduction to programming languages and writing programs.
  3. Full-on “we’re writing code, here’s how to do it, now go kick butt.”

A room of 50 computers of any caliber gets hot, and you can’t air-condition the entire building. Instead, we’d use thin clients connected to a VM cluster running virtual desktops, so only the server room needs to be kept moderately cool. Thin clients also make it easy to expand or shrink classes as needed.

We’d bring in a couple of teachers on a work, vacation or sabbatical program to live in the Village for up to a year at a time and share everything they know. A visitor’s visa is easy to get and can be extended to one year; beyond that, you have to leave the country for a night or two.

Funding the Project

How do we pay for it? Do we pay the teachers a salary? Where do the computers come from? Who pays for the generator fuel?

I expect we could find generous angel investors to fund this as a 10-year, and possibly 20-year, project. Along the way we’d learn what happens when you take a group of people with limited access to technology and give them a skill they can use anywhere in the world.

Who Takes Part

I’m not expecting every child to take part. Some will still want to be fishermen, doctors, teachers and farmers. But there are kids whose talent has historically gone untapped, and they can make a difference for their country and their Village.

How I Came Up with This Idea

The first time I went to the Village, I was struck by how remote it was and in awe of its untouched natural environment. I thought, wow, we could set up a backpackers’ resort here so everyone could come see this place. Then, on my most recent trip, I saw other backpacker and “exclusive” resorts starting up around the area. I began to think: with so many resorts, we’re training the locals to be subservient, and that’s not good. I visited one of the more exclusive resorts and spoke with the owner at length, and I decided there was no way I would become like that person. It’s not in my heart or my mind.

Then I thought about all the infrastructure these resorts need: all the materials imported into the most remote parts of the world just so someone can see them in comfort. That model isn’t sustainable without a constant influx of money. For example, Laucala Island Resort uses over 80,000 liters of fuel every month. Fiji isn’t an oil-producing nation, and most of its electricity comes from diesel generators. Garment factories import cloth and machines so workers can make shirts for very low wages in poor conditions, often working long hours for slave-driving bosses.

The software industry, on the other hand, looks for creative minds, can be done anywhere, has a very open structure, and can be very profitable when it succeeds. We’d only be importing the hardware to do the work, not materials to be processed.

Once we have several successful graduates, they can help teach the younger generation. With internet connectivity, the learning process can sustain itself, and the project can become self-sufficient.

Will You Help?

Exchange 2010: Where to Change Message Size Limits to Allow Larger Attachments

To allow larger attachments in Microsoft Exchange 2010, you may need to raise the message size limit in several places. A lower limit at any one of them will still block the message, so check each of these in the Exchange Management Console.

1. Organization Transport Settings

Organization Configuration > Hub Transport > Global Settings tab > Transport Settings

2. Receive Connectors

Server Configuration > Hub Transport > select a Hub Transport server > Receive Connectors > select a connector > Properties

3. Send Connectors

Organization Configuration > Hub Transport > Send Connectors > select a connector > Properties

4. Individual Mailboxes

Recipient Configuration > Mailbox > select a mailbox > Properties > Mail Flow Settings > Message Size Restrictions

5. Distribution Groups

Recipient Configuration > Distribution Group > select a group > Properties > Mail Flow Settings > Message Size Restrictions

6. Global Settings in ADSI Edit

Use ADSI Edit to connect to the Configuration container, then go to Configuration > Services > Microsoft Exchange > YourOrgName > Global Settings > Message Delivery > Properties and check these values:

  • delivContentLength
  • submissionContentLength
  • msExchRecipLimit

7. Transport Rules

Organization Configuration > Hub Transport > Transport Rules. Check for any rule that restricts attachment or message size.

Related Microsoft article: Mailbox Size Limits Are Not Enforced in a Reasonable Period of Time. See also enabling an internal SMTP relay in Exchange 2010.

How Windows DNS Scavenging Works (and What It Won’t Remove)

DNS scavenging is a Windows DNS Server feature that removes expired (stale) resource records based on their timestamps. Here are the key points to know before you rely on it.

  • Scavenging is not enabled by default. You have to turn it on.
  • It only removes dynamically updated records that have reached their timestamp age.
  • It will not remove static records, the ones you create by hand, unless you run dnscmd /AgeAllRecords. That command stamps those records with a timestamp, which makes them eligible for scavenging, so use it with care.

Viewing a Record’s Timestamp

  • Windows Server 2003: in the DNS console, open the View menu and select Advanced. Then open a record’s properties to see its timestamp.
  • Windows Server 2008 and newer: the timestamp appears as its own column in the DNS console.

Vulnerability in SSL 3.0 Could Allow Information Disclosure: Disable It with Group Policy or IE Settings

A vulnerability in SSL 3.0 could allow information disclosure. The fix is to turn off SSL 3.0 and use TLS instead. Here are two ways to do that on Windows clients: centrally with Group Policy, or per machine in Internet Explorer. To disable SSL 3.0 on the server side, see how to disable SSL 3.0 on Microsoft IIS.

Option 1: Disable SSL 3.0 with Group Policy

Use the Turn off Encryption Support setting to disable SSL 3.0 and enable TLS 1.0, TLS 1.1 and TLS 1.2 across the domain.

  1. Open Group Policy Management.
  2. Right-click the Group Policy Object to modify and select Edit.
  3. In the Group Policy Management Editor, browse to Computer Configuration > Administrative Templates > Windows Components > Internet Explorer > Internet Explorer Control Panel > Advanced Page > Turn off Encryption Support.
  4. Double-click Turn off Encryption Support and click Enabled.
  5. In the Options pane, set Secure Protocol combinations to Use TLS 1.0, TLS 1.1, and TLS 1.2.
  6. Click OK.

Option 2: Disable SSL 3.0 in Internet Explorer

To change the protocol versions Internet Explorer uses for HTTPS on a single computer:

  1. On the Internet Explorer Tools menu, click Internet Options.
  2. Click the Advanced tab.
  3. In the Security category, uncheck Use SSL 3.0 and check Use TLS 1.0, Use TLS 1.1 and Use TLS 1.2 (if available).
  4. Click OK, then exit and restart Internet Explorer.

Want to check whether a server still accepts SSLv3? Here’s a quick way to test for SSLv3.

How to Auto-Redirect a Web Page with HTML or JavaScript

There are two easy ways to send visitors from one web page to another automatically: an HTML meta refresh tag, or a few lines of JavaScript.

Redirect with an HTML Meta Refresh

This page points the browser to a different page after 2 seconds. The number in content is the delay in seconds. It’s good practice to include a manual link in case the browser doesn’t follow the redirect.

<html>
<head>
<title>A web page that points a browser to a different page after 2 seconds</title>
<meta http-equiv="refresh" content="2; URL=http://example.com/services/computing/">
<meta name="keywords" content="automatic redirection">
</head>
<body>
If your browser doesn't automatically go there within a few seconds,
you may want to go to
<a href="http://example.com/">the destination</a>
manually.
</body>
</html>

Redirect with JavaScript

You can also do it with JavaScript. This example opens the new site in a new browser window after a 4.5-second (4500 ms) delay:

<script type="text/javascript">
  window.setTimeout('window.open("http://example.com/","newsite")', 4500);
</script>