Category: infrastructure

Posted on

Increase efficiency with vRealize Log Insight

Syslog Server – a time saving tool

Today I’m writing about a use case, which is not very popular amongst IT professionals. Troubleshooting by parsing system logs. Sounds attractive as a dental surgery.

Almost any system and any component logs events, warnings and errors into some kind of internal log. Emphasis is on any and internal, because that’s part of the problem. Log information isn’t usually easy accessible. And once you’ve copied all logs to a common location, you need to scroll through it by a text editor. This is cumbersome and tricky. If you – for example – have to align events from a server with events from a switch, you’ll need multiple steps to achieve it. A very time-consuming procedure. If you have bad luck (Murphy says, you will..), one of the components is unavailable, because an error occurred. No log – no analysis. Continue reading “Increase efficiency with vRealize Log Insight”

Posted on

Change Brocade FOS default passwords

Brocade FC-Switches are equipped with four default useraccounts: admin, root, user and factory.

By connectiong an SSH session with user ‘root’ and default password ‘fibranne’ you will be prompted to change logins for accounts root, user and factory.

 

This happens at login as long as you did not change default passwords. The process can be started by pressing <ENTER>. If it is skipped by pressing Ctrl-C you will be prompted again at next login of user ‘root’

Show users

userconfig --show -a

This command will show a list aof all local users and their settings.

 

Posted on

vMotion fails at 21% with error 195887371

How to troubleshoot vMotion issues

Troubleshooting vMotion issues is in most cases a matter of networking issues. I will demonstrate in this case how to trace down the problem and how to find possible culprits.

What’s the problem?

Initiating a host vMotion between esx1 and esx2 passes all pre-checks, but then fails at 21% progress.

Migrate virtual machine:Failed waiting for data. Error 195887371. The ESX hosts failed to connect over the VMotion network.

See the error stack for details on the cause of this problem.
Time: 07.01.2018 19:08:08
Target: WSUS
vCenter Server: vc
Error Stack
Migration [167797862:1515348488969364] failed to connect to remote host <192.168.45.246> from host <10.0.100.102>: Timeout.
vMotion migration [167797862:1515348488969364] vMotion migration [167797862:1515348488969364] stream thread failed to connect to the remote host <192.168.45.246>: The ESX hosts failed to connect over the VMotion network
The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network. Check the vMotion network settings and physical network configuration. 
Migration [167797862:1515348488969364] failed to connect to remote host <10.0.100.102> from host <192.168.45.246>: Timeout.
vMotion migration [167797862:1515348488969364] failed to create a connection with remote host <10.0.100.102>: The ESX hosts failed to connect over the VMotion network
Failed waiting for data. Error 195887371. The ESX hosts failed to connect over the VMotion network.

Continue reading “vMotion fails at 21% with error 195887371”

Posted on

Runecast-Analyzer 1.5 – Hands-on

VMware veröffentlich in regelmäßigen Abständen neue Artikel in der VMware-Knowledgebase. Darüber hinaus gibt es Hardening-Guides und Best-Practises Guides, deren Inhalt immer wieder aktualisiert und angepasst wird. Hier verliert man schon einmal den Überblick, welcher der ESXi-Hosts noch im Einklang mit den Guides, oder den KB-Artikeln ist. Er war es vielleicht zum Zeitpunkt der Installation, aber inzwischen können sich viele Dinge geändert haben.

Auftritt Runecast-Analyzer

Hier kann der Runecast-Analyzer ein wertvolles Hilfsmittel sein. Er analysiert automatisch vCenter und ESXi-Server, vergleicht die Installation gegen aktuelle KB-Artikel, Hardening-Guides und Best-Practises Guides.

Die Installation ist recht einfach. Die Runecast-Appliance wird im Cluster bereitgestellt und mit dem vCenter verbunden. Soviel zur Konfiguration. Seit der Version 1.5 können auch mehrere vCenter mit der Runecast-Appliance verbunden werden.

Die Analyse erfolgt nicht in der Cloud, sondern im eigenen Datacenter. Es werden also keine vertraulichen Daten an Dritte weitergegeben. Continue reading “Runecast-Analyzer 1.5 – Hands-on”