Friday, December 12, 2014

VMware SRM stuff

note to self

Came across this weird error and spent a good amount of time searching around with not much luck. As it turned out, lot of time could have been saved with a simple reboot of the vCenter server appliance.

SRM 5.8
vCenter Server Appliance 5.5, vSphere Web Client

SRM was fully functional when accessed via one of the vCenters while other gave error "getAttribute: Session already invalidated" when provided the credentials to access the remote vCenter.

A simple reboot of the problematic vCenter brought everything back to normal state, many hours later. When in doubt, reboot is the lesson i suppose.

2 comments:

GandalfUFR said...

Had the same issue, looked for hours in LOG files and WEB ... until I found your post. Thanks a lot for publishing!!!

Yajith Dayarathna said...

@GandalfUFR Thanks for the feedback. Glad to hear it was helpful! :-)

changing opnsense mtu

 note to self When an OpnSense is deployed on Proxmox environment where MTU is <1500, it doesn't seem to auto-detect and leaves the O...