[
https://issues.apache.org/jira/browse/CLOUDSTACK-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054357#comment-15054357
]
ASF GitHub Bot commented on CLOUDSTACK-9151:
--------------------------------------------
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/1231#issuecomment-164161230
Ping @remibergsma @DaanHoogland @borisroman
Could you guys test it before the RC? I just fixed, but have to go to a
concert now.
> As a Developer I want the VRID to be set within the limits of KeepaliveD
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9151
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9151
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router, VPC
> Affects Versions: 4.6.0, 4.6.1
> Reporter: Wilder Rodrigues
> Assignee: Wilder Rodrigues
> Priority: Blocker
> Fix For: 4.7.0, 4.6.2
>
>
> Dec 12 14:36:10 r-996-VM Keepalived_vrrp[28477]: VRRP Error : VRID not valid !
> Dec 12 14:36:10 r-996-VM Keepalived_vrrp[28477]: must be between
> 1 & 255. reconfigure !
> [3:38]
> inside the /etc/keepalived/keepalived.conf
> [3:38]
> vrrp_instance inside_network {
> state EQUAL
> interface eth4
> virtual_router_id 459
> [3:43]
> The current code uses the VPC ID as VRID, but it doesn't have to be unique
> per VPC, but for NIC. So, we can simply use 51, as the KeepaliveD suggests.
> # arbitary unique number 0..255 # used to differentiate multiple instances of
> vrrpd # running on the same NIC (and hence same socket). virtual_router_id 51
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
