how to resolve this issue???
real error on # service network restart
kernel ==> 2.6.32-200.21.1.el5uek, oracle linux 5.6
Shutting down interface <<vlan intrface >>: bonding: bond1: Warning: the permanent HWaddr
of <<vlan intrface>>- 00:14:5E:xx:1C:xx - is still in use by bond1. Set the HWaddr of <<vlan intrface>>
to a different address to avoid conflicts.
how to resolve this issue???
I have no idea.
If you read my earlier statement, you were simply being guided to NOT multi-post.
That is poor forum etiquette here and every other legitimate online forum web site I've ever examined.
Keep your forum inquiries in a single discussion thread.
Next time there wont be any duplicate pls
From what I understand, bonding is designed to work with different physical interfaces, each having its unique MAC address. A VLAN interface uses the same MAC address as the physical device it binds to. Since you have only one NIC, all VLAN devices have the same MAC address, which conflicts with NIC bonding. What are you trying to accomplish to bond 2 VLAN interfaces that use one and the same NIC?
Can able to assign hardware address(dummy mac) to each vlan only for bonding interface? is there anyway
I have Oracle Virtual Box
i need this if somebody can suggest is this possible if yes,,,pls let me know how do i achieve this
1) Exalogic vm1 - here i have eth0, bond0, [bonding bond1& (vlan121, vlan122)], ilom(vlan120)
1) Exalogic vm2 - here i have eth0, bond0, [bonding bond1 & (vlan131, vlan132)], ilom(vlan130)
The idea of using VLAN interfaces is to setup different Ethernet networks using a single interface. Bonding creates a single network access point comprised of two or more ethernet devices for performance and redundancy.
What is your idea behind bonding two VLAN's? What are you trying to accomplish?
How does VirtualBox fit into the picture?
Does the Exalogic server not have more than 1 Ethernet port?
yes you are right with VLAN and bonding interfaces
cloud will communicate fast and relaible between N compute nodes, storage nodes, where N is the number here bonding is needed for fast & active backup betweek networks
i need to simulate the exalogic cloud, to experiment i can't go for buying a exalogic machine[full, half...etc rack] with so much of cost involved. I am trying to simulate the same environment using the oracle provided exalogic software(cloud) and having vlans to fulfill the gateway switch related issues and multiple NICs on the single exalogic compute node.
Hence i create 2 compute nodes and 1 sun zfs storage node , put together into the cloud stack, this is my goal using Virtual Machines (Oracle Virtual Box)
hope u get me by now
have a look the network diagram here http://docs.oracle.com/cd/E18476_01/doc.220/e18479/net.htm#BHCJBICD
Not sure, so you are using VirtualBox now, trying to simulate the setup?
If that's the case, why don't you simpy add another virtual machine Ethernet adapter in the virtual machine setup? You can then bond the interfaces and create your VLAN's on top of it.
To find out how to simulate bonding under VirtualBox you may find the following useful:
Thanks a lot Dude about this info,
i will try to simulate this and will see the progress
I have a basic query
if single machine has 4 NICs [physical and virtual] and another machine has 4 NICs[physical and virtual]
How do i make interaction between them
gateway : 192.168.1.1
nic0 of box1 to nic0 of box2 --done working ex: 192.168.1.12, 255.255.255.0, 192.168.1.13, 255.255.255.0,
vlan120 of box1 to vlan130 of box2 not working ex: 192.168.100.2, 255.255.255.0, 192.168.100.3, 255.255.255.0,
box1#ping 192.168.1.13 -- works well
box1#ping 192.168.100.3 -- network unreachable how do i make this working? this is what oracle cloud uses
I'm not really sure I understand your question. If you want any or all network interface cards in a computer to be used for communication, then any or all need to be connected to a switch or network router using a cable. Every real and virtual NIC has a physical address (MAC), which the device broadcasts when initialized to tell other devices that it's there. The MAC address is a unique number. The mapping of an IP address to a MAC address is maintained by an ARP table.
Network redundancy typically shifts an IP address among available devices. If a devices fails, a standby is activated, which updates the ARP table to inform other devices of the change and IP communiation can continue. I have also seen non Linux systems, which actually modify the phsycial MAC address of a device. If you want to use mutliple NIC's to work in a team for performance, the system network stack needs to support inverse multiplexing and you need to connect each device to a managed network switch that supports Link Aggregation Ccontrol Protocol (802.3ad).
Your ping issue might be due to TCP/IP routing. Devices by default see each other only if they are phycially connected through a switch and share the same network or subnet. If you have devices with different subnets you need to configure a TCP/IP gateway or bridge. This is basic TCP/IP routing and knowledge, which is explained by many free sources available on the Internet. Just search Google for TCP/IP routing basics.
Looking at your TCP/IP configuration from the information you provided, your VLAN interface is not within the network (netmask) of your gateway, hence the VLAN interface has no knowledge of your other networks. So perhaps if you change your VLAN to 255.255.0.0 it will work.
No linux Network admin good help till now
How do i make connectivity between these subnets?
I need to setup this lab and communicate with each other
I need some assistance this lab setup from Linux Network Admin person
is this correct what im trying to achive, the subnets?
xeon <--> vm1 <--> vm2
Xeon Host CentOS 6.4 i686
- eth0 - 192.168.1.10, 255.255.255.0
Oracle Virtual Box 4.2.16 and used bridge adaptor
Guest OS - Oracle 5.3
- eth0 - 192.168.1.12, 255.255.255.0
Bond1[eth1,eth2] - 192.168.10.12, 255.255.255.0
eth3[ilom] - 192.168.100.12, 255.255.255.0
bond0 - 10.0.0.2, 255.0.0.0
- eth0 - 192.168.1.13, 255.255.255.0
Bond1[eth1,eth2] - 192.168.10.13, 255.255.255.0
eth3[ilom] - 192.168.100.13, 255.255.255.0
bond0 - 10.0.0.3, 255.0.0.0
The subnets together with your IP address define the network broadcast address range. You have 3 different networks. You can setup your 192.168 network using a 255.255.0.0 netmask which will allow you to use the full 192.168.0.0 - 192.168.255.255 IP range. You will need an IP gateway to connect the 10.0 network with the 192.168. network. If you do not understand what this means I suggest to fire up google, e.g. Understanding TCP/IP addressing and subnetting basics