Thanks, Steve for the reply.
I also noticed while creating my separate prefix-list's that it did not like having both in the policy-statement unless they were on separate terms. I kept getting a combined error message.
A lot more work but I ended up creating a separate IPV4 and IPV6 group for everything, along with separate IPV4 and IPV6 PREFIX-LIST'S and policy statements.
I also ran into an issue where some groups were inheriting the family statement from the global BGP hierarchy, so I added the family inet and inet6 at the group level for the associated groups.
Hopefully, this should avoid issues in the future.
------------------------------
COREY HENDERSON
------------------------------
Original Message:
Sent: 01-02-2021 12:32
From: STEVE PULUKA
Subject: add a ipv6 / inet6 address to a prefix-list
The issue is that you really cannot mix ipv4 and ipv6 prefixes on the same list because ultimately they get applied to either family inet or family inet6 somewhere in the configuration.
Once the prefix list is used under one of the families then the other family cannot exist on the list as it is not valid for that application.
------------------------------
Steve Puluka BSEET - Juniper Ambassador
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
http://puluka.com/home
Original Message:
Sent: 12-31-2020 19:26
From: COREY HENDERSON
Subject: add a ipv6 / inet6 address to a prefix-list
I'm trying to add an ipv6 address to my prefix-list and I get an error that say
[edit policy-options prefix-list LocallyOriginated]
'1111:2222::/32'
RPD Policy: invalid prefix 1111:2222::/32 for family inet
error: configuration check-out failed
So it appears it thinks its an ipv4 address,
I'm using set policy-options prefix-list LocallyOriginated 1111:2222::/32 to add it to my prefix-list
Any help would be appreciated as I can not seem to find anything related to adding ipv6 to prefix-lists.
Thanks in advance.
------------------------------
COREY HENDERSON
------------------------------