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:-
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:-
Verification commands:
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
rp
RP(4) BSD Kernel Interfaces Manual RP(4)NAME
rp -- driver for Comtrol RocketPort Intelligent Serial Port Cards
SYNOPSIS
device rp
For ISA cards, you must specify the port address in /boot/device.hints:
hint.rp.0.at="isa"
hint.rp.0.port="0x100"
DESCRIPTION
This driver provides a kernel device driver for the RocketPort and RocketPort RA serial boards. These boards provide 8, 16, or 32 high-speed
serial ports while requiring only 68 bytes of I/O space for all 8, 16, or 32 ports, and do not require an interrupt channel. This driver
supports up to four RocketPort or RocketPort RA boards in one machine simultaneously. If you are using four 32 port RocketPort boards, you
can put as many as 128 intelligent serial ports on your system.
The rp driver supports the following speeds: 50, 75, 110, 134, 150, 200, 300, 600, 1200, 1800, 2400, 4800, 9600, 19200, 38400, 7200, 14400,
57600, 76800, 115200, and 230400. (You must use termios(4), rather than the old style ioctl interface to use non-traditional speeds.)
An open on the rp driver will block until carrier is present, unless O_NONBLOCK or CLOCAL is set.
HARDWARE CONFIGURATION
The first RocketPort or RocketPort RA card requires a 68-byte contiguous block of I/O addresses, starting at one of the following: 0x100h,
0x140h, 0x180h, 0x200h, 0x240h, 0x280h, 0x300h, 0x340h, 0x380h. The second, third, and fourth RocketPort cards require only a 64-byte con-
tiguous block of I/O addresses, starting at one of the above address ranges. The I/O address range used by any of the RocketPort cards must
not conflict with any other cards in the system, including other RocketPort cards. The starting range of the I/O ports used by each card
must match with the I/O address specified in /boot/device.hints.
Since the first RocketPort uses 68 I/O addresses, if the first card is set to use an I/O block starting at 0x100, it will occupy the I/O
ports between 0x100 and 0x143. This means that the second, third, or fourth RocketPort board may not use the block of addresses starting at
0x140, since the first three I/O addresses of that range are used by the first board. This is an important point to keep in mind.
If you have two ISA cards, one installed at 0x100 and the second installed at 0x180, then you should add the following to /boot/device.hints:
hint.rp.0.at="isa"
hint.rp.0.port="0x100"
hint.rp.1.at="isa"
hint.rp.1.port="0x180"
The configuration of the RocketPort cards is done via the set of 8 DIP switches, labeled SW1 on the RocketPort card:
+-------------------------------+
| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
+-------+-------+---------------+
| Unused| Card | I/O Port Block|
+-------------------------------+
DIP switches 7 and 8 are unused, and must be left on.
DIP switches 6 and 5 identify the card number of each RocketPort card. The first card installed in the system must have its DIP switches set
as card number one; the second card installed in the system must have its DIP switches set as card number two; and so on. As shipped from
the factory, DIP switches 6 and 5 are both on by default, indicating that this is the first card installed on the system:
DIP Switches
6 5
===================
On On First Card
On Off Second Card
Off On Third Card
Off Off Fourth Card
DIP switches 4, 3, 2, and 1 indicate the I/O address range used by the first RocketPort card. If there are more than one RocketPort cards
installed in a system, the second, third and fourth RocketPort cards must also be set to the I/O address range used by the first RocketPort
card; all cards must have these DIP switches set identically for proper operation. As shipped from the factory, DIP switch 4 is on, and
switches 3, 2, and 1 are off by default, indicating an I/O address range used by the first card which starts at 0x180 and extends to 0x1C3.
DIP Switches I/O Address Range
4 3 2 1 Used by the First Card
=====================================
On Off On Off 100-143
On Off Off On 140-183
On Off Off Off 180-1C3
Off On On Off 200-243
Off On Off On 240-283
Off On Off Off 280-2C3
Off Off On Off 300-343
Off Off Off On 340-383
Off Off Off Off 380-3C3
FILES
/dev/ttyR[0-4][0-9a-f]
AUTHORS
Theodore Ts'o <tytso@mit.edu>
This driver was written under contract for Comtrol Corporation. For dealer, distributor and other information regarding Comtrol RocketPort,
contact Comtrol Corporation at (800) 926-6876 or send email to <info@comtrol.com>. To report bugs for this driver, please send email to
<bug-bsdi-rocketport@comtrol.com>.
BUGS
If incoming software flow control is enabled on a 486 or Pentium machine, and the flow control is very heavily exercised, on rare occasions a
character will get dropped. This problem does not occur on a 386, and it is not currently known whether the bug is in the rp driver or in
the BSD/OS tty layer.
BSD November 15, 1995 BSD