QuickTask: Locating the Serial Number by CLI on a Juniper QFX5100 switch

product-line-qfx5100QFX5100 switches are flexible data center switching platforms that provide a universal building block for multiple fabric architectures, including Juniper’s mixed 1/10/40GbE Virtual Chassis, Virtual Chassis Fabric, Junos Fusion and QFabric® System architectures, as well as open architectures such as Spine and Leaf, Layer 3 and Open Clos IP fabrics. All QFX5100 switches support unified in-service software upgrades (unified ISSU) to deliver hitless data center operations for high availability. QFX5100 switches also include support for virtualized network environments including Juniper Contrail and VMware NSX Layer 2 gateway services.

To list the QFX3500 device and components and their serial numbers, use the show chassis hardware CLI operational mode command. 

show chassis hardware 
Chassis SN

Chassis SN

ou use bellow command ( in example we are use two SN because we use virtual chassis ):

show configuration | display set | grep serial
Chassis SN from configuration

Chassis SN from configuration

Much faster for take serial numbers from QFX5100 worked in virtual chassis use this command:

show virtual-chassis
show virtual-chassis

show virtual-chassis

I hope this is informative for you. Thanks for Reading!.  Be Social and share it in social media, if you feel worth sharing it. Please comment if you have some own experience related with this topic.

source: Juniper

Linux Utilities Cookbook – only today from www.packtpub.com

 

 

Everything you need to know about Linux but were afraid to ask. This book will make you a master of the command line and teach you how to configure the network, write shell scripts, build a custom kernel, and much more.
  • Use the command line like a pro
  • Pick a suitable desktop environment
  • Learn to use files and directories efficiently

3008OS

 

 

 

 

QuickFix: Virtual machine Consolidation is needed – Unable to access file since it is locked – ESXi 5.5

Problematic VM: xxxxTSS001

Symptoms

  • Configuration issues: Virtual machine Consolidation is needed
Configuration issues: Virtual machine Consolidation is needed

Configuration issues: Virtual machine Consolidation is needed

  • Task name: Consolidate virtual machine disk files
  • Task results: Unable to access file since it is locked
Consolidate virtual machine disk files / Unable to access file since it is locked

Consolidate virtual machine disk files / Unable to access file since it is locked

  • Events: Virtual machine disks consolidation failed
  • Related task: Remove snapshot
Virtual machine disks consolidation failed / Remove snapshot

Virtual machine disks consolidation failed / Remove snapshot

Affected VM xxxxTSS001 has “Hard disk 2” with last snapshot file xxxxTSS001_1-000028.vmdk.

Virtual Machine Properties

Virtual Machine Properties

In folder where is VM we see many xxxxTSS001_1-0000xx.vmdk files related with previous snapshots which was created during backup jobs.

VM files

VM files

VM files

VM files

Cause

VMDK file xxxxTSS001_1-000002.vmdk which was attached to one of disk “Hard Disk 6” in VM “xxxxVDP001” ( vSphere Data Protection ) was causing locking error during consolidation process.

Screenshot_4

 

After manually removed “Hard Disk 6” from VM “xxxxVDP001” ( vSphere Data Protection ) consolidation process completed successful.

How we saw this time locked file xxxxTSS001_1-000002.vmdk related was with VDP appliance “xxxxVDP001” which during backup proccess always temporary attach VMDK files in VM which is during backup task. In this case for some reason this VMDK file xxxxTSS001_1-000002.vmdk wasn’t unlocked after backup and that was source of problem. Manually removed attached before VMDK file resolved problem.

Additional information , observation::

  • #My tips

Is not easy to find where some VMDK is attached (locked) in VSAN configuration. Some tips which we can use for this is use this command on every ESXi host ( yes i know if we have many hosts in cluster this is not the best solution but is some way):


egrep -i VMNAME /vmfs/volumes/*/*/*.vmx

 

  • #My observation

VMDK file xxxxTSS001_1-000002.vmdk which was attached to VDP and not unlocked after backup complete in this view has different date than other VMDK files in VM folder. This time that information was not helpful but maybe good to know this behavior.

Screenshot_6_

Screenshot_5

I hope this is informative for you. Thanks for Reading!.  Be Social and share it in social media, if you feel worth sharing it. Please comment if you have some own experience related with this topic.

QuickTip: Keyboard Shortcuts of VMware vSphere Web Client

Keyboard Combination Action
Ctrl+Alt+Home OR Ctrl+Alt+1
Home Screen
Ctrl+Alt+2
Virtual Infrastructure Inventory
Ctrl+Alt+3
Hosts and Clusters Inventory
Ctrl+Alt+4
VMs and Templates Inventory
Ctrl+Alt+5
Datastores and Datastore Clusters Inventory
Ctrl+Alt+6
Networking Inventory
Ctrl+Alt+s
Inventory Search

I hope this is informative for you. Thanks for Reading!.  Be Social and share it in social media, if you feel worth sharing it. Please comment if you have some own experience related with this topic.

 

QuickFix: The type initializer for ‘VirtualInfrastructure.Utils.ClientsXml’ threw an exception

My Environment:

  • ESXi 5.5 u2
  • vCenter 5.5 u2
  • 1 cluster in vCenter
  • Lab in Ravello Cloud

In some beauty day during day:

Symptom:

  • The type initializer for ‘VirtualInfrastructure.Utils.ClientsXml’ threw an exception

In logs: “C:\Users\username\AppData\Local\VMware\vpx\viclient-0.log” i found only:

:Error :P: 3] 2016-06-26 14:05:37.790 possible failure processing clients.xml
System.Net.WebException: The request failed because the client could not validate the server's SSL certificate. (The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.)
at VirtualInfrastructure.Utils.WebQuery.LocalizeWebException(WebException exception)
at VirtualInfrastructure.Utils.WebQuery.Request(String url, Nullable`1 timeoutSecs)
at VirtualInfrastructure.Utils.ClientsXml.ParseXml(Int32 timeoutSecs)
at VpxClient.Login.ClientsXmlLoader.TrySinglePort(ClientsXml clientXml, Exception& activeError)
System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Server stack trace:
at System.Net.HttpWebRequest.GetResponse()
Exception rethrown at [0]:
...
at System.Net.HttpWebRequest.GetResponse()
at VirtualInfrastructure.Utils.WebDownload.GetResponse()
at VirtualInfrastructure.Utils.WebDownload.get_ResponseStream()
at VirtualInfrastructure.Utils.WebQuery.Request(String url, Nullable`1 timeoutSecs)
System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
...
at System.Net.ConnectStream.WriteHeaders(Boolean async)

--- End of inner exception stack trace ---

--- End of inner exception stack trace ---
[ :Error :M: 1] 2016-06-26 14:05:38.040 Error retrieving clients.xml
Exception already logged, summary: System.Net.WebException:The request failed because the client could not validate the server's SSL certificate. (The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.)
[ :Warning :M: 1] 2016-06-26 14:05:46.776 A certificate for "10.0.0.10" is already trusted but is not the same as the certificate being presented now.
If you choose to install the new certificate for this connection it will replace the existing trusted certificate.

Resolution:
Restart server where is installed vSphere Client helped.

I hope this informative for you. Thanks for Reading!.  Be Social and share it in social media, if you feel worth sharing it. Please comment if you have some own experience related with this topic.

 

QuickTask: How check grace period in Windows Server

Sometimes we need to know how long will be working grace period for specific server:

You can take this information from:

  •  warning after login to server:

Screenshot_3

  • or use this command:
wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting WHERE (__CLASS !="") CALL GetGracePeriodDays

Screenshot_1
I hope this informative for you. Thanks for Reading!.  Be Social and share it in social media, if you feel worth sharing it. Please comment if you have some own experience related with this topic.

QuickFix: Virtual machine Consolidation is needed – ESXi 5.5

My Environment:

  • ESXi 5.5 u2
  • vCenter 5.5 u2
  • only 1 VSAN datastore in cluster
  • 2 cluster in vCenter

Symptoms:

  • Cannot perform snapshot consolidation in VMware ESXi 5.5
  • Performing a snapshot consolidation in ESXi 5.5 fails.

Screenshot_2aScreenshot_1 Screenshot_2Screenshot_5Screenshot_3Screenshot_6 Screenshot_7 Screenshot_8 Screenshot_8a Screenshot_9 Screenshot_10

In logs on this VM (vmware.log) we found:



2016-05-04T20:03:57.420Z| vcpu-0| I120: DISKLIB-LIB   : Free disk space is less than imprecise space neeeded for combine (0x1fbd3800 < 0xd3714800, in sectors). Getting pre
cise space needed for combine...
2016-05-04T20:04:10.494Z| vcpu-0| I120: SnapshotVMXConsolidateHelperProgress: Stunned for 13 secs (max = 12 secs). Aborting consolidate.
2016-05-04T20:04:10.494Z| vcpu-0| I120: DISKLIB-LIB   :DiskLibSpaceNeededForCombineInt: Cancelling space needed for combine calculation
2016-05-04T20:04:10.495Z| vcpu-0| I120: DISKLIB-LIB   : DiskLib_SpaceNeededForCombine: failed to get space for combine operation: Operation was canceled (33).
2016-05-04T20:04:10.495Z| vcpu-0| I120: DISKLIB-LIB   : Combine: Failed to get (precise) space requirements.
2016-05-04T20:04:10.495Z| vcpu-0| I120: DISKLIB-LIB   : Failed to combine : Operation was canceled (33).
2016-05-04T20:04:10.495Z| vcpu-0| I120: SNAPSHOT: SnapshotCombineDisks: Failed to combine: Operation was canceled (33).

After fast troubleshooting with VMware engineer we receive summary:

“I tracked down that KB I mentioned, and it’s somewhat related but it also seems to be related to a newer VSAN-specific bug.

I mentioned this calculation that must be done in certain cases.

When a consolidation is called, the host does a basic check – is the snapshot file larger than the amount of free space on the datastore. If there is definitely enough free space, itt proceeds with the consolidation.

However, if the snapshot file is larger than the amount of free space then we need to do a more detailed calculation to determine if we will be able to consolidate without filling up the datastore.

We allow 12 seconds to perform this calculation – if it takes any longer, then we abort the consolidation.

This is exactly what we see in your logs.

As we saw, there is more than enough free space on the VSAN datastore

Screenshot_9_datastore

so we should not need to be doing this precise calculation. I’ve found a bug in VSAN where there is a problem with the calculation, meaning that consolidation may fail for VMs with large snapshot files:

https://kb.vmware.com/kb/2118663

We don’t see the exact symptoms here – your consolidation is not failing with ‘insufficient space’, it is failing with ‘operation was cancelled’. But it seems to be related to the same root cause.

The fix for the problem went into 5.5U3b so obviously that is not an option right now.

As far as I know, the workaround mentioned in the KB may also not be an option as I don’t think you would have a suitable datastore to send the clone to.

However, there is another workaround which has helped some other customers:

  • – Shut down the virtual machine
  • – Right-click the virtual machine and click Edit Settings.
  • – Click the Options tab.
  • – Under Advanced, click General.
  • – Click Configuration Parameters and add snapshot.maxConsolidateTime = 120

  This should allow more time for the calculation to complete and may allow consolidation to proceed.”

After this investigation i additional KB which can confirm this way of working:

VMware KB:    Snapshot consolidation in VMware ESXi 5.5.x and ESXi 6.0.x  fails with the error: maximum consolidate ret…

Resolution:

I belive is many ways to remove “Virtual machine Consolidation is needed” warning but in my case that way was that working way. After some preparation we shutdown VM and add advanced parameter to VM

snapshot.maxConsolidateTime = 120

Screenshot_12

and start VM again. Next manually performed consolidation with success.

Screenshot_3

Sources:

I hope this informative for you. Thanks for Reading!.  Be Social and share it in social media, if you feel worth sharing it. Please comment if you have some own experience related with this topic.

QuickFix: vROPS 6.0 services not working

Symptoms:

  • vROPS login page is not loading – blank page
  • after use command: service vmware-vcops status during generate results command is hanging
  • after use command vmware-vcops restart process is hanging
  • No activity on Network performance chart and small activity on CPU chart
Blank Page

Blank Page

Screenshot_6

Screenshot_5 Screenshot_4

 

Resolution:

Restart vROPS Appliance:

 

During restart appliance some services can start with some delay...

During restart appliance some services can start with some delay…

After login by SSH service status command is working fine

Login window has been loaded succesfull

 

For your information. Service restart process should looks how bellow  and dont take longer than 2 minutes:

Screenshot_11

If you have some other suggestion to resolve above issue please comment.

QuickFix: vSphere Web Client 5.5 doesn’t load after login

During login to vSphere Web Client 5.5 we have this situation ( only vmware logo or initializing info… ):

vSphere Web Client

vSphere Web Client – only vmware logo

vSphere Web Client

vSphere Web Client – initiailizing… information

In vCenter Appliance portal:   https://vcenter:5480

vSphere Web Client

vSphere Web Client – service is running but not working correctly

vSphere Web Client

vSphere Web Client – after restart vSphere Web Client service is starting….

vSphere Web Client

After few minutes we can try login again with success.