Unitrends Appliance Adapter Naming Conventions

SUMMARY

Unitrends Appliances default vs added network adapters may include varying names. With the transition to CentOS 7 this is somewhat more complicated. This article will define the default and additional adapter names you may find in your appliance.

ISSUE

Unitrends Appliances default vs added network adapters may include varying names.  With the transition to CentOS 7 this is somewhat more complicated.  This article will define the default and additional adapter names you may find in your appliance.  

It is important that the default onboard or virtual hardware adapter be used as the Unitrends license keys are bound to this address.  

If you have disconnected the default NIC to use another, this will invalidate the appliance software license.  Unitrends Support can re-bind the software license to an alternate port for systems with active support agreements if you do not wish to reconnect the default adapter and re-activate your software key.  This process REQUIRES direct tunnel access to your system and CANNOT be perfomed via webex.  

RESOLUTION

CentOS 5/6 based appliances (Generation 1 thru 8 and CentOS 5/6 UBs) 
Onboard NICs are labled as ETH0 and increment in number sequntially
When re-imaging a CentOS 6 appliance, if add-in adapters are left in the appliance. NIC ordering may be modified.  Unitrends Support can adjust these values for you if given remote access to correct the ordering for those systems with active support agreements.  

CentOS 7 based appliances (Generation 8 or MAX series and CentOS 7 UBs)
 

Appliance Model Default NIC Port
(MAC License Bound)
Other NIC ports Dedicated IPMI
8002/8004 eno1                  as P1 (1gbit) N/A N/A
8006/8008/8010/8012 enp27s0            as P0 (1gbit) N/A N/A
Max2/Max4/Max8 eno1                  as eno1 (1gbit) eno2 (1gbit) eno3/4 (10gbit) Yes
8016S/8020S eno1                  as P1 (10gbit) eno2                   as P2 (10gbit) Yes
8024S/8032S enp3s0f0           as P0 (10gbit) enp3s0f1            as P1 (10gbit) Yes
8040S/8060S/8080S enp3s0f0           as P0 (10gbit) enp3s0f1            as P1 (10gbit) Yes
8100S/8120S enp3s0f0           as P0 (10gbit) enp3s0f1            as P1 (10gbit) Yes
UB Virtual Appliance      

TASKS

If your appliance will use multipole network adapters concurrently to access multiple independent subnets, it is required by Linux and TCP/IP rules those subnets are non-routable from each other.  Connection of multiple adapters in the same subnet will result in ARP storms and will reduce functionality and potentially impact your network negatively.  .  

Unitrends does not at this time support bonding of adapters in Generation 7 or 8 systems or virtually in UB systems (appliance bonding at a host adapter level that is invisible to a VM is accept\able and in fact recommended).   Legacy appliances equipped with 4x1gbit Intel adapters would support bonding on those connections, but these components are EOL and can no longer be provided.  Due to IPMI integration, onboard adapters in Unitrends appliances are not compatible with bonding at all. We are researching adapter inclusion for the future to provide CentOS 7 compatible bonding adapters for 2U and higher appliances. There is no ETA for this support.  

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section