That works.  Thanks!

Nick


On Mon, Mar 25, 2013 at 4:22 AM, Keisuke MORI <keisuke.mori...@gmail.com>wrote:

> 2013/3/25 Nick Walke <tubaguy50...@gmail.com>:
> > Looks like 3.9.2-5.  So I need to statically assign the address I want to
> > use before using it with IPv6addr?
>
> Yes.
>
>
> > On Mar 25, 2013 3:44 AM, "Keisuke MORI" <keisuke.mori...@gmail.com>
> wrote:
> >
> >> Hi Nick,
> >>
> >> Could you privide which version of resource-agents you're using?
> >>
> >> Prior to 3.9.2, IPv6addr requires a static IPv6 address with the
> >> exactly same prefix to find out an apropriate nic; so you should have
> >> statically assigned   2600:3c00::34:c003/116 on eth0 for example.
> >>
> >> As of 3.9.3, it has relaxed and the specified nic is always used no
> >> matter if the prefix does not match; so it should just work. (at least
> >> it works for me)
> >>
> >> Alternatively, as of 3.9.5, you can also use IPaddr2 for managing a
> >> virtual IPv6 address, which is brand new and I would prefer this
> >> because it uses the standard ip command.
> >>
> >> Thanks,
> >>
> >> 2013/3/25 Nick Walke <tubaguy50...@gmail.com>:
> >> > This the correct place to report bugs?
> >> > https://github.com/ClusterLabs/resource-agents
> >> >
> >> > Nick
> >> >
> >> >
> >> > On Sun, Mar 24, 2013 at 10:45 PM, Thomas Glanzmann <
> tho...@glanzmann.de
> >> >wrote:
> >> >
> >> >> Hello Nick,
> >> >>
> >> >> > I shouldn't be able to do that if the IPv6 module wasn't loaded,
> >> >> > correct?
> >> >>
> >> >> that is correct. I tried modifying my netmask to copy yours. And I
> get
> >> >> the same error, you do:
> >> >>
> >> >>     ipv6test_start_0 (node=node-62, call=6, rc=1, status=complete):
> >> >> unknown error
> >> >>
> >> >> So probably a bug in the resource agent. Manually adding and removing
> >> >> works:
> >> >>
> >> >> (node-62) [~] ip -6 addr add 2a01:4f8:bb:400::2/116 dev eth0
> >> >> (node-62) [~] ip -6 addr show dev eth0
> >> >> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
> >> >>     inet6 2a01:4f8:bb:400::2/116 scope global
> >> >>        valid_lft forever preferred_lft forever
> >> >>     inet6 2a01:4f8:bb:400:225:90ff:fe97:dbb0/64 scope global dynamic
> >> >>        valid_lft 2591887sec preferred_lft 604687sec
> >> >>     inet6 fe80::225:90ff:fe97:dbb0/64 scope link
> >> >>        valid_lft forever preferred_lft forever
> >> >> (node-62) [~] ip -6 addr del 2a01:4f8:bb:400::2/116 dev eth0
> >> >>
> >> >> Nick, you can do the following things to resolve this:
> >> >>
> >> >>         - Hunt down the bug and fix it or let someone else do it for
> you
> >> >>
> >> >>         - Use another netmask, if possible (fighting the symptoms
> >> instead
> >> >> of
> >> >>           resolving the root cause)
> >> >>
> >> >>         - Write your own resource agent (fighting the symptoms
> instead
> >> of
> >> >>           resolving the root cause)
> >> >>
> >> >> Cheers,
> >> >>         Thomas
> >> >> _______________________________________________
> >> >> Linux-HA mailing list
> >> >> Linux-HA@lists.linux-ha.org
> >> >> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> >> >> See also: http://linux-ha.org/ReportingProblems
> >> >>
> >> > _______________________________________________
> >> > Linux-HA mailing list
> >> > Linux-HA@lists.linux-ha.org
> >> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> >> > See also: http://linux-ha.org/ReportingProblems
> >>
> >>
> >>
> >> --
> >> Keisuke MORI
> >> _______________________________________________
> >> Linux-HA mailing list
> >> Linux-HA@lists.linux-ha.org
> >> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> >> See also: http://linux-ha.org/ReportingProblems
> >>
> > _______________________________________________
> > Linux-HA mailing list
> > Linux-HA@lists.linux-ha.org
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
>
>
>
> --
> Keisuke MORI
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to