[ixpmanager] New install step by step

[Nishal Goburdhan]

On 23 Jul 2018, at 18:36, Vladislav Bidikov wrote:


> This trunk to the VM based on Debian (which run on VmWare) will be 
> working fine since the port itself is as Eth-Trunk and MRTG is 
> monitoring it that way...
> Also, after we resolve (4) with a separate port for FCSE, the only 
> traffic there will be for RS/RC/AS112 and the 2x1G trunk is more for 
> redundancy purposes...

we keep the route servers are on dedicated NICs, directly into the 
peering switch.  it means you lost 2 (in our case, 4) ports on the 
peering fabric, but that there’s no interruption of service to peers 
that are using the route-servers, should we need to do something to the 
management domain.   (ironically, the one failure we did have, was a 
14year old management switch :-) that failed at a site, and although we 
lost remote management abilities, until someone got onsite, peering was 
completely uninterrupted.  that’s worth burning the peering ports, for 
peace of mind, imho!)

if you keep the route servers on dedicated NICs, it becomes really easy 
to setup a customer called “xy-IX Route Servers” and simply assign 
the ports as necessary to these, nicely fitting into the standard model 
..

—n.