NSX-T and AVI networks via policy api
Moved to Ansible with NSX-T and AVI part 1 – cloudworkspace.blog
vSphere 7 workload manager with NSX-T 403 issue
When enabling workload manager in vSphere 7 i ran in some issue. Status MessagesFailed to list all distributed switches in vCenter 067d9c9e-af02-42aa-87d1-5bc31a43df86.API request to NSX Manager failed. Status code: 403, Status: 403 . You can solve this by enabling ‘trust’ in nsx-t manager
Vmware NSX isis between ESG and juniper/cisco
To get this running, you need metric-style wide configured on juniper/cisco cisco: conf t router isis metric-style wide Juniper: set protocols isis level 2 wide-metrics-only set protocols isis level 1 wide-metrics-only
Vmware NSX Distributed Loadbalancer
When i was figuring out the new Centralized CLI in NSX 6.2, i found an interesting command. manager> show ..snip.. dlb Distributed LoadBalancer Commands ..snip.. manager> show dlb host host-176 filter test addrsets test validity show ERROR: failed to read agent name from filter test So it looks like distributed loadbalancer is on the
VCIX-NV exam
First of all, the exam was much fun. More fun then answering a, b, c I did my exam at global knowledge in Amsterdam. The latency was really acceptable, it was not worse then labs.hol.vmware.com. Monitor resolution is just fine. It is not 1920×1080 of course, but it just fine. The web client crashes allot.
Linux filesystem becomes read-only in some cases
It has to do with: mptscsi adds DID_BUS_BUSY host status when scsi status of BUSY is returned Short description: When the SCSI I/O command is returned to the Linux SCSI midlayer with a host status of DID_BUS_BUSY, the command will be retried five times and then if the target continues to return a status of
Update Child Resource Configuration
There is a bug somewhere that causes this problem on a host. The host thinks the resource pool is not there, VC says, go ahead add it, but it already exists. You will go into a loop. Do NOT turn off DRS, this will remove all your resource pools, but put it on partial automated.
A new day with a new problem…
Today one of the SAN’s thought it was vacation. A nice error showing there was something wrong ‘vmware Failing I/O due to too many reservation conflicts’ Reading through http://kb.vmware.com/kb/1005009… Checked the volume on the console and could not even enter the directory. Management of the SAN was also unreachable. Rebooted the SAN.
Local user creation bug
Yesterday i added a local user to vSphere 4 host with the vSphere client. I forgot the ‘shell access’ box. After that i enabled the box for shell access, when logging in, the home directory did not exist. Solution for this: cd /home mkdir username chown username dirname chmod 700 dirname
Vmware blog
I will be posting vmware things i run into during my day job. This is the first post \o/ I did my vcp-410 exam on 18-dec-2009 with a score of 488/500 🙂