Interface number not reflected in the reporter setup

Products

• Reporter-VA

Issue/Introduction

Environment

Release : 11.0.x.x

Resolution

The Reporter supported only the 0:0 interface configuration, before 10.1.5.x. within the initial configuration. The initial configuration script has been modified to include an input field for the Interface ID, which is a number corresponding to the available ports. For example: 1. 0:0, 2. 1:0, 3. 1:1. NIC 0 is provisioned for this VM instance. So, enter "0" instead of "1". It should be 0:0. It will always default to the interface numbering for the VM's virtual interface assigned to the VM instance.

Ref.: Perform Initial Configuration on the Reporter Appliance

The issue points to a challenge with the instance not being able to sense and pick up the presence of the assigned network interface. For this, we recommend to have the VM team engaged, to investigate the setup from the VM environment. 

Note that for a VA of the product, the image utilizes the network interfaces set up in the VM infra and if the VM setup of the network interface is right, the interface will be visible within the Reporter instance.

For Reporter deployment options, we have two documented:

• Install Reporter on a VMware Host

• Deploy on Hyper-V Hypervisor

Ref.: Install Reporter on a VMware Host

Add. Doc.: Pre-Installation Planning and Verification

It is recommended to follow the steps detailed in the install guide, while having your VM team correctly provision the network interface, to have it visible within the Reporter instance.

In a particular use case, it was found that the VM host network adapter provisioned for the Reporter instance had 10GB speed, and by adjusting the speed to 1GB, the host adapter became visible on the deployed Reporter VA instance, for configuration and use. Auto-negotiation of the speed could be tried as well.

We see the VM resource doc. below, for some reference.

Configuring the speed and duplex of an ESXi host network adapter