Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zebra process getting the following error message #25

Open
maheshloni opened this issue Oct 17, 2017 · 3 comments
Open

Zebra process getting the following error message #25

maheshloni opened this issue Oct 17, 2017 · 3 comments

Comments

@maheshloni
Copy link
Contributor

after starting the zebra and getting the following error message :

root@stack:/opt/quagga/sbin# vty_read_config: failed to open configuration file /opt/quagga/etc/zebra.conf: No such file or directory
can't open configuration file [/opt/quagga/etc/zebra.conf]

@xiaofeng6WIND
Copy link
Contributor

Hi @maheshloni

Why did you run zebra? because zebra is not necessary in QBGP.
If you want to start zebra, a minimum config file is required. For example:

cat /opt/quagga/etc/zebra.conf
! -- zebra --
!
! zebra sample configuration file
!
! $Id: zebra.conf.sample,v 1.1 2002/12/13 20:15:30 paul Exp $
!
hostname Router
password zebra
enable password zebra
!
! Interface's description.
!
!interface lo
! description test of desc.
!
!interface sit0
! multicast

!
! Static default route sample.
!
!ip route 0.0.0.0/0 203.181.89.241
!

!log file zebra.log

@maheshloni
Copy link
Contributor Author

HI Philippe,
Can you please add zebra.conf file since we need to create loopback interface to talk to from openstack VM to QBGP interface

@pguibert6WIND
Copy link
Contributor

Hi Mahesh,
I am not sure zebra is the good tool to create loopback interfaces.
loopback interfaces are created by system.
Then read by zebra.
I dont see the advantage of having zebra.
could you explain more, please or show us by a simple setup, what you can achieve ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants