You can communicate with the Fibre Channel Hub via a terminal or PC connected to it, or remotely. This chapter explains
In most cases, you can accomplish these tasks using either the command-line interface or the Internet browser interface. The sections in this chapter give instructions for each interface as appropriate.
You can communicate with the Fibre Channel Hub via a terminal or PC connected to it. Local communication requires an ANSI console terminal or a PC; for requirements, see “Determining Hub Management” in Chapter 2.
This section consists of the following:
To log in via a console, follow these steps:
Verify that the following software is installed on the system and configured correctly:
eoe.sw.uucp
/etc/uucp/Devices configuration file
For example, this file should contain a line like the following:
Direct ttyd2 - 9600 direct
In a window, enter
cu -l /dev/ttydX
where X is the port number; for example, ttyd2. (The cu command is “call UNIX.”) A message appears:
Connected
Press Esc twice. A prompt appears:
Enter username or HELP>
Press the space bar and Enter. The hub prompt appears, indicating normal privilege:
Server>
For full access to the hub, enter
Server> su
At the Password prompt, enter the password. The initial (and default) password is system.
Password> system
The characters you enter do not echo to the screen.
For information on setting passwords and on administrator privilege, see “Setting Passwords”.
For information on logging out, see “Terminating the Connection”.
To use a terminal emulation program for managing the hub, assign IP address, subnet mask, and default gateway as explained in “Changing TCP/IP Settings”.
This section explains how to set up remote communication—Telnet or Internet browser—for Fibre Channel Hub management. It consists of the following:
For remote communication, the Fibre Channel Hub must
be connected to the network via the hub's 10-Base-T Ethernet port
have an IP address assigned
be on the same subnet as the server or workstation you are using, for initial installation
For more information, see “Determining Hub Management” in Chapter 2.
If the workstation you are using for remote communication with the hub is not on the same LAN segment as the hub, define a subnet mask and default gateway, as explained in “Changing TCP/IP Settings: Command-Line Interface”.
 | Note: Instead of following the steps below, you can assign the IP address through local communication as explained in “Logging In via a Console Terminal”. |
To use the command-line interface to log in remotely to the Fibre Channel hub, follow these steps:
Obtain a unique IP address; to verify that it is available, enter:
% ping ipaddress
where ipaddress is the IP address as assigned by the network administrator. Enter the IP address with periods, in this pattern:
xxx.xxx.xx.xx
For example:
123.456.78.90
You can stop ping command output with Ctrl+C.
You should not receive a response. If you do, obtain another IP address and repeat this step.
Get the MAC (Ethernet) address of the Channel Hub; Figure 2-8 in Chapter 2 points out the location.
-
% arp -s ipaddress macaddress
where ipaddress is the IP address as assigned by the network administrator and macaddress is the hub's MAC address, such as 08-00-69-00-c1-a9. For example:
% arp -s 138.239.252.183 08-00-69-00-c1-a9
Verify that the IP address was assigned:
% ping ipaddress
When the ping command is issued, the Fibre Channel Hub automatically assigns a default subnet mask based on the class of IP address. If the hub is to receive communication from a system on another LAN segment, define a subnet mask and default gateway for the hub as described in “Changing TCP/IP Settings: Command-Line Interface”, or an SNMP MIB browser, since the server or workstation is on the same Ethernet subnet as the hub.
To use the Internet browser interface to log in remotely to the Fibre Channel Hub, start the Internet browser interface: for the URL, enter http://, followed by one of the these choices:
the device IP address as assigned in “Setting Up Remote Communication for Hub Management”
the full name of the device as specified in the etc/hosts file
the short name of the device as specified in the etc/hosts file
The status screen appears, as shown in Figure 4-1. Note features pointed out in this illustration.
Use this procedure to connect to a Fibre Channel Hub from a workstation with Telnet. Follow these steps:
Make sure that the workstation is on the same LAN segment as the hub. If it is not, define a subnet mask and default gateway, as explained in “Changing TCP/IP Settings”.
In a shell window, enter
% telnet ipaddress
where ipaddress is the newly assigned IP address of the hub, in this pattern:
xxx.xxx.xxx.xxx
For example:
123.456.123.456
If the connection is successful, the Telnet> prompt appears.
Log in to the hub:
Telnet> access
where access is the default remote login password (it does not echo to the screen).
The prompt changes to Local>.
Enter su; enter the password. The default administrator password is system. (It does not echo to the screen.)
If desired, define the subnet mask and default gateway following instructions in “Changing TCP/IP Settings”.
A user who knows the administrator password has administrator privilege and can control Fibre Channel Hub configuration. Most commands in this chapter require privileged status.
To obtain administrator privilege, follow these steps:
Make a connection to the Fibre Channel Hub. The prompt appears, indicating normal privilege:
Server>
To gain administrator privilege, enter
Server> su
The prompt changes; enter the administrator password (the default password is system):
Password> password
The characters you type do not echo to the screen.
The prompt changes to Server>>. The double angle bracket indicates full administrator privilege.
This section explains how to view and change TCP/IP settings using the command-line interface and the Internet browser interface, in separate subsections.
To display TCP/IP settings, enter
Server> show server tcp |
To enable or disable TCP/IP on the hub manager, a user with administrator privilege enters
Server>>define server authorize protocol tcp [enable|disable] |
If you disable TCP, you can manage the hub only via local communication.
To change the hub's IP address, a user with administrator privilege enters
Server>>change server ip ipaddress |
where ipaddress is the address assigned by the network administrator. Enter the IP address in decimal dot notation, in this pattern:
xxx.xxx.xx.xx |
For example:
123.234.22.22 |
To change the hub's subnet mask for the hub, a user with administrator privilege enters
Server>>change server subnet subnetmask |
where subnetmask is a number between 0 and 255. Enter the subnet mask with periods, in this pattern:
xxx.x.x.x |
For example:
255.0.0.0 |
To define a gateway, a user with administrator privilege enters
Server>>change server gateway gatewayipaddress |
where gatewayipaddress is the address assigned by the network administrator, in decimal dot notation (xxx.xxx.xx.xx).
The gateway node address must be identified before the hub can communicate across a router. The gateway provides access to the router and the rest of the network segment.
To view or change TCP/IP parameters using the Internet browser interface, follow these steps:
Click Setup in the menu (navigation) bar. The Setup menu screen appears, as shown in Figure 4-2.
Click Hub Setup; the Hub Setup menu appears, as shown in Figure 4-3.
Select TCP Setup; Figure 4-4 shows the screen that appears.
Note: The default settings in this screen are recommended; do not change these values unless you have good reason to do so. Enter the IP address, and, if applicable, subnet mask and gateway address.
The check boxes at the bottom of this screen control automatic IP address maintenance. Automatic IP maintenance can make use of any combination of BootP, RARP, and DHCP. The choices have the following meanings:
Manual: automatic acquisition is not used.
Automatic - Permanent: The software looks for an automatically acquired address only when the Digital Hub Manager has no IP address. Once an IP address is found, it is saved for subsequent restarts.
Automatic - Temporary: The software looks for an automatically acquired address every time the Digital Hub Manager restarts.
If required, change subnet mask and gateway address in this screen.
When the entries are the way you want them, click Apply.
In the prompt window that appears, enter a username, a user ID (such as su), and the password (the default is system). Click OK.
The changes take several minutes to go into effect.[1] When the process is complete, a message flashes near the top of the window:
CHANGED AS REQUESTED
The BootP, DHCP, and RARP parameters determine how the hub communicates with the host. At restart, the default sequence of IP address acquisition is as follows:
Attempt BootP.
If BootP fails, attempt DHCP.
If DHCP fails, attempt RARP.
You can change the thresholds at which the hub gives up one IP address acquisition method for the next. This section explains how to change these thresholds using the command-line interface and the Internet browser interface, in separate subsections.
To set the number of times BootP attempts IP address acquisition, a user with administrator privilege enters
Server>>define server bootp n m [temp|permanent] |
where
| n | Is the number of broadcast requests between 0 (the default) and 7 to be made if the digital hub IP address is not known. This option prevents the use of automatic IP address assignment. | |
| m | Is the number of broadcast attempts to make if the hub IP address is known. The default is 0. | |
| temp | Puts the response in volatile memory only. This option forces automatic IP address assignment every time the hub is rebooted. | |
| permanent | Stores the response for future address acquisition attempts. This choice is the default. |
To set the number of times DHCP attempts IP address acquisition, a user with administrator privilege enters
Server>>define server dhcp n m [temp|permanent] |
To set the number of times RARP attempts IP address acquisition, a user with administrator privilege enters
Server>>define server rarp n m [temp|permanent] |
To test if a local or remote IP address exists and is responding, use ping.
To view or change BootP, DHCP, or RARP parameters using the Internet browser interface, click Setup in the menu bar, click Hub Setup, and then click TCP Setup. Figure 4-4 on page 47 shows the screen that appears.
Change the settings as desired; click Apply when they are the way you want them. In the window that appears, enter a user name (su) and password.
A user with administrator privilege can enable or disable the Internet browser connection to the hub as follows:
Server>>change service http connections [enabled|disabled] |
To enable or disable the connection to the hub through Telnet, enter
Server>>change service telnet connections [enabled|disabled] |
To test if a local or remote IP address exists and is responding, use ping.
This section explains how to segment the hub into two five-port hubs, or how to return it to normal operation. (See “Hub Segmentation” in Chapter 2.) You can use the command-line interface or the Internet browser interface; instructions are in separate subsections:
To segment the hub into two five-port hubs, a user with administrator privilege enters
Server>>change hub cascade disable |
When you segment the hub (disable the factory default ten-port functionality), the green power LED at the top left of the Ethernet socket on the hub's front panel blinks at high intensity. At low intensity, this LED indicates that the hub is powered on. Figure 4-5 points out this LED.
To return a segmented hub to ten-port operation, a user with administrator privilege enters
Server>>change hub cascade enable |
The power LED returns to low intensity.
To use the Internet browser interface to split the hub into two five-port hubs, select Setup in the menu bar and click Hub Setup. Figure 4-6 shows the Digital Hub setup screen that appears.
In this screen, check the top check box, Act as two 5-port hubs, so that a check mark appears. Click Apply to put the change into effect.
When you segment the hub (disable the factory default ten-port functionality), the green power LED at the top left of the Ethernet socket on the hub's front panel blinks at high intensity. At low intensity, this LED indicates that the hub is powered on. Figure 4-5 points out this LED.
To return a segmented hub to normal operation, click the check box to remove the check mark; click Apply. In the window that appears, enter a user name (su) and password. The power LED returns to low intensity.
This section explains how an administrator can set passwords. It consists of the following subsections:
The default password for remote Telnet and rcf access is access. To change it using the command-line interface, follow these steps:
Enter the following:
Server>>change server login password
The prompt changes; enter the new password:
Login Password> newpassword
where newpassword is a string of 0 to 16 letters or numerals, in any combination. If you do not enter any letters or numerals, the password remains set to the default.
The characters you type do not echo to the screen.
The prompt changes; enter the new password a second time to verify it:
Verification> newpassword
The characters you type do not echo to the screen.
The default administrative (administrator superuser, or read/write) password controls which users can change the Fibre Channel Hub manager configuration. The factory default for this password is system. To change it, follow these steps:
Enter the following:
Server>>change server privilege password
The prompt changes; enter the new password:
Privileged Password> newpassword
where newpassword is a string of 0 to 16 letters or numerals, in any combination. If you do not enter any letters or numerals, the password remains set to the default.
The characters you type do not echo to the screen.
The prompt changes; enter the new password a second time to verify it:
Verification> newpassword
To change the default administrative password using the Internet browser interface, click Setup, then click, Manager Setup, and then select Set Password. Figure 4-7 shows the screen that appears.
Change the password as desired; fill in all three fields. Click Apply when it is set.
To terminate the local or remote connection with the hub, enter
Server> logout |
or, with privileged status, enter
Server>>logout |
To kill the cu command, type a tilde and a period:
% ~. |
| Note: If you kill the cu command without first logging out at the Server prompt, when you try to log in again (see step 3 on page 38), you must press Esc twice and Enter to see the Server prompt. |
[1] The first change requiring a user ID and password usually takes several minutes; subsequent changes take less time.