This appears to be a conflict between the server and the network switches all along. We have redefined them as LACP balanced connections and later the network team have done the same to the switch ports. This broke everything because there was still the default route going out on the old card which had been configured by the network team to be in the team. I removed the default route from that port and hey-presto, I've got on to the new IP address properly with data being returned so a proper connection could be established.
I have then reconfigured the now redundant link to be part of the team and restarted the network services. I now have multiple LACP balanced active links.
For anyone else who may find this thread, I have two cards with four ports, so eight possible eno interfaces. Only 1, 2, 5 & 6 are cabled, so the full commands I used to bond them all together are:-
Code:
nmcli con add type team con-name team0 ifname team0 config '{"runner": {"name": "loadbalance", "tx_hash": ["eth", "ipv4", "ipv6"], "tx_balancer": {"name": "basic"} } }'
nmcli con mod team0 ipv4.addresses '10.102.16.13/24' ipv4.method manual
nmcli con add type team-slave ifname eno2 con-name team0-eno2 master team0
nmcli con add type team-slave ifname eno5 con-name team0-eno5 master team0
nmcli con add type team-slave ifname eno6 con-name team0-eno6 master team0
A new MAC address is created for the team and each bonded interface gets the same MAC address.
After the original connection was redundant, I added it to the group with this command and this edit:-
Code:
nmcli con add type team-slave ifname eno1 con-name team0-eno1 master team0
sed -i 's/ONBOOT="yes"/ONBOOT="no"/' /etc/sysconfig/network-scripts/ifcfg-eno1
Verification commands:
Code:
ip ad s
teamdctl team0 state (and variations from this)
nmcli -p
ethtool -S eno1 (or eno2, eno5 & eno6)
I hope that this is useful to someone, but at least I have it documented for myself too!
I have an OpenBSD 3.7 firewall with five network interfaces on it, one of which is connected to the Internet. I'd like to use the remaining four interfaces as a network switch for a single internal subnet. The main problem I have is that the DHCP daemon doesn't like multiple interfaces matching... (0 Replies)
I understand how to change the ip address permanently however, I need to also make a permanent change to the subnet mask. How would I accomplish this. (5 Replies)
Hi,
My project needs to migrate the existing Subnet (255.255.255.0) to a new subnet and change the ipaddresses (currently C class). How can I do that. I need some information.
John (0 Replies)
Hi,
I have a task to edit the subnet mask in almost 100+ solaris servers.Few of the servers are configured with IPMP.There will be no change of IP address or default gateway.If its a single IP we can bring NIC down,change the subnet mask in /etc/netmasks,then bring the NIC back to normal.But... (3 Replies)
I am new to this forum so please bare with me. I did search for this answer prior to posting but no luck.
Running an AIX NIM Master at 5.3TL9SP4, with about 100 clients. The subnet of one of the networks defined in the NIM env has changed. When I go to Manage Networks, Change/Show... (0 Replies)
Hello,
can anyone help me with the command to change the subnet mask on solaris 10? The mask is currently 255.255.255.255 I will like to change it to 255.255.2555.0.
Thank you (5 Replies)
I have a Solaris 11 machine with 2 network cables attached. The first one is the default route and is working okay. I am trying to activate the second on another subnet, but am sure missing something.
The first one is on 10.30.128. and with it everything works fine,
but when I try to add the... (0 Replies)
posted this on the other sub-forum
https://www.unix.com/unix-for-dummies-questions-and-answers/246504-solaris-11-2nd-nic-different-subnet.html
apologies if linking is not appropriate
Thanks for your help. (0 Replies)
Hi Guys,
Our lpars is currently running on 2 different vlans (20, 30). Now we have a requirement that vlan 30 needs to be change to vlan 31 at the same subnet. I'm not sure on what is the best approach for this or what change is involve on the AIX side.
This is our setup.
Network switch -... (5 Replies)
Hello Admins,
My ask is how can I add two different subnet IPs to same box with two different gateways?
The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware.
How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
LEARN ABOUT FREEBSD
mtest
MTEST(8) BSD System Manager's Manual MTEST(8)NAME
mtest -- test multicast socket operations
SYNOPSIS
mtest
DESCRIPTION
The mtest utility is a small program for testing multicast socket operations.
It accepts the following commands, interactively, or as part of a scripted input file (useful for automated testing):
a ifname mac-addr Join the link-layer group address mac-addr on interface ifname. The group address should be in IEEE 802 MAC
format, delimited by colon (':') characters.
d ifname mac-addr Leave the link-layer group address mac-addr on interface ifname.
m ifname 1/0 Set or reset ALLMULTI mode on interface ifname. This option is deprecated and is now a no-op.
p ifname 1/0 Set or reset promiscuous mode on interface ifname.
j mcast-addr ifname [source-addr]
Join the multicast address mcast-addr on the interface with name ifname.
If an optional source source-addr is specified, a source-specific join will be performed; if mtest is already
joined to the multicast address, the source will be added to its filter list.
l mcast-addr ifname [source-addr]
Leave the multicast address mcast-addr on the interface with address ifname. If a source source-addr is
specified, only that source will be left.
i mcast-addr ifname n source-addr ...
Set the socket with membership of mcast-addr on interface ifname to include filter mode, and add n sources
beginning with source-addr to the inclusion filter list.
e mcast-addr ifname n source-addr ...
Set the socket with membership of mcast-addr on interface ifname to exclude filter mode, and add n sources
beginning with source-addr to the exclusion filter list.
t mcast-addr ifname source-addr
Set the socket with membership of mcast-addr on interface ifname to block traffic from source source-addr.
b mcast-addr ifname source-addr
Set the socket with membership of mcast-addr on interface ifname to allow traffic from source source-addr.
g mcast-addr ifname n Print n source filter entries for mcast-addr on interface ifname.
f filename Read commands from the file filename.
s n Sleep for n seconds.
? List legal commands.
q Quit the program.
IMPLEMENTATION NOTES
For each command implemented by mtest, the address family of each argument must be identical; it is not possible to mix IPv4 multicast mem-
berships with IPv6, for example.
To support IPv6, all commands have now changed to accept an interface name rather than an interface address. For IPv4, the program will per-
form a lookup of the primary IP address based on the interface name. This may fail if no primary IP address is assigned.
SEE ALSO
D. Thaler, B. Fenner, and B. Quinn, Socket Interface Extensions for Multicast Filters, RFC 3678.
AUTHORS
Bruce Simpson
Steve Deering
Wilbert De Graaf
BSD April 29, 2009 BSD
10-08-2019
