Management ip address cannot be seen again

[DavidyPalo]

Hi Management interface ip address is configured, and it could work before. but now I cannot see it. After the ip address is reconfigured(and commit), I still cannot see it. Below is its config. Anyone can take a look at it? Thank you!

set deviceconfig system ip-address 192.168.1.6 netmask 255.255.255.0 default-gateway 192.168.1.1

show interface management

-------------------------------------------------------------------------------
Name: Management Interface
Link status:
Runtime link speed/duplex/state: unknown/unknown/down
Configured link speed/duplex/state: auto/auto/auto
MAC address:
Port MAC address 08:66:66:66:66-

Ip address: unknown
Netmask: unknown
Default gateway:
Ipv6 address: unknown
Ipv6 link local address: unknown
Ipv6 default gateway:
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
Logical interface counters:
-------------------------------------------------------------------------------
bytes received 3629
bytes transmitted 4362
packets received 47
packets transmitted 15
receive errors 0
transmit errors 0
receive packets dropped 0
transmit packets dropped 0
multicast packets received 1

[nikoolayy1 · Accepted solution]

Try to see that the DHCP is not enabled:

set deviceconfig system type static

Also try the command :

show system state filter cfg.net.s1.eth0.cfg

How to view Management Interface Setting in the CLI - Knowledge Base - Palo Alto Networks

Also is your device a palo alto VM?

Also check for known issues for your version:

https://docs.paloaltonetworks.com/pan-os/8-1/pan-os-release-notes/pan-os-8-1-release-information/kno... 

[DavidyPalo]

Thank you! It can work!

[nikoolayy1]

If it does not help then shutdown and unshut the interface. I wouldn't suggest for cosmetic bug to redeploy the config that almost always helps by saving the config doing factory reset and then adding the config back. Also for info  I have seen such an issue on firewalls 3000/3200.