Differences between revisions 4 and 25 (spanning 21 versions)
⇤ ← Revision 4 as of 2015-12-22 13:56:10 →
Size: 743
Editor: localhost
Comment:
← Revision 25 as of 2019-11-03 09:22:18 → ⇥
Size: 2941
Editor: merlin
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
= NSX how to = == NSX requirement ==
  * No matter the size of the NSX deployment, VMware requires that each NSX Controller cluster contain three controller nodes. Having a different number of controller nodes is not supported.
  * The cluster requires that each controller's disk storage system has a peak write latency of less than 300ms, and a mean write latency of less than 100ms. If the storage system does not meet these requirements, the cluster can become unstable and cause system downtime.
Line 6: Line 8:
辕 == NSX check ==
  * Log in to the NSX Controller CLI.
{{{
get control-cluster status
}}}
Line 8: Line 14:
 I. XXX
 I. 23324
 I. AFASD		 {{{
show control-cluster status
show control-cluster connections
}}}
Line 12: Line 19:
== xxx ==
adsfdsa
=== 32432 ===		   * Log in to the NSX Manager CLI.
{{{
# nsx-manager
show logical-switch list all
get management-cluster status
}}}
Line 16: Line 26:
== test2 ==
alkjflkdsa		 == Notes ==
  * All NSX Edge services run on the active appliance. The primary appliance maintains a heartbeat with the standby appliance and sends service updates through an internal interface. If a heartbeat is not received from the primary appliance within the specified time (default value is 15 seconds), the primary appliance is declared dead.

  * By default when we’re creating a firewall rule in NSX, the “Applied to” field is set to “Distributed Firewall”. The firewall rule will be stored in NSX manager’s database and will be applied to all VMs vNICs, regardless of the VMs location. It’s important to mention that even when dFW rule is applied to all VMs, we still need a match on source/destination to take action on that rules.
= Troubleshooting =
== How to Cleanly Uninstall Legacy NSX and Trend Micro from ESXi ==
  * http://virtuallystable.com/2018/11/08/how-to-cleanly-uninstall-legacy-nsx-and-trend-micro-from-esxi/
  * http://www.vmwarearena.com/how-to-manually-install-nsx-6-3-0-vibs-on-esxi-6-5-hosts/
Line 19: Line 35:
list
ls
$ df
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/sdb2 btrfs 29296908 20777208 8243032 72% /
devtmpfs devtmpfs 10240 0 10240 0% /dev
tmpfs tmpfs 1612996 728 1612268 1% /run
cgroup_root tmpfs 10240 0 10240 0% /sys/fs/cgroup
shm tmpfs 8064976 0 8064976 0% /dev/shm
/dev/sda3 btrfs 15128576 5657344 7597440 43% /var
/dev/sda4 reiserfs 419827180 402075372 17751808 96% /mnt/play		 #esxcli software vib remove -n epsec-mux
Line 31: Line 37:
== Restoring vCenter access after being blocked by a Deny All rule in NSX DFW ==
  * http://www.etgoesvirtual.com/vmware/nsx/restoring-vcenter-access-after-publishing-a-deny-all-rule-in-nsx-dfw/

= KEYS =
{{{
License Key : UC3RA-D3XD4-H817Z-UEMNG-WC0WF
License Key:UC3RA-D3XD4-H817Z-UEMNG-WC0WF

http://vcloudtip.com/vmware-nsx-manager-6-3-4/
https://technet24.ir/vmware-nsx-for-vsphere-6-3-4-9579


vSphere with Operations Management 6 Enterprise Plus keys
NA2JH-A9L4L-H89Q0-G12GM-1QR28
5G45A-6520K-08990-6V350-03HLF
HG2ER-4TJE0-088P0-428Q2-1ZANA
MF61K-4LL5N-08879-JA1ZH-2384F
1Y2T8-0PK9N-M89W1-J9CQP-9GRN2
0U202-2X113-48DU9-M90EM-2AU60
0Z01A-4A05J-085M9-33C5K-0UHLD




vCenter 6 Standard keys
5Y6VG-0W3E7-9Z9P8-8U8X0-C2KJJ
NU490-8N39K-9ZZK9-8RCX0-CCC11
HF45X-200D3-RZ778-GL05M-32064
MG0LW-4V01L-DZUG8-21152-8A11K
MF4V0-8HH8M-GZ521-DH374-A2678
1F4A5-02K95-GZ9C1-200N4-0AR72

NSX 6.3.3
License Key : UC3RA-D3XD4-H817Z-UEMNG-WC0WF

http://cursuri.cheche.ro/vmw/

Contents

    1. NSX requirement
    2. NSX check
    3. Notes
  2. Troubleshooting
    1. How to Cleanly Uninstall Legacy NSX and Trend Micro from ESXi
    2. Restoring vCenter access after being blocked by a Deny All rule in NSX DFW
  3. KEYS

NSX requirement

  • No matter the size of the NSX deployment, VMware requires that each NSX Controller cluster contain three controller nodes. Having a different number of controller nodes is not supported.
  • The cluster requires that each controller's disk storage system has a peak write latency of less than 300ms, and a mean write latency of less than 100ms. If the storage system does not meet these requirements, the cluster can become unstable and cause system downtime.

NSX check

  • Log in to the NSX Controller CLI. 

get control-cluster status

show control-cluster status
show control-cluster connections
  • Log in to the NSX Manager CLI. 

# nsx-manager
show logical-switch list all
get management-cluster status

Notes

  • All NSX Edge services run on the active appliance. The primary appliance maintains a heartbeat with the standby appliance and sends service updates through an internal interface. If a heartbeat is not received from the primary appliance within the specified time (default value is 15 seconds), the primary appliance is declared dead.
  • By default when we’re creating a firewall rule in NSX, the “Applied to” field is set to “Distributed Firewall”. The firewall rule will be stored in NSX manager’s database and will be applied to all VMs vNICs, regardless of the VMs location. It’s important to mention that even when dFW rule is applied to all VMs, we still need a match on source/destination to take action on that rules.

Troubleshooting

How to Cleanly Uninstall Legacy NSX and Trend Micro from ESXi

#esxcli software vib remove -n epsec-mux

Restoring vCenter access after being blocked by a Deny All rule in NSX DFW

KEYS

désert/VMware/NSX (last edited 2019-11-03 09:22:18 by merlin)