In Transaction Replication, the transactions are not moving from secondary replica to Subscriber When primary replica nodes are down

Hello,

Looking for your help on the Multi-Subnet - SQL Alwayson with transnational Replication setup. 

Bullet Point about environment

1. Node1 and Node2 are part of VLAN 10.10.XX.XX VLAN
2. Node3 and Node4 are part of VLAN 10.20.XX.XX VLAN
3. Using all four nodes, I have configured multi-subnet  windows clustering “WINCLUST01”
4. Using Node1&2, I've installed SQL clustered instance “2K12AGDB01”, it CANNOT failover to other 2 nodes (node3 & 4)
5. Using Node3&4, I've installed SQL clustered instance “2K12AGDB02”, it CANNOT failover to other 2 nodes (node1 & 2)
6. Configured Availability group (Listener) using both the VLAN 10.10 and10.20 (Just to remind- If node1 &2 both are down, after manual fail-over data can be read/written from other two nodes 3 & 4 using listener.)
7. Setup 4 nodes SQL Clustered Replication instance “SQLRPL” which can failed over to any node for remote Distributor
8. Have one subscriber server “Node5” (which is on in below table

What has been achieved?

1. Windows Cluster “WINCLUST01” has been setup and failing over on other sub-net nodes without any error.
2. Using node1 and node2, SQL Cluster “2K12AGDB01” has been configured successfully and working perfectly fine
3. Using node3 and node4, SQL Cluster  “2K12AGDB02” has been configured successfully and working perfectly fine
4. Configured Availability group (Listener) “AvailGroup01” ” has been configured successfully and working perfectly fine
5. 4 node replication instance “SQLRPL” has been configured and working perfectly fine, it can be failed over to any nodes.
6. All the linked Server has been configured with SQL “SA” login and test the connection they are working fine perfectly.
7. Replication has been configured using Primary Replica “2K12AGDB01”
8. Redirected Mode has been configured using Original primary replica "2K12AGDB01" & listener "AvailGroup01" successfully
9. Data is moving from original publisher to Subscriber perfectly fine
10.  After failing over Alwayson to secondary replica SQL Server instance “2K12AGDB02”, inserted data  is reaching to Subscriber server. There is no issue at all

Issues which I have been facing?

1.  When I open the replication monitor on the primary replica, I am able to see Publication detail in the replication monitor but when I go to secondary replica and open the replication monitor, I can not see anything in the replication monitor. Even if i fail-over the Alwayson to secondary replica, I am not able to see anything into secondary replica replication monitor. Is it a normal behivour?
2. As I wrote above point number-10 that when I insert data from Secondary Replica (after fail-over of AlwaysOn to secondary replica "2K12AGDB02"), the data is reaching to subscriber "node-5"- at this time original primary replica (2K12AGDB01) is available in ready-only mood. But when I bring down the primary replica instance "2K12AGDB01" (at this time, it is not available even with readonly option), No data is moving from Secondary replica "2K12AGDB02" to Subscriber"node-5"

Does it mean data will be only send from secondary replica to subscriber when primary replica is available?

Note: - I brought down the primary replica and inserted records from secondary replica, it is NOT reaching from secondary replica to subscriber (but the records are reaching to subscriber when primary replica is available as read-only). The most important things that I cannot see any job -  distribution or log reader agent are throwing any error or retrying. 

Please do let me know, if you need additional information to help me on this