Configuring DNS with NetWare 5 and NetWare 6 and OES

 

Launching the DNS/DHCP Management Console
Launch the DNS/DHCP Management Console by double-clicking its icon. The DNS/DHCP Management Console can be installed on a client workstation, or it can be accessed from Tools menu of the NetWare Administrator utility.

The first time you launch the DNS/DHCP Management Console, you are prompted to enter the name of the NDS tree where you want to set up DNS. You can click in the Enter NDS Tree Name field to select an NDS tree that you are logged into. Creating a DNS Server Object
Use the DNS/DHCP Management Console to create and set up a DNS Server object for each DNS server you plan to operate.

To create and set up a DNS Server object, complete the following steps:

1.Click the DNS Service tab of the DNS/DHCP Management Console, if necessary.
The All Zones object is the only object displayed on the DNS/DHCP Management Console’s left pane.

2.Click Create on the tool bar.
The Create New DNS Object dialog box is displayed, enabling you to create a DNS Server object or a Zone object.

3.Select DNS Server and click OK.
The Create New DNS Server dialog box is displayed, prompting you to select a DNS Server object.

4.Enter the desired server’s name or use the browse button to select the server.
5.Enter the server’s Fully Qualified Domain name, then click Create.
The DNS Server object is created and displayed in the lower pane of the DNS/DHCP Management Console.

6. Add a forwarder. Hightlight the DNS_Server object you just created. Click on Forwarding List. Click ADD, Add your ISP DNS servers IP addresses
D.        Creating a Primary DNS Zone Object

After you create a DNS Server object, use the DNS/DHCP Management Console to create and set up a Primary DNS zone. For information about how to create a secondary DNS Zone object refer to “Creating a Secondary DNS Zone Object.” For information about how to create an IN-ADDR.ARPA Zone object, refer to “Creating an IN-ADDR.ARPA Zone Object.” For information about how to create an IP6.INT Zone object,
refer to “Creating an IP6.INT Zone Object.”

To create a primary DNS Zone object, complete the following steps:

1.Click the DNS Service tab of the DNS/DHCP Management Console.
The All Zones object and the Root Server Info Zone object are displayed in the DNS/DHCP Management Console’s left pane.

2.Click Create on the tool bar, select Zone, then click OK.
The Create Zone dialog box is displayed. The default setting is to create a new, primary zone.

3.Use the browse button to select the NDS context for the zone.

4.Enter a name for the Zone object in the Zone Domain Name field.

5.In the Assign Authoritative DNS Server field, select a DNS server.
Once you have selected an authoritative DNS server, the Name Server Host Name field is filled with name of the authoritative DNS server.

6.Click Create.
A message is displayed indicating that the new zone has been created, and you are reminded to create the Address record for the host server domain name and corresponding Pointer record in the IN-ADDR.ARPA zone (if you have not already done so).

E.        Starting the DNS Server

After you have created and set up a DNS Server object and a DNS Zone object, enter the following command at the DNS server console:
LOAD NAMED

After NAMED.NLM is loaded, the DNS server can respond to queries for the zone. For more detailed information about NAMED.NLM command line options, refer to “NAMED Command Line Options.”
F.        Configuring Clients to Use DNS
Configuring clients to use DNS is performed at the client workstation.
To configure Windows NT or Windows 95 client workstations to use DNS, complete the following steps:

1.At the client desktop, select Start > Settings > Control Panel, then double-click Network.
The Network window is displayed, listing the network components installed on the client workstation.

2.Select TCP/IP, then click Properties.
The TCP/IP Properties window is displayed, usually showing the IP Address tab page.

3.Click the DNS Configuration tab.

4.Provide a hostname and domain name for each client.

5.Enter the IP address of DNS servers for this client in the reverse search order of preference, then click OK.
The client can now send DNS queries to the DNS name server.

How to install & configure a SunRay Server 4.2 on Solaris 10

 

[SRSS 4.2] How to install Sunray Server 4.2 on Solaris 10?
Posted in: Sun by Nico Maas on July 30, 2009
Download
Sun Ray Server Software (SRSS) 4.2 http://wikis.sun.com/display/SRS5/Home#tab:SRS-5-Documentation
Patches for SRSS4.2 http://www.sun-rays.org/srss.html#patches
Preparation:
Solaris Version: SRSS 4.2 requires Solaris 05/09 (u7) verify you have the correct version.
#cat /etc/release
Solaris 10 5/09 s10x_u7wos_08 X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 30 March 2009
Installation:
1.) Got root?
su
2.) Extract the software:
# unzip srss_4.2_solaris.zip
3.) Install Java (SRSS 4.2 needs java 1.6 or higher.)C
Check your java version with the following command:
# java -version
Install java 1.6 on your system. The script is chip dependent. Pick x64 or Sparc
# ./srss_4.2/Supplemental/Java_Runtime_Environment/Solaris/jre-6u13-solaris-i586.sh
# mv jre1.6.0_13/ /usr/jdk/
# rm /usr/java
# ln -s /usr/jdk/jre1.6.0_13/ /usr/java
4.) Install Apache Tomcat
# /usr/sfw/bin/gtar -xvz -C /opt -f srss_4.2/Supplemental/Apache_Tomcat/apache-tomcat-5.5.20.tar.gz
# ln -s /opt/apache-tomcat-5.5.20 /opt/apache-tomcat
5.) Install the Sun Ray Server Software
# ./srss_4.2/utinstall
take all of the defaults
Note: Now is when we would apply patches. Since this a new release there are not any yet.
# reboot
6.) Configure the Sun Ray Server Software:
# /opt/SUNWut/sbin/utconfig
Take all of the defaults except for:
Enable remote server administration? (y/[n])? y
Configure Sun Ray Kiosk Mode? (y/[n])? y
#reboot
7.) Configure the parms file and tell the server what firmware to offer out
# mkdir /tftpboot
# vi /tftpboot/srssconfig
The file should look like the following:
servers=
# /opt/SUNWut/sbin/utfwadm -A -a -V -i /tftpboot/srssconfig -f /opt/SUNWut/lib/firmware
8.) Turn on LAN connections:
# /opt/SUNWut/sbin/utadm -L on
# /opt/SUNWut/sbin/utrestart -c
At this point you have a basic Sun Ray server up and running. Any Sun Rays on the network should be displaying the Solaris log in and you should be able to log into your Solaris server through a Sun Ray.
Personal Notes:  Be careful when you make the link for Java.

To Change a Network Card to Use DHCP–Solaris 10

The following can be done

ifconfig -a — Use this to find the NIC interface

touch /etc/<interface-name>.dhcp — This will be an empty file

touch /etc/hostname.<interface-name> — This file should contain the hosname of the machine

Reboot the machine (or)

ifconfig <interface-name> unplumb
ifconfig <interface-name> plumb
ifconfig <interface-name> dhcp (or)
ifconfig <interface-name> dhcp start

eg

touch /etc/hme0.dhcp

echo “sunfire” > /etc/hostname.hme0

ifconfig hme0 unplumb
ifconfig hme0 plumb
ifconfig hme0 dhcp (or) ifconfig hme0 dhcp start

Change from DHCP to Static IP on Solaris 10

 

Reconfigure DHCP for a Static IP.
Had to do this to many times and its easy to miss a step, so here is how you change your previously DHCP configured network interface to have a Staticly assigned IP address. This is for Solaris 10 specifically, but its the same concept for linux systems as well. Most of the files will be the same as well.

1. First you need to find out the interfacename. Simplest way is probably to do an ‘ifconfig -a’ and see which interface has an ipaddress. Also there are two DHCP files for each network interface, they are:
/etc/dhcp.INTERFACENAME
and
/etc/dhcp/INTERFACENAME.dhc
2. So you know your interface now (possibly, hme0, qfe0, eth0, eth1 etc). Now we are going to manually edit/create some networking config files if they don’t exist.
Insert the hostname you want your machine to have into the file:
# echo flossyface > /etc/hostname

Insert the same hostname and ip address into the file /etc/hosts. (Seperated by a tab).
123.456.789.012 flossyface
Insert the same hostname into the file /etc/hostname.INTERFACENAME
# echo flossyface > /etc/hostname.qfe0
Insert the network name and the netmask into /etc/inet/netmasks
Insert your default router ip address into /etc/defaultrouter
add your nameservers to /etc/resolv.conf
3. Delete the dhcp files mentioned in the beginning. (qfe0 in this example.)

# rm /etc/dhcp.qfe0
# rm /etc/dhcp/qfe0.dhc
now that all files are prepared do the following:
# pkill dhcpagent
# svcadm restart network/physical

‘ifconfig -a’ – if the right interface has the right address.
‘netstat -nrv’ – if you have the right routes setup.
‘dladm show-link’ – if you are running Solaris 10 check that command as well.
Category: Solaris

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