Please see the below config. Why is the vrrp not running in two juniper routers? Thank you
PN# run show vrrp briefVRRP is not running
PN# run show configuration | display set | match 220.127.116.11set interfaces em0 unit 0 family inet address 18.104.22.168/30 vrrp-group 1 virtual-address 22.214.171.124set interfaces em0 unit 0 family inet address 126.96.36.199/30 vrrp-group 1 priority 110set interfaces em0 unit 0 family inet address 188.8.131.52/30 vrrp-group 1 accept-dataset interfaces em1 unit 0 family inet address 184.108.40.206/24
K# run show configuration | display set | match 220.127.116.11set interfaces em0 unit 0 family inet address 18.104.22.168/30 vrrp-group 1 virtual-address 22.214.171.124set interfaces em0 unit 0 family inet address 126.96.36.199/30 vrrp-group 1 priority 100set interfaces em0 unit 0 family inet address 188.8.131.52/30 vrrp-group 1 accept-dataset interfaces em1 unit 0 family inet address 184.108.40.206/24
for me it seesm that the VIP address (.12) does not belong to the network 220.127.116.11/30
the vip-adress is outside the /30 network
PS independent of teh fact that the em interfaces are RE-based and not PFE based, so maybe this is also a reason
Hi Thanks for your reply. After I changed interface and ip, vrrp can run, but it is down status. The two router are connected with 18.104.22.168/24 and 22.214.171.124/24. The ip address can ping each other. Please see below:
1. Change your em0 addresses to some other subnet
2. Bridge irb.0 between your two routers with a cable
3. Upgrade to something higher than 12.1R1
This will help us with some insight on the observation,
Logs/Traceoptions: set protocols vrrp traceoptions file vrrp files 10 size 50m set protocols vrrp traceoptions flag general set protocols vrrp traceoptions flag packets set protocols vrrp traceoptions flag state
Also, do a TCPdump on the interface connecting between them and look for vrrp packets from peer on the both sides,
Also, look for extensive command for brief idea on PDU;s sent/received,
root@Backup> show vrrp extensive Interface: fe-0/0/0.0, Interface index :72, Groups: 1, Active :1 Interface VRRP PDU statistics Advertisement sent :0 Advertisement received :8890 Packets received :8890 No group match received :0 Interface VRRP PDU error statistics Invalid IPAH next type received :0 Invalid VRRP TTL value received :0 Invalid VRRP version received :0 Invalid VRRP PDU type received :0 Invalid VRRP authentication type received:0 Invalid VRRP IP count received :0 Invalid VRRP checksum received :0
You need to remove manual configuration from the em interfaces. These are internal Junos interfaces and are not for use and manual configuration.
Hi Spuluka, Sorry for the delay since i had another project. The below are all interface the router has. so do you think which interface can be used for vrrp configuration? thank you
PN# run show interfaces terseInterface Admin Link Proto Local Remotecbp0 up updemux0 up updsc up upem0 up upem0.0 up up inet 126.96.36.199/24 188.8.131.52/24em1 up upem1.0 up up inet 184.108.40.206/24em2 up downgre up upipip up upirb up upirb.0 up down inetlo0 up uplo0.16384 up up inet 127.0.0.1 --> 0/0lo0.16385 up up inet 220.127.116.11 --> 0/0 inet6 fe80::200:f:fc00:1111lsi up upmtun up uppimd up uppime up uppip0 up uppp0 up uptap up up
You don't seem to have any ethernet interfaces visible. What type of device is this?
Use this to verify what is installed
show chassis hardware
or on a chassis device like the MX
show chassis hardware models
For devices with dedicated management ports, Junos OS automatically configures the router’s management Ethernet interface, as either em0 or fxp0. You can use the show interfaces terse | match fxp0 or show interfaces terse | match em0 command to display management interface information.
To use the management Ethernet interface as a management port, you must configure its logical port, em0.0 or fxp0.0, with a valid IP address.
For PTX Series Packet Transport Routers, the Junos OS automatically creates the router’s management Ethernet interface, em0. To use em0 as an out-of-band management port, you must configure its logical port (for example, em0.0) with a valid IP address.
Please avoid enabling protocls on the router’s management Ethernet interface.
Take a look at this explanation for these interfaces
See this article understanding the interface requirements for vrrp
IRB interfaces and RVIs are similar to switch virtual interfaces (SVIs) and bridge-group virtual interfaces (BVIs), which are supported on other vendors’ devices. They can also be combined with other functions: