zonefcg to set autoboot to False for each non-global zone.
Create a script that calls zoneadm to boot each zone.
You may also have some alternate script to make sure a db zone is fully up, for example.
This User Gave Thanks to jim mcnamara For This Post:
Hi all,
I am trying to configure my HPUX host 11.31 IA64 to boot from a LUN for EMC clariion CX3-80 (Flaire PNR 26).
I am following the below mentioned steps..
vi /tmp/idf
3
EFI 500MB
HPUX 100%
HPSP 400MB
idisk -f /tmp/idf -w /dev/rdisk/diskxxx
insf -e
pvcreate -B... (0 Replies)
I want to configure one service to come up as a normal strat-up process after reboot, instead of starting it manually.
I tried to configure it in inetd.conf but it didn't work.
Could you please suggest, how I can achieve this ?? (3 Replies)
Hi,
I have an IA machine on which I want to install the HP 11.31 from LAN.
I have the lan card and ignite server available.
How do I need to configure the LAN card to be able to boot from it and install the OS?
Thanks in advance
Pritam (2 Replies)
Hi experts,
I want to configure a boot server, tried googling for some document for steps and all leads to JumpStart server.
Any help with be much appreciated
Thanks (9 Replies)
Hi All,
Please help me in configuring interface in zone
I've zone with dedicated interface and I want this interface to get up with global system boot. I am struggling with IP, as always after reboot interface is not getting up automatically and I understand the reason for that.... (10 Replies)
I have two physical servers, with zones that mount local storage.
We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point).
It failed to mount on every boot because the directory existed in the zone.
I... (6 Replies)
Solaris for Sparc 11.1 with the latest patches. Created a Guest LDOM with two vnet's net0 and net1, installed a guest whole root, ip exclusive zone that I want to be able to utilize DHCP. I have been able to create the zone but unable to get it to boot because I am unable to assign an anet to it.... (4 Replies)
Need assitance in troubleshooting steps . Below is the issue
I have LDOM which has 4 zones on it . One zone logging into the server takes 13sec where as other zones are quick .
Troubleshooting steps which I did
- Checked /var/tmp . Not many files
- We have LDAP but thought that wouldnt be... (7 Replies)
Discussion started by: ajayram_arya
7 Replies
LEARN ABOUT DEBIAN
shorewall6-nesting
SHOREWALL6-NESTING(5) [FIXME: manual] SHOREWALL6-NESTING(5)NAME
nesting - shorewall6 Nested Zones
SYNOPSIS
child-zone[:parent-zone[,parent-zone]...]
DESCRIPTION
In shorewall6-zones[1](5), a zone may be declared to be a sub-zone of one or more other zones using the above syntax. The child-zone may be
neither the firewall zone nor a vserver zone. The firewall zone may not appear as a parent zone, although all vserver zones are handled as
sub-zones of the firewall zone.
Where zones are nested, the CONTINUE policy in shorewall6-policy[2](5) allows hosts that are within multiple zones to be managed under the
rules of all of these zones.
EXAMPLE
/etc/shorewall6/zones:
#ZONE TYPE OPTION
fw firewall
net ipv6
sam:net ipv6
loc ipv6
/etc/shorewall6/interfaces:
#ZONE INTERFACE BROADCAST OPTIONS
- eth0 detect blacklist
loc eth1 detect
/etc/shorewall6/hosts:
#ZONE HOST(S) OPTIONS
net eth0:[::]
sam eth0:[2001:19f0:feee::dead:beef:cafe]
/etc/shorewall6/policy:
#SOURCE DEST POLICY LOG LEVEL
loc net ACCEPT
sam all CONTINUE
net all DROP info
all all REJECT info
The second entry above says that when Sam is the client, connection requests should first be processed under rules where the source zone is
sam and if there is no match then the connection request should be treated under rules where the source zone is net. It is important that
this policy be listed BEFORE the next policy (net to all). You can have this policy generated for you automatically by using the
IMPLICIT_CONTINUE option in shorewall6.conf[3](5).
Partial /etc/shorewall6/rules:
#ACTION SOURCE DEST PROTO DEST PORT(S)
...
ACCEPT sam loc:2001:19f0:feee::3 tcp ssh
ACCEPT net loc:2001:19f0:feee::5 tcp www
...
Given these two rules, Sam can connect with ssh to 2001:19f0:feee::3. Like all hosts in the net zone, Sam can connect to TCP port 80 on
2001:19f0:feee::5. The order of the rules is not significant.
FILES
/etc/shorewall6/zones
/etc/shorewall6/interfaces
/etc/shorewall6/hosts
/etc/shorewall6/policy
/etc/shorewall6/rules
SEE ALSO shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(5),
shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5),
shorewall6-tcdevices(5), shorewall6-tcrules(5), shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5)NOTES
1. shorewall6-zones
http://www.shorewall.net/manpages6/shorewall-zones.html
2. shorewall6-policy
http://www.shorewall.net/manpages6/shorewall6-policy.html
3. shorewall6.conf
http://www.shorewall.net/manpages6/shorewall6.conf.html
[FIXME: source] 06/28/2012 SHOREWALL6-NESTING(5)