athisesan07's Posts

Hi All,  I'm struggling last 1 months to get the NSX T SNMP related monitoring with inhouse tools and zabbix/solarwinds/prtg and etc.  My basic questions is,  NSX T support Traps, also we have an ... See more...
Hi All,  I'm struggling last 1 months to get the NSX T SNMP related monitoring with inhouse tools and zabbix/solarwinds/prtg and etc.  My basic questions is,  NSX T support Traps, also we have an alram definition with OIDs as true/false noted. while trying snmpwalk on NSX manager nodes and edge nodes and I could see only receive the system related details instead of OID walk.  How can I achieve this to work, is that API to get system alerts?  any expertise can help us to actual workaround for this ?    GET https://<nsx-ip>/api/v1/alarms GET https://<nsx-ip>/api/v1/events NSX-T Version: 3.1.3.5 and 4.0.0.1   Note: Using vROPs and vRNi providing lot of things, yup I knew its SDK to fetch data. but real-world expectation is different based on all tool integrity. 
Hi All, We have some Migration scenario such as below, (Fortigate VDOM to NSX Edge) 1.  Customer have dedicated internet with /30 range on static route format. 2. Customer have dedicated P2P with ... See more...
Hi All, We have some Migration scenario such as below, (Fortigate VDOM to NSX Edge) 1.  Customer have dedicated internet with /30 range on static route format. 2. Customer have dedicated P2P with /26 range on static route format. 3. Customer have dedicated MPLS with /30 range on static/BGP route format.   Thought to NSX Side configuration We have PE-T0 with aligned with Shared-T0 toward all the customer VRF is to be connected.  Creation customer VRF and connected T1 is completed (T1 creation by VCD), but how to be assign the that above scenarios in VCD Edge gateway and customer VM segments.  Note: we knew service interface will not support the IPsec and tunnel.  Are we go single node point of interface to configure the static route without any BGP?   
Hi Sreec, thanks for your revert., As you said is correct, we are migrating VDOMs to Edges by using VCD.  this MPLS Scenario, we have L3 interface in VDOM using one IP and second IP will may apply o... See more...
Hi Sreec, thanks for your revert., As you said is correct, we are migrating VDOMs to Edges by using VCD.  this MPLS Scenario, we have L3 interface in VDOM using one IP and second IP will may apply on MPLS router which full of /30. So this this scenario how we can achieve by NSX T,  >VIP Configuration not possible with Active-Active Cluster >VRRP not compatible with NSX.  The Idea to be we thinking below,  However, T0 interface creation to mapping with external uplink, - having this Idea, we need to put some extra IPs to configure the IBGP and EBGP to achieve the MPLS with NSX T HA ensure.   Check the attached ref image,    
Hi, we thought to migrate our Fortigate vDOMs customer into NSX T Edge . Following pre- requesting been verified Internet - completed Routed Network - Completed Ipsec - Completed SSL - using ope... See more...
Hi, we thought to migrate our Fortigate vDOMs customer into NSX T Edge . Following pre- requesting been verified Internet - completed Routed Network - Completed Ipsec - Completed SSL - using open vpn with org vdc been completed MPLS - Current VDOM has /30 ips with MPLS to use the policy in physical firewall. But how to replicate same format in NSX-T 3.1.3.5 setup Can any one help out this scenario.!