paloalto:paloalto
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| paloalto:paloalto [2026/02/05 08:55] – v1ctor | paloalto:paloalto [2026/02/05 09:11] (current) – [MANAGEMENT] v1ctor | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| ==== MANAGEMENT ==== | ==== MANAGEMENT ==== | ||
| - | It's possible to use data ports for management. It's done via '' | + | It's possible to use data ports for management. It's done via '' |
| + | * Create in //Network | Network Profiles | Interface Management Profile// | ||
| + | * Then attach to //Network | Interfaces on the Advanced// | ||
| + | |||
| + | CLI verison: | ||
| + | < | ||
| + | set network profiles interface-management-profile mgmt https yes ssh yes permitted-ip 10.15.15.37 | ||
| + | set network profiles interface-management-profile mgmt permitted-ip 192.168.0.5 | ||
| + | </ | ||
| + | |||
| + | **Service Route Configuration** | ||
| + | |||
| + | If the management interface does not have access to the internet, this can create interesting challenges as it will not be able to retrieve updates or perform cloud lookups. A workaround is to enable service routes that route specific applications, | ||
| + | |||
| + | |||
| + | * //Device | Setup | Services// | ||
| + | * //Service Route Configuration// | ||
paloalto/paloalto.1770281751.txt.gz · Last modified: by v1ctor
