¯ The green LED on the C0 port is illuminated when the manager module is the primary manager, and not illuminated when it is the secondary manager
¯ The green LED on the C0 port blinks when the manager module has not yet determined if it is the primary or secondary manager
¯ The amber LED on the C0 port is illuminated when it receives a message from the other manager module
1. Verify that your PortMaster 4 chassis has the Revision C backplane.
Check the backplane for the revision letter C . The revision letter is located behind slot 2.
2. Make sure that both system manager modules are capable of redundancy.
Verify that the model number on each module ends in R . Or check the label on the box that each module was shipped in for a manufacture date after July 1999 .
3. Verify that both system manager modules have ComOS 4.2 loaded.
Warning ¯ Use of a version earlier than ComOS 4.2 can damage PortMaster 4 hardware.
Warning ¯ (DC models only) Before working on equipment that is connected to power lines, remove jewelry such as rings, necklaces, and watches. Metal objects will heat up when connected to power and ground and can cause serious burns or weld the metal object to the terminals.
Warning ¯ To avoid damaging the internal components of the PortMaster 4, follow antistatic precautions by wearing a grounding wrist strap.
Figure 1-2 Grounding Strap Attachment --Front Panel
1. Line up the edge of the module with the card guide in slot 5 (Figure 1-4).
Note ¯ The physical slots are numbered 0 through 9 from left to right. Although a manager module is physically installed in slot 4 or slot 5, the Ethernet board of the module functioning as the primary manager is monitored through virtual slot 10.
2. Insert the manager module in slot 5, gently guiding the module into the slot.
If you have trouble sliding the module into the card guide, gently wiggle it back and forth to help it slide in.
Figure 1-4 Installing the Redundant System Manager Module
3. When the module is completely inserted in the slot, close the top and bottom tabs so they are flush with the face of the chassis.
Closing the tabs causes the module to connect with the backplane.
Procedures for netbooting are located at http://www.livingston.com/tech/technotes . Scroll to PortMaster Troubleshooting , click Netboot Procedures , then select the procedure for your platform.
o If you are using a PC, a RJ-45-to-DB-25 console cable with a 25-to-9-pin female adapter (See "Console Cable" on page A-2 for more information.)
1. Remove the cover from the cable guide if necessary.
2. Run the end of the cable with the RJ-45 connector through the cable guide duct until it is directly over the manager module.
3. Pull the end of the cable with the RJ-45 connector through the fingers of the cable guide duct as shown in Figure 1-6.
Figure 1-6 Pulling a Cable through the Cable Guide
4. Attach the RJ-45 connector to the C0 or C1 port of the manager module (see Figure 1-7).
Figure 1-7 Asynchronous Ports on the System Manager Module
5. Attach the RS-232 end of the cable to a dumb terminal or computer running terminal emulation software.
6. If you have finished inserting modules and boards and connecting lines, replace the cable guide cover by squeezing the duct fingers together with one hand, and sliding the cover over the duct fingers with the other.
7. Ensure that DIP switch 1 on the manager module is turned to the left.
8. Set the PC or terminal to 9600 baud, 8 data bits, 1 stop bit, a parity of none, and software flow control on (XON/XOFF).
o RJ-45-to-RS-232 modem cable (See "Modem Cable" on page A-1 for more information.)
1. Remove the cover from the cable guide, if necessary.
2. Run the end of the cable with the RJ-45 connector through the cable guide duct until it is directly over the manager module.
3. Pull the cable through the fingers of the cable guide duct as shown in Figure 1-8.
Figure 1-8 Pulling a Cable through the Cable Guide
4. Attach the RJ-45 end of the cable to the C0 port of the manager module (see Figure 1-9).
Figure 1-9 Console Port on the System Manager Module
5. If you have finished inserting modules and boards and connecting lines, replace the cable guide cover by squeezing the duct fingers together with one hand, and sliding the cover over the duct fingers with the other.
6. Ensure that DIP switch 1 is turned to the right.
7. Attach the RS-232 end of the cable to the external modem.
Refer to the documentation that came with your external modem for information on how to attach the RS-232 cable.
Note ¯ The PROM of the Ethernet card attached to the manager module contains the MAC address, which is actually a MAC address range. Conceptually, the Ethernet card has the MAC address, and MAC addresses for other devices in the system are software assigned from the address range based on the Ethernet card's MAC address. The primary manager in slot 4 assigns MAC addresses immediately after bootup. During failover, system components retain the MAC address assigned by the primary manager in slot 4.
o Category 5 twisted pair cable, as specified by the EIA/TIA-568-B wiring standard, with an RJ-45 connector (See "RJ-45 Cable" on page A-2 and "Ethernet Cable Specifications" on page A-3 for more information.)
1. Remove the cover from the cable guide, if necessary.
2. Run the cable through the cable guide duct until it is directly over the manager module.
3. Pull the cable through the fingers of the cable guide duct as shown in Figure 1-10.
4. Connect the cable to the RJ-45 or MII Ethernet 10/100BaseT interface (see Figure 1-11).
If both interfaces are connected, the system uses the MII by default.
5. If you have finished inserting modules and boards and connecting lines, replace the cable guide cover by squeezing the duct fingers together with one hand, and sliding the cover over the duct fingers with the other.
Figure 1-10 Pulling a Cable through the Cable Guide
Figure 1-11 Ethernet 10/100BaseT Interfaces on the Redundant Manager Module
o Category 5 unshielded twisted pair cable, as specified by the EIA/TIA-568-A wiring standard, with an RJ-45 connector (See "RJ-45 Cable" on page A-2 and "Ethernet Cable Specifications" on page A-3 for more information.)
1. Remove the cover from the cable guide, if necessary.
2. Run the cable through the cable guide duct until it is directly over the manager module.
3. Pull the cable through the fingers of the cable guide duct as shown in Figure 1-12.
Figure 1-12 Pulling a Cable through the Cable Guide
4. Connect the cable to the Ethernet 10BaseT interface (see Figure 1-13).
Figure 1-13 Ethernet 10BaseT Interface on the Manager Module
5. If you have finished inserting modules and boards and connecting lines, replace the cable guide cover by squeezing the duct fingers together with one hand, and sliding the cover over the duct fingers with the other.
1. Review "Installation and Configuration Requirements" on page 1-3 to make sure you are ready to configure.
2. Connect to the primary manager module in slot 4 via the console or an Ethernet port and enter the following command:
This command copies the system configuration from the primary manager module to the redundant (secondary) manager module's nonvolatile memory.
1. Connect to the secondary manager in slot 5 via the console port and use the following command to assign an IP address and netmask:
Command (Secondary)> set Ether0 address Ipaddress [/NM] [Ipmask]
To communicate with the redundant module on the network, you must assign it an IP address.
2. Enter the following commands to activate the configuration:
Command (Secondary)> save all
Command (Secondary)> reboot secondary
The save all command, entered on the redundant manager, saves the configuration to nonvolatile memory on the secondary manager.
When using a redundant manager, entering the save all command on the primary manager console saves the configuration to nonvolatile memory on both manager modules.
3. Use the commands in Table 1-1 as necessary to configure and operate the redundant manager module.
Refer to Chapter 3, "ComOS 4.2 Commands," for a detailed description of each command.
Note ¯ The redundant manager always displays (Secondary) in the prompt. You can observe in the logs how the prompt shifts from one manager to the other when they change roles.
1. A manager module is primary if it does not encounter another manager module for 4 seconds during the boot-up process.
2. If two manager modules boot at the same time, the manager in slot 4 is primary and the manager in slot 5 is secondary.
Note ¯ Be sure to use PMVision 1.8 on a PortMaster 4 with a redundant system manager module. Earlier versions of PMVision and the older programs pminstall , PMconsole, and PMconsole for Microsoft Windows do not recognize the redundant system manager module feature and view each manager module in the PortMaster 4 as a separate system.
Figure 1-14 PMVision Showing a Primary and Secondary Manager
LED Behavior | Possible Cause | Explanation or Possible Solution |
---|---|---|
Green C0 LED is lit. | Manager module is primary | Normal behavior when a redundant manager module is installed. |
Green C0 LED off. | Manager module is secondary | Normal behavior when a redundant manager module is installed. |
Green C0 LED is flashing. | Manager module is booting and negotiating with the other manager to determine which is primary. | Normal behavior for a few seconds during bootup. Persistent flashing indicates trouble in the communications path between the two manager modules. See "Troubleshooting Communication between Manager Modules" on page 1-23. |
Amber C0 LED is flashing. | Peer-to-peer messages are traveling between manager modules. | Normal behavior when a redundant manager module is installed. |
All LEDs fail to light. | Power is not present. | Check the power switch, power cable, outlet, and fuse. For instructions on checking and changing the fuse in the AC version, see "Replacing a Fuse" on page 4-10 of the PortMaster 4 Installation Guide . Contact Lucent NetCare technical support if power is not present on the DC version. |
Amber DIAG LED on the manager module does not light. | Board malfunction. | Contact Lucent NetCare technical support. |
During startup, the DIAG LED on the manager module fails to light, stays lit, or blinks three times per second continuously. | A hardware problem has occurred. | Contact Lucent NetCare technical support. |
During startup, the DIAG LED on the manager module blinks once per second for more than a minute. | · DIP switch 2 is turned to the left and no boot server is present. | · If no boot server is available, verify that DIP switch 2 is turned to the right and reboot; otherwise, see the network booting procedure in the PortMaster Troubleshooting Guide. · If nonvolatile RAM contents are corrupt, follow the PortMaster Troubleshooting Guide procedure for network booting and rewriting the contents of nonvolatile RAM. |
Immediately after booting, the DIAG LED on the manager module stays solidly lit or does not light. This behavior does not refer to the boot sequence, during which the DIAG LED is not lit for between 5 and 7 seconds. | A component might have loosened during shipping. | Remove the manager module from the PortMaster 4 chassis and verify the following:
· The nonvolatile RAM is firmly in place. If all items have been verified and the problem is not fixed, refer to "Observing Boot Messages" on page 4-3 in the PortMaster 4 Installation Guide , and boot in console mode. If the boot messages do not suggest a solution, record the information and contact Lucent NetCare technical support. |
During operation, the DIAG LED on the manager module stays solidly lit or does not light. | A hardware problem might have been caused by an external device. | If the LED stays solidly lit or does not light after you have removed all external devices, contact Lucent NetCare technical support. |
No console login prompt is displayed. | Terminal settings are incorrect or a connection or cable is inoperable. | · Verify terminal settings of 9600 baud, 8 data bits, 1 stop bit, a parity of none, and software control on (XON/XOFF). · Verify that DIP switch 1 is turned to the left. · Verify that you have a working console (null modem) cable and that it is properly connected at both ends. For cable information see "Console Cable" on page A-2. |
Link (green) LED on an Ethernet interface is not lit when connected to an Ethernet hub. | There is no link integrity. | Check the connection to the hub. |
Network (amber) LED on an Ethernet interface is solidly lit. | Heavy traffic can cause the network LED to blink so rapidly that it appears to be solidly lit. However; If packets cannot be passed, you might have an incorrectly cabled network. | Verify that the network cabling is correct. |
Network (amber) LED on an Ethernet interface is not lit. | If the PortMaster 4 is not receiving or sending traffic, the network LED is not lit. | Verify that the network cabling is correct. |
An undefined problem occurred at startup, but the cause cannot be determined from LED behavior. | Refer to the solution column. | Try booting in console mode, and observe the boot messages. See "Observing Boot Messages" on page 4-3 of the PortMaster 4 Installation Guide . If the boot messages do not suggest a solution, record the information and contact Lucent NetCare technical support. |
1. If the secondary manager module does not receive responses to five consecutive hello messages, it listens for the heartbeat of the primary.
2. If it detects a heartbeat, the secondary does not take over as primary manager but generates a "Can't hear manager in slot 4." SNMP alarm.
3. If the secondary manager does not detect a heartbeat from the primary, it takes over and becomes primary.
4. The new primary manager reboots the system. All calls and network connections to the PortMaster are dropped, and dynamic routing information is lost.
1. Check for the following two events, which can indicate channel failure:
a. The secondary manager does not detect a heartbeat from the primary and generates a "Primary manager in slot 4 failed." SNMP alarm. If you can verify that the primary manager is functioning properly, proceed to Step 5. If the secondary generates a "Can't hear manager." alarm, proceed to Step 2.
b. The primary receives no communication from the secondary for 30 seconds and generates a "Secondary manager in slot 5 failed." SNMP alarm. (The primary does not check for the secondary's heartbeat.)
2. If you receive these failure alarms on both manager modules, wait and monitor the problem for several minutes.
3. If the problem persists for more than a minute or two, reboot the secondary manager module from the secondary's console.
4. If the reboot fails to correct the problem, turn power to the PortMaster 4 off and on.
5. If the manager modules are still not communicating, reseat the secondary manager module by pulling it out and reinserting it into the slot.
See "Safety Precautions" on page 1-4 and "Grounding Wrist Strap Instructions" on page 1-4 before proceeding.
6. If reseating the secondary manager fails to correct the problem, reseat the primary manager module.
7. If the communication problem persists, contact Lucent NetCare technical support.
1. Make sure that you have the proper hardware and software, and take the proper safety precautions.
See "Installation and Configuration Requirements" on page 1-3 for instructions.
2. Disconnect lines to the failed manager module.
3. Open the top and bottom tabs on the failed manager module and remove it from the slot in the PortMaster 4 chassis.
4. Insert a new manager module.
See "Installing a Redundant System Manager Module" on page 1-5 for instructions.
5. Connect a console cable and Ether0 and Ether1 lines.
See "Connecting a Console" on page 1-7 and "Connecting an Ethernet Cable" on page 1-10.
6. Enter the following command to configure an Ethernet address for Ether0:
Command> set ether0 address Ipaddress
See "Configuring the Ethernet Interfaces" on page 1-15 for more information.
7. Enter the following commands to save changes to nonvolatile memory and activate the configuration:
Note ¯ Be sure to use PMVision 1.8 on a PortMaster 4 with a redundant system manager module. Earlier versions of PMVision and the older programs pminstall , PMconsole, and PMconsole for Microsoft Windows do not recognize the redundant system manager module feature and view each manager module in the PortMaster 4 as a separate system.
1. Make sure that you have the proper hardware and software, and take the proper safety precautions.
a. See "Installation and Configuration Requirements" on page 1-3 for instructions.
b. Make sure that the manager module in slot 4 is running ComOS 4.2. If it is not, upgrade this manager before going on to Step 2
2. Prepare the spare manager module for netbooting:
a. Set DIP switch 2 to the left.
See "DIP Switch Settings" on page 1-6 for more information.
b. Set up a directory structure to load ComOS 4.2 for netbooting to the manager's Ether0 IP address.
Procedures for netbooting are located at http://www.livingston.com/tech/technotes . Scroll to PortMaster Troubleshooting , click Netboot Procedures , then select the procedure for your platform.
3. Insert the spare manager module in slot 5.
See "Installing a Redundant System Manager Module" on page 1-5 for instructions.
4. Connect a console cable and Ether0 and Ether1 lines.
See "Connecting a Console" on page 1-7 and "Connecting an Ethernet Cable" on page 1-10.
5. Connect to the spare manager module.
6. If an IP address, netmask, and gateway address for the Ether0 interface are not provided by Dynamic Host Configuration Protocol (DHCP) services, enter the following commands to configure them:
Command> set ether0 address Ipaddress
Command> set netmask Netmask
Command> set gateway Ipaddress
Command> save all
See "Configuring the Ethernet Interfaces" on page 1-15 for more information.
7. Upgrade ComOS on the spare manager module to ComOS 4.2.
¯ You can use the tftp get command to download ComOS by entering the command as follows from the spare manager module:
Command> tftp get Ipaddress Filename
Replace Ipaddress with the IP address of the TFTP server and Filename with the name of the ComOS image.
¯ You can also use PMVision 1.8 or later to upgrade the manager.
8. Set DIP switch 2 to the right to turn off netbooting on the manager module.