Migración de Sistema Operativo, Software Aplicativo y Base de Datos Instalados en un Servidor Sun Fire V440 con Solaris 8 a un Servidor Sun Sparc T4-1 con Solaris 10 sin reinstalación.
El objetivo es llevar todo lo instalado en el servidor Sun Fire V440, Sistema Operativo Solaris 8 y aplicativos Oracle sin tener que reinstalar el software.
El Sistema Operativo Solaris 8 no puede ser instalado en el Servidor Sun Sparc T4-1, la version mínima soportada en este servidor es Solaris 10 10/09(u8), No podemos cambiar la version del software aplicativo y bases de datos ni se cuenta con los medios para una reinstalación.
Para lograr esto sin perder la información se instaló primero el Sistema Operativo Solaris 10 u13 en el servidor Sun Sparc T4-1 con el ultimo set de parches disponible.
Luego procedí a tomar una imagen flar completa del Sistema Operativo Solaris 8 2/04 en el servidor Sun Fire V440:
La imagen flar fue creada en los discos internos del servidor Sun Fire V440 y posteriormente copiado al Servidor T4-1
Para crear la imagen flar me conecté al Servidor Sun Fire V440 con usuario root y ejecuté el comando flarcreate de la siguiente manera:
**La ejecución de este comando requiere usuario root y debemos estar posicionados en el directorio raiz /
root@roatan # cd /
root@roatan # flarcreate -S -n s8-roatan /flar/s8-roatan.flar
Determining which filesystems will be included in the archive...
Creating the archive...
cpio: File size of "etc/mnttab" has
increased by 463
2756850 blocks
1 error(s)
Archive creation complete.
Una vez con la imagen flar creada en el servidor Sun Fire V440, copié el archivo flar a uno de los discos internos del servidor Sparc T4-1.
Me conecté al servidor T4-1 que tiene nombre de host guanaja y procedí con la creación de la zona para albergar el sistema operativo y aplicativos del servidor V440.
Cree la Zona para solaris 8 (branded zone) de la siguiente manera:
#el nombre de la zona se definió como s8-roatan, s8 versión de sistema operativo y roatan el nombre original del host
root@guanaja # zonecfg -z s8-roatan
#se creo una nueva configuración de zona de solaris8 usando el template SUNWsolaris8.
create -t SUNWsolaris8
# se definió el path de instalación de la zona
set zonepath=/zonas/roatan
set autoboot=true
#se seteó la dirección ip para la zona como interface de red virtual heredada de la zona global. aqui se cambió la ip original
add net
set address=172.16.1.18
set physical=bge0
set defrouter=172.16.1.1
end
#debido a que hay aplicativos en el Sistema operativo Solaris 8 instalado cuya licencia esta amarrada al hostid del equipo se definió el parametro hostid en la zona y se seteo con el mismo valor del servidor físico v440
add attr
set name=hostid
set type=string
set value=83123e3e
end
# se definió el parametro machine type para que quedará con la especificación del hardware original Sun Fire V440(sun4u)
add attr
set name=machine
set type=string
set value=sun4u
end
verify
#se salvó la configuración de la zona
commit
exit
#validé la información de definición de la zona
root@guanaja # zonecfg -z s8-roatan info
zonename: s8-roatan
zonepath: /zonas/roatan
brand: solaris8
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
hostid:
net:
address: 172.16.1.18
physical: igb0
defrouter: 172.16.1.1
attr:
name: hostid
type: string
value: 83123e3e
attr:
name: machine
type: string
value: sun4u
#exportamos la configuración de la zona para tener un respaldo de la misma
root@guanaja # zonecfg -z s8-roatan export > s8-roatan.config
#Una vez con la zona creada y el archivo imagen flar en el servidor procedimos a instalar la zona utilizando la imagen original del servidor Sun Fire v440, este procedimiento tomó al rededor de 2 horas
#Esta instalación se ejecutó de la siguiente manera:
root@guanaja # zoneadm -z s8-roatan install -p -a /flar/s8_roatan.flar
#despues de instalar la zona se procedió con el boot de la misma con el comando zoneadm boot
root@guanaja # zoneadm -z s8-roatan boot
#validamos que la zona hiso boot
root@guanaja # zoneadm list -icv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
1 s8-roatan running /zonas/roatan solaris8 shared
#Despues de esto procedimos a hacer login a la zona para validar la instalación y configuración de la misma con el comando zlogin:
root@guanaja # zlogin s8-roatan
[Connected to zone 's8-roatan' pts/1]
Your password will expire in 5 days.
Last login: Wed Jan 30 23:54:08 from 172.16.1.3
Sourcing //.profile-EIS.....
root@roatan # netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ---------- ---------
default 172.16.1.1 UG 1 429
172.16.1.0 172.16.1.18 U 1 51 igb0:1
224.0.0.0 172.16.1.18 U 1 0 igb0:1
127.0.0.1 127.0.0.1 UH 3 9 lo0:1
root@roatan # uname -X
System = SunOS
Node = roatan
Release = 5.8
KernelID = Generic_Virtual
Machine = sun4u
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 64
La zona fue instalada y todos los aplicativos iniciaron sin problemas, la ventana para esta actividad tomó 12 horas desde el inició de la creación de la imagen flar hasta las pruebas finales de los usuarios.
Despues de esto y un periodó de validación de una semana el servidor Sun Fire V440 fue reconfigurado para ambiente de desarrollo y test del aplicativo y base de datos.
El Objetivo de este blog es mostrar ejemplos de configuraciones y procedimientos en la administración de Sistemas Operativos Unix(Solaris y Linux) y Bases de Datos Oracle. Los ejemplos ya han sido probados y utilizados en la implementacion de muchos ambientes.
Mostrando entradas con la etiqueta Solaris 10. Mostrar todas las entradas
Mostrando entradas con la etiqueta Solaris 10. Mostrar todas las entradas
miércoles, 31 de agosto de 2016
Migrar de Servidor Sun Fire V440 y Sistema Operativo Solaris 8 a Servidor Sun Sparc T4-1(Solaris10) sin Reinstalación.
Etiquetas:
migration,
oracle,
Solaris,
Solaris 10,
Solaris 8,
solaris containers,
solaris zones,
Sun Fire V440,
Sun Sparc T4-1,
SUNWsolaris8,
zones
miércoles, 27 de julio de 2016
Solaris 10 VNC: Script para Habilitar VNC en Solaris 10
Solaris ofrece muchas interfaces de acceso remoto como ssh, X11, server remote redirection, etc.
En muchas ocasiones nos es requerido ejecutar tareas o procesos sin que estas se pierdan o se detengan cuando se pierde la conexion al Servidor o Sistema Operativo. Para esto lo mejor es usar VNC, para lo cual Solaris 10 ya incluye su propio vnc basado en servidor X standard lo cual nos permite redireccionar la pantalla o display en modo virtual a traves de vnc como si fuera un X Display.
A continuación presento un script el cual pueden copiar y ejecutar en el Sistema Operativo Solaris 10 para habilitar el xvnc sin tener que instalar software VNC de terceros:
#!/bin/sh
#
# habilitavnc.sh
# Script para habilitar el vnc en Solaris 10
#
# Ejecutar este script con usuario root
#
# Despues de ejecutar el script puede ingresar con VNC Viewer a
# la ip del servidor a los display :1 y :2
#
# Agrega el display 1 a la configuracion del vnc
svccfg -s application/x11/x11-server add display1
svccfg -s application/x11/x11-server:display1 addpg options application
svccfg -s application/x11/x11-server:display1 addpropvalue options/server astring: "/usr/X11/bin/Xvnc"
svccfg -s application/x11/x11-server:display1 addpropvalue options/server_args astring: '"SecurityTypes=None"'
# Agrega el display 2 a la configuracion del vnc, para poder
# utilizar dos display
svccfg -s application/x11/x11-server add display2
svccfg -s application/x11/x11-server:display2 addpg options application
svccfg -s application/x11/x11-server:display2 addpropvalue options/server astring: "/usr/X11/bin/Xvnc"
svccfg -s application/x11/x11-server:display2 addpropvalue options/server_args astring: '"SecurityTypes=None"'
svccfg -s application/x11/x11-server:display2 addpropvalue options/server_args astring: '"-alwaysshared"'
# Configura el dtlogin para que cargue configuración en cada
# reboot
if [ ! -d /etc/dt/config ] ; then
mkdir -p /etc/dt/config
fi
if [ ! -f /etc/dt/config/Xservers ] ; then
cp /usr/dt/config/Xservers /etc/dt/config/Xservers
fi
echo " :1 Local local_uid@none root /usr/X11/bin/Xserver :1" >> /etc/dt/config/Xservers
echo " :2 Local local_uid@none root /usr/X11/bin/Xserver :2" >> /etc/dt/config/Xservers
pkill -HUP dtlogin
En muchas ocasiones nos es requerido ejecutar tareas o procesos sin que estas se pierdan o se detengan cuando se pierde la conexion al Servidor o Sistema Operativo. Para esto lo mejor es usar VNC, para lo cual Solaris 10 ya incluye su propio vnc basado en servidor X standard lo cual nos permite redireccionar la pantalla o display en modo virtual a traves de vnc como si fuera un X Display.
A continuación presento un script el cual pueden copiar y ejecutar en el Sistema Operativo Solaris 10 para habilitar el xvnc sin tener que instalar software VNC de terceros:
#!/bin/sh
#
# habilitavnc.sh
# Script para habilitar el vnc en Solaris 10
#
# Ejecutar este script con usuario root
#
# Despues de ejecutar el script puede ingresar con VNC Viewer a
# la ip del servidor a los display :1 y :2
#
# Agrega el display 1 a la configuracion del vnc
svccfg -s application/x11/x11-server add display1
svccfg -s application/x11/x11-server:display1 addpg options application
svccfg -s application/x11/x11-server:display1 addpropvalue options/server astring: "/usr/X11/bin/Xvnc"
svccfg -s application/x11/x11-server:display1 addpropvalue options/server_args astring: '"SecurityTypes=None"'
# Agrega el display 2 a la configuracion del vnc, para poder
# utilizar dos display
svccfg -s application/x11/x11-server add display2
svccfg -s application/x11/x11-server:display2 addpg options application
svccfg -s application/x11/x11-server:display2 addpropvalue options/server astring: "/usr/X11/bin/Xvnc"
svccfg -s application/x11/x11-server:display2 addpropvalue options/server_args astring: '"SecurityTypes=None"'
svccfg -s application/x11/x11-server:display2 addpropvalue options/server_args astring: '"-alwaysshared"'
# Configura el dtlogin para que cargue configuración en cada
# reboot
if [ ! -d /etc/dt/config ] ; then
mkdir -p /etc/dt/config
fi
if [ ! -f /etc/dt/config/Xservers ] ; then
cp /usr/dt/config/Xservers /etc/dt/config/Xservers
fi
echo " :1 Local local_uid@none root /usr/X11/bin/Xserver :1" >> /etc/dt/config/Xservers
echo " :2 Local local_uid@none root /usr/X11/bin/Xserver :2" >> /etc/dt/config/Xservers
pkill -HUP dtlogin
lunes, 18 de julio de 2016
Administración de Privilegios y Roles en Solaris, RBAC
Se puede dar privilegios especificos a usuarios no root para que ejecuten tareas avanzadas o solo permitidas a usuarios root, esto se puede completar con los siguientes y sencillos pasos:
1. Crear una Cuenta de Role.
2. Setear Password a la cuenta Role.
3. Editar el archivo /etc/security/prof_attr y crear o buscar el profile con la descripcion de las tareas que queremos permitir ejecutar al usuario.
4. Editar el archivo /etc/security/exec_attr para ver o definir lo que el profile puede hacer o ejecutar.
5. Asociar el profile con la cuenta de role con el siguiente comando /usr/bin/rolemod.
6. Agregar el role al usario con el comando usermod.
Ejemplo:
Usar RBAC para permitir a un usuario general o no root reiniciar o apagar el servidor en ventanas de mantenimiento.
Rolename: mantenimiento
Username: operador
Profile Name: Maintenance and Repair
1. Crear la cuenta de role:
# roleadd -d /export/home/mantenimiento -m mantenimiento
Asignar password a la cuenta de role
# passwd mantenimiento
2. validar el profil Maintenance and Repair.
Ver el archivo /etc/security/prof_attr y buscar la linea de Maintenance and Repair:
Maintenance and Repair:::Maintain and repair a system:auths=solaris.smf.manage.system-log,solaris.label.range,solaris.admin.logsvc.write,solaris.admin.logsvc.read,solaris.compsys.write,solaris.compsys.read,solaris.system.shutdown;help=RtMaintAndRepair.html
3. Validar los atributos de ejecución en el archivo /etc/security/exec_attr.
Este define el comando o script a ejecutar y el uid que el role asume al ejecutarlo.
Ver el archivo /etc/security/exec_attr:
Maintenance and Repair:suser:cmd:::/sbin/bootadm:uid=0
Maintenance and Repair:suser:cmd:::/sbin/init:euid=0
Maintenance and Repair:suser:cmd:::/usr/bin/date:euid=0
Maintenance and Repair:suser:cmd:::/usr/bin/ldd:euid=0
Maintenance and Repair:suser:cmd:::/usr/bin/mdb:euid=0
Maintenance and Repair:suser:cmd:::/usr/bin/vmstat:euid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/eeprom:euid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/halt:euid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/poweroff:uid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/prtconf:euid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/reboot:uid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/syslogd:euid=0
4. Use el comando rolemod para agregar los profiles Maintenance and Repair y All al role de la siguiente manera:
# rolemod -P "Maintenance and Repair",All Mantenimiento
5. El comando rolemod actualiza el archivo /etc/user_attr file. Verifique que los cambios fueron hechos.
# more /etc/user_attr
mantenimiento::::type=role;profiles=Maintenance and Repair,All
operador::::type=normal;roles=mentenimiento
Aqui puede ver facilmente que el role mantenimiento a sido asignado al usuario operador. El profile Maintenance and Repair esta ahora asociado al role mantenimiento.
6. Use el comando usermod para agregar el role al usuario.
# usermod -R mantenimiento <username>
Listo!
Instrucciones para el Usuario:
Debe estar logeado con la cuenta de usuario requerida (en este caso usuario operador).
Cambiar el usuario al Role de la siguiente manera:
$ su - mantenimiento
Password: <enter password>
Una vez que se ha autenticado con el Role puede ejecutar cualquier comando del Profile Maintenance and Repair de la siguiente manera:
$ /sbin/init 5 #para apagar
$ /usr/sbin/reboot #para reiniciar
etc!
Para salir del Role y regresar al usuario inicial escriba exit.
1. Crear una Cuenta de Role.
2. Setear Password a la cuenta Role.
3. Editar el archivo /etc/security/prof_attr y crear o buscar el profile con la descripcion de las tareas que queremos permitir ejecutar al usuario.
4. Editar el archivo /etc/security/exec_attr para ver o definir lo que el profile puede hacer o ejecutar.
5. Asociar el profile con la cuenta de role con el siguiente comando /usr/bin/rolemod.
6. Agregar el role al usario con el comando usermod.
Ejemplo:
Usar RBAC para permitir a un usuario general o no root reiniciar o apagar el servidor en ventanas de mantenimiento.
Rolename: mantenimiento
Username: operador
Profile Name: Maintenance and Repair
1. Crear la cuenta de role:
# roleadd -d /export/home/mantenimiento -m mantenimiento
Asignar password a la cuenta de role
# passwd mantenimiento
2. validar el profil Maintenance and Repair.
Ver el archivo /etc/security/prof_attr y buscar la linea de Maintenance and Repair:
Maintenance and Repair:::Maintain and repair a system:auths=solaris.smf.manage.system-log,solaris.label.range,solaris.admin.logsvc.write,solaris.admin.logsvc.read,solaris.compsys.write,solaris.compsys.read,solaris.system.shutdown;help=RtMaintAndRepair.html
3. Validar los atributos de ejecución en el archivo /etc/security/exec_attr.
Este define el comando o script a ejecutar y el uid que el role asume al ejecutarlo.
Ver el archivo /etc/security/exec_attr:
Maintenance and Repair:suser:cmd:::/sbin/bootadm:uid=0
Maintenance and Repair:suser:cmd:::/sbin/init:euid=0
Maintenance and Repair:suser:cmd:::/usr/bin/date:euid=0
Maintenance and Repair:suser:cmd:::/usr/bin/ldd:euid=0
Maintenance and Repair:suser:cmd:::/usr/bin/mdb:euid=0
Maintenance and Repair:suser:cmd:::/usr/bin/vmstat:euid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/eeprom:euid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/halt:euid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/poweroff:uid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/prtconf:euid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/reboot:uid=0
Maintenance and Repair:suser:cmd:::/usr/sbin/syslogd:euid=0
4. Use el comando rolemod para agregar los profiles Maintenance and Repair y All al role de la siguiente manera:
# rolemod -P "Maintenance and Repair",All Mantenimiento
5. El comando rolemod actualiza el archivo /etc/user_attr file. Verifique que los cambios fueron hechos.
# more /etc/user_attr
mantenimiento::::type=role;profiles=Maintenance and Repair,All
operador::::type=normal;roles=mentenimiento
Aqui puede ver facilmente que el role mantenimiento a sido asignado al usuario operador. El profile Maintenance and Repair esta ahora asociado al role mantenimiento.
6. Use el comando usermod para agregar el role al usuario.
# usermod -R mantenimiento <username>
Listo!
Instrucciones para el Usuario:
Debe estar logeado con la cuenta de usuario requerida (en este caso usuario operador).
Cambiar el usuario al Role de la siguiente manera:
$ su - mantenimiento
Password: <enter password>
Una vez que se ha autenticado con el Role puede ejecutar cualquier comando del Profile Maintenance and Repair de la siguiente manera:
$ /sbin/init 5 #para apagar
$ /usr/sbin/reboot #para reiniciar
etc!
Para salir del Role y regresar al usuario inicial escriba exit.
lunes, 19 de enero de 2015
Oracle Solaris 10 Installation on Netra Sparc T4-1
Oracle Solaris 10 Installation on Netra Sparc T4-1
Oracle(R) Integrated Lights Out Manager
Version 3.2.1.7.f r87330
Copyright (c) 2014, Oracle and/or its affiliates. All rights reserved.
Hostname: test-1-mgmt
--> start /HOST/console
Are you sure you want to start /HOST/console (y/n)? y
Serial console started. To stop, type #.
{0} ok
{0} ok
{0} ok
{0} ok boot cdrom
Boot device: /pci@400/pci@2/pci@0/pci@4/scsi@0/disk@p6 File and args:
|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-|/-\|/-\|/-\|/
SunOS Release 5.10 Version Generic_147147-26 64-bit
Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.
Configuring devices.
Using RPC Bootparams for network configuration information.
Attempting to configure interface nxge1...
NOTICE: nxge0: xcvr addr:0x10 - link is up 10000 Mbps full duplex
NOTICE: nxge1: xcvr addr:0x11 - link is up 10000 Mbps full duplex
Skipped interface nxge1
Attempting to configure interface nxge0...
Skipped interface nxge0
Attempting to configure interface igb3...
Skipped interface igb3
Attempting to configure interface igb2...
Skipped interface igb2
Attempting to configure interface igb1...
Skipped interface igb1
Attempting to configure interface igb0...
Skipped interface igb0
Attempting to configure interface ixgbe1...
Skipped interface ixgbe1
Attempting to configure interface ixgbe0...
Skipped interface ixgbe0
svc:/system/filesystem/local:default: WARNING: /usr/sbin/zfs mount -a failed: one or more file systems failed to mount
Setting up Java. Please wait...
Serial console, reverting to text install
Beginning system identification...
Searching for configuration file(s)...
Search complete.
Discovering additional network configuration...
Select a Language
0. English
1. Brazilian Portuguese
2. French
3. German
4. Italian
5. Japanese
6. Korean
7. Simplified Chinese
8. Spanish
9. Swedish
10. Traditional Chinese
Please make a choice (0 - 10), or press h or ? for help: 0
=========================================================================
What type of terminal are you using?
1) ANSI Standard CRT
2) DEC VT52
3) DEC VT100
4) Heathkit 19
5) Lear Siegler ADM31
6) PC Console
7) Sun Command Tool
8) Sun Workstation
9) Televideo 910
10) Televideo 925
11) Wyse Model 50
12) X Terminal Emulator (xterms)
13) CDE Terminal Emulator (dtterm)
14) Other
Type the number of your choice and press Return: 3
Completing system identification...
=========================================================================
The Oracle Solaris Installation Program
The Solaris installation program is divided into a series of short sections
where you'll be prompted to provide information for the installation. At
the end of each section, you'll be able to change the selections you've
made before continuing.
About navigation...
- The mouse cannot be used
- If your keyboard does not have function keys, or they do not
respond, press ESC; the legend at the bottom of the screen
will change to show the ESC keys to use for navigation.
F2_Continue F6_Help
=========================================================================
Identify This System
On the next screens, you must identify this system as networked or
non-networked, and set the default time zone and date/time.
If this system is networked, the software will try to find the information
it needs to identify your system; you will be prompted to supply any
information it cannot find.
> To begin identifying this system, press F2.
F2_Continue F6_Help
=========================================================================
Network Connectivity
Specify Yes if the system is connected to the network by one of the Solaris
or vendor network/communication Ethernet cards that are supported on the
Solaris CD. See your hardware documentation for the current list of
supported cards.
Specify No if the system is connected to a network/communication card that
is not supported on the Solaris CD, and follow the instructions listed under
Help.
Networked
[x] Yes
[ ] No
F2_Continue F6_Help
=========================================================================
Configure Multiple Network Interfaces
Multiple network interfaces have been detected on this system. Specify all
of the network interfaces you want to configure.
Note: You must choose at least one interface to configure.
Network interfaces
[ ] ixgbe0
[ ] ixgbe1
[ ] igb0
[ ] igb1
[ ] igb2
[ ] igb3
[X] nxge0
[ ] nxge1
F2_Continue F6_Help
=========================================================================
DHCP for nxge0 Specify whether or not this network interface should use DHCP
to configure itself. Choose Yes if DHCP is to be used, or No if the network
interface is to be configured manually.
NOTE: DHCP support will not be enabled, if selected, until after the system reboots.
Use DHCP for nxge0
[ ] Yes
[X] No
F2_Continue F6_Help
=========================================================================
Host Name for nxge0
Enter the host name which identifies this system on the network. The name
must be unique within your domain; creating a duplicate host name will cause
problems on the network after you install Solaris.
A host name must have at least one character; it can contain letters,
digits, and minus signs (-).
Host name for nxge0: test-1
F2_Continue F6_Help
=========================================================================
IP Address for nxge0
Enter the Internet Protocol (IP) address for this network interface. It
must be unique and follow your site's address conventions, or
a system/network failure could result.
IP addresses contain four sets of numbers separated by periods (for example 129.200.9.1).
IP address for nxge0 10.1.51.13
F2_Continue F6_Help
=========================================================================
Subnet for nxge0
On this screen you must specify whether this system is part of a subnet. If you specify incorrectly, the system will have problems communicating on the network after you reboot.
> To make a selection, use the arrow keys to highlight the option and press Return to mark it [X].
System part of a subnet
[X] Yes
[ ] No
F2_Continue F6_Help
=========================================================================
Netmask for nxge0
On this screen you must specify the netmask of your subnet. A default netmask is shown; do not accept the default unless you are sure it is correct for your subnet. A netmask must contain four sets of numbers separated by periods (for example 255.255.255.0).
Netmask for nxge0 255.255.255.0
F2_Continue F6_Help
=========================================================================
IPv6 for nxge0
Specify whether or not you want to enable IPv6, the next generation Internet Protocol, on this network interface. Enabling IPv6 will have no effect if this machine is not on a network that provides IPv6 service. IPv4 service will not be affected if IPv6 is enabled.
> To make a selection, use the arrow keys to highlight the option and
press Return to mark it [X].
Enable IPv6 for nxge0
[ ] Yes
[X] No
F2_Continue F6_Help
=========================================================================
Please wait...
Set the Default Route for nxge0
To specify the default route, you can let the software try to detect one upon reboot, you can specify the IP address of the router, or you can choose None. Choose None if you do not have a router on your subnet.
> To make a selection, use the arrow keys to select your choice and press
Return to mark it [X].
Default Route for nxge0
[ ] Detect one upon reboot
[X] Specify one
[ ] None
F2_Continue F6_Help
=========================================================================
Default Route IP Address for nxge0
Enter the IP address of the default route. This entry will be placed in the /etc/defaultrouter file and will be the default route after you reboot (example 129.146.89.225).
Router IP Address for nxge0 10.1.51.2
F2_Continue F6_Help
=========================================================================
Confirm Information for nxge0
Confirm the following information. If it is correct, press F2;
to change any information, press F4.
Networked: Yes
DHCP: No
Host name: srp-1
IP address: 10.1.51.13
System part of a subnet: Yes
Netmask: 255.255.255.0
Enable IPv6: No
Default Route: Specify one
Router IP Address: 10.1.51.2
F2_Continue F4_Change F6_Help
=========================================================================
Just a moment...
Configure Security Policy:
Specify Yes if the system will use the Kerberos security mechanism.
Specify No if this system will use standard UNIX security.
Configure Kerberos Security
[ ] Yes
[X] No
F2_Continue F6_Help
=========================================================================
Confirm Information
Confirm the following information. If it is correct, press F2; to change any information, press F4.
Configure Kerberos Security: No
F2_Continue F4_Change F6_Help
=========================================================================
Please wait...
Starting remote procedure call (RPC) services:
Name Service
On this screen you must provide name service information. Select the name service that will be used by this system, or None if your system will either not use a name service at all, or if it will use a name service not listed here.
> To make a selection, use the arrow keys to highlight the option and press Return to mark it [X].
Name service
[ ] NIS+
[ ] NIS
[ ] DNS
[ ] LDAP
[X] None
F2_Continue F6_Help
=========================================================================
Confirm Information
> Confirm the following information. If it is correct, press F2; to change any information, press F4.
Name service: None
F2_Continue F4_Change F6_Help
Just a moment...
NFSv4 Domain Name
NFS version 4 uses a domain name that is automatically derived from the system's naming services. The derived domain name is sufficient for most configurations. In a few cases, mounts that cross domain boundaries might cause files to appear to be owned by "nobody" due to the lack of a common domain name.
The current NFSv4 default domain is: ""
NFSv4 Domain Configuration
[X] Use the NFSv4 domain derived by the system
[ ] Specify a different NFSv4 domain
F2_Continue F6_Help
=========================================================================
Confirm Information for NFSv4 Domain
> Confirm the following information. If it is correct, press F2; to change any information, press F4.
NFSv4 Domain Name: << Value to be derived dynamically >>
F2_Continue F4_Change F6_Help
=========================================================================
Time Zone
On this screen you must specify your default time zone. You can specify a time zone in three ways: select one of the continents or oceans from the list, select other - offset from GMT, or other - specify time zone file.
> To make a selection, use the arrow keys to highlight the option and press Return to mark it [X].
Continents and Oceans
[ ] Africa
[X] Americas
[ ] Antarctica
[ ] Arctic Ocean
[ ] Asia
[ ] Atlantic Ocean
[ ] Australia
[ ] Europe
[ ] Indian Ocean
F2_Continue F6_Help
=========================================================================
Country or Region
> To make a selection, use the arrow keys to highlight the option and press Return to mark it [X].
Countries and Regions
[ ] United States
[ ] Anguilla
[ ] Antigua & Barbuda
[ ] Argentina
[ ] Aruba
[ ] Bahamas
[ ] Barbados
[ ] Belize
[ ] Bolivia
[ ] Bonaire Sint Eustatius & Saba
[ ] Brazil
[ ] Canada
[ ] Cayman Islands
[ ] Guyana
[ ] Haiti
[X] Honduras
[ ] Jamaica
[ ] Martinique
[ ] Mexico
[ ] Montserrat
[ ] Nicaragua
[ ] Panama
[ ] Paraguay [K
[ ] Peru
[ ] Puerto Rico
F2_Continue F6_Help
=========================================================================
Please wait...
Date and Time
> Accept the default date and time or enter
new values.
Date and time: 2014-11-06 11:41
Year (4 digits) : 2014
Month(1-12) : 11
Day (1-31) : 06
Hour (0-23) : 11
Minute (0-59): 41
F2_Continue F6_Help
=========================================================================
Confirm Information
> Confirm the following information. If it is correct, press F2; to change any information, press F4.
Time zone: America/Tegucigalpa
Date and time: 2014-11-06 11:41:00
F2_Continue F4_Change F6_Help
Please wait...
Root Password
Please enter the root password for this system.
The root password may contain alphanumeric and special characters. For security, the password will not be displayed on the screen as you type it.
> If you do not want a root password, leave both entries blank.
Root password:
Root password:
F2_Continue F6_Help
=========================================================================
Enabling remote services
Would you like to enable network services for use by remote clients?
Selecting "No" provides a more secure configuration in
which Secure Shell is the only network service provided to
remote clients. Selecting "Yes" enables a larger set of
services as in previous Solaris releases. If in doubt, it is
safe to select "No" as any services can be individually enabled after installation.
Note: This choice only affects initial installs. It doesn't affect upgrades.
Remote services enabled
[X] Yes
[ ] No
F2_Continue F6_Help
=========================================================================
Provide Oracle Configuration Manager Registration Information
To improve products and services, Oracle Solaris communicates configuration data to Oracle after rebooting.
You can register your version of Oracle Solaris to capture this data for
your use, or the data is sent anonymously.
For information about what configuration data is communicated and how to
control this facility, see the Release Notes or
www.oracle.com/goto/solarisautoreg
> Use the arrow keys to select the option and press Return to mark it [X].
[ ]I would like to register using My Oracle Support information.
F2_Continue F6_Help
=========================================================================
Provide Oracle Configuration Manager Registration Information
To send the configuration data anonymously, complete the following fields.
If using a proxy server, provide the proxy settings.
For information about what configuration data is communicated and how to
control this facility, see the Release Notes or
www.oracle.com/goto/solarisautoreg
Proxy Server Host Name:
Proxy Server Port Number:
Proxy User Name:
HTTP Proxy Password:
F2_Continue F6_Help
=========================================================================
System identification is completed.
System identification complete.
Starting Solaris installation program...
Executing JumpStart preinstall phase...
Searching for SolStart directory...
Checking rules.ok file...
Using begin script: install_begin
Using finish script: patch_finish
Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed.
Solaris Interactive Installation
On the following screens, you can accept the defaults or you can customize how Solaris software will be installed by:
- Selecting the type of Solaris software to install
- Selecting disks to hold software you've selected
- Selecting unbundled products to be installed with Solaris
- Specifying how file systems are laid out on the disks
After completing these tasks, a summary of your selections (called a profile) will be displayed.
There are two ways to install your Solaris software:
- "Standard" installs your system from a standard Solaris Distribution.
Selecting "Standard" allows you to choose between initial install
and upgrade, if your system is upgradable.
- "Flash" installs your system from one or more Flash Archives.
F2_Standard F4_Flash F5_Exit F6_Help
=========================================================================
iSCSI Installation
Do you want to install Oracle Solaris 10 on an iSCSI target?
NOTE: You must have created the iSCSI target before beginning the OS
installation and the target system should be running Oracle Solaris 11 or
Solaris 10 U5 or greater.
If you choose to install the OS on a non-iSCSI target, you will be taken
directly to the Oracle Solaris 10 installation screens.
[X] Install on non-iSCSI target
[ ] Install on iSCSI target [8B
F2_Continue F3_Go Back F5_Exit
=========================================================================
Eject a CD/DVD Automatically?
During the installation of Solaris software, you may be usingone or more CDs/DVDs. You can choose to have the system eject each CD/DVD automatically after it is installed or you can choose to manually eject each CD/DVD.
[X] Automatically eject CD/DVD
[ ] Manually eject CD/DVD [14B
F2_Continue F3_Go Back F5_Exit
=========================================================================
Reboot After Installation?
After Solaris software is installed, the system must be rebooted. You can
choose to have the system automatically reboot, or you can choose to
manually reboot the system if you want to run scripts or do other
customizations before the reboot. You can manually reboot a system by using
the reboot(1M) command.
[X] Auto Reboot
[ ] Manual Reboot [12B
F2_Continue F3_Go Back F5_Exit
=========================================================================
Choose Media
Please specify the media from which you will install the Solaris Operating System.
Media:
[X] CD/DVD
[ ] Network File System
F2_Continue F3_Go Back F5_Exit
=========================================================================
Initializing
The system is being initialized.
Loading install media, please wait...
License
You acknowledge that your use of this Oracle Solaris software product is subject to (i) the license terms that you accepted when you obtained the right to use Oracle Solaris software; or (ii) the license terms that you agreed to when you placed your Oracle Solaris software order with Oracle; or (iii) the Oracle Solaris software license terms included with the hardware that you acquired from Oracle; or, if (i),
(ii) or (iii) are not applicable, then, (iv) the OTN License Agreement
for Oracle Solaris (which you acknowledge you have read and agree to)
available at http://www.oracle.com/technetwork/licenses/solaris-cluster-express-license-167852.html
Note: Software downloaded for trial use or downloaded as replacement
media may not be used to update any unsupported software.
F2_Accept License F5_Exit
=========================================================================
Select Geographic Regions
Select the geographic regions for which support should be installed.
> [ ] South America
> [ ] Central America
> [ ] Australasia
> [ ] Southern Europe
> [ ] Eastern Europe
> [ ] Middle East
> [ ] Northern Africa
> [ ] Southern Africa
> [ ] Asia
> [ ] Central Europe
> [ ] North America
> [ ] Western Europe
> [ ] Northern Europe
Press Return to show components
F2_Continue F3_Go Back F5_Exit F6_Help
=========================================================================
Move left, right, up, down using the arrow keys
Select System Locale
Select the initial locale to be used after the system has been installed.
[X]POSIX C ( C )
F2_Continue F3_Go Back F5_Exit F6_Help
=========================================================================
Additional Products
To scan for additional products, select the location you wishto scan.
Products found at the selected location that are in a Web Start Ready install form will be added to the Products list.
Web Start Ready product scan location:
[X] None
[ ] CD/DVD
[ ] Network File System
F2_Continue F3_Go Back F5_Exit
=========================================================================
Choose Filesystem Type
Select the filesystem to use for your Solaris installation
[X] UFS
[ ] ZFS
F2_Continue F3_Go Back F5_Exit F6_Help
=========================================================================
Select Software
Select the Solaris software to install on the system.
NOTE: After selecting a software group, you can add or remove software by
customizing it. However, this requires understanding of software
dependencies and how Solaris software is packaged.
[X] Entire Distribution plus OEM support... 10358.00 MB
[ ] Entire Distribution ...................... 10317.00 MB
[ ] Developer System Support ................. 10088.00 MB
[ ] End User System Support ................... 9048.00 MB
[ ] Core System Support ...................... 5097.00 MB
[ ] Reduced Networking Core System Support .... 5041.00 MB
F2_Continue F3_Go Back F4_Customize F5_Exit F6_Help
Please wait ...
On this screen you must select the disks for installing Solaris software.
Start by looking at the Suggested Minimum field; this value is the
approximate space needed to install the software you've selected. Keep
selecting disks until the Total Selected value exceeds the Suggested Minimum
value.
NOTE: ** denotes current boot disk
Disk Device Available Space
=============================================================================
[X] c0t5000CCA0541D3CA4d0 286090 MB
[ ] c0t5000CCA0541DBA88d0 286090 MB
[X] c0t5000CCA0541EBFA4d0 286090 MB
[ ] c0t5000CCA0541F1018d0 286090 MB
Total Selected: 0 MB
Suggested Minimum: 5323 MB
F2_Continue F3_Go Back F4_Edit F5_Exit F6_Help
=========================================================================
Preserve Data?
Do you want to preserve existing data? At least one of the disks you've selected for installing Solaris software has file systems or unnamed slices that you may want to save.
F2_Continue F3_Go Back F4_Preserve F5_Exit F6_Help
Automatically Layout File Systems?
Do you want to use auto-layout to automatically layout file systems?
Manually laying out file systems requires advanced system administration skills.
F2_Auto Layout F3_Go Back F4_Manual Layout F5_Exit F6_Help
=========================================================================
File System and Disk Layout
The summary below is your current file system and disk layout, based on the information you've supplied.
NOTE: If you choose to customize, you should understand file systems, their
intended purpose on the disk, and how changing them may affect the operation
of the system.
File sys/Mnt point Disk/Slice Size
================================================================
Overlap c0t5000CCA0541D3CA4d0s2 286090 MB
overlap c0t5000CCA0541EBFA4d0s2 286090 MB
F2_Continue F3_Go Back F4_Customize F5_Exit F6_Help
Preparing system for Solaris install
Configuring disk (c0t5000CCA0541D3CA4d0)
- Creating Solaris disk label (VTOC)
Configuring disk (c0t5000CCA0541EBFA4d0)
- Creating Solaris disk label (VTOC)
Creating and checking file systems
- Creating / (c0t5000CCA0541D3CA4d0s0)
- Creating /var (c0t5000CCA0541D3CA4d0s3)
- Creating /globaldevices (c0t5000CCA0541D3CA4d0s6)
Beginning Solaris software installation
=========================================================================
Solaris Initial Install
MBytes Installed: 0.00
MBytes Remaining: 4066.34
Installing: Fujitsu SunOS Header Files
Suscribirse a:
Entradas (Atom)