ned_a
asked on
Configure IPv4 IPv6 dual stack on solaris zones
I need to configure some solaris zones with IPv4 IPv6 dual stack so we can use both IPv4 and IPv6 ip addresses to connect to the server. I have done this for solaris servers without any zones. In that case, it was just a matter of creating the hostname6.<> file , having both IPv4 and IPv6 addresses in the hosts file and making sure that nsswitch.conf file has dns lookups configured.
But the same does not apply for the individual zones.
Anyone got any tips?
But the same does not apply for the individual zones.
Anyone got any tips?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
amolg, I got some very useful information from the link you provided .
Blu, I saw the steps you mentioned in a similar document but I think the implementation of it is what is catching me now. http://blogs.sun.com/seb/entry/ipv6_in_shared_stack_zones. I included the default router in the creation of the net but it didn't help.
After running the steps I get this on my zone..
#ifconfig -a
lo0:1: flags=2001000849<UP,LOOPBA CK,RUNNING ,MULTICAST ,IPv4,VIRT UAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0:1: flags=1000843<UP,BROADCAST ,RUNNING,M ULTICAST,I Pv4> mtu 1500 index 2
inet XX.42.9.XXX netmask fffffe00 broadcast XX.42.9.255
lo0:1: flags=2002000849<UP,LOOPBA CK,RUNNING ,MULTICAST ,IPv6,VIRT UAL> mtu 8252 index 1
inet6 ::1/128
====== replaced part of IP address with X'x for security reasons . Sorry about that ========
I tried using fe80::1234/10 for the address of the link-local , I even tried using a variation of the MAC address. Neither worked.
I used physical=e1000g0 , is this correct ? As you can see from the ifconfig -a above, the zone has e1000g0:1
Any more tips?
Blu, I saw the steps you mentioned in a similar document but I think the implementation of it is what is catching me now. http://blogs.sun.com/seb/entry/ipv6_in_shared_stack_zones. I included the default router in the creation of the net but it didn't help.
After running the steps I get this on my zone..
#ifconfig -a
lo0:1: flags=2001000849<UP,LOOPBA
inet 127.0.0.1 netmask ff000000
e1000g0:1: flags=1000843<UP,BROADCAST
inet XX.42.9.XXX netmask fffffe00 broadcast XX.42.9.255
lo0:1: flags=2002000849<UP,LOOPBA
inet6 ::1/128
====== replaced part of IP address with X'x for security reasons . Sorry about that ========
I tried using fe80::1234/10 for the address of the link-local , I even tried using a variation of the MAC address. Neither worked.
I used physical=e1000g0 , is this correct ? As you can see from the ifconfig -a above, the zone has e1000g0:1
Any more tips?
The default router is not an issue with IPv6, it is designed to not need it.
I don't know what you have done wrong. If you look at Seb's article, there is a
point where he prints out the zoen config info. Maybe if you did that and posted it I could see where you are having trouble. The command would be "zonecfg -z zonename info"
I don't know what you have done wrong. If you look at Seb's article, there is a
point where he prints out the zoen config info. Maybe if you did that and posted it I could see where you are having trouble. The command would be "zonecfg -z zonename info"
ASKER
zonecfg -z zone3 info
zonename: zone3
zonepath: /tank/zones/zone3
brand: native
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
net:
address: XX.42.9.XXX/23
physical: e1000g0
defrouter: XX.42.8.XX
net:
address: XXX:XXX:111:200:XX:42:9:XX X/64
physical: e1000g0
defrouter: XX.42.8.XX
net:
address: fe80::0:14:4f:aa:95:56/10
physical: e1000g0
defrouter: XX.42.8.XX
zonename: zone3
zonepath: /tank/zones/zone3
brand: native
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
net:
address: XX.42.9.XXX/23
physical: e1000g0
defrouter: XX.42.8.XX
net:
address: XXX:XXX:111:200:XX:42:9:XX
physical: e1000g0
defrouter: XX.42.8.XX
net:
address: fe80::0:14:4f:aa:95:56/10
physical: e1000g0
defrouter: XX.42.8.XX
ASKER
I set up the global zone for IPv6 and rebooted the server. I wasn't able to bring it down any earlier because of project work.
The zones are now configured with IPv6.
Thanks very much for your help.
The zones are now configured with IPv6.
Thanks very much for your help.
http://docs.sun.com/app/docs/doc/816-4554/ipv6-planning-1?l=en&a=view