Photon OS – no ping and no ICMP replies? Other quick hints on Photon too.

Updated – July 9th, 2020 with password policy and complexity.

So I’ve been playing with Photon OS recently with a few of our Cloud Provider solutions, very nice lightweight appliance.

However, one thing that surprised me is the minimal/lightweight install does not have ping installed nor can you ping it (ICMP echo replies). In my opinion, this is a basic function for any type of network troubleshooting. I understand it’s minimal…but go cut something else out. 🙂

So how do we set up some basic network functions?

Setting up a Static IP

cd to /etc/systemd/network

vi (or use your preferred text editor) a file called

There’s three sections required: Match, Network, and DHCP

Below is the code required:

Domains=HOSTNAME domain.local

Save it (wq!), and now it’s time to chmod the file so it can be read by the OS

chmod 644

Now we should see the correct permissions: 

Now restart the network daemon service.

systemctl restart systemd-networkd


Installing Ping on Photon OS

Pretty easy – as you can see, doesn’t exist. 

Now there’s two different versions of Photon – version 1 and 2. On version 1, it’s pretty easy – type in the following:

yum install iputils

Now for Photon 2.0 (which I’m currently using), repos are disabled by default and so I was getting a message stating “package not found” which was odd. However, digging in further, I found the repos were not enabled.

Enabling Repos so we can pull iputils

cd /etc/yum.repos.d/

I enabled three repos:




We need to edit each file and change the enabled=0 to enabled=1

Once I did this, run “tdnf repolist” and we should now see the following:

Now let’s install it!

tdnf install iputils

Now we should see the following: 

Sucess! Ping is available now, along with netstat too.

Allow ICMP echo responses

This is a change in the firewall table. By default, ICMP echo and replies are dropped.

Here are the two commands required to enable ICMP traffic:

iptables -A OUTPUT -p icmp -j ACCEPT
iptables -A INPUT -p icmp -j ACCEPT

Before I make the change on my system, I’m unable to ping

Make the iptables change….

Voila! We now get a response. 

DNS Configuration

Currently, I found a DNS issue with the vami_config_net file with a Photon 3.0 appliance deployment – it was not setting the DNS correctly and resorting to a address. Moreover, the /etc/resolv.conf file should not be modified and if it is, changes do not persist post-reboot.

Two options:

  1. Set DNS inside of the /etc/systemd/network/ network configuration file
  2. Change it under /etc/systemd/resolved.conf

Option 1 Example:



Option 2

root@vcav [ ~ ]# more /etc/systemd/resolved.conf 

# See resolved.conf(5) for details




#FallbackDNS= 2001:4860:4860::8888 2001:4860:4860::8844








Resetting the Root Password

I’ve had situations where I’ve locked myself out of a Photon instance. The process is pretty simple – follow this link:

Removing Password Expiration Policy

By default, Photon has a one year password expiration policy for accounts, including the root account. One can modify this and establish a no expiration policy, but also adjust other parameters.

From a root account, one can see the following:

root@vcd [ ~ ]# chage -l root

Last password change					: Mar 30, 2020

Password expires					: Mar 30, 2021

Password inactive					: never

Account expires						: never

Minimum number of days between password change		: 0

Maximum number of days between password change		: 365

Number of days of warning before password expires	: 7

One can modify this by using the “chage” command.

chage -m 0 root

From there, we can now see the password expiration has been removed.

root@vcd [ ~ ]# chage -l root

Last password change : Mar 30, 2020

Password expires : never

Password inactive : never

Account expires : never

Minimum number of days between password change : 0

Maximum number of days between password change : 99999

Number of days of warning before password expires : 7

Password Complexity

Photon utilizes the standard PAM modules for password complexity. For those of you in a lab environment that utilize the same password or standard password methodology, one might need to adjust this.

The configuration file is under:


We can see under this file that we have three lines –

root@usagemeter42 [ /etc/pam.d ]# more system-password 

# Begin /etc/pam.d/system-password

password    requisite     minlen=8 minclass=4 difok=4 maxsequence=0 retry=3 enforce_for_root

password    requisite    retry=3 remember=5 enforce_for_root

password    required         sha512 shadow use_authtok

# End /etc/pam.d/system-password

For me, I wanted to just disable the policy in its entirety. To do this, comment out the first line:

# Begin /etc/pam.d/system-password

#password    requisite     minlen=8 minclass=4 difok=4 maxsequence=0 retry=3 enforce_for_root

password    requisite    retry=3 remember=5 enforce_for_root

password    required         sha512 shadow use_authtok

# End /etc/pam.d/system-password

From there, one can change their password –

root@usagemeter42 [ /etc/pam.d ]# passwd

New password: 

Retype new password: 

passwd: password updated successfully

Setting the Hostname

Need help changing it from the default photon-appliance hostname?

Hostnamectl is the command for permanently changing the name – not just editing the /etc/hosts file.

hostnamectl set-hostname DanielApp-B

Reboot the system.

One last tidbit – SSHD not starting?

During some of my testing, my lab environment went bottoms up – thanks, Timo 😉

After my Photon appliances started back up, I could not SSH to them. So after some troubleshooting and help from the VMware internal team, figured out what happened.

Steps to resolve:

Log into the console and ls -l /var/vmware/skip_sshd and you can also check the status of sshd by typing “systemctl status sshd”

If the file does exist, you need to remove it. No clue why it was added when I had a hard power outage, but it did.

rm /var/vmware/skip_sshd

Now start up ssh..

systemctl start sshd

Voila! we can now see it’s started

Now, SSH works! 

Other great details on Photon commands can be found here: Photon OS Troubleshooting Guide


vSAN Specialist Exam 2VB-601 – Tips

This was on my radar from last year but did not have enough time to get this done. I sat and passed the vSAN Specialist Exam today and wanted to share my feedback and experiences on how I approached it.

Read the Exam Preparation Guide

I know this is stating the obvious, but the blueprint should be your compass on preparing for this test. It reviews the Exam Sections and what to know before taking this test. Moreover, there are 10 practice questions to gauge your level of knowledge. When I started, I tested myself and knew what areas I had to prepare further for.

Download the latest guide here.

Read Storage Hub!!!!

I cannot stress this enough – is a WEALTH of information.

I went through each section and read each pertinent area of focus. Moreover, the Storage Hub has some nice features. Did you know you can export each respective section to PDF or mark it offline?

Very nice options for travel. I read quite a bit on my iPad and highlighted things I did not know.

What’s amazing is the depth and completeness of our documentation. I learned SO much by reading through many of these detailed documents. This should be everyone’s single source of truth for all things vSAN. Our vSAN Technical Marketing and Engineering teams have done a great job of making the inner-workings of vSAN public.

Do the Hands-on Labs!

There are three great labs available:

  1. vSAN 6.6 – Getting Started
  2. vSAN 6.6 – Challenge Lab
  3. Storage Policy Based Management

They are very comprehensive and cover your typical tasks within vSAN deployments and designs.

Exam Experience

I haven’t taken any of the Specialist exams before, so this was my first experience. I thought the test was fair, and not easy but not very difficult either. If you know vSAN, you should be able to knock this out. Key factors for preparation:

  1. Ensure you know how to size an environment. This is important in real life, but you should be able to calculate raw and usable sizes on the back of a napkin.
  2. Know your FTT policies.
  3. Go build vSAN in your lab and play around with it. I think this is critical to the learning process and also passing this exam.
  4. Last of all, know how storage operates. Having a storage background *does* help here.

It’s 60 questions and you have 105 minutes to complete, which in my opinion is plenty of time. I think I went through all 60 questions in about 35 minutes or so and was able to go through again and review all of the questions.

Good luck and onward to my next challenge!


Meltdown and Spectre Vulnerabilities

25Jan2018 – Updated with latest VMware Public KB for vCloud Director info

I’m sure many of you have heard of the Intel CPU vulnerabilities and how they can impact x86 architectures – I have a feeling this is just the start of something larger too.

I’ve had many Providers reach out to me, very concerned about how this can impact a SP design, especially with virtualization.

To step back, I found this very simple depiction that was shared on Twitter that summarizes the two vulnerabilities – thank you Daniel Miessler (link to his blog article):

So, what does this mean for VMware Cloud Providers? Well, official statements are underway, but here’s what I know so far – again, this is NOT an official statement:

Further information on Spectre and Meltdown on the newly created URL:

As I see further information, I will continue to share – this impacts everyone and I have a feeling this is something we all will be dealing with for a long time.


vROps Management Pack for vCD – NOW Tenant App!

I recently did a blog on the Management Pack for vCD on vROps – great way of a vCD admin to manage their vCD solution.

VMware just released the vRealize Operation Tenant App for vCloud Director 1.0 – this now allows you to provide tenant access to their org/VDC and provide tenant-level metrics! Very excited about this.

What’s New?

  1. Tenant Admin specific views to enable Operations Management solving monitoring, troubleshooting and capacity planning use cases
  2. Provider Admin can pick and choose the tenants to whom access it to be provided
  3. Photon OS based Virtual appliance (OVA) for easier installation
  4. HTML5 Client based on VMWare Clarity

Get it here: