Cluster Network 2 is missing from Failover cluster Manager

Question

I have two node Windows 2008 R2 SP1 MS SQL cluster, there was an issue with one node NIC card which was replaced and since then "Cluster Network 2" is not visible in failover cluster manager, also Heartbeat and Public IP nic card of both nodes
are appearing in "Cluster Network 1" container. even though both network public and hearbeat are on differenet subnet, but still cluster detects it as one subnet. Need to know how to bring back "Cluster Network 2"

Answer 1

After replacing NIC, cluster worked fine on other node for couple of days and then cluster services started terminating on both the nodes.
when checked cluster logs found below error.
"ERR   [CORE] Node 2: exception caught AlreadyExists(183)' because of 'already exists'(AODBP2DB1 - Local Area Connection)"
Hence to correct this problem, renamed both nodes NIC cards as Public and Private and cluster was started and tested the failover also. but since then only able to see "Cluster Network 1" and all NIC are listed under this container.
Though when looked at cluster validation report, it shows Cluster Network 1 and Cluster Network 2 entries in it
Pasted network section from Cluster Validation report
Network: Cluster Network 1
DHCP Enabled: False
Network Role: Enabled
Prefix
Prefix Length
10.100.18.0
25
Item
Value
Network Interface
Node1 - Public
DHCP Enabled
False
IP Address
10.100.18.11
Prefix Length
25
Item
Value
Network Interface
Node2 - Public
DHCP Enabled
False
IP Address
10.100.18.16
Prefix Length
25
Network: Cluster Network 2
DHCP Enabled: False
Network Role: Internal
Prefix
Prefix Length
10.101.130.0
25
Item
Value
Network Interface
Node1 - Private
DHCP Enabled
False
IP Address
10.101.130.11
Prefix Length
25
Item
Value
Network Interface
Node2 - Private1
DHCP Enabled
False
IP Address
10.101.130.13
Prefix Length
25
Verifying that each cluster network interface within a cluster network is configured with the same IP subnets.
Examining network Cluster Network 1.
Network interface Node1- Public has addresses on all the subnet prefixes of network Cluster Network 1.
Network interface Node2- Public has addresses on all the subnet prefixes of network Cluster Network 1.
Examining network Cluster Network 2.
Network interface Node1- Private has addresses on all the subnet prefixes of network Cluster Network 2.
Network interface Node2- Private1 has addresses on all the subnet prefixes of network Cluster Network 2.
Verifying that, for each cluster network, all adapters are consistently configured with either DHCP or static IP addresses.
Checking DHCP consistency for network: Cluster Network 1. Network DHCP status is disabled.
DHCP status (disabled) for network interface Node1- Public matches network Cluster Network 1.
DHCP status (disabled) for network interface Node2- Public matches network Cluster Network 1.
Checking DHCP consistency for network: Cluster Network 2. Network DHCP status is disabled.
DHCP status (disabled) for network interface Node1- Private matches network Cluster Network 2.
DHCP status (disabled) for network interface Node2- Private1 matches network Cluster Network 2.