Thanks for bringing up the Transient/Persistent IP checking Ujwol, that certainly applies to web agents. And come to think of it, for web agents the IP can also be used in policies to limit authorization by workstation IP address.
But when writing custom agents, in practice I don't remember ever setting workstation IP. So what I should have said is that the user's IP address MAY only be used for logging purposes, depending upon how the agent is used and how the data the agent provides is used in policies.
In any event, the issue has probably nothing to due with SiteMinder, and can't be fixed by changing any SiteMinder configuration. The problem is most likely a firewall/proxy/load balancer issue and any of those devices that are used must be configured to pass through the user's IP address in a way that can be accessed by standard header variables.
But Priyotosh, before you contact the network administrators, you need to ask yourself how the IP address is going to be used and whether or not you really even need it.
Rick