Page History

...

4) To stop/start/list internal lb vm, use existing new stop/start/listRouters command.listInternalLoadBalancer API commands.

ApiName	RequestParameters	ResponseParameters	AvailableToRegularUser
stopInternalLoadBalancerVM	id(required) force(optional, defaulted to false if not specified)	internalloadbalancervm object having parameters (the same parameters regular VR vm has): id zoneId zoneName zoneType dns1 dns2 networkdomain name podid hostId state account/domainId serviceOfferingId/serviceOfferingName	no
startInternalLoadBalancerVM	id(required)	the same as the above	no
listInternalLoadBalancerVMs	id - list by id name - list by name podId - list by podId the internal LB vm belongs to hostId - list by hostId where internal LB VM runs state - list by state zoneId - list by zoneId vpcId - list by VPC id forVpc (boolean) - list only internal LB vms that belong to vpc	the same as the above	no

Internal and Public Lb are mutually exclusive on a network/tier. If the tier has LB on the public side, then it can't have the Internal LB
Supported just on VPC networks in 4.2 release.
Only InternalLB vm can act as Internal LB provider in 4.2 release

TBD

Space shortcuts