2010-10-12 11:01 AM
About 50% of the time, when I use the connect-nacontroller cmdlet I get the following error:
Connect-NaController : RPC Error - The RPC server is unavailable.
At line :1 char:21
+ Connect-NaController <<<< (filername)
+ CategoryInfo : NotSpecified: ( [Connect-NaController], EAPITRANSMISSION
+ FullyQualifiedErrorID : Netapp.Ontapi.Filer.ErrnoException+EAPITRANSMISSION,DataONTAP.PowerShell.SDK.ConnectNaController
Is this a problem with the cmdlet, or do I have issues with my filers? Neither is a comforting thought.
Solved! SEE THE SOLUTION
2010-10-13 10:28 AM
I can think of quite a few things; windows firewall issues, RPC timeout issues, etc. There's not a lot to go on here other than the error that says the packet never made it. I'd start by getting the Microsoft RPC ping utility and quantifying RPC connectivity.
2010-10-13 10:31 AM
You might try running through "cifs setup" at the filer CLI. I have resolved RPC issues that way on rare occasions, even if nothing else appeared to have changed.
2010-10-13 10:34 AM
Once upon a time, I had a situation where I mistakedly had SnapMirror traffic going over the E0M interface. It caused all sorts of unexpected RPC timeouts. The Microsoft RPC Ping utility should help sort it out.