All Posts

Another option would be to leverage VMware Aria Operations for Networks  
yes that option is there but i was looking for a better formatted data. As the one we get from the gui export is little more of data which again needs to be formatted per requirement.
Gotcha. Only other config item I can think of is that the alert itself might be set for "Rolling window" instead of instance. It might be worth a check, my personal next stap would be to contact supp... See more...
Gotcha. Only other config item I can think of is that the alert itself might be set for "Rolling window" instead of instance. It might be worth a check, my personal next stap would be to contact support and ask them
Well currently I'm just going in and marking a pool member as "disabled/down", so I'm not even using the health check to mark it as down.   That event shows up under Operations/Events/All Events inst... See more...
Well currently I'm just going in and marking a pool member as "disabled/down", so I'm not even using the health check to mark it as down.   That event shows up under Operations/Events/All Events instantly,  however its around 2 minutes before I receive an email telling me that the backend server is down.  Also coincidentally ,  it also takes about 2 minutes before I receive a syslog event in Splunk that the backend server is down.  I feel like this alert should happen instantly. Thank you, Tony
HI All,   We recently faced a storage failure in one of our secondary sites, which resulted into NSX edge node being completely deleted (the edge VMs no longer exists). As a result we had to redplo... See more...
HI All,   We recently faced a storage failure in one of our secondary sites, which resulted into NSX edge node being completely deleted (the edge VMs no longer exists). As a result we had to redploy the edge node and reconfigure the NSX on the hosts. For the task, we removed previously used T1, T0 and were trying to remove the failed Edge nodes but when we initiated the edge node deletion, it could not be deleted and the status is set to Deletion Failed. We did try the KB https://kb.vmware.com/s/article/89283 but the api call does not do anything, the Failed Edge nodes still exists. I will be very grateful for any suggestions. NSX-T Version:  4.1.0.2.0.21761691 Thank You.
This can be tested with the example provided in the documentation, it end with the response: Response: { "error": "Input object does not have model_name field" } ERROR!: 400 Client Error: BAD REQ... See more...
This can be tested with the example provided in the documentation, it end with the response: Response: { "error": "Input object does not have model_name field" } ERROR!: 400 Client Error: BAD REQUEST for url: https://{base_url}/api/macro   I get the same response with my custom VS:   payload = { "model_name": "VirtualService", "data": { "name": "n_vs", "services": [ { "port": 80 } ], "vip":[ { "ip_address": { "type": "V4", "addr": "2.2.2.2" } } ], "application_profile_ref": "/api/applicationprofile?name=n_app_http", "pool_ref_data": { "name": "n_pool", "servers": [ { "ip": { "type": "V4", "addr": "1.1.1.1" } } ], "health_monitor_refs_data": [ { "type": "HEALTH_MONITOR_HTTP", "name": "n_http", "http_monitor": { "http_response_code": [ { "code": "HTTP_2XX" } ] } } ] } } }  
Have you checked the health monitor to make sure it triggers instantly? Generally, you want some leniency to make sure you don't generate false alerts. 
I believe your issue might be that you're adding multiple ports to both the original and the translated ports. Adding multiple ports is generally used for NAT overload.  Based in your screenshot, yo... See more...
I believe your issue might be that you're adding multiple ports to both the original and the translated ports. Adding multiple ports is generally used for NAT overload.  Based in your screenshot, you're trying to NAT all traffic to an IP, but only allow certain ports in. This would be better handled using a firewall rule. If you are specifically trying to NAT only 3 ports (while handling traffic to other ports differently), I think you'll need multiple NAT rules.
Do you have a (cleaned up if needed) example of the payload you used?
It should be possible (the Terraform provider supports it at least). Make sure you have the syntax completely correct. Based on the output there, you'll need both expression AND expressions in your ... See more...
It should be possible (the Terraform provider supports it at least). Make sure you have the syntax completely correct. Based on the output there, you'll need both expression AND expressions in your body.
Replying to my own with solution:  VMware Support says this is indeed a bug, and is "addressed in an upcoming version". This fixed all 5 of my instances Why? Still scratching my head on it.  (I didn... See more...
Replying to my own with solution:  VMware Support says this is indeed a bug, and is "addressed in an upcoming version". This fixed all 5 of my instances Why? Still scratching my head on it.  (I didn't make the suggested clones.  Call me crazy.)... Workaround steps :  A. Take a backup of nsx manager (My suggestion is to have powered off clones of each manager).  B. Log in to manager node as root and take a backup of cbm jar files as below (MUST take a backup of jars before any operation)     a. mkdir jarFileBackup     b. cp /opt/vmware/cbm/cbm-app/libweb-server-cbm.jar jarFileBackup/     c. Ensure that libweb-server-cbm.jar is copied into jarFileBackup folder C. Copy the same jar files to an additional folder to update the jar data with header size limits         a. mkdir jarFileUpdate     b. cp /opt/vmware/cbm/cbm-app/libweb-server-cbm.jar jarFileUpdate/     c. cd jarFileUpdate     d. unzip libweb-server-cbm.jar     e. cat application.properties and check the contents of application.properties     f. Append "server.max-http-header-size=32KB" to application.properties file  :        echo "server.max-http-header-size=32KB" >> application.properties        Ensure that the line gets appended to application.properties     g. rm libweb-server-cbm.jar (Removing the old jar without header size info)     h. zip -r libweb-server-cbm.jar *     i. cp libweb-server-cbm.jar /opt/vmware/cbm/cbm-app/     D. Restart cluster boot manager to use the updated jar with increased header limit using below command      /etc/init.d/nsx-cluster-boot-manager restart E. Ensure that cluster status shows correct values in UI.
Hi @ukonstantin , you mentioned problem solved but also mentioned it is not possible. Its confusing. Please confirm what you did.
Hello team, I'm currently facing an issue during the NAPP deployment using the automation appliance. The deployment process appears to be stuck with the message "TKGs status is configuring, please wa... See more...
Hello team, I'm currently facing an issue during the NAPP deployment using the automation appliance. The deployment process appears to be stuck with the message "TKGs status is configuring, please wait." In the course of troubleshooting, I also identified an error message in the vCenter logs, which reads as follows: "Resource Type Deployment, Identifier vmware-system-netop/vmware-system-netop-controller-manager is not found." If any of you have experience with a similar problem or have suggestions for how to address this error, please do not hesitate to share your thoughts.
I just successfully upgraded 5 instances of NSX 3.2.2. to 4.1.2 (using VMware-NSX-upgrade-bundle-4.1.2.0.0.22589037.mub). In the Appliances view of all five instances, the cluster is showing as orang... See more...
I just successfully upgraded 5 instances of NSX 3.2.2. to 4.1.2 (using VMware-NSX-upgrade-bundle-4.1.2.0.0.22589037.mub). In the Appliances view of all five instances, the cluster is showing as orange "unavailable". But the manager cluster is fine. A "get cluster status" shows the cluster as Stable and all manager nodes participating and "Up". The cluster VIP is working fine as well. I rebooted each manager node, but still no change. It's just the UI that is reporting it as "unavailable". I also used different web browsers. is this a bug in 4.1.2?
The maximum is 8 ECMP links/hop for each T0/VRF
Hi Team Physical uplink ECMP up to 8 Ways (Towards 8 different uplinks) Each SR support ECMP up to 8 paths (8 different Next Hop)   That means we can have  1edge cluster= SR(8nexthop)*8= total 64... See more...
Hi Team Physical uplink ECMP up to 8 Ways (Towards 8 different uplinks) Each SR support ECMP up to 8 paths (8 different Next Hop)   That means we can have  1edge cluster= SR(8nexthop)*8= total 64 paths supported Is my understanding correct ? Regards, Miltan    
Good to hear that your issue got resolved. I upgraded from 3.x to 4.x and I tried all those things but sync was not working seems that some files were missing from the upgrade on one of the managers ... See more...
Good to hear that your issue got resolved. I upgraded from 3.x to 4.x and I tried all those things but sync was not working seems that some files were missing from the upgrade on one of the managers however, I extracted .mib and copy pasted manually on all three repos and issue got resolved. 
I'm not sure if this is exactly what you are trying to do, but I was able to create a new group with two expressions using the NSX-T REST API. I'm using a direct rest call from vRO, but the principle... See more...
I'm not sure if this is exactly what you are trying to do, but I was able to create a new group with two expressions using the NSX-T REST API. I'm using a direct rest call from vRO, but the principle should be the same for PowerCLI     var expression = []; expression.push({ "member_type": "VirtualMachine", "value": "tag-1", "key": "Tag", "operator": "EQUALS", "resource_type": "Condition" }) // Not Adding a ConjunctionOperator to the expression list will make the API Call Fail // The expression array index lenght must always be odd expression.push({ "conjunction_operator": "AND", "resource_type": "ConjunctionOperator" }); expression.push({ "member_type": "VirtualMachine", "value": "tag-2", "key": "Tag", "operator": "EQUALS", "resource_type": "Condition" }) // expression.length == 3 var group = { "expression": expression, "display_name": "NewGroup", "description": "Testing Gropu Creation with multiple expressions" }; var content = JSON.stringify(group); System.log("Request Body is: " + content); var restHost = System.getModule("com.domain.basic").getConfigurationElementAttributeValueWithPath("Domain", "NSXT", "restHost"); var restRequest = restHost.createRequest("PUT", "policy/api/v1/infra/domains/{yourdomain]/groups/NewGroup", content); restRequest.contentType = "application/json"; var requestResponse = restRequest.execute();     Here is the result of the API Call in NSX-T
I've started evaluating the Avi/NSX ALB product a short while ago and try to automate the creation of some of the objects. When using the macro API to create a virtual service I cannot get past the ... See more...
I've started evaluating the Avi/NSX ALB product a short while ago and try to automate the creation of some of the objects. When using the macro API to create a virtual service I cannot get past the "Input object does not have model_name field" error. How this works is pretty confusing. First I have created a new virtual service using the UI and captured the query using the browsers' developer mode. Afterwards I used curl to make a request, for which I copied the payload 1:1 from what was captured earlier. The error "Input object does not have model_name field" accompanzing a http error 400 was returned. I've checked the payload, the model_name field was actually missing. Instead the "uri_path":"/api/virtualservice" was present. Manually adding the "model_name": "VirtualService" field to the payload did not resolve the error. Using the example provided in MACRO API (avinetworks.com) also results in the error mentioned above. Am I doing something wrong here? How does the query work, when executed using the UI without the model_name field? Overall, the REST API makes a pretty janky first impression. I've noticed a similar problem when creating a new server pool. Copied the payload from browser dev mode, query returns an errro 400 with reason of being not able to interpret the healt monitor field...
Hi everyone, Let say we have single converge vds with single vtep. We create two separate t0 and t1 routers: T0-a, t1-a T0-b, t1-b Can we do that ? Or do we need two converge vds with their vtep... See more...
Hi everyone, Let say we have single converge vds with single vtep. We create two separate t0 and t1 routers: T0-a, t1-a T0-b, t1-b Can we do that ? Or do we need two converge vds with their vteps , one vds for t0-a,t1-a, and other vds for t0-b,t1-b? Much appreciated!!