cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1251
Views
0
Helpful
1
Replies

in NSO HA (tailf-hcc), failover-master template isn't applied

yeepsae17
Cisco Employee
Cisco Employee

I'm testing the NSO HA - BGP Anycast (L3) method, everything works as explained in the tailf_hcc.pdf except failover-master.

 

The SLAVE moves to MASTER, not to FAILOVERMASTER, and the failover-master templates is not applied to slave's quagga device, even the master template is not applied!!!!  only the state is changed. 

(please find attached log for the details)

 

Actually, I looked over the tailf-hcc package code and there's no FAILOVER-MASTER state in the HaStateType definition.. there are only NONE, SLAVE, MASTER, SLAVE_RELAY...  How can a node move to FAILOVER-MASTER state?

 

Please guide me to right direction!

 

the configurations are following..

 

=================================================

root@ncs# show running-config ha
ha token kilskils
ha local-user root
ha interval 3
ha failure-limit 3
ha bgp failure-limit 3
ha bgp anycast-prefix 2.2.2.2/32
ha bgp anycast-path-min 1
ha bgp clear-enabled true
ha member nso-2nd
address 192.168.124.210
default-ha-role slave
failover-master true
quagga-device nso-2nd
!
ha member nso-kils
address 192.168.124.209
default-ha-role master
quagga-device nso-kils
!

 

 

=================================================

root@ncs# show running-config devices template hcc*
devices template hcc-failover-master
config
quagga-bgp:hostname FAILOVERMASTER
quagga-bgp:route-map SET-MED 10
operation permit
set metric 10
!
!
!
devices template hcc-master
config
quagga-bgp:hostname MASTER
quagga-bgp:route-map SET-MED 10
operation permit
set metric 12
!
!
!
devices template hcc-none
config
quagga-bgp:hostname NONE
quagga-bgp:route-map SET-MED 10
operation permit
set metric 20
!
!
!
devices template hcc-slave
config
quagga-bgp:hostname SLAVE
quagga-bgp:route-map SET-MED 10
operation permit
set metric 15
!
!
!

 

=================================================

root@ncs# show ncs
ncs-state patches patches-directory /opt/ncs/current/lib/ncs/patches
ncs-state version 4.7

 

 

=================================================

root@ncs# show packages package quagga-bgp
packages package quagga-bgp
package-version 4.0.1
description "NED package for the Quagga BGP daemon"
ncs-min-version [ 4.2.2 4.3.0.2 4.4.2 ]
directory /var/opt/ncs/state/packages-in-use/1/quagga-bgp
component quagga-bgp
ned cli ned-id quagga-bgp
ned cli java-class-name com.tailf.packages.ned.bgp.QuaggaBgpNedCli
ned device vendor Quagga
NAME VALUE
--------------------------------------------------------------------------------------------------
show-tag hostname
entitlement-tag regid.2015-10.com.cisco.quagga-bgp-NED,1.0_3aefd7ee-0b72-4598-907d-c44d407949d5

build-info date "2018-09-19 06:44:32"
build-info file ncs-4.7-quagga-bgp-4.0.1.tar.gz
build-info arch linux.x86_64
build-info java "compiled Java class data, version 51.0"
build-info python ""
build-info erlang ""
build-info package name quagga-bgp
build-info package version 4.0.1
build-info package ref 4.0.1
build-info package sha1 fdce3f5
build-info ncs version 4.7
build-info ncs sha1 ""
build-info dev-support version 1.0
build-info dev-support branch 270f126
build-info dev-support sha1 270f126
oper-status up

 

 

=================================================

root@ncs# show packages package tailf-hcc
packages package tailf-hcc
package-version 4.3.2
description "Package for Tail-f HA Cluster Control Interface"
ncs-min-version [ 4.2 ]
directory /var/opt/ncs/state/packages-in-use/1/tailf-hcc
component TcmCmdDp
callback java-class-name [ com.tailf.ns.tailfHcc.TcmCmdDp ]
component tailf-hcc
application java-class-name com.tailf.ns.tailfHcc.TcmApp
application start-phase phase2
oper-status up
root@ncs#

 

 

 

 

1 Reply 1

Jan Lindblad
Cisco Employee
Cisco Employee

As you noted yourself, there is no state called FAILOVERMASTER. This is just a hostname used in the examples to keep track of which device is in which state.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the NSO Developer community: