Otherwise, assuming Netbackup was not installed cluster-aware, from Cluster Adminstrator, take the PBX stuff offline and delete.
Reference: http://seer.entsupport.symantec.com/docs/304228.htm
Wednesday, January 13, 2010
Thursday, January 7, 2010
8925 Tilt Mac Address
With the wireless adapter on, if you go into Settings - Connections (tab) - Wireless LAN - Advanced (tab). You should see a line for the MAC.
Tuesday, December 29, 2009
Unpublish network printers
To uncheck the "List in the directory" for all print queues on \\printserver use this command:
- C:\Program Files\Windows Resource Kits\Tools>setprinter \\printserver 7 "dwAction=unpublish"
Thursday, December 24, 2009
Adding new MSCS node with Snapdrive and iSCSI
I was having problems replacing a failed node in a Windows 2003 MSCS cluster. With Netapp storage, I had the LUNs mapped to both nodes, but I could not add the shared disks to the new node unless I added it the cluster first.
Use Cluster Administrator to add a new node and specify "Advanced", then click "Advanced (minimum) configuration". This will add the node without shared disks. Once complete, I was able to open SnapDrive and the shared LUNs showed up.
For some strange reason, the only weird think in the System event logs was this warning, Event ID 20:
"A Path Verification request to a device on \Device\MPIODisk2 that is controlled by Microsoft iSCSI DSM has failed. This may indicate a Path Failure."
When I booted the new node alone (with other cluster node off), the LUNs showed up, but as "dedicated" LUNs in SnapDrive.
This led me to try and see if I could add the node to the cluster without shared disk, then to try and access the LUNs after that to see if they showed up as "clustered", which they did!
Reference: http://support.microsoft.com/kb/331801/en-us
Use Cluster Administrator to add a new node and specify "Advanced", then click "Advanced (minimum) configuration". This will add the node without shared disks. Once complete, I was able to open SnapDrive and the shared LUNs showed up.
For some strange reason, the only weird think in the System event logs was this warning, Event ID 20:
"A Path Verification request to a device on \Device\MPIODisk2 that is controlled by Microsoft iSCSI DSM has failed. This may indicate a Path Failure."
When I booted the new node alone (with other cluster node off), the LUNs showed up, but as "dedicated" LUNs in SnapDrive.
This led me to try and see if I could add the node to the cluster without shared disk, then to try and access the LUNs after that to see if they showed up as "clustered", which they did!
Reference: http://support.microsoft.com/kb/331801/en-us
Monday, December 21, 2009
Friday, December 18, 2009
Adding an Netbios alias to a filer
This is located under CIFS, Configure, Options. Fill in the NetBIOS Aliases box, comma separated, then click Apply button.
Monday, December 7, 2009
Setting SSL on Netapp Filer
For some reason the GUI doesn't work too well.
secureadmin setup ssl
Answer the prompts and at the end, the setup generates a self-signed certificate for temporary use and a certificate signing request that can be sent to your CA for certificate creation.
2. Installing the signed certificate
1. Creating a certificate signing request
From the command line, enter:secureadmin setup ssl
Answer the prompts and at the end, the setup generates a self-signed certificate for temporary use and a certificate signing request that can be sent to your CA for certificate creation.
2. Installing the signed certificate
- Create a text file with the signed certificate, ie. /etc/keymgr/cert.cer
- Install the certificate: secureadmin addcert ssl /etc/keymgr/cert.cer
- From the GUI, you can Restart SSL to enable new certificate.
Subscribe to:
Posts (Atom)