Thanks Albrecht,
I could see the dplane and mplane interfaces of Maestro SG from the PDP gateway. Somehow it does automatically.
The maestro SG will be identified at management server through the mplane interface and hence when we configure identity sharing, while selecting the gateway it list the Firewall/SG object identified using the mplane interface IP.
Is there anyway we could configure the identity sharing connecting to dplane and not tp mplane?. One way I could think about is by adding the SG to management server by using the dplane interface, which defeats the purpose of MDPS.
[Expert@gw0011:0]# pdp connections pep
----------------------------------------------------------------------------------------------------------------
| Direction | IP | Port | Name | Type | Status | Location | IPv6 Supported |
----------------------------------------------------------------------------------------------------------------
| Incoming | 10.x.x.x | 28581 | sgfw001 | Single Gateway | Connected | Remote | No | -> Dplane interface (SG)
----------------------------------------------------------------------------------------------------------------
| Outgoing | 10.y.y.y | 15105 | sgfw001 | Single Gateway | Disconnected | Remote | Yes | ->Mplane interface(SG)
----------------------------------------------------------------------------------------------------------------
| Outgoing | 127.0.0.1 | 15105 | sgfwclu0001 | Cluster | Connected | Locally | No |
----------------------------------------------------------------------------------------------------------------
| Outgoing | 10.x.x.y | 15105 | sgfw001 | Single Gateway | Connected | Remote | No | ->dplane(SG)
----------------------------------------------------------------------------------------------------------------
Bibin