10-18-2017
This could be caused by a number of things. What follows is not an exhaustive list but let's highlight a few.
1. Is that zone really busy for some reason? Try running performance stats (sar)
2. Is that zone being strangled by some resource constraint imposed when the zone was configured. Compare config with other zones. (zonecfg)
3. Are these zones whole root or sparse? Is usage of the global zone affecting this zones performance?
4. How is the user authentication carried out? Locally or remotely? Compare with other zones.
5. Can the login delay be interrupted? Can you break out of the delay time by hitting Ctrl-C? Does the prompt appear immediately if you do that? Or is the process uninterruptable?
6. The zone may be doing a reverse lookup to a node that isn't responding. Compare resolv.conf files between zones. Is the server(s) reachable? Working with one login client can you fix the problem by putting it's name & ip into that zones /etc/hosts making it instantly resolvable.
7. Does that zone have exclusive use of its own network interface? If it's sharing an interface (with the global zone for example) is traffic generated by the other zone delaying a reverse lookup?
Let me stop there for the moment. It's difficult to provide a definitive answer without you doing some of your own research. Do please post back your progress.
We're all here to help.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi
i am not able to the zones after i enable BSM, but i am able to login using "zlogin -S" option.
is there any command which i can use to troubleshoot.
thanks a lot! :cool: (0 Replies)
Discussion started by: legato
0 Replies
2. Solaris
Hi Folks
My Sun Solaris servers are waiting for a long time after keying in the User-ID. There is a big delay in getting to the password prompt. But once the password is keyed in,it goes through in a second.
The servers in which i am facing this issue is an NIS client. But i am facing this... (7 Replies)
Discussion started by: Hari_Ganesh
7 Replies
3. Solaris
hi,
what is the difference between ldom and zone. can we install any other os than sun in ldom.
thanks,
snj. (2 Replies)
Discussion started by: snjksh
2 Replies
4. Solaris
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)
Discussion started by: os2mac
4 Replies
5. Solaris
Hi ,
I am not able to exit fom zone console login prompt.
I have tried options like
~. ~~. and @. but it is not working fo me.
Could someone Please help me on this.
Thanks in Advance!!
Regards,
Laxxi (7 Replies)
Discussion started by: Laxxi
7 Replies
6. Solaris
Is anyone aware of a method of configuring the boot order of zones and or LDOMS? (2 Replies)
Discussion started by: os2mac
2 Replies
7. Solaris
tldr; We've installed a non-global-zone from a unified archive which once booted, we're unable to gain access to the system either through zlogin or zlogin -C.
Errors;
svc.startd: instance svc:/system/console-login:default exited with status 127
Investigation;
1) Already opened a SR with... (1 Reply)
Discussion started by: samthewildone
1 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)