A coworker of mine and I where chatting about VCSA Replication Agreements and the agreement is that there should be a fling for mapping replication agreements. So that night I thought about it. Really there is nothing stopping me from doing this. I pulled out the computer and in a few lines of code I had it working. I took the time over the next few nights making it more robust, and work through getting it to accept a seed node and and find all its VCSA replication partners and report back replication status. So turns out that the seeding loop was a little more than I had bargained for. Reached out to the community and talked with my friend Joe Houges @jhoughes and worked out the issues with the looping issues. Also helped with reminding me about SSH code stream.
Below is an example of the report the script with return. This shows the Source vCenter, Replication Partners, Replication Sequence Numbers, and validate the numbers are not off.
| Source | Partner | Host_Available | Status_Available | Last_Change_Number | Partner_Change_Number | Replication_Satus |
| TestvCenter1.chrislab.com | TestvCenter2.chrislab.com | Yes | Yes | 171728 | 171728 | Good |
| TestvCenter1.chrislab.com | TestvCenter3.chrislab.com | Yes | Yes | 171728 | 171728 | Good |
| TestvCenter2.chrislab.com | TestvCenter1.chrislab.com | Yes | Yes | 166648 | 166648 | Good |
| TestvCenter2.chrislab.com | TestvCenter3.chrislab.com | Yes | Yes | 166648 | 166648 | Good |
| TestvCenter3.chrislab.com | TestvCenter2.chrislab.com | Yes | Yes | 168975 | 168975 | Good |
| TestvCenter3.chrislab.com | TestvCenter1.chrislab.com | Yes | Yes | 168975 | 168975 | Good |

The Script will log into VCSA, enable bash, Pull replication status, clean up the data, and report the info and export it to a CSV, then disable bash. The code lives here:


