Apple Filing Protocol, the principal file-sharing protocol in Mac OS 9 systems, used by AppleShare servers and clients. Network File System, the main file-sharing protocol used by UNIX systems. Server Message Block /Common Internet File System, a file-sharing protocol used on Windows and UNIX systems. Apple Mac OS X connect to SMB (samba/CIFS) share. Go Connect to Server. Smb://servername/sharename (in this case, acfiles is 10.1.16.112 currently).
--____LPHMXLZMXOMRLFKSEJCW____ Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable We have a 2.5T SAN with 14 NW servers and no clustering. We are about to = implement a 10T SAN and about 10 NW servers. Our basic applications are = file & print, iPrint, Zen desktop management, zen app delivery, Groupwise = & NetMail. Does clustering actually improve online availability from an = end users perspective. I realize this is kind-of the point, but am = curious if this is in fact the case for those using the product. Part II, is one larg..
Any compelling reasons to upgrade NW6 cluster to NW6.5 cluster
I have a customer who has 2 x 2 Node clusters (Compaq Proliants) attached to 2 separate HDS SAN's. They are running NW6 SP3 and apart from NDPS (memory hog issues) the cluster has been stable. Hopefully the NDPS issues will be sorted by applying SP4. The clusters are really only providing file access, printing and ftp services. They use NFAP (CIFS and MAC access)and this is critical to the business as there are more than 100 Mac's in production as well as 100 Windows 2k/XP clients (with no Netware client). The remaining (400+) PC's do have the novell client inst..
Migrating to 6.5 clusters services from 5.1 cluster services
Hi all, I have a question regarding an upcoming migration from 5.1 cluster sevices to 6.5 cluster services with a fiber attached SAN. We are getting 3 new servers to upgrade the nodes which make up our cluster. So current 3 node cluster to a new 6.5 3 node cluster. If we follow the migration instructions setup the new server with a temp name and temp tree migrate the first server etc etc ending up with all three new servers migrated to 6.5. Do I then install clustering services for 6.5 on the new servers? How do i get the 5.1 nss volumes updated to work with 6.5? We can not do an in..
EAServer clustering with MS Cluster Service
Hello, We are considering running Sybase EAServer 3.6.1 (and soon 4.1) along with IBM MQSeries 5.2.1 on a pair of clustered Intel boxes running MS Windows NT 4.0 Enterprise Edition (and at some point MS Windows 2000 Advanced Server) with MS cluster service enabled on shared storage (MQSeries requires MS clustering to operate properly in a cluster). EAS (advanced edition) would be properly configured to use Sybase clustering with proper licensing to support both servers running simultaneously. The EAS would NOT be using the shared storage and would NOT be taking advantage of the MS ..
How to remove cluster node from 3 node NW6 cluster
Can someone tell me how to properly remove a server from a 3 node Netware 6 SP5 cluster. The Novell documentation doesn't mention how to do this. One of the servers in the 3 node cluster is a bit flaky and I would like to totally remove it before upgrading the other 2 nodes to Netware 6.5. Modify your Cluster resources so that they are appropriate for the new configuration Type CLUSTER LEAVE on the node to remove Type ULDNCS on the node to remove Delete the Cluster Object (the one that represents the Cluster Node). Remove the LDNCS.NCF file from the AUTOEXEC.NCF Remove ..
Migrating a NetWare Cluster Services to a New OES2 Cluster
--____YVDUOLWVHAYJTNLYLWYJ____ Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; modification-date='Tue, 9 Nov 2009 02:25:04 -0600' I have a 3-node NetWare 6.5sp7 cluster. I am building a new 3-node = OES2sp2 cluster in the same tree and OU. I would like to move a few of = the NetWare cluster services (data volumes and GroupWise POs) over to the = new OES2sp2 cluster. Can you migrate cluster services from one cluster to another? --____YVDUOLWVHAYJTNLYLWYJ____ Content-Type: multipart/related; bou..
Clusternode can�t join the cluster after reinstall cluster services
Hello, the scenario: NetWare 5.1 SP5 two-node cluster (CS 1.01) with shared san storage. After first installation it works fine. I deleted the clusterobjects from NDS Edir 8.62, perform nds repair, removed the cluster startup command (ldncs.ncf) on the nodes, deleted the cluster splitbrain partition from shared storage and restart the server�s. After the new installation of clusterservices (no errors by installation!!) and the reboot of the nodes, one node can�t join the cluster. I can manage the node that can joined the cluster very fine. On the dead node I perform to sta..
Upgrading Cluster Services to NW6.5
I need to upgrade a Cluster running NW6.0/ NCS 1.6 to NW 6.5. Any advice on procedures or potential pitfalls would be very welcome. Whilst I maintain and administer these boxes I did not install them and the upgrade would novel territory for me. TIA novel novell trerritory, huh? :-) the upgrade is fairly straightforward. the online docs and nwdeploy (root of the 6.5 cd) contain all you need to know. -- Cheers! Richard Beels ~ Network Consultant ~ Sysop, Novell Support Connection ~ MCNE, CNE*, CNA*, CNS*, N*LS ..
uninstall cluster services from NW6.0
external storage disk is bad and i need to uninstall and reinstall cluster in NW60SP5. I found TID 10015339, is there anything else i should do before reinstallting it? To reinstall i should use the NW60SP5 overlay CD? Are there any other patches i need to do after? thanx haydee On Fri, 23 Jun 2006 19:10:59 +0000, roblesh wrote: That all looks good. Yes reinstall using the overlay CD that way you wont have to reapply the Service Pack after the NCS install has finished. I can't remember off the top of my head if there were any post SP5 patches specific for NCS. ..
Migrate from NW5.1 non-clustered to NW6 with cluster 1.6
I need to migrate one NW5.1 server to a 3-server NW6 clustered environment. I've looked at the Migration Wizard v6 but it doesn't talk about migrating to a clustered system. I see lots of TIDs about missing attributes on the shared volumes if you use the Migration Wizard. I've just come across the NW Consolidation Utility. I don't know much about that yet. I'm not sure the it can do the server replacement functions like the Wizard does. It seems like I need a utility that has some of the functionality of the Wizard and some of the Consolidation ..
Service Pack 2 NW6.5 Cluster
HI, I am new to Novell Clusters. Can anybody tell me why after installing SP2 (NW6.5) that the Cluster services can no longer find the SBD partition? If I uninstall SP2 then the cluster finds the SBD partition. Is the only answer to run SBD install? If so, then TID10082213 states to delete the cluster partition but with my scenario this does not exist as there is no SBD partition. I would appreciate any help that can be offered. > HI, > > I am new to Novell Clusters. Can anybody tell me why after installing SP2 > (NW6.5) that the Cluster services can no lo..
NW6.5SP2 Cluster Services Stop Communicating
This problem has been intermittent since NW6.5sp1. Open Console1 and Cluster State View is all grey and state 'unknown' All 3 nodes seem responsive. NRM was able to communicate for a while then that went away as well. Rebooting a node with most of the cluster volumes on it seemed to bring it back to life. When it's in this state, how can I troubleshoot? In NRM server health is all green (good) Server console command 'cluster status' shows all volumes except a large volume says 'unloading' (stuck there for days - but didn't unload) In this state ..
nw6.5 sp1 Cluster Services and NTP
is it possible to cluster the ntpd (time services)? How? thanks No, nor is there any reason to do so. -- Andrew C Taubman Novell Support Forums Volunteer SysOp http://support.novell.com/forums (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Novell Inc. ..
nw6.5 sp3 cluster abend in wspdsi.nlm
Hi, I am getting the following abend on multiple nodes of a 6.5 SP3 cluster on wspdsi.nlm. The 5 nodes are all compaq proliant BL20p G3 blades. I don't know if this is important or not, but so far the only nodes it's happened on are 5 and 1. 5 was the first to abend, and it's resources (3 pools with 1 volume each) migrated to 1. Then the next day 1 abended, same abend. This was late last week and now 5 has abended again. I don't know if this means it is volume related? I have not yet applied any nss or tcp or server.exe patches past SP3, I don't know if tho..
Go to 'Control Panel' > 'Network Services' > 'Win/Mac/NFS' to configure networking services.
To allow access to the NAS on Microsoft Windows Network, enable file service for Microsoft networking. Specify also how the users will be authenticated.
Use local users for authentication. The NAS will use the local user accounts information (created in 'Privilege Settings' > 'Users') to authenticate the users who access the NAS.
|Server Description (optional): Describe the NAS so that the users can easily identify the server on Microsoft Network.
|Workgroup: Specify the workgroup to which the NAS belongs. A workgroup name supports up to 15 characters but cannot contain: ' + = / : * ? < > ; [ ] % , `
AD Domain Member
Use Microsoft Active Directory (AD) to authenticate the users. To use this option, enable Active Directory authentication in 'Privilege Settings' > 'Domain Security' and join the NAS to an Active Directory.
LDAP Domain Authentication
Use Lightweight Directory Access Protocol (LDAP) directory to authenticate the users. To use this option, enable LDAP authentication and specify the settings in 'Privilege Settings' > 'Domain Security'. When this option is enabled, you need to select either the local NAS users or the LDAP users can access the NAS via Microsoft Networking.
|WINS server: If the local network has a WINS server installed, specify the IP address. The NAS will automatically register its name and IP address with WINS service. If you have a WINS server on your network and want to use this server, enter the WINS server IP. Do not turn on this option if you are not sure about the settings.
|Local Domain Master: A Domain Master Browser is responsible for collecting and recording resources and services available for each PC on the network or a workgroup of Windows. When you find the waiting time for connecting to the Network Neighborhood/My Network Places too long, it may be caused by failure of an existing master browser or a missing master browser on the network. If there is no master browser on your network, select the option 'Domain Master' to configure the NAS as the master browser. Do not turn on this option if you are not sure about the settings.
|Allow only NTLMv2 authentication: NTLMv2 stands for NT LAN Manager version 2. When this option is turned on, login to the shared folders by Microsoft Networking will be allowed only with NTLMv2 authentication. If the option is turned off, NTLM (NT LAN Manager) will be used by default and NTLMv2 can be negotiated by the client. The default setting is disabled.
|Name resolution priority: You can select to use DNS server or WINS server to resolve client host names from IP addresses. When you set up your NAS to use a WINS server or to be a WINS server, you can choose to use DNS or WINS first for name resolution. When WINS is enabled, the default setting is 'Try WINS then DNS'. Otherwise, DNS will be used for name resolution by default.
|Login style: DOMAINUSERNAME instead of DOMAIN+USERNAME for FTP, AFP, and File Station: In an Active Directory environment, the default login formats for the domain users are:
When you turn on this option, the users can use the same login name format (domainusername) to connect to the NAS via AFP, FTP, and File Station.
|Automatically register in DNS: When this option is turned on and the NAS is joined to an Active Directory, the NAS will register itself automatically in the domain DNS server. This will create a DNS host entry for the NAS in the DNS server. If the NAS IP is changed, the NAS will automatically update the new IP in the DNS server.
|Enable trusted domains: Select this option to load the users from trusted Active Directory domains and specify their access permissions to the NAS in 'Privilege Settings' > 'Shared Folders'. (The domain trusts are set up in Active Directory only, not on the NAS.)
|Enable Asynchronous I/O: Enable this option to speed up the SAMBA performance, but an UPS is strongly recommended to prevent power interruption if this option is to be enabled.
|Highest SMB version: Choose the version of the SMB protocol (Server Message Block) from the drop down list for your Microsoft Networking operations. If you are not sure, please use the default one on the list.
To connect to the NAS from Mac, enable Apple Filing Protocol. If the AppleTalk network uses extended networks and is assigned with multiple zones, assign a zone name to the NAS. Enter an asterisk (*) to use the default setting. This setting is disabled by default. To allow access to the NAS from Mac OS X 10.7 Lion, enable 'DHX2 authentication support'. Click 'Apply' to save the settings. You can use the Finder to connect to a shared folder from Mac. Go to 'Go' > 'Connect to Server', or simply use the default keyboard shortcut 'Command+k'. Enter the connection information in the 'Server Address' field, such as 'afp://YOUR_NAS_IP_OR_HOSTNAME'. Here are some examples:
Note: Mac OS X supports both Apple Filing Protocol and Microsoft Networking. To connect to the NAS via Apple Filing Protocol, the server address should start with 'afp://'. To connect to the NAS via Microsoft Networking, please use 'smb://'.
To connect to the NAS from Linux, enable NFS service. To configure the NFS access right to the shared folders on the NAS, go to 'Privilege Settings' > 'Share Folders'. Click the Access Permission button on the 'Action' column.Select NFS host access from the drop-down menu on top of the page and specify the access right. If you select 'No limit' or 'Read only', you can specify the IP address or domains that are allowed to connect to the folder by NFS.
|No limit: Allow users to create, read, write, and delete files or folders in the shared folder and any subdirectories.
|Read only: Allow users to read files in the shared folder and any subdirectories but they are not allowed to write, create, or delete any files.
|Deny access: Deny all access to the shared folder.
Connecting to the NAS by NFS
On Linux, run the following command:
mount -t nfs <NAS IP>:/<Shared Folder Name> <Directory to Mount>
For example, if the IP address of your NAS is 192.168.0.1 and you want to link the shared folder 'public' under the /mnt/pub directory, use the following command:
mount -t nfs 192.168.0.1:/public /mnt/pub
Note: You must login as the 'root' user to initiate the above command.
Login as the user ID you define, you can use the mounted directory to connect to your shared files.
© 2015 QNAP Systems, Inc. All Rights Reserved.