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 fwmike2
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About fwmike2
05-24-2023
3Posts
1Like
0Solutions
May 24, 2023Last Visited
User
Activity
User
Profile
Latest posts by fwmike2
| Subject | Views | Posted |
|---|---|---|
| 1616 | 11-08-2022 11:59 AM | |
| 1933 | 10-05-2022 07:53 PM | |
| 13478 | 01-28-2022 07:29 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 10-05-2022 07:53 PM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 2 Likes |
User Badges
Community Statistics
| Member Since | 12-22-2020 12:53 PM |
| Date Last Visited | 05-24-2023 11:03 AM |
| Posts | 3 |
| Total Likes Received | 1 |
02-16-2023
12:39 AM
Hi @KTompkins ,
The CLI command is :
> show system raid detail
Here's the full KB article: https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000wkxPCAQ
Kind regards,
-Kiwi.
... View more
01-28-2022
07:29 AM
@TMSSupport If you have the issue again, get on the CLI and use: show arp all to see if you have an entry for your device's default route next hop. If it's not in the ARP table, you may be having a physical or layer 2 issue where the firewall is not able to forward to your Internet provider's upstream device because it doesn't have a MAC for it.
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks