An A.I. Ecosystem – How I Seen.

anAISteps Hi Friends,  Here I’m going to share my understanding about A.I. and it’s ecosystem. Hope you like new LOGO “an A.I.Steps” which I designed.

Please post your comment and responses on this post to help me better understand AI, also to address your feedback. 

So lets first discuss about A.I. (Artificial Intelligence), “Soothing to EAR and complex in deeper”. YES!!!  Once heard A.I. feels cool gadget or application but tough to study, complex in design and adventure to implement.

A.I.  can understood by its type 1. AGI , 2. ANI , 3. ASI ,  and other branch like Machine Learning and Deep learning. If wish to go more deeper please see the below reference blog post Thank you and kudos  Mitchell Tweedie for precise write-up Checkout here for AI types.  

Here is the types of AI.

anAISteps03

A.I. Ecosystem, which is completely my understanding. See the below A.I. ecosystem framework.

anAISteps02

So A.I. ecosystem contains various type of Agent (Hard & Soft), which do handshake and sync with endpoint and devices to receive data & sent instruction and alert, based on collected data analysis and other agent responses. 

Its learn and create its own learning pattern and index for Past and future reference, Raw Data has very significant role in A.I., which can be refer Machine learning (ML) and deep learning (DL).

I can not conclude A.I.without talking about intelligent agent of A.I.   Agent can be Sensors like a sonic sensor, a touch sensor, a proximity sensor, a sniffer sensor and RF sensor,  which detect Signals,  VOICE, Light, Image and Temperature etc.    

For more details about A.I. agent, Click here

See How agent work and its basic architecture.

anAISteps04

Picture source Wikipedia. 

Thank you.

 

 

 

 

 

 

 

Advertisements

My IAC Journey

Hi Friends,

See once again transformation ERA came back even I would say it is technology journey which travel continue, it just because of our necessity which give force to innovation move ahead.

This transformation touched IT operation and  touched every corner of  other’s Technology too also few of IT transformation we knew like Virtual server (VMs), Hypervisior (A version of Hardware), vSAN and NFV. Don’t forget cloud journey also.

Those transformation are more into platform agnostic like Data Center, Operating System, Compute, Storage, Network and Security so on. Now its turn for IT operation transformation through scripting, orchestration, robotic process automation and open source project, which called as Infrastructure as a Code and in short it is IAC.

See DevOps more into automation of application life cycle like Build–>Test–>Deploy vice versa Re-assess–>Modification–>Re-Test–>Deploy using CI/CD tools  but these all process very quick and efficient to reduced error along with effective rollback.

IAC is not a DevOps!!! It is part of Devops practice and believe me doing Devops or IAC it’s all about you and your way of thinking to define your strategy, see the below point…

  1. Clear plan Low hanging and Less critical first.
  2. Selection of language & tools.
  3. Re-skill.
  4. Consistent configuration.
  5. Team work.

IAC more about automation of IT operation things like

  1. Servers build.
  2. Patch life cycle.
  3. Self healing of INCIDENT.
  4. Agents and APIs monitoring.
  5. House Keeping.
  6. Automated reports & KPI.
  7. Auto scale-up & scale-in.
  8. Capacity monitoring and alert.
  9. Auto call logging.
  10. Analysis for prediction in operation.

Tools which can help for IAC drive:-

I did tools selection based on below strategy..

  1. Scripting  –  Think about OS (Microsoft, RHEL & AIX) Deployed Technology like Compute Hardware, Hypervisior, SAN, Backup, Database, FileSystem & Network devices, Thank you to Team SCMGlaxy for a useful post  Check here to know more about scripting language. 
  2. Orchestration – Orchestrator help to enable self healing and pure for of protectiveness in stead of proactive alertness. Here is the orchestration details. Credit goes to Devopscube for such a nice blog post.
  3. Next Generation Monitoring – Why NextGen? because it give me full right to do what ever customizing I wish do I can, few of agent based and few of agentless too also centralized logs collection that help to enable Machine learning and prediction for feature risk. Trust me here open source are best none other that than these OSS Tools  . Credit goes to Techgenix Team.
  4. Robotic process Automation – RPA can be GUI based and API based also but I would recommend to use API based RPA solution because GUI can change and Here is RPA Tools info. Thanks to Edureka Team for awesome comparison.
  5. Code version Control – Yes we must has control over code via using version framework and find here more about tools for version control. Credit goes to Rahul Sharma (FileCloud) for nice post.
  6. Open Source License – Read care fully to understand OSS license. Click here

Here some basic prerequisite list required IAC project:

  1. Know your Team and their skill too.
  2. Know about infra inventory.
  3. Know your Operation (L1, L2 and Hygienic Task).
  4. Know your alert and INCIDENT.
  5. Know your security and exception.
  6. Know your mission critical application.
  7. Know your messaging system.
  8. Know your logs and syslog.
  9. know your filesystem.
  10. know your agents.
  11. know your APIs.
  12. Know your OEM Partner.

In conclusion IAC project must has  GOAL like INCIDENT Reduction, Time saving, capabilities to predict, automation of report and KPI dashboard so on.

Just be with soon I’ll share deep dive for IAC practice in Operation.

Thank You

Kuver P Singh

 

 

 

 

 

 

How to configure vRealize LogInSight Agent?

Hi Friends,

Thank you for asking query that How to configure and vRLI (vRealize LogInSight) Agent with other operating system. I gone through below process to configure on one of my Windows Server. Sharing steps below….

  1. To get/Download agent from vRLI, need to logged in vRLI portal with Admin right select Administration  from top right corner and you will find below option to download vRLI Agent.vRLI01

2. To choose your vRLi agent, click on drop down option and select your required version of vRLI agent.

vRLI02

3. Copy the downloaded vRLI agent on Widows Server and install also, now you have to configure “liagent.ini” which located here C:\ProgramData\VMware\Log Insight Agent.

Configuring of “liagent.ini” file is very simple you just have to uncomment required parameter, See the below in pic.

 

vRLI03

5. Here is the Windows Server reporting in vRLi now.

vRLI04

Thank you for all your query and ask that I learn and hope it will help other.

 

 

VMware NSX :Underlying Gear & Physical Networking.

Hello Friends,

I am back on VMware NSX  track and This is my first post NSX. Now  going to do revised my NSX study, Hands-On and re-skill myself.   So I would love to hear you for any suggestion, correction that will help myself and other also.

Before begin want to give all credit to Blogger, VMware and Partner for their great write-up and sharing to enhance other knowledge also. 

It is my insight view on VMware NSX in reference of planning to deploy NSX for any Enterprise class environment.  Their few of requirement must to check and few of must to addressed, so here below those are:

  1. ESXi: Minimum Two (02) Host (ESXi) in each vSphere DRS cluster. Stop!!! Thinking because I am not saying that you cannot have a single standalone host within a cluster, absolutely its work but for HA (ESXi High availability) you have at least 02 Host in cluster.  I highly recommend to having three separate clusters with minimum three (03) Host.
  2. NSX License : NSX come with 3 different license editions; Standard, Advanced, and Enterprise. For more info check this NSX Licensing
  3. Max Minimum: It is bare minimum on the stand-alone Host clusters, the entire minimum to be one compute cluster, one edge and one management NSX. It is highly not recommended for any Production except PoC (Proof of concept).
  4. Network Minimum: With 1 Gig speed all just work well means if think that having 10 gigabit is a requirement for NSX that is not a true declaration.
  5. JUMBO Frame: Jumbo frames must be enabled and must to enabled on end to end communicated device like Physical switch and vNIC.
  6. TCP/IP Stack: TCP/IP stack got introduced in vSphere 5.5!!! Question what it does? Sure it is allow to create separate routing table for every different network that we create with default gateway per instance stack. So when you think of your default TCP/IP stack, you can think of things such as your Management kernel port, your vMotion kernel port, NFS, and iSCSI.
  7. VTEP & VXLAN: Cool VTEP is middle MAN who seat between L2 Fabric and Virtual Machine. VTEP remember connectivity flow of VMs with L2 logical networking. Its act as bridge.

Even though VXLAN is VLAN of VLANs to overcome of it limitation 4000 VLANs and its create logical VXLAN network through combing two or more VLANs. It support Layer 3 routing like OSPF, BGP & IS-IS, Also support multicast like IGMP & PIM.

Check this for more deep into VXLAN and VTEP

  1. VTEP HA : Now wish to share my environment which is running on a 1 gigabit fabric that have four NICs per host and I used two to have HA VTEPs, and two for HA management configuration. Let’s talk in details, if anyone running a 10G NIC configuration. I wish to have HA VTEPs however because it help to load balance my VXLAN tunnels between the two VTEPs on my hypervisor. So the recommendation is to have at least two…10 gigabit NIC.
  2. EDGE Racks: Yup!!! Most of flow going through edge racks even most of the tenants and customer connectivity will land here, so this major area there must have 10G speed and remain like management and Host networking OK with 1G speed.

Also shared L2 connectivity between management rack to edge rack to do fail over between the two and lets vSphere HA switch that.

  1. LEAF & SPINE: Not all but few folks are confuse between Leaf and spine, Let see what is Leaf and Spine. Leaf has access switches that connect to end point devices like servers, firewalls, load balancers, and edge routers etc. Spine nodes are aggregation nodes that provide connectivity between different racks in your datacenter.

Spine has leaf in it, like Network backbone where every Leaf switch is interconnected with each and every Spine switch. Leaf nodes are going to be your top-of-rack switch.

For more info click here Spin & Leaf

  1. STP: Do not use Spanning Tree Protocols (STP) not supported even not going to help because it is only help to avoid getting into any sort of networking loop.
  2. Layer 2 fabric: Let’s think about huge environment because Scale, so need to design carefully. L2 Fabric learn MAC address and use MAC to do communication and it can learn and save thousands or millions of MAC address entries.

Precisely you got it, also known as your ARP and MAC table.L2 Fabric has a limitation of just over 4000 VLANs in most of environments.

So I am going to take pause here and I’ll resume myself with next post soon. Once again Please do comment as your feedback and share your thought foe better understanding of mine and other also.

Thank you

Kuver P Singh

VMware Command Alphabet : A to Z

Hi,

I have tested below ESXi command line in my Lab and documented for my VMware friends. Hope you all like it and it would help you.

Important Tips: Before connect or do putty of ESXi, set the logging output to get all command history saved.

# auto-backup.sh [To take ESXi configuration backup, see the KB2043048]

# df [To get filesystem info]

# env [To see ESXi basic connection setings]

# ethtool -i vmnic0 [To see Network Card driver and firmware version]

# ethtool -S vmnic0 [To see Network TX & RX packet stats]

# ethtool -c vmnic0 [To see Network Coalesce parameters]

(Coalesce: Help tune network latency and performance, refer vSphere performance guide)

# esxcfg-info | grep -i xxxx [To see ESXi component detailed information]

# firmwareConfig.sh [To troubleshoot hardware firmware issue]

# fdisk -l [To see device list and partition table.

# hostd -v [To check ESXi Agent info and version]

# hostname [To know ESXi Name]

# hwclock [To get ESXi Date & Time]

# irqinfo [To see shared IRQ]

# kill  [To kill process]

# lspci [To check PCI hardware manufacture vendor info]

# lsof [To see locked file map with process]

# localcli [Similar to ESXCLi but can be used when hostd service not starting or for troubleshooting]

# memstats [To see memory stats because webclient does not show all information, see the KB2043413]

# net-cdp | net-dvs | net-lacp | net-lbt | net-stats [To use for network Troubleshooting and see the stats]

# pktcap-uw [To capture the packet, see the KB2051814]

# partedUtil [To manage, create anfd delete disk partition (VMFS), see the KB1036609]

# passwd [To reset ESXi password]

# ps [To get ESXi process list]

# sched-stats [To see ESXi vmkernel stats for each event]

# services.sh [To troubleshooting issue, start or restarting ESXi service will not impact running VM]

# tcpdump-uw [To capture TCP dump for network issue investigation]

[Thank you @ Viren – http://www.virten.net/2015/10/esxi-network-troubleshooting-with-tcpdump-uw-and-pktcap-uw/]

# uwstats {To see user world stats]

# vdf [To see VMFS space usages in detailed, see the KB1003564]

# vdu [VMware disk utility]

# vdq [VMware vSAN utility]

# vmkping [To ping IP and test MTU packet using -l switch]

# vmware -lv [To see VMware ESXi version and build]

# vmkchdev -l | grep vmnic0 [ VM kernel change device, see the KB1027206]

# vm-support [To generate VMware support bundle log “.tgz” that can shared with VMware support]

# voma -m vmfs -d /vmfs/devices/disks/xxxxx [vSphere On-disk Metadata Analyzer (VOMA), see the KB2036767]

# vmkfstools [To perform VMFS operation, see this http://pubs.vmware.com/esx254/admin/wwhelp/wwhimpl/common/html/wwhelp.htm?context=admin&file=esx25admin_disks.10.13.html]

Thank you

ESXCLi for VMWARE Administration

Hello Friend,

On your demand, I have listed down few useful ESXCli command and hoping it will help you to make your operation easy.

I would like to Thank you and recommend to read 

Automated Report of ESXi HW Driver&Firmware info

vDocumentation : Automate VMware Config documentation

If you face any difficulties to execute above script comment me below with your issue.

####ESXCLi Operation ################################
# Below statement I found very useful for VMware Administration#
######### ESXi Version Info #################################
vmware -vl

#Output: VMware ESXi 6.0.0 build-5224934
#VMware ESXi 6.0.0 Update 3

esxcli system version get

#[root@localhost:~] esxcli system version get
#Product: VMware ESXi
#Version: 6.0.0
#Build: Releasebuild-5224934
#Update: 3
#Patch: 58

####### Network Adapter Info ###############################
esxcli network nic list
ethtool -i vmnic0
esxcli network nic get -n vmnic0
vmkchdev -l | grep vmnic0
vmkchdev -l | grep vmnic5
esxcli network nic get -n vmnic5

####### HBA Adapter Info #################################
esxcfg-scsidevs -a # Choose your driver in my case Qlogic
vmkload_mod -s qlnativefc | grep -i version
vmkchdev -l | grep vmhba1
vmkload_mod -s mpt2sas | grep -i version
vmkchdev -l | grep vmhba0

########## ESXCLi system ############################################
esxcli system # To use for esxi operation and output give all option

#Show ESXi version and build
esxcli system version get

#Enter Maintenance Mode
esxcli system maintenanceMode set –-enable yes

#Exit maintenance Mode
esxcli system maintenanceMode set –enable no

#List only advanced settings that have been changed from the system defaults
esxcli system settings advanced list

#List only kernel settings that have been changed from the system defaults
esxcli system settings kernel list –d

#List / Change / Test SNMP
esxcli system snmp get # Use these switch “| hash | set | test”

############# ESXCLi VM ######################

#List VMs on the ESXi server with the World ID
esxcli vm process list

#Kill a VM
esxcli vm process kill –t soft -w WorldID

##########ESXCLi software####################################

Install updates and drivers on a ESXi host (make sure the ESXI host is MaintenanceMode)
esxcli software vib install -d /vmfs/volumes/VMFS01/patches/nameoftheupdate.zip #Install will replace old file/driver
esxcli software vib update -d /vmfs/volumes/VMFS01/patches/nameoftheupdate.zip #Update will keep and overwrite old file & driver safe to use.

##############ESXCLi network #################################

#List physical NICs and connection state
esxcli network nic list

#List network information for the VM
esxcli network vm list

#############ESXCLi storage ######################################

#List the devices currently controlled by the VMware NMP Multi path Plugin and show the SATP and PSP information associated with that device
esxcli storage nmp device list

#List VAAI properties for devices currently registered with the PSA.
esxcli storage core device vaai status get

#Change the default pathing policy to Round Robin and choose yout Storage Vendor
esxcli storage nmp satp set –default-psp VMW_PSP_RR –satp youre_satp_policy

Thank You

 

 

Lets meet at Delhi VMUG Event 23-Sep-17

Hello Friends,

Do register to your self for Delhi VMUG event, Announced date is Saturday, 23-Sep-2017.  It is first time in Delhi any event organized for local VMware user community.

So don’t missed it, You will have a chance to make new friends to expand your professional networking, you will learn about new technology such as NSX, vROPS & vRA and get free vSphere Tips & Tricks along with Career guidance.

Click here for Register yourself

If anyone failed to register or facing any issue. Please comment below this post.

Thanks to VMware VMUG Team @MyVMUG to design cool logo for Delhi_VMUG.

c678f0ba-bac4-4339-9879-5653d861ad02