Uncategorized
Oracle Database Appliance (ODA) Firstnet Utility In Action
About Firstnet Utility
The “oakcli configure firstnet” command is used to configure an initial network on Oracle Database Appliance (ODA) that enables you to copy ODA End User Bundle software to ODA server.
oakcli configure firstnet allows you to establish the network interfaces for the Oracle Database Appliance upon first usage.
Once you have completed the reimaging of ODA servers, you should log onto the one of the node ILOM console and do the initial configuration of the Oracle Database Appliance network using the command firstnet.
The bond0 interface is configured when execute the firstnet utility.
Before running firstnet, ensure that you allocated IP addresses and verify that their entries in the DNS have been completed.
Execute firstnet utility
Default password for root user on ILOM is “changeme”
login as: root
Using keyboard-interactive authentication.
Password:
Oracle(R) Integrated Lights Out Manager
Version 3.2.4.46.a r101689
Copyright (c) 2015, Oracle and/or its affiliates. All rights reserved.
Warning: password is set to factory default.
Hostname: ORACLESP-1113NML13N
->
(->) This means you are connect to ILOM now.
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type ESC (
Oracle Linux Server release 6.8
Kernel 2.6.39-400.290.1.el6uek.x86_64 on an x86_64
oak1 login: root
Password:
Last login: Wed Jun 7 11:32:57 on tty1
/opt/oracle/oak/bin/oakcli
Select the Interface to configure the network on (bond0 bond1) [bond0]:
Configure DHCP on bond0 (yes/no) [no]:
INFO: You have chosen Static configuration
Enter the IP address to configure : 10.10.17.11
Enter the Netmask address to configure : 255.255.255.0
Enter the Gateway address to configure[10.10.17.1] : 10.10.15.1
INFO: Plumbing the IPs now
INFO: Restarting the network
Shutting down interface bond0: bonding: bond0: Removing slave eth2.
bonding: bond0: Warning: the permanent HWaddr of eth2 – 00:10:e0:62:3f:f2 – is still in use by bond0. Set the
HWaddr of eth2 to a different address to avoid conflicts.
bonding: bond0: releasing active interface eth2
bonding: bond0: Removing slave eth3.
bonding: bond0: releasing backup interface eth3
[ OK ]
Shutting down interface bond1: bonding: bond1: Removing slave eth4.
bonding: bond1: Warning: the permanent HWaddr of eth4 – 00:10:e0:62:3f:f4 – is still in use by bond1. Set the
HWaddr of eth4 to a different address to avoid conflicts.
bonding: bond1: releasing backup interface eth4
bonding: bond1: Removing slave eth5.
bonding: bond1: releasing backup interface eth5
[ OK ]
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: bonding: bond0: setting mode to active-backup (1).
bonding: bond0: Setting MII monitoring interval to 100.
bonding: bond0: Adding slave eth2.
bonding: bond0: enslaving eth2 as a backup interface with a down link.
bonding: bond0: Adding slave eth3.
bonding: bond0: enslaving eth3 as a backup interface with a down link.
bonding: bond0: Setting eth2 as primary slave.
Determining if ip address 172.16.202.71 is already in use for device bond0…
ixgbe 0000:20:00.0: eth2: NIC Link is Up 1 Gbps, Flow Control: RX
bonding: bond0: link status definitely up for interface eth2, 1000 Mbps full duplex.
bonding: bond0: making interface eth2 the new active one.
bonding: bond0: first active interface up!
[ OK ]
Bringing up interface bond1: bonding: bond1: setting mode to active-backup (1).
bonding: bond1: Setting MII monitoring interval to 100.
bonding: bond1: Adding slave eth4.
bonding: bond1: enslaving eth4 as a backup interface with a down link.
bonding: bond1: Adding slave eth5.
bonding: bond1: enslaving eth5 as a backup interface with a down link.
bonding: bond1: Setting eth4 as primary slave.
[ OK ]
Bringing up interface eth0: Determining if ip address 192.168.16.24 is already in use for device eth0…
ixgbe 0000:a0:00.0: eth0: detected SFP+: 3
ixgbe 0000:a0:00.0: eth0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ OK ]
Bringing up interface eth1: Determining if ip address 192.168.17.24 is already in use for device eth1…
ixgbe 0000:a0:00.1: eth1: detected SFP+: 4
ixgbe 0000:a0:00.1: eth1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ OK ]
[root@oak1 ~]#
Once the network interfaces have been configured, you need to test them by using the ping command on the node.
[root@oak1 ~]# ping 10.10.17.11
PING 172.16.202.71 (10.10.17.11) 56(84) bytes of data.
64 bytes from 10.10.17.11: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 10.10.17.11: icmp_seq=2 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=3 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=4 ttl=64 time=0.006 ms
64 bytes from 10.10.17.11: icmp_seq=5 ttl=64 time=0.005 ms
— 172.16.202.71 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4544ms
rtt min/avg/max/mdev = 0.005/0.010/0.027/0.009 ms
[root@oak1 ~]# ifconfig
bond0 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
inet addr:10.10.17.11 Bcast:10.10.17.255 Mask:255.255.255.0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)
bond1 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
UP BROADCAST MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B4
inet addr:192.168.16.24 Bcast:192.168.16.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:138257 errors:0 dropped:0 overruns:0 frame:0
TX packets:138436 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11200490 (10.6 MiB) TX bytes:11134648 (10.6 MiB)
eth1 Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B5
inet addr:192.168.17.24 Bcast:192.168.17.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:138217 errors:0 dropped:0 overruns:0 frame:0
TX packets:138434 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11197894 (10.6 MiB) TX bytes:11134800 (10.6 MiB)
eth2 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)
eth3 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth4 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth5 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:512371 errors:0 dropped:0 overruns:0 frame:0
TX packets:512371 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:38908072 (37.1 MiB) TX bytes:38908072 (37.1 MiB)
Conclusion:
In this short article we have learned about Firstnet utility and have seen to use it to configure initial network to copy software to ODA servers.
The “oakcli configure firstnet” command is used to configure an initial network on Oracle Database Appliance (ODA) that enables you to copy ODA End User Bundle software to ODA server.
oakcli configure firstnet allows you to establish the network interfaces for the Oracle Database Appliance upon first usage.
Once you have completed the reimaging of ODA servers, you should log onto the one of the node ILOM console and do the initial configuration of the Oracle Database Appliance network using the command firstnet.
The bond0 interface is configured when execute the firstnet utility.
Before running firstnet, ensure that you allocated IP addresses and verify that their entries in the DNS have been completed.
Execute firstnet utility
- Connect to the ILOM console using browser or putty to configure the initial IP address for the node you are connected to.
Default password for root user on ILOM is “changeme”
login as: root
Using keyboard-interactive authentication.
Password:
Oracle(R) Integrated Lights Out Manager
Version 3.2.4.46.a r101689
Copyright (c) 2015, Oracle and/or its affiliates. All rights reserved.
Warning: password is set to factory default.
Hostname: ORACLESP-1113NML13N
->
(->) This means you are connect to ILOM now.
- Start the Serial console by executing the following command. When prompted, enter y and then root and it’s password. Default root password for ODA servers is “welcome1”
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type ESC (
Oracle Linux Server release 6.8
Kernel 2.6.39-400.290.1.el6uek.x86_64 on an x86_64
oak1 login: root
Password:
Last login: Wed Jun 7 11:32:57 on tty1
- oakcli used to execute the firstnet utility
/opt/oracle/oak/bin/oakcli
- Now execute the firstnet utility as follows:
Select the Interface to configure the network on (bond0 bond1) [bond0]:
Configure DHCP on bond0 (yes/no) [no]:
INFO: You have chosen Static configuration
Enter the IP address to configure : 10.10.17.11
Enter the Netmask address to configure : 255.255.255.0
Enter the Gateway address to configure[10.10.17.1] : 10.10.15.1
INFO: Plumbing the IPs now
INFO: Restarting the network
Shutting down interface bond0: bonding: bond0: Removing slave eth2.
bonding: bond0: Warning: the permanent HWaddr of eth2 – 00:10:e0:62:3f:f2 – is still in use by bond0. Set the
HWaddr of eth2 to a different address to avoid conflicts.
bonding: bond0: releasing active interface eth2
bonding: bond0: Removing slave eth3.
bonding: bond0: releasing backup interface eth3
[ OK ]
Shutting down interface bond1: bonding: bond1: Removing slave eth4.
bonding: bond1: Warning: the permanent HWaddr of eth4 – 00:10:e0:62:3f:f4 – is still in use by bond1. Set the
HWaddr of eth4 to a different address to avoid conflicts.
bonding: bond1: releasing backup interface eth4
bonding: bond1: Removing slave eth5.
bonding: bond1: releasing backup interface eth5
[ OK ]
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: bonding: bond0: setting mode to active-backup (1).
bonding: bond0: Setting MII monitoring interval to 100.
bonding: bond0: Adding slave eth2.
bonding: bond0: enslaving eth2 as a backup interface with a down link.
bonding: bond0: Adding slave eth3.
bonding: bond0: enslaving eth3 as a backup interface with a down link.
bonding: bond0: Setting eth2 as primary slave.
Determining if ip address 172.16.202.71 is already in use for device bond0…
ixgbe 0000:20:00.0: eth2: NIC Link is Up 1 Gbps, Flow Control: RX
bonding: bond0: link status definitely up for interface eth2, 1000 Mbps full duplex.
bonding: bond0: making interface eth2 the new active one.
bonding: bond0: first active interface up!
[ OK ]
Bringing up interface bond1: bonding: bond1: setting mode to active-backup (1).
bonding: bond1: Setting MII monitoring interval to 100.
bonding: bond1: Adding slave eth4.
bonding: bond1: enslaving eth4 as a backup interface with a down link.
bonding: bond1: Adding slave eth5.
bonding: bond1: enslaving eth5 as a backup interface with a down link.
bonding: bond1: Setting eth4 as primary slave.
[ OK ]
Bringing up interface eth0: Determining if ip address 192.168.16.24 is already in use for device eth0…
ixgbe 0000:a0:00.0: eth0: detected SFP+: 3
ixgbe 0000:a0:00.0: eth0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ OK ]
Bringing up interface eth1: Determining if ip address 192.168.17.24 is already in use for device eth1…
ixgbe 0000:a0:00.1: eth1: detected SFP+: 4
ixgbe 0000:a0:00.1: eth1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[ OK ]
[root@oak1 ~]#
Once the network interfaces have been configured, you need to test them by using the ping command on the node.
[root@oak1 ~]# ping 10.10.17.11
PING 172.16.202.71 (10.10.17.11) 56(84) bytes of data.
64 bytes from 10.10.17.11: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 10.10.17.11: icmp_seq=2 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=3 ttl=64 time=0.008 ms
64 bytes from 10.10.17.11: icmp_seq=4 ttl=64 time=0.006 ms
64 bytes from 10.10.17.11: icmp_seq=5 ttl=64 time=0.005 ms
— 172.16.202.71 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4544ms
rtt min/avg/max/mdev = 0.005/0.010/0.027/0.009 ms
[root@oak1 ~]# ifconfig
bond0 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
inet addr:10.10.17.11 Bcast:10.10.17.255 Mask:255.255.255.0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)
bond1 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
UP BROADCAST MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B4
inet addr:192.168.16.24 Bcast:192.168.16.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:138257 errors:0 dropped:0 overruns:0 frame:0
TX packets:138436 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11200490 (10.6 MiB) TX bytes:11134648 (10.6 MiB)
eth1 Link encap:Ethernet HWaddr 90:E2:BA:81:2B:B5
inet addr:192.168.17.24 Bcast:192.168.17.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:138217 errors:0 dropped:0 overruns:0 frame:0
TX packets:138434 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11197894 (10.6 MiB) TX bytes:11134800 (10.6 MiB)
eth2 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:762 (762.0 b) TX bytes:546 (546.0 b)
eth3 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F2
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth4 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth5 Link encap:Ethernet HWaddr 00:10:E0:62:3F:F4
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:512371 errors:0 dropped:0 overruns:0 frame:0
TX packets:512371 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:38908072 (37.1 MiB) TX bytes:38908072 (37.1 MiB)
Conclusion:
In this short article we have learned about Firstnet utility and have seen to use it to configure initial network to copy software to ODA servers.