Cisco Switches info

Nexus Family switches :-

Nexus 7000 family 7009 7010 7018 very dense 10 Gigi core

Nexus 5500 second generation top-of-rack 10Gb optional layer 3 capability

Nexus 5010 and 5020 --layer 2 swtiches only,supports FCOE
5010 --1U --20 10Gb ports plus module
5020 --2U --40 10Gb ports plus module

Nexus 2000 series (top of rack) these are not ture switches they are called FEX must be connected
with Nexus 5K or 7K .No local switching .All the switching is done by talking to 5K and 7K.
support FCOE.

FEX : FEX is a tecnology where the switching fabric is extended  by using devices,adapters or software.
requires connectivty back to a smart device.

Switch FEX :Examples Nexus 2K of a5548up.

Adapater FEX :Split a physical adapter in to mutiple logical adapters.

VM FEX :Extends adapter FEX in to a Virtual machine.

Nexus 1000v :Software switches
two Modules VSM Virtual Supervisor Module -(Mgmt Control plane)
            VEM Virtual Ethernet Module -(Dataplane)

MDS Switches Cisco Fibre Channel Switches

Cloud Provisioning and Automation:
Tidal is cisco orchetration
Newscale is Cisco Cloud Protal like cloud Director from Vmware but is provides support for other hyperisors as well.and chargeback

ESXi/ESX cmd for VM's

ESXi VMX files

vim-cmd vmsvc/getallvms
vim-cmd vmsvc/power.off vmid
vim-cmd vmsvc/power.on vmid
vim-cmd vmsvc/power.reboot vmid
vim-cmd solo/registervm  name.vmx

vmfsktools -D name.vmx would show you the MAC address of NIC associated 


ESX cmd:
vmware-cmd  /vmname.vmx  getstate
vmware-cmd  /vmname.vmx  reboot
vmware-cmd  /vmname.vmx  start
vmware-cmd  /vmname.vmx  shutdown
vmware-cmd  /vmname.vmx  suspend
vmware-cmd  /vmname.vmx  hassnapshot (Query if VM has snapshot)
vmware-cmd  createsnaspshot nameofvm quiesce memory
vmware-cmd  /vmname.vmx  revertsnapshot
vmware-cmd  /vmname.vmx  removesnapshots
vmware-cmd  -s register /vmname.vmx   
vmware-cmd  -s unregister /vmname.vmx 

Hub Network :Everything goes everywhere in a hub network.

Switch Network would get
1)Broadcast Traffic
2)Multicast Traffic
3)Traffice to and from a specfic MAC address
4)Any Traffic going to or from UNKNOWN MAC address which is very rare.

Since it is not possible to discconect your server and inject hub in a real time network problem we go for SPAN (Swtiched Port Anaylsis)  also called Port Mirroring.Port Mirroring we configure the switch to copy servers traffic to a alyser port


Analyzer Placement :
1)Hub - Switch all network can be captured when analyser is placed at HUB
2)Switch - Switch  use Port mirroing  SPAN a port  and copy all the traffic on that port to anaylzer port.
3)Switch -Router - Switch traffic between switch and router can be traced ,but not both the layer2 traffics on the switch.
-------------------------------------------------
Packet Transmittal :-

TCP  Source port 1024 (can be anything)
     destination port 21

IP protocal  6  (Reolve name to IP)
   source Ip 192.16.1.4
   destination IP 192.11.1.5

Eth  Destination MAC B (Ip to mAC)
     Source MAC      A
     Ether Type : xyx800
---------------------------------------------
Transulate FTP to port number 21
Get Host IP address resultion(Cache,Hosts file,Network)
Local or remote destination (SUbnet mask)
Local Get MAC address (ARP) (Cache or Network)
Remote Lookup route Inforation (Host,Network or Gateway)
Get MAC address (ARP) (Cache,Network)

Network issue to look into

No retransmissions

No Delays

No errors

No service refusals

Minimal Back Ground traffic (becoz of broad cast or Multicast)

Direct Routes

SRM overview

1 high speed SAN replication

2 SRM application on Vcenter ot separate win 2003 or 2008 server.

3 SRA (Site Replication Adapater) software are VMware prodies for SRM server to speak with diffrent storage arrays.

4 SRM plugin on your client machine

5 SRM should be insalled per site and vcenter basis.

6 SRM needs it own database and DSN to speak with it database.

7 first pair the Protected site and recovery site and vise versa by logging into repective Vcenter servers.

8 confiure SRA on each VCenter

9 Inventory mapping.for configuring valid inventory mapping of revory site network,Folder,resource pool and others

10 protection groups organize VM's based on replicated datastores they are stored in.

create and test recovery plans

Command to check snapshot

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007566

Stopping and starting SSH on ESX multiple

Get-Cluster nameofcluster | Get-VMHost | Foreach { Start-VMHostService -HostService ($_ | Get-VMHostService | Where { $_.Key -eq “TSM-SSH”} ) }


Get-Cluster nameofcluster | Get-VMHost | Foreach { Stop-VMHostService -HostService ($_ | Get-VMHostService | Where { $_.Key -eq “TSM-SSH”} ) }

ESXTOP metrics

Metrics and Thresholds

Display	Metric	Threshold	Explanation
CPU	%RDY	10	Overprovisioning of vCPUs, excessive usage of vSMP or a limit(check %MLMTD) has been set. See Jason’s explanation for vSMP VMs
CPU	%CSTP	3	Excessive usage of vSMP. Decrease amount of vCPUs for this particular VM. This should lead to increased scheduling opportunities.
CPU	%SYS	20	The percentage of time spent by system services on behalf of the world. Most likely caused by high IO VM. Check other metrics and VM for possible root cause
CPU	%MLMTD	0	The percentage of time the vCPU was ready to run but deliberately wasn’t scheduled because that would violate the “CPU limit” settings. If larger than 0 the world is being throttled due to the limit on CPU.
CPU	%SWPWT	5	VM waiting on swapped pages to be read from disk. Possible cause: Memory overcommitment.
MEM	MCTLSZ	1	If larger than 0 host is forcing VMs to inflate balloon driver to reclaim memory as host is overcommited.
MEM	SWCUR	1	If larger than 0 host has swapped memory pages in the past. Possible cause: Overcommitment.
MEM	SWR/s	1	If larger than 0 host is actively reading from swap(vswp). Possible cause: Excessive memory overcommitment.
MEM	SWW/s	1	If larger than 0 host is actively writing to swap(vswp). Possible cause: Excessive memory overcommitment.
MEM	CACHEUSD	0	If larger than 0 host has compressed memory. Possible cause: Memory overcommitment.
MEM	ZIP/s	0	If larger than 0 host is actively compressing memory. Possible cause: Memory overcommitment.
MEM	UNZIP/s	0	If larger than 0 host has accessing compressed memory. Possible cause: Previously host was overcommited on memory.
MEM	N%L	80	If less than 80 VM experiences poor NUMA locality. If a VM has a memory size greater than the amount of memory local to each processor, the ESX scheduler does not attempt to use NUMA optimizations for that VM and “remotely” uses memory via “interconnect”.
NETWORK	%DRPTX	1	Dropped packets transmitted, hardware overworked. Possible cause: very high network utilization
NETWORK	%DRPRX	1	Dropped packets received, hardware overworked. Possible cause: very high network utilization
DISK	GAVG	25	Look at “DAVG” and “KAVG” as the sum of both is GAVG.
DISK	DAVG	25	Disk latency most likely to be caused by array.
DISK	KAVG	2	Disk latency caused by the VMkernel, high KAVG usually means queuing. Check “QUED”.
DISK	QUED	1	Queue maxed out. Possibly queue depth set to low. Check with array vendor for optimal queue depth value.
DISK	ABRTS/s	1	Aborts issued by guest(VM) because storage is not responding. For Windows VMs this happens after 60 seconds by default. Can be caused for instance when paths failed or array is not accepting any IO for whatever reason.
DISK	RESETS/s	1	The number of commands reset per second.
DISK	CONS/s	20	SCSI Reservation Conflicts per second. If many SCSI Reservation Conflicts occur performance could be degraded due to the lock on the VMFS.

Restart management agents in ESXi through SSH

1. Go to the ESXi console and press alt+F1
2. Type: unsupported
3. Enter the root password(No prompt, typing is blindly)
4. At the prompt type “vi /etc/inetd.conf”
5. Look for the line that starts with “#ssh” (you can search with pressing “/”)
6. Remove the “#” (press the “x” if the cursor is on the character)
7. Save “/etc/inetd.conf” by typing “:wq!”
8. Restart the management service “/sbin/services.sh restart”