About gc227s

Hello,   A check of the Web GUI of the devices shows a green gear icon for those sections affected, namely interfaces, sub-interface and static routes in a non-default VR.   The Push to Device from the Panorama to the devices is not predictable.  For example, when setting up a log forwarding profile the commit to the devices fails to both devices.  This failed with an error as follows: Details: . Validation Error: . log-settings -> profiles -> syslog -> match-list -> ABC_RTW_LFP_Traffic -> send-syslog 'abc_panorama_syslog_rtw' is not a valid reference . log-settings -> profiles -> syslog -> match-list -> ABC_RTW_LFP_Traffic -> send-syslog is invalid . Commit failed   Warnings: The Panorama Managed Devices view at this point shows the shared policy template as in-sync but the Template out-of sync.  Another more common error is that we create a brand new sub-interface in Panorama, that most definately does not exist on the device, along with an IPv4 address, a new zone and a static route or two.  The commit to Panorama is successful but the commit to device fails to only one device this time, namely the passive device in the cluster. A check of the devices shows config has been pushed.  The error in this case is as follows: To ABCFWDRTW1 device   Details: . Configuration committed successfully   Warnings:   To ABCFWDRTW2 Details: . Validation Error: . network -> interface -> ethernet -> ethernet1/4 -> layer3 -> units -> ethernet1/4.180 -> ip -> 10.215.227.254_26 10.215.227.254_26 is an invalid ipv4/v6 address . network -> interface -> ethernet -> ethernet1/4 -> layer3 -> units -> ethernet1/4.180 -> ip -> 10.215.227.254_26 '10.215.227.254_26' is invalid. Invalid IPv4 address . network -> interface -> ethernet -> ethernet1/4 -> layer3 -> units -> ethernet1/4.180 -> ip is invalid . invalid interface address 10.215.227.254_26(Module: routed) . Commit failed   Warnings: Any thoughts, suggestions are appreciated.    Regards ... View more

Yes, the devices are already in a device group. ... View more