Provision Remote Access for Support Ops


For instances when DNIF support team requires an authorised access to your network devices in order to help you better. A provision for remote access via a VPN tunnel helps in resolving issues promptly.

Installation and configuration processes are streamlined to a great extent, DNIF is designed to ease end-user efforts with a crisp documentation. Although, if a remote access is required by the support team, following requisites should be met for smooth and secure remote sessions:

  • For customers with privately owned and managed VPN servers, please enable/update your ACL with following details for DNIF components:
Protocol Source IP Source Port Direction Destination IP Destination Port
TCP DNIF Support Cloud Server Any Ingress DNIF [AD,DS,CR, A10] host SSH PORT [22 or Custom-Port if changed]
TCP DNIF Support Cloud Server Any Ingress DNIF [A10,DS] host API PORT [443]
Required network details

Note: DNIF Support Cloud Server IP will be provided by DNIF support team on request.

  • If VPN access cannot be provisioned, then a direct access to DNIF host machines over SSL is recommended by using either 1:1 Public Address [Direct/NAT] or 1:1 Public Address [PAT] configuration.

1:1 Public Address [Direct/NAT]: Using direct 1:1 mapping for Public IP to DNIF host machines via secured channels.

Network Address Translation
Protocol Source IP Source Port Direction Destination IP Destination Port
TCP DNIF Support Cloud Server Any Ingress DNIF [AD,DS,CR, A10] host public IP SSH PORT [22 or Custom-Port if changed]
TCP DNIF Support Cloud Server Any Ingress DNIF [A10,DS] host public IP API PORT [443]

Note: DNIF Support Cloud Server IP will be provided by DNIF support team on request.