Activating the Network Management Port–serial port setup

Activate the Network Management Port
By itsiti on November 12, 2010 in Solaris · 1 Comment · Updated on Sep 13, 2011

1. Log in to ILOM service processor via serial management port [SER MGT].
2. Set the working directory.
-> cd /SP/network
3. Type the following commands [static IP address]:
-> set /SP/network state=enabled
Set ’state’ to ’enabled’

-> set /SP/network pendingipaddress=xxx.xxx.xx.xxx
Set ’pendingipaddress’ to ’xxx.xxx.xx.xxx’

-> set /SP/network pendingipdiscovery=static
Set ’pendingipdiscovery’ to ’static’

-> set /SP/network pendingipnetmask=xxx.xxx.xxx.xxx
Set ’pendingipnetmask’ to ’xxx.xxx.xxx.0’

-> set /SP/network pendingipgateway=xxx.xxx.xx.xxx
Set ’pendingipgateway’ to ’xxx.xxx.xx.xxx’

-> set /SP/network commitpending=true
Set ’commitpending’ to ’true’
4. To verify
-> show /SP/network
5. Test the network management port [NET MGT] connection.
Tags: net management port
Get Daily Updates Directly to Your Mailbox:
Read more: http://itsiti.com/activate-the-network-management-port#ixzz27wE773rj

Solaris & Oracle Linux Link Aggregation

Link Aggregation is useful if you need more bandwidth for a particular server.

Here is the quick and simple way:

SOLARIS AGGREGATING PORTS:

dladm create-aggr -l active -PL3 (if 3 ports) -d igbo -d igb1 -d igb2 1

Remember to unplumb all ports– do command, then plumb the port with the following command:
Ifconfig aggr1 plumb 10.138.82.7 net mask 255.255.255.0 up

You will also need to change the host file name and make sure the IP is correct– also check other important Internet files.

__________________________________________________________________________________

Here it is explained in more detail:

Link aggregation (also known as trunking or link bonding) is a mechanism for combining one or more network interfaces to provide better throughput and failover capabilities. To use link aggregation, you need a switch that supports the Link Aggregation Control Protocol (LACP). The following provides separate configuration examples for Oracle Solaris and Oracle Linux platforms.

Steps for Oracle Solaris Platforms

In the following steps, you aggregate devices e1000g0 and e1000g1. You can list the available devices on your system using the dladm command:

# dladm show-dev
e1000g0 link: up speed: 1000 Mbps duplex: full
e1000g1 link: up speed: 1000 Mbps duplex: full
e1000g2 link: down speed: 0 Mbps duplex: half
e1000g3 link: down speed: 0 Mbps duplex: half
Interfaces e1000g0 and e1000g1 are connected to ports 0 and 1 respectively on the switch.

For further information about link aggregation, refer to the documentation for your Oracle Solaris release.

Identify the switch ports that each network interface in the aggregation uses.

In this example, ports 0 and 1 are used.

Configure the switch to use aggregation (LACP) on ports 0 and 1.

Consult the switch’s documentation for instructions on how to do this.

Create the aggregation.

Consult the dladm man page for more information on the parameters below. The policy (-P L3) must match the policy you configured for the switch ports. The last parameter, ‘1’, indicates the aggregation key.

# dladm create-aggr -P L3 -l active -T short -d e1000g0 -d e1000g1 1
You can view the aggregated device with dladm show-link and dladm show-aggr.

# dladm show-link
e1000g0 type: non-vlan mtu: 1500 device: e1000g0
e1000g1 type: non-vlan mtu: 1500 device: e1000g1
e1000g2 type: non-vlan mtu: 1500 device: e1000g2
e1000g3 type: non-vlan mtu: 1500 device: e1000g3
aggr1 type: non-vlan mtu: 1500 aggregation: key 1
#
# dladm show-aggr
key: 1 (0x0001) policy: L3 address: 0:14:4f:40:d2:4a (auto)
device address speed duplex link state
e1000g0 0:14:4f:40:d2:4a 0 Mbps half down standby
e1000g1 80:9c:4c:0:80:fe 0 Mbps half down standby
To make the device persistent, create a hostname file with the IP address assigned to the device, and reboot.

# echo “192.168.1.101” > /etc/hostname.aggr1
# reboot — -r
After the system is rebooted, verify that the device is plumbed and available.

# ifconfig -a

Adding Static, Persistent Routes on Solaris 10 and Linux

This information came from the internet–I don’t remember the source except that the route below in bold might give you a clue.

How to add static routes on Solaris or Linux

The Geek Diary ➢ Solaris ➢ Examples of adding static routes in Solaris
Examples of adding static routes in Solaris
Static Vs Dynamic routes

Static routes are added using the route command either by a script or by using command line. Dynamic routes are added by some routing daemon. Daemons that are responsible for adding dynamic routes that are currently bundled/supported with Solaris are /usr/sbin/in.routed (Routing Information Protocol(RIP)) and /usr/sbin/in.rdisc (Router Network Discovery Protocol).

Using command line

To add a non-persistent route we just simply use route add command without the option -p. Note that these routes gets flushed if you reboot the system. Below are 2 examples of adding a route (192.168.1.1) for the network 10.10.10.0/24

# route add 10.10.10.0 -netmask 255.255.255.0 192.168.1.1
# route add 10.10.10.0/24 192.168.1.1
To add a persistent route we need to use the -p parameter with the route command. In the following examples the network 10.10.10.0/24 network uses the gateway 192.168.1.1.
In most cases you will want to add a persistent route–one that is still available after reboot.
# route -p add 10.10.10.0 -netmask 255.255.255.0 192.168.1.1
# route -p add 10.10.10.0/24 192.168.1.1
To add a persistent default route (192.168.1.1) :

# route -p add default 192.168.1.1
To retrieve information about a specific route :

# route get default
route to: default
destination: default
mask: default
gateway: 192.168.1.1
interface: e1000g0
flags:
recvpipe sendpipe ssthresh rtt,ms rttvar,ms hopcount mtu expire
0 0 0 0 0 0 1500 0
To display the complete routing table :

# netstat -nr

Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
——————– ——————– —– —– ———- ———
192.168.1.0 192.168.1.30 U 1 23 e1000g0
224.0.0.0 192.168.1.30 U 1 0 e1000g0
224.0.0.0 192.168.1.30 UG 1 0
127.0.0.1 127.0.0.1 UH 4 121 lo0
The various flags (in the Flags column) :

U – The interface is up.
H – Host route. The destination is a system, not a network.
G – The delivery system is another system (an indirect route).
D – The entry was added dynamically by an ICMP redirect.
To see the persistent routes added in the system :

# route -p show
persistent: route add 10.10.10.0/24 192.168.1.1
To delete a persistent route (persistently) :

# route -p delete 10.10.10.0/24 192.168.1.1
Using rc script

The above command line method will not work in solaris 8 and 9, also in some older patch versions of solaris 10. To overcome this we have another method. We can create a rc script in /etc/rc2.d, say with name S91routes. Add the route add command in this script :

# /usr/sbin/route add 10.10.10.0 -netmask 255.255.255.0 192.168.1.1
Now when the next time the system boots up this script would run and add the route specified in the script.

Other examples

To change a route, we can use route change command ( to change default route from 192.168.1.1 to 10.10.10.1) :

# route change default 10.10.10.1
To continuously monitor any changes to the Routing table and route lookup misses we can use route monitor command :

# route monitor
got message of size 124
RTM_DELETE: Delete Route: len 124, pid: 633, seq 1, errno 0, flags:
locks: inits:
sockaddrs:
192.168.3.0 sys11ext 255.255.255.0
To flush (remove) the routing table of all gateway entries, use the route flush command.

# route flush
default 192.168.1.1 done
10.10.10.0 10.10.10.1 done
To cause the routing table to flush before the remaining options are evaluated, use the flush option before using other options :

# route -f add 10.10.10.0/24 192.168.1.1
To add a route manually to the multicast address range of 224–239 :

# route add 224.0/4 `uname -n`
To add a default static route using the /etc/defaultrouter file, add the default router IP address to the file /etc/defaultrouter. A system that is configured with an /etc/defaultrouter file does not execute the in.routed daemon.

# echo “192.168.1.1” >> /etc/defaultrouter
We can also use the /etc/gateways file to add static routes. If the /etc/gateways file exists, the in.routed daemon reads the file when it starts. Now to add a static route (192.168.1.1) for network 192.168.1.0, edit the /etc/gateways file and add below entry

# cat /etc/gateways
net 192.168.1.0 gateway 192.168.1.1
SHARE ON