COMMS Suite 7u2 on Solaris 11 in Solaris 10 branded Zone

Unfortunately it is not possible to install Communication Suite 7u2 native on Solaris 11 because the packaging system has changed in Solaris 11. Unfortunately there is no patchadd available any more. To get benefits of Solaris 11 for COMMS Suite, it is possible to install the COMMS Suite into a Solaris 10 branded Zone.

What's new in Solaris 11


Installation Notes COMMS Suite on Solaris 11 in Solaris 10 branded Zone

NOTE: Use two Network Adapter for Virtual Machine Setup, and configure the second Network Adapter to be used by the Solaris 10 branded Zone. It turns out that I can not connect to the Zone if only one Network Adapter is configured for the Virtual Machine Setup. My wild guess on this, it is a regression (or Security Rule) of the Virtual Machine, to 'allow' only one MAC address for the Virtual Machine.

Install Solaris 11


Configure Zone

root@host:~# /usr/sbin/zonecfg -z s10
s10: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:s10>  create -t SYSsolaris10
zonecfg:s10>  set zonepath=/export/s10
zonecfg:s10>  verify
zonecfg:s10>  commit
zonecfg:s10>  exit

Install Solaris 10 Zone from flash archive.
More about flash archive can be found here.

zoneadm -z s10 install -a s10u9b14ax.flar -u

Install rpc.rstatd from pkg
The rpc.rstatd is not on Solaris 11 and need to be installed from the repository.

pkg install service/network/legacy-remote-utilities

Solaris 11 Network Configuration
Use net0 for Solaris 11 and use net1 for Solaris 10 branded Zone. Furthermore I choose net0 as 'bridged' and net1 as 'nat' with static IP in the Virtual Machine setup.

# dladm show-vnic
LINK                OVER         SPEED  MACADDRESS        MACADDRTYPE       VID
s10/net0            net1         1000   2:8:20:16:87:a5   random            0


# dladm show-phys
LINK              MEDIA                STATE      SPEED  DUPLEX    DEVICE
net0              Ethernet             up         1000   full      e1000g0
net1              Ethernet             up         1000   full      e1000g1

# dladm show-link
LINK                CLASS     MTU    STATE    OVER
net0                phys      1500   up       --
net1                phys      1500   up       --
s10/net0            vnic      1500   up       net1

# ipadm show-if
IFNAME     CLASS    STATE    ACTIVE OVER
lo0        loopback ok       yes    --
net0       ip       ok       yes    --

# ipadm show-addr
ADDROBJ           TYPE     STATE        ADDR
lo0/v4            static   ok           127.0.0.1/8
net0/_b           dhcp     ok           129.157.155.89/24
lo0/v6            static   ok           ::1/128
net0/_a           addrconf ok           fe80::20c:29ff:fe21:1364/10


Configure second Network Adapter to used by the Solaris 10 branded Zone

dabrain@eleven:~$ dladm show-phys
LINK              MEDIA                STATE      SPEED  DUPLEX    DEVICE
net0              Ethernet             up         1000   full      e1000g0
net1              Ethernet             unknown    0      unknown   e1000g1


root@eleven:~# zonecfg -z s10
zonecfg:s10> info
zonename: s10
zonepath: /export/s10
brand: solaris10
autoboot: false
bootargs:
file-mac-profile:
pool:
limitpriv:
scheduling-class:
ip-type: exclusive
hostid:
fs-allowed:
anet:
    linkname: net0
    lower-link: auto
    allowed-address not specified
    configure-allowed-address: true
    defrouter not specified
    allowed-dhcp-cids not specified
    link-protection: mac-nospoof
mac-address: random
    auto-mac-address: 2:8:20:16:87:a5
    mac-prefix not specified
    mac-slot not specified
    vlan-id not specified
    priority not specified
    rxrings not specified
    txrings not specified
    mtu not specified
    maxbw not specified
    rxfanout not specified
zonecfg:s10> select anet linkname=net0
zonecfg:s10:anet> set lower-link=net1
zonecfg:s10:anet> info
anet:
    linkname: net0
    lower-link: net1
    allowed-address not specified
    configure-allowed-address: true
    defrouter not specified
    allowed-dhcp-cids not specified
    link-protection: mac-nospoof
mac-address: random
    auto-mac-address: 2:8:20:16:87:a5
    mac-prefix not specified
    mac-slot not specified
    vlan-id not specified
    priority not specified
    rxrings not specified
    txrings not specified
    mtu not specified
    maxbw not specified
    rxfanout not specified
zonecfg:s10:anet> end
zonecfg:s10> verify
zonecfg:s10> commit
zonecfg:s10> exit


Boot up Solaris 10 Zone

zoneadm -z s10 boot
zlogin -C -d s10



Install COMMS Suite in Solaris 10 branded Zone

Communications Suite on a Single Host is the Deployment Guide I used for my Lab System.



NOTE:
For some reason Convergence did not fully work when GlassFish server.http-service.request-processing.thread-count is on 2, as it is mention in the Deployment Guide. This might be an issue of Non-Global Zone and/or Machine under VMWare control.


[#|2012-02-08T15:08:31.293+0100|INFO|sun-appserver2.1.1|org.apache.catalina.session.ManagerBase|
 _ThreadID=19;_ThreadName=RMI TCP Connection(26)-127.0.0.1;|PWC2785: Cannot serialize session attribute
 WizardPageModel_1651029014 for session d4ae7931196f8463f24bb0bda2b7
java.io.NotSerializableException: com.iplanet.jato.view.html.OptionList
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
    at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346)

Set thread-count to 1

./asadmin set server.http-service.request-processing.thread-count=1


NOTE:
JISS needs a running LDAP Server, when LDAP is not under SMF control we need to disable JISS or enable SMF for LDAP Server.

svc:/application/jiss-indexSvc:default (JISS Index Service)
 State: maintenance since Thu Feb 09 13:28:55 2012
Reason: Start method failed repeatedly, last exited with status 1.
   See: http://sun.com/msg/SMF-8000-KS
   See: /var/svc/log/application-jiss-indexSvc:default.log
Impact: 1 dependent service is not running:
        svc:/application/jiss-jmqconsumer:default

svc:/application/jiss-searchSvc:default (JISS search service)
 State: maintenance since Thu Feb 09 13:28:55 2012
Reason: Start method failed repeatedly, last exited with status 1.
   See: http://sun.com/msg/SMF-8000-KS
   See: /var/svc/log/application-jiss-searchSvc:default.log
Impact: This service is not running.


bash-3.00# svcadm disable /application/jiss-indexSvc:default
bash-3.00# svcadm disable /application/jiss-searchSvc:default

Enable SMF for LDAP Server check Directory Server Configuration and Administration Guide

# dsadm stop /export/home/ds/instances/your-instance
# dsadm enable-service -T SMF /export/home/ds/instances/your-instance
# dsadm start /export/home/ds/instances/your-instance


Overall the COMMS Suite is running fine in the Solaris 10 branded Zone, which did not really surprise me. On the other hand the COMMS Suite performance is better as an 'old' native Solaris 10 installation, most likely caused by the use of ZFS.

If you want to check latest Solaris technology but still need Solaris 10 packaging System then installing your Software in a Solaris 10 branded zone might be the answer.


Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Andreas Breuer - TSC Engineer - writes about his life in support.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today