Resolution:
From 5.1.3, the hawkagent.cfg file of &ltyourdomain> will have ami_rvd_session entry uncommented.
The entry would be :  -ami_rvd_session &ltrvd_session's service+1> &ltrvd_session's network> &ltrvd_session's daemon> .  

This was done to segment the local hawk RV traffic from the network Hawk RV traffic.  Traffic-wise, there is no difference.  It is actually more efficient on RV to do this, as it segments the transports onto separate threads in the RVD.

You can use any port for ami_rvd_session as it is going to create a local rvd on that port which will be used for ami transport where the application talks to the  hawkagent(local Hawk RV traffic) via this ami transport. It's just the easy convention to use n+1 of rvd_session service so that we can find the ami transport easily.