Basic Network Configuration
Basic Network Configuration
The objectives for this module are shown here. Please take a moment to read them.
The objectives for this lesson are shown here. Please take a moment to read them.
To modify and display the hardware configuration for the Celerra, click on the Network folder in the left navigation tree. Here you will find Data Mover interfaces, device information, NIS and DNS settings, routing information, statistics, and the ping utility for troubleshooting.
Before you configure hardware parameters, list the network interfaces (PCI devices) to see what is available. Click on the Network folder in the left navigation tree. Next, select the Devices tab. Listed here are all the devices available to be used when creating interfaces.
Transmission Speed
Defaults to auto Use maximum speed supported on the network between the Celerra and the client
Celerras default duplex setting is Auto Negotiate and the default transmission speed is also auto. The entire network should run in the same duplex mode. It is preferred that the Data Mover transmit at 100Mbps, Full Duplex. However, 10 Mbps, Half Duplex, can also be used when necessary. For GigE connections, best practice setting should be auto/auto. In order for a network to function well, the same settings should be deployed across the network. Since Ethernet hubs are not capable of operating in Full Duplex mode, it is strongly recommended that all Ethernet hubs in EMC Celerra environments be removed from the network and replaced with Ethernet switches. If the network does not fully support Full Duplex, then implementing Full Duplex on Celerra could cause connectivity devices in the network to fill their buffers which would have a drastic effect on the performance of the network as well as possible data loss.
Setting Speed/Duplex
Network > Devices tab > right click Device > Properties > set Speed/Duplex
To set the speed and duplex on a particular device right-click the device and select Properties. Next, select the desired speed and duplex from the Speed/Duplex drop down menu and click OK.
The objectives for this lesson are shown here. Please take a moment to read them.
Required IP Parameters
IP address Subnet Broadcast address
The IP address, subnet mask, and broadcast address are all required when configuring the interface.
IPv6 Support
Celerra supports IPv6 IP addresses IPv6 address example:
2620:0000:0170:0062:021B:D5FF:FE25:7082
Network Portion Subnet Interface ID
Celerra supports IPv6 addresses for networks that are IPv6 compatible. An IPv6 address is 128 bits long, compared to IPv4 32 bit long address. The single most important IPv4 problem to address is the address space. IPv6 provides a larger address space. An IPv6 address is also written in Hexadecimal notation instead of IPv4s decimal notation. Another improvement of the new IP protocol is that security is integrated into the protocol, not treated as an add-on. IPsec protects message confidentiality & authenticity. Beyond the added addresses, security and features of IPv6; another reason why networks are moving to IPv6 is because there are a number of IPv6 initiatives within governments around the world. IPv6 is now widely deployed in Asia due to initiatives in China, Japan and South Korea. For more information on IPv6, please refer to the 3-day IPv6 Workshop provided by EMC.
IP Address Configuration
Network > Interfaces > New
To configure an IP address click on the Network folder in the left navigation tree. Under the Interfaces tab, click on the New button at the bottom of the window. The Network Interface Properties window will appear. Next, select the Data Mover and Device Name from the drop-down menus. Enter the IP address of the new interface and the netmask. The interface name is optional. You may enter a value of 1500 for the MTU size or leave it empty. If the MTU size value and the VLAN ID is left empty, Celerra will automatically enter the default value for you. Click OK when finished. Note: By default, the name of the interface will be the IP address with hyphens if left empty. For example, the first interface shown in the interface list is named 10-127-57-152. The new interface being created will have a regular name of cel5dm2. The broadcast address is not configurable.
Displaying IP Configuration
Network > Interfaces tab
To display the IP configuration click on the Network folder in the left navigation tree and select the Interfaces tab. Note: When deleting or modifying an IP configuration for an interface, remember to update the appropriate CIFS servers that may be using that interface and any NFS exports that may depend on the changed interface.
The objectives for this lesson are shown here. Please take a moment to read them.
The routing table of a Data Mover is used to direct outgoing network traffic via both external (router) and internal (individual network interfaces such as cge0, cge1, etc.) gateways. For network activity initiated by the Data Mover, the system uses the routing table to get destination and gateway information. Routes to a particular host must be distinguished from those to a network. The optional keywords net and host specify the address type and force the destination to be interpreted as a network or a host, respectively. The Routing Information Protocol (RIP) is a dynamic routing protocol supported by the Celerra Network Server. RIP determines a network route based on the smallest hop count between the source and the destination. By default, the Data Mover listens for RIP routes on all interfaces.
This slide shows how to view configured routes using Celerra Manager. Click the Network folder in the left navigation tree and select the Routing tab.
This slide shows how to configure a default gateway route. Different types of subnet masks are supported, however, Celerra does not support noncontiguous network masks; that is, masks without a continuous stream of 1 bits. A netmask of 0.0.0.0 or 255.255.255.255 is invalid for net routes. By default, a netmask of 255.255.255.255 is assigned to host routes.
Deleting Routes
Network > Routing tab > Select the route to delete > Delete
The objectives for this lesson are shown here. Please take a moment to read them.
Celerra Data Movers support both traditional DNS and Dynamic DNS in a Microsoft Windows network. When configuring the Data Mover for DNS, multiple DNS servers can be included, separated by spaces, in the command statement. Celerra Manager allows you to configure an unlimited number of DNS domains per Data Mover. Additionally, although the default protocol for DNS is UDP, the TCP protocol can be specified. Note: EMC recommends that two DNS name servers are employed and configured for the Celerra. This allows for redundancy in case of a DNS server failure. The same is true for NIS.
The objectives for this lesson are shown here. Please take a moment to read them.
NTP
Sophisticated algorithms for time correction and maintenance to allow time synchronization with an accuracy of about a millisecond
SNTP
Subset of NTP for use in environments with less stringent synchronization and accuracy requirements
The Data Mover implements an NTP client that can synchronize the system clock with an NTP or SNTP server. NTP is a standard timekeeping protocol used on many platforms, including both Windows and UNIX environments. The full NTP specification uses sophisticated algorithms for time correction and maintenance to allow time synchronization with an accuracy of about a millisecond. This high level of accuracy is achieved even in large networks with long network delays or in cases where access to a time server is lost for extended periods of time. SNTP implements a subset of NTP for use in environments with less-stringent synchronization and accuracy requirements. SNTP uses simple algorithms for time correction and maintenance and is capable of accuracy to the level of a fraction of a second. To an NTP or SNTP client, NTP and SNTP servers are indistinguishable. SNTP can be used: When the ultimate performance of the full NTP implementation is not needed or justified. In environments where accuracy on the order of large fractions of a second is good enough.
To configure an NTP server click on the Data Mover folder in the left navigation tree so it expands. Select server_2 and scroll down to the bottom of the page. Next, enter the IP address of the NTP server. Click Apply to accept the changes. Note: To verify NTP status, at the CLI Command window, run the server_date command. Example: server_date server_2 timesvc stats ntp
The objectives for this lesson are shown here. Please take a moment to read them.
TFTP
Simple, UDP based protocol to read and write files
FTP is a client/server protocol that operates over TCP/IP and allows file uploading and downloading across heterogeneous systems. FTP includes functions to log on to remote systems, list directories, and copy files. TFTP is a simple, UDP based protocol to read and write files. TFTP lacks many of the features of regular FTP. It provides no mechanism for user authentication, nor does it let you display a remote directory, invoke a shell or manipulate files and directories.
You can perform FTP operations by typing commands at a command prompt or by using an FTP utility running under a graphical interface such as Windows. Both UNIX and Windows users can use FTP to access file systems on a Celerra Network Server on the local subnet. Authentication is performed using the local hosts file or NIS for UNIX users, and using CIFS authentication for Windows users. Any file system mounted on a Data Mover is available for FTP access as long as the FTP daemon, ftpd, is running on that Data Mover. In a default Data Mover configuration, ftpd is automatically started. During a Data Mover failover, any FTP sessions that were active when the failure occurred are automatically disconnected. You must manually restart those sessions when the failover is completed. When a user creates a file or directory through FTP, the access permissions on the file depend on the umask in effect on the FTP client. This may or may not result in the same file access permissions as if the same user created the file through UNIX (NFS) or Windows (CIFS). You can check the umask by issuing the quote site umask command in the FTP session. Refer to the documentation with your FTP client for more information.
FTP Access
User Accounts
UNIX username Windows domain and username
Anonymous FTP
User logs in with anonymous or ftp User prompted for password ftp user must be configured in /.etc/passwd or NIS
When a Data Mover accepts login for an FTP session, the user is placed in a working directory
At the FTP logon prompt, a user may use either a UNIX username or a Windows domain and username (domain\username). If the user logs in without a domain name, UNIX authentication is used. The anonymous FTP facility allows a user to log in with the username anonymous or ftp. The system prompts for a password, to which the user is expected to respond with some kind of identification, usually a username or email address. To allow anonymous FTP to a Data Mover, the administrator must configure a user with a username of ftp in /.etc/passwd or in NIS. When a Data Mover accepts a users login for an FTP session, the user is placed in a working directory. The working directory depends on: Is the user anonymous, or a UNIX or Windows user? For UNIX users, does the user have a home directory specified in NIS or /etc/passwd? For Windows users, does the user have a home directory specified in /etc/homedir? Is the users home directory available on the Data Mover? Does the user have access to the home directory? Is there a default FTP working directory configured on the Data Mover? Note: For complete details on the behavior of each of these conditions, check Using FTP on Celerra Network Server.
The TFTP daemon, tftp, runs on the Data Mover and services requests from clients. This daemon must be started manually. TFTP for the Celerra is implemented using UDP. TFTP lacks many of the features of FTP. It provides no mechanism for user authentication, nor does it let you display a remote directory, invoke a shell, or manipulate files and directories. Celerra supports both read and write TFTP requests, but recommends read-only because of the limited security features of TFTP.
Module Summary
Key points covered in this module:
The device speed and duplex must be set on each Data Mover
interface to match the current network environment
The Data Mover interface IP address, mask, and broadcast address are configured through the GUI Default, network, and host routes can be configured for the each Data Mover DNS and NTP are services typically configured on each Data Mover FTP and TFTP services are supported by Celerra
These are the key points covered in this module. Please take a moment to review them.