I configure a single vcs cluster with vvr. I save the configuration on the following pictures
As you see on these pictures, I configure a service named apache2 using the RVGPrimary of vvrgroup, and set the relation between two service groups with command:
>hagrp -link apache2 vvrgrp online local hard
You are missing an IP resource in your VVR service group for replication to use. In a typical GCO configuration, the VVR service group has an IP resource with its own virtual IP, then replication is configured to use this IP address for that site. When the VVR service fails over to another node the virtual IP used for replication also fails over.
What is not clear is where your VVR secondary is located. If it is somewhere out side of this cluster then you will be fine by adding an IP resource and configuring replication to use it for both nodes in this cluster.
If however, this is a Replicated Data Cluster and you are replicating the data between vcs1 and vcs2, then the service group need to be altered to a Parallel or Hybird group with an IP resource configured to have unique IPs for each node. and repilclation needs to be setup to use one IP for the VVR primary and the other for the VVR secondary.
You do not need to use virtual IPs, but you must use a hybrid or parallel group for the vvrgrp. If you are replicating between vcs1 and vcs2 then diskgroup needs to be imported on both nodes, but as vvrgrp is configured as a failover group it is only online on one node.
I don't think you can change the "Parallel" attribute for a service group that contains resources, so easiest way is to stop VCS and add "Parallel = 1" to service group definition so you have:
If you use a parallel group with static IPs then this makes it more difficult to add more nodes in the future, so if it is possible you may adds more nodes in the future, then it is better to use virtual IPs for replication and create a hybrid service group (Parallel = 2 which also requires SystemZones to be setup)