[BlueOnyx:18518] Re: How can one configure additional ethernet ports on BlueOnyx 5209R?

[Peter Yim]

Thank you, Michael, for the lightning response ...

(Unfortunately, due to other priorities) I will have to work on that
early next week.

I'd like to know, though, whether that would break the GUI, if I just
manually create config files for the extra NICs under
/etc/sysconfig/network-scripts/ as per the last part of your message.

Thanks & regards. =ppy
-- 



On Thu, Oct 15, 2015 at 7:12 PM, Michael Stauber <mstauber at blueonyx.it> wrote:
> Hi Peter,
>
>> My hardware has 3 NIC ports
>>
>> When installing a plain vanilla CentOS 7 on the same hardware, one
>> would see these 3 ports as
>> - Ethernet (enp2s0f0)
>> - Ethernet (enp2s0f1)
>> - Ethernet (enp3s0)
>>
>> Upon initial successful installation of 5209R, only 1 of those 3 ports
>> was configurable ( via /root/network_settings.sh ).
>>
>> If I go to the Hardware Information page now -
>> https://{myHost}:81/phpsysinfo/sysinfo - I can see (at the bottom of
>> that screen):
>> //
>> ========== Network Usage ===========
>> Device         Received          Sent        Err/Drop
>>  enp2s0f1     0.00 KiB       0.00 KiB       0/0
>>  eth0              2.75 MiB     22.41 MiB      0/0
>>  lo              278.92 KiB   278.92 KiB      0/0
>>  enp3s0        0.00 KiB        0.00 KiB      0/0
>>
>> The Active Monitor - https://{myHost}:81/network/network_details -
>> also shows a "Secondary Interfece (eth1)" with the status of
>> "Interface Disabled"
>>
>> On the Admin GUI, I am not seeing any screen that will allow me to
>> configure the "enp2s0f1" and "enp3s0" NIC's.
>
> Yeah, the BlueOnyx GUI chokes on the crazy network device names that the
> new UDEV changes assign to network interfaces. We want (and support)
> straightforward network interface names such as "eth0", "eth1" and so on.
>
> To this end the initial setup of BlueOnyx made use of this script:
>
> /usr/sausalito/sbin/write_udev.pl
>
> It was used by /root/network_settings.sh in this way:
>
> # Create/Update /etc/udev/rules.d/70-persistent-net.rules:
> if [ ! -f /etc/udev/rules.d/70-persistent-net.rules ]; then
>         /usr/sausalito/sbin/write_udev.pl >
> /etc/udev/rules.d/70-persistent-net.rules
>         # Let's get rid of ifcfg-* files for non-ethX interfaces:
>         /bin/cp /etc/sysconfig/network-scripts/ifcfg-* /tmp/
>         /bin/rm -f /etc/sysconfig/network-scripts/ifcfg-*
>         /bin/cp /tmp/ifcfg-lo /etc/sysconfig/network-scripts/
> fi
>
> The script renames the obscured network devices to ethX (and so on) and
> stores that info in /etc/udev/rules.d/70-persistent-net.rules
>
> Which restores the traditional behaviour. Please run
> /usr/sausalito/sbin/write_udev.pl and see if it dumps info for all your
> network interfaces. If it does, you might want to redirect that info to
> your 70-persistent-net.rules:
>
> /usr/sausalito/sbin/write_udev.pl >
> /etc/udev/rules.d/70-persistent-net.rules
>
> Then (after a reboot) the interfaces should all be renamed to the
> traditional forms and can be configured through the GUI.
>
> Short of that: You can always manually create config files for the extra
> NICs under /etc/sysconfig/network-scripts/
>
> For example: If you want to configure your "enp2s0f1" interface, create
> a /etc/sysconfig/network-scripts/ifcfg-enp2s0f1 and put the network
> settings into it. Use /etc/sysconfig/network-scripts/ifcfg-eth0 as an
> example.
>
> --
> With best regards
>
> Michael Stauber
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx