NSX troubleshooting commands

summarize-dvfilter
vsipioctl
nsxcli

MS Windows 10 ISO

https://www.microsoft.com/en-us/software-download/windows10ISO

Configure Cisco SG300 Switch Layer 3 Mode

https://www.bytesizedalex.com/configure-cisco-sg300-switch-layer-3-mode/

The Cisco SG300 switch series can act as a standard layer 2 switch or be enabled for layer 3 functionality. Typically the switch will come in layer 2 mode (also called switch mode in the CLI). There are a couple of ways layer 3 functionality can be enabled and I will demonstrate them both below.



Command Line Configuration

To configure the SG300 to layer 3 or router mode through the command line is very easy. Log in through your SSH client of choice and leverage the ‘set system mode’ command. Here you see I have entered part of the command and then hit enter so that it shows the possible options for command completion.


SG300-20#set system mode
   router               System will run as a IP router
   switch               System will run as a switch


In our case, we want to enable router mode which is of course layer 3 functionality.


SG300-20#set system mode router

ESXi update over internet

Sources:
http://www.virtubytes.com/2017/07/10/online-upgrade-esxi-6-5-using-esxcli/
https://cloudhat.eu/update-esxi-6-5-command-line/


esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | grep -
i ESXi-6.5 | grep 201811

ESXi-6.5.0-20181104001-standard   VMware, Inc.  PartnerSupported  2018-11-30T06:47:01  2018-11-30T06:47:01
ESXi-6.5.0-20181104001-no-tools   VMware, Inc.  PartnerSupported  2018-11-30T06:47:00  2018-11-30T06:47:00
ESXi-6.5.0-20181101001s-no-tools  VMware, Inc.  PartnerSupported  2018-11-30T06:47:00  2018-11-30T06:47:00
ESXi-6.5.0-20181103001-standard   VMware, Inc.  PartnerSupported  2018-11-30T06:47:00  2018-11-30T06:47:00
ESXi-6.5.0-20181101001s-standard  VMware, Inc.  PartnerSupported  2018-11-30T06:47:00  2018-11-30T06:47:00
ESXi-6.5.0-20181103001-no-tools   VMware, Inc.  PartnerSupported  2018-11-30T06:47:00  2018-11-30T06:47:00


esxcli software profile update -p ESXi-6.5.0-20181104001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

ESXi NIC information

Run this command to check if the legacy driver "ixgbe" has been loaded for 10 Gigabit Network card: /usr/lib/vmware/vm-support/bin/nicinfo.sh | less

You see output:

NIC: vmnic4

NICInfo:
Advertised Auto Negotiation: false
Advertised Link Modes: 10000BaseX/Full
Auto Negotiation: false
Cable Type: FIBRE
Current Message Level: -1
Driver Info:
NICDriverInfo:
Bus Info: 0000:04:00:0
Driver: ixgbe (or similar)
Firmware Version: 0x80000838
Version: 1.0.0.0

Dohoda o provedeni prace

https://muj-pravnik.cz/dohoda-provedeni-prace-2018-vzor-ke-stazeni/


https://www.legito.cz/dohoda-o-provedeni-prace?ref=mujpravnik&utm_source=muj-pravnikcz

Skyline - collected data

Before sending collected data to VAC, Skyline Collector (ccf-collector) store cache files to local.
These cache files (formatted by JSON) are located under "/usr/local/skyline/ccf/output" directory. These cache files are compressed in gzip format.
For example, output_<TIMESTAMP>_Topology.json.gz is a full topology data of endpoints.
These files are retained until the number of total files reaches 1000 OR the size of total files reaches 500 MB.

Password expires in X days notification in web client

Password expires in X days notification in web client

This is configurable as part of the vSphere Web (Flex) / H5 (HTML) Client configuration

Web Client - /etc/vmware/vsphere-client/webclient.properties

H5 Client - /etc/vmware/vsphere-ui/webclient.properties

The default is 30 days

# The number of days before the notification about expiring password appears.

sso.pending.password.expiration.notification.days = 30

You'll probably need to restart the service for the change to take affect

MultiNIC vMotion

Posílám info k MultiNIC

AdvSystemSettings	Default	Tunning	Desc
Migrate.VMotionStreamHelpers	0	8	Number of helpers to allocate for VMotion streams
Net.NetNetqTxPackKpps	300	600	Max TX queue load (in thousand packet per second) to allow packing on the corresponding RX queue
Net.NetNetqTxUnpackKpps	600	1200	Threshold (in thousand packet per second) for TX queue load to trigger unpacking of the corresponding RX queue
Net.MaxNetifTxQueueLen	2000	10000	Maximum length of the Tx queue for the physical NICs

MySQL Administration

HOW TO RESET  MYSQL ROOT PASSWORD

  # start MySQL without permissions
  /usr/local/bin/mysqld_safe --skip-grant-tables &

  # login to mysql as root without password
  mysql -uroot

  # flush privileges
  flush privileges;

  # change root password
  set password for 'root'@'localhost' = PASSWORD('new-password');


OTHER COMMANDS

# show version
select version();

# change root password
set password for 'root'@'localhost' = PASSWORD('new-password');

PowerCLI - attach baseline

$vms = get-content c:\PS\MK\A1Category.txt
Get-Baseline -Name "VMware Tools Upgrade to Match Host (Predefined)" | Attach-Baseline -Entity $vms
Get-Baseline -Name "VM Hardware Upgrade to Match Host (Predefined)" | Attach-Baseline -Entity $vms

FCoE

FCoE

QLA - 

http://www.qlogic.com/OEMPartnerships/Dell/Documents/ds_QLE8152.pdf

Host Connectivity

• On QLogic CNAs, set the Link Down Timeout to 60 seconds (the default is 30 seconds) in the Advanced HBA Parameters. This is necessary to ensure proper recovery or failover if a link fails or becomes unresponsive.
  
  Switch Configuration
  
  
  fka-adv-period

  
  

  VFC down due to FIP keepalive misses

  The VFC goes down due to FIP keepalive misses.

  Possible Cause

  When FIP keepalives (FKA) are missed for a period of approximately 22 seconds, this means that approximately three FKAs are not continuously received from the host. Missed FKAs can occur for many reasons, including congestion or link issues.

  FKA timeout : 2.5 * FKA_adv_period.

  The FKA_adv_period is exchanged and agreed upon with the host as in the FIP advertisement when responding to a solicitation.

  Observe the output from the following commands to confirm FKA misses:

  •  show platform software fcoe_mgr info interface vfc <id>
  •  show platform software fcoe_mgr event-history errors
  •  show platform software fcoe_mgr event-history lock
  •  show platform software fcoe_mgr event-history msgs
  •  show platform fwm info pif ethernet <bound-ethernet-interface-id>

  Solution

  Sometimes when congestion is relieved, the VFC comes back up. If the symptom persists, then additional analysis is required. The possible considerations are:

  • The host stopped sending the FKA.
  • The switch dropped the FKA that was received.