[ixpmanager] New install step by step

Sat Aug 11 09:28:45 IST 2018

Hi all,

The previous problem was resolved by a bad template file (which got corrupted on the FS by a person editing it and changing the permissions)...

IXP manager works fine now for a week...

The only last and not so clear thing is that which is the best way to run the mrtg config script - which cron entry as root maybe ?

And any experience if after you regenerate the mrtg.cfg - do we need a mrtg restart since the script from the IXP manager runs MRTG as daemon ??

for example our cron file looks like this:

/etc/cron.d/ixpmanager
0 2   * * *   www-data        /srv/ixpmanager/artisan grapher:upload-stats-to-db
*/15  * * * * /srv/ixpmanager/gen-mrtg-conf

Thanks...

Regards,

--
V.B
FCC

________________________________
From: ixpmanager <ixpmanager-bounces at inex.ie> on behalf of Vladislav Bidikov <vladislav.bidikov at finki.ukim.mk>
Sent: Monday, August 6, 2018 6:02:46 PM
To: INEX IXP Manager Users Mailing List
Subject: Re: [ixpmanager] New install step by step

Hi,

Just to further update on the matter - on ~ 20.07 the API configuration was working perfectly fine...

The result was a good Bird config file... nothing was done in the period between then and today (vacation time)

Here is the config of RS1:

http://prntscr.com/kfddq8

The Laravel error says something about api missing in the router and creates this:

HTTP_USER_AGENT: curl/7.38.0
REMOTE_PORT: 40402
REQUEST_METHOD: GET
REQUEST_URI: /api/v4/router/gen-config/rs1-v4-ixpmk

2018-08-06T15:40:48+00:00 DEBUG (7) [194.149.136.160]: Logger instantiated
2018-08-06T15:40:48+00:00 DEBUG (7) [194.149.136.160]:

2018-08-06T15:40:48+00:00 DEBUG (7) [194.149.136.160]: ErrorController::errorAction()
2018-08-06T15:40:48+00:00 DEBUG (7) [194.149.136.160]:

************************************************************************
****************************** EXCEPTIONS *******************************
************************************************************************

--------------------------- EXCEPTION --------------------------

Message: Invalid controller specified (api)
Line: 248
File: /srv/ixpmanager/vendor/zendframework/zendframework1/library/Zend/Controller/Dispatcher/Standard.php

Trace:

#0 /srv/ixpmanager/vendor/zendframework/zendframework1/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#1 /srv/ixpmanager/vendor/zendframework/zendframework1/library/Zend/Application/Bootstrap/Bootstrap.php(105): Zend_Controller_Front->dispatch()
#2 /srv/ixpmanager/vendor/zendframework/zendframework1/library/Zend/Application.php(384): Zend_Application_Bootstrap_Bootstrap->run()
#3 /srv/ixpmanager/app/Exceptions/Handler.php(62): Zend_Application->run()
#4 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(83): IXP\Exceptions\Handler->render(Object(Illuminate\Http\Request), Object(Symfony\Component\HttpKernel\Exception\NotFoundHttpException))
#5 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(32): Illuminate\Routing\Pipeline->handleException(Object(Illuminate\Http\Request), Object(Symfony\Component\HttpKernel\Exception\NotFoundHttpException))
#6 /srv/ixpmanager/vendor/fideloper/proxy/src/TrustProxies.php(56): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#7 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(149): Fideloper\Proxy\TrustProxies->handle(Object(Illuminate\Http\Request), Object(Closure))
#8 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#9 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(30): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#10 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(149): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#11 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#12 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(30): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#13 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(149): Illuminate\Foundation\Http\Middleware\TransformsRequest->handle(Object(Illuminate\Http\Request), Object(Closure))
#14 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#15 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#16 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(149): Illuminate\Foundation\Http\Middleware\ValidatePostSize->handle(Object(Illuminate\Http\Request), Object(Closure))
#17 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#18 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(46): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#19 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(149): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#20 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#21 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#22 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(151): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#23 /srv/ixpmanager/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#24 /srv/ixpmanager/public/index.php(85): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#25 {main}

If needed i can provide more detailed logs - but i'm still completely clueless...

Please advice....

Best regards,

--

V.B

FCC

________________________________
From: ixpmanager <ixpmanager-bounces at inex.ie> on behalf of Vladislav Bidikov <vladislav.bidikov at finki.ukim.mk>
Sent: Monday, August 6, 2018 3:05:39 PM
To: Barry O'Donovan
Cc: INEX IXP Manager Users Mailing List
Subject: Re: [ixpmanager] New install step by step

Hi team,

Today we where going to connect the first "customer" and something strange is happening with the automatic script for generation of the config:

In the script we have the url:

URL="http://194.149.136.158/api/v4/router/gen-config"

And today we see a 404 error...

Runing:

URL="http://194.149.136.158/api/v4/test"

Says we are ok (API test fine, authenticated OK)

We did not any change on the IXP manager instance... any idea where to look into this ?

Best regards,

--

V.B

FCC

________________________________
From: Barry O'Donovan <barry.odonovan at inex.ie>
Sent: Friday, July 27, 2018 10:44:30 AM
To: Vladislav Bidikov
Cc: INEX IXP Manager Users Mailing List
Subject: Re: [ixpmanager] New install step by step

Vladislav Bidikov wrote on 25/07/2018 21:38:
> Sorry - i mixed 2 different slide decks (someone needs to grab a coffee
> ) - and this old one (which is not the one i thought on the IXP manager
> site) is definitely one that can help

Cool.

> That slide deck - solved the Cisco people...
>
> I have solved the Mikrotik ones... and i have a BIRD to try for the bird
> one 😊

Bird have some examples here:

https://gitlab.labs.nic.cz/labs/bird/wikis/Examples

While the slide deck I provided has Cisco examples, a network engineer
familiar with Juniper should be able to use the examples to program a
JunOS BGP config / any other device.

> At the end of the day - what is the worse that could happen if we
> miss-configure a router - we will not brake the internet just the ISP we
> experiment with .... :)

Any possibly any bilateral peers and possibly their upstreams. Big
internet outages are usually caused by human's fat-fingering a BGP
configuration.

If you're using the IXP Manager generated route server configuration,
then that'll ensure nothing bad happens with those sessions.

  - Barry

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20180811/23c93859/attachment-0001.html>