This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About JeffreyDenton
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About JeffreyDenton
12-20-2016
2Posts
1Like
0Solutions
Dec 20, 2016Last Visited
User
Activity
User
Profile
Latest posts by JeffreyDenton
| Subject | Views | Posted |
|---|---|---|
| 1206 | 11-23-2016 07:36 PM | |
| 3741 | 07-19-2016 08:15 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 07-19-2016 08:15 AM |
User Badges
Community Statistics
| Member Since | 07-18-2016 12:59 PM |
| Date Last Visited | 12-20-2016 08:40 AM |
| Posts | 2 |
| Total Likes Received | 1 |
11-23-2016
07:36 PM
Figured this out the hard way. If you create a custom BFD profile in Active / Active HA mode, the BFD profile names need to be unique to each device. If you try to configure a BFD profile with the same name on both devices, BFD will not come up. If you do try to configure a BFD profile with the same BFD profile name and you make and commit changes afterwards, the second PA will complain that the BFD profile does not exist when you try to commit changes on the second PA. In short, the second PA will have the BFD profile removed from the config. Again, this only happens if you try to use the same BFD profile name on both PAs.
... View more
07-19-2016
08:15 AM
1 Kudo
From Support, this is still not supported. T here is an existing Feature Request (FR ID 3591).
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks