Nutanix Prism Rest API V2.
This does not work.
Nutanix Prism Rest API V2.
This does not work.
I had the chance to attend vSphere 6.5 ICM training at VMware office in Bangalore recently. My last ICM was 5 or 5.1 some years ago. The world does not need another “what’s new in vSphere 6.5” post. I took some notes during the training and I thought I would dump it here anyway.
1.VCSA 6.5 is based on Photon OS and not SLES as before. Photon OS began its life as VMware’s customized for container Linux distro that does not depend directly on any other distro.
2.vSphere Update Manager (VUM) is now apart of VCSA 6.5. Before 6.5, you have to run it on Windows.
3.Dump Collector is also apart of VCSA (not sure from which version).
4.VCSA 6.5 has a management portal which can be accessed at VCSA_IP:5480. You can create a backup from here and restore from it using the installer.
5.You can still use service-control to manage vCenter services from the command. From 6.5, you can also manage vCenter Services from the Web client.
6.Speaking of Web Client, there are two web clients. The old vSphere Web Client (Flash/Flex client) and the new vSphere Client (HTML 5).
7.The legacy C# client is not available for 6.5
8.During the training, I used the HTML 5 client as much as possible. It has limited functionality right now. I found the following not working:
You cannot increase datastore
It is hard coded to create VMFS5 type data store only
You cannot create NFS datastore
You can do host migration only
The full set of features available in the HTML 5 client:
9.There is a new version of VMFS, VMFS 6. ESXi 6.5 can create VMFS 5 and 6. VMFS6 supports 1 MB and 512 MB block sizes.
10.In addition to LSI Logic SAS, BusLogic, PVSCSI and AHCI SATA, ESXi 6.5 has virtual NVMe storage controller for virtual machine.
11.Support for 32 Gbps HBA in ESXi 6.5
12.VCSA 6.5 has native HA – Enabling it deploys in passive mode and quorom appliance
13.DRS evenly distributes VMs
I was not aware of the following:
1.vpxa is baked into ESXi
2.SRM can use vSphere Replication.
3.VIB = vSphere Infrastructure Bundle.
4.Enhenced Linked mode since vSphere 6.0
5.e1000e virtual NIC since vSphere 5.0 with HW version 8.
6.Enhenced Linked mode since 6.0
7.iSCSI HBA- The configuration is done from the HBA BIOS.
8.ToE NIC- The configuration is done from vSphere client.
9.Starting with vSphere 6.0, there are two Lockdown Modes – Normal and Strict. (KB 1008077)
Run it as root or with sudo to be able to see all sessions. The options are case insensitive. For example, tcp or TCP are accepted.
TLDR: List all network connections and repeat it every second.
lsof -i -r1
1.List all network connections.
2.List all network connections without resolving IP and port number to names.
lsof -i tcp
lsof -i udp
7.List all network connections associated with a specific host.
lsof -i @IP_ADDRESS lsof -i @HOSTNAME
8.List all network connections associated with a specific port.
lsof -i :PORT_NUMBER
lsof -i :25 lsof -i :25,22 lsof -i :1-1023 lsof -i :ssh
Now, let’s combine the options.
9.List all connections related to TCP port 22.
lsof -i tcp:22
10.List all connections related to a host and a port.
lsof -i @HOSTNAME:22
11.List all connections related to a host, a port and TCP.
lsof -i tcp@HOSTNAME:22
12.Repeat the command every 2 seconds whether or not there are matching sessions.
lsof -i tcp@HOSTNAME:22 -r2
13.Repeat that command every 2 seconds only as long as there are matching sessions.
lsof -i tcp@HOSTNAME:22 +r2
So far, we have not considered the state of the sessions whether they are listening, idle or closed. We can combine -i with -s [p:s] to include the state of the session.
14.List all TCP connections with state LISTEN
lsof -iTCP -sTCP:LISTEN
15.List all TCP connections with state other than LISTEN
lsof -iTCP -sTCP:^LISTEN
According to the man page, these are the possible states:
State names vary with UNIX dialects, so it’s not possible to provide a complete list. Some common TCP state names are: CLOSED, IDLE, BOUND, LISTEN, ESTAB‐LISHED, SYN_SENT, SYN_RCDV, ESTABLISHED, CLOSE_WAIT, FIN_WAIT1, CLOSING, LAST_ACK, FIN_WAIT_2, andTIME_WAIT. Two common UDP state names are Unbound and Idle.
“lsof -iTCP -sTCP:LISTEN” doesn’t work for me. It complains “lsof: no UDP state names available: UDP:Idle”.
This means that this dialect of UNIX which is Linux, where I ran the command, does not support UDP state.
There is very little I can find about vmkvsitools on the internet. VMware document says “vmkvsitools is intended for use with VMware Technical Support. Do not use vmkvsitools to manage your system.”. But we normally don’t care as long as we know what we are doing, do we?
The following commands are available under vmkvsitools in ESXi 6.0 U1.
vmkvsitools usage: vmkvsitools [options] [function] [arguments] or [function] [arguments] Options: --cache, -c Perform the operation on a given VSI cache file Functions: lspci ps hwclock vmware irqinfo bootOption amldump pci-info pidof userspaceof vdu lsof vdf pkill pgrep uptime
You can run them using “vmkvsitools function”. For example-
vmkvsitools hwclock 04:26:29 07/17/2017 UTC
You can also run them directly by typing just the command as they are symblinked from /bin.
ls -l /bin | grep vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 amldump -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 bootOption -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 hwclock -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 irqinfo -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 lsof -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 lspci -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 pgrep -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 pidof -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 pkill -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 ps -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 uptime -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 vdf -> /bin/vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 vdu -> /bin/vmkvsitools -r-xr-xr-x 1 root root 75868 Sep 16 2015 vmkvsitools lrwxrwxrwx 1 root root 16 Sep 16 2015 vmware -> /bin/vmkvsitools
(Get-WmiObject -Namespace root\wmi -Class MSiSCSIInitiator_MethodClass).iSCSINodeName