In this example Raphael set two different addresses for fxp0 for each RE
(.10, .11) and a 'virtual' one (.9) which reside only on the master RE.
I do not recommend the use of fxp0, (rather use in -band management, and
serial oob in case of failure), unless you are totally sure of your
management network.
--
Raphael Mazelier
Le 09/05/2016 à 14:19, Raphael Maunier a écrit :
Here the config for the 2 re
groups {
re0 {
system {
host-name re0.mx1.fqdn;
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 10.10.10.9/24 {
master-only;
}
address 10.10.10.10/24;
}
}
}
}
}
re1 {
system {
host-name re1.mx2.fqdn;
}
interfaces {
fxp0 {
unit 0 {
family inet {
address 10.10.10.9/24 {
master-only;
}
address 10.10.10.11/24;
}
}
}
}
}
And then apply-group [re0 re1]
Raphael
On 09/05/16 14:11, "juniper-nsp on behalf of v"
<juniper-nsp-boun...@puck.nether.net on behalf of vekt...@gmx.net> wrote:
Hello,
I am new to networking and trying to understand the initial configuration on a
Juniper MX router with dual REs:
http://www.juniper.net/techpubs/en_US/junos14.2/topics/task/configuration/routing-engine-dual-initial-configuration.html
Step 6 is the following:
" Set the loopback interface address for the re0 configuration group:
[edit groups]
root@host# set re0 interfaces lo0 unit 0 family inet address
address/prefix-length"
Why do I need to give the re0 group a loopback interface address in the first
place?
What address should I give to the loopback interface?
Regards,
v
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
