Description of problem:
When a geo-replication relationship is established, it is only visible from the source cluster. This is an operational risk, and has been picked up not only through internal SA testing but also on customer POC engagements.

Not understanding the volume relationships across clusters can lead to data loss and human error - both of which woul dbe bad for RHS!

Version-Release number of selected component (if applicable):
2.0

How reproducible:
Whenever geo-replication is used.

Steps to Reproduce:
1. Create a geo-replication configuration
2. Login to the target/slave
3. Using the CLI attempt to show the replication status
  
Actual results:
Replication state is not shared between source and target clusters

Expected results:
Slave's should show the replication state either through vol info, or vol ge-replication commands or preferably both

Additional info: