Forum Discussion

Blizzie's avatar
Blizzie
11 years ago

Network adaptor unavailable

Hi All,

After upgrading a cluster server from windows 2008 R1 to windows 2008 R2 the server cannot connect to the network anymore.

The adaptor is still there and the heartbeats are working , but the principal network cannot be reached.

The server is an HP and the veritas cluster software is 5.1 SP2.

Any suggestions how to fix ?

Since the portal from Symantec is unavailable to log a case , i need some help ?

 

ApplicationHA
business continuity
Troubleshooting
Windows Server (2003-2008)
  • Wally_Heim's avatar
    Wally_Heim
    11 years ago

    Hi Blizzie,

    It sounds like you maybe hitting a basic Windows 2008 R2 network security issue and not a problem with SFW-HA configuration.  Windows 2008 R2 adds some security fixes and enhancements to the server when installed.  It may have enabled the Windows Firewall or restricted it to the point clients are not able to connect to the server again. 

    Check to make sure that basic Windows TCP/IP connectivity is working as expected.  If you are able to go out from the server other network resources and connect to these servers from a client, then check to make sure that the NIC configuration is still as expected and that he MAC address has not changed for the public NIC.

    Thank you,

    Wally

2 Replies

Sort By
Replies have been turned off for this discussion
  • Gaurav_S's avatar
    Gaurav_S
    Moderator
    11 years ago

    need little more clarity, are you saying that your VCS is working fine (cluster joined) as heartbeats are available however the public network is having issues ? You have a third public NIC (other than 2 private heartbeats) which has been configured in VCS service groups ?

    Can your OS see the network card ? This seems to be more of OS issue with first information.

    From below post

    https://www-secure.symantec.com/connect/forums/how-replace-network-adapter-cards-win2008-vcs-cluster

    I see this information

    Each NIC and IP resource configured in the cluster has a copy of the public NIC MAC on each server.  You will need to modify each NIC and IP resource to have the correct MAC address for the server where the NIC adaptor was changed.  The good news is that this only needs to be done on 1 node in the cluster since the configuration is shared between all nodes.  Just make sure that you save and close the configuration when done making these changes.

    Though with windows upgrade MAC shouldn't change as hardware is still same however have you checked if above information(IP & MAC) has correct ?

     

    G
     

  • Wally_Heim's avatar
    Wally_Heim
    Level 6
    11 years ago

    Hi Blizzie,

    It sounds like you maybe hitting a basic Windows 2008 R2 network security issue and not a problem with SFW-HA configuration.  Windows 2008 R2 adds some security fixes and enhancements to the server when installed.  It may have enabled the Windows Firewall or restricted it to the point clients are not able to connect to the server again. 

    Check to make sure that basic Windows TCP/IP connectivity is working as expected.  If you are able to go out from the server other network resources and connect to these servers from a client, then check to make sure that the NIC configuration is still as expected and that he MAC address has not changed for the public NIC.

    Thank you,

    Wally