paco94's Posts

@p0wertje  Thank you for this tips. It helped me to spot the misplace of tier1_lr key in the vsvip part. From now, I know how to set up a vs with all its elements (vsvip and pool). So I have made... See more...
@p0wertje  Thank you for this tips. It helped me to spot the misplace of tier1_lr key in the vsvip part. From now, I know how to set up a vs with all its elements (vsvip and pool). So I have made a step beyond. Next step, modifying this vs. The short piece of available documentation says "Additionally, the same API (macro) can be used to modify any of the objects using PUT" So I was hoping of a kind of declarative API but it seems not that simple.          
Question Hi everybody, I want to provide to application responsibles an easy way to manage their Virtual Servers. I have spent few hours to try virtualservice model of ALB macro API method but th... See more...
Question Hi everybody, I want to provide to application responsibles an easy way to manage their Virtual Servers. I have spent few hours to try virtualservice model of ALB macro API method but this latter is not well documented. Until now, I have only configured successfully virtual servers and all its related components in the default cloud in the admin tenant. Unfortunately, it is not my use case and I still receive the response below as soon I try to specify another cloud. { "error": "Error in creating VirtualService test1_vs: Error in creating VirtualService test1_vs: tier1_lr not configured" } I use AVI 21.1.4 version and here is the body I use. { "model_name": "VirtualService", "data": { "name": "test1_vs", "vrf_context_ref":"/api/vrfcontext?name=sirveglabnsxt1t11", "tenant_ref": "/api/tenant?name=admin", "cloud_ref": "/api/cloud?name=POD_lab_alw", "se_group_ref": "/api/serviceenginegroup?name=lab_alw_seg1", "tier1_lr": "/infra/tier-1s/sirveglabnsxt1t11", "services": [ { "port": 80 } ], "vsvip_ref_data": { "name": "test1_vsvip", "vip": [ { "ip_address": { "type": "V4", "addr": "10.253.222.162" }, "cloud_ref": "/api/cloud?name=POD_lab_alw", "vrf_context_ref":"/api/vrfcontext?name=sirveglabnsxt1t11", "tier1_lr": "/infra/tier-1s/sirveglabnsxt1t11" } ] }, "application_profile_ref": "/api/applicationprofile?name=http_application_profile", "pool_ref_data": { "name": "test1_pool", "cloud_ref": "/api/cloud?name=POD_lab_alw", "tier1_lr": "/infra/tier-1s/sirveglabnsxt1t11", "servers": [ { "ip": { "type": "V4", "addr": "10.253.221.45" } }, { "ip": { "type": "V4", "addr": "10.253.221.46" } } ], "health_monitor_ref": "/api/healthmonitor?name=monitor_http_standard" } } } Thank in advance for any help.     Answer  
Hello Khalid, I have a similar issue on NSX-T LB 3.1.2.1 version. Uploading file with an http post request fails via a NSX-T L7 VS when the file is quite big. It works fine when the file are about... See more...
Hello Khalid, I have a similar issue on NSX-T LB 3.1.2.1 version. Uploading file with an http post request fails via a NSX-T L7 VS when the file is quite big. It works fine when the file are about 10Mb and it fails when they are about 400Mb. I don't know precisely what is the limit. It works always fine via a NSX-T L4 VS. I think about the client_max_body_size limit of NGINX but I don't know how to verify that on the edge. There is no error in error.log. Have you any clue ? Regards, Patrice