|
|
The Cisco Optical Regenerator is a bidirectional Optical Carrier-48/Synchronous Transport Module-16 (OC-48/STM-16) regenerator that transmits optical signals up to distances of 50 miles (80 kilometers). In an OC-48 SONET installation, the Cisco Optical Regenerator significantly extends the separation between two routers, depending on the quality of the fiber optic cabling. (See Figure 1.)
The regenerator provides an end-to-end Internet Protocol (IP) transport for long distances by forwarding Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) traffic at OC-48 line rates.
When you connect the regenerator's OC-48 regeneration ports to an OC-48 line card in a router, you also connect to SDCC interfaces, SDCC0 or SDCC1, and regenerator controller modules, Regen 0 and Regen 1. The SDCC interfaces and regenerator controller modules regenerate traffic and manage traffic paths.
When you power up the regenerator for the first time, it goes through a system bootstrap startup sequence that boots the Cisco IOS software that is installed from Flash memory. The regenerator runs a power-on self-test (POST) that verifies basic operation of the CPU, memory, and interfaces. When all of the configuration files are loaded, the console terminal displays the following System Configuration Dialog prompt:
--- System Configuration Dialog --- Would you like to enter the initial configuration dialog? [yes/no]:
(Portion of displayed text omitted from example)
You can use AutoInstall to automatically configure the Cisco Optical Regenerator. When the regenerator is connected to the Ethernet port, AutoInstall starts after the power-on self test completes.
To ensure that AutoInstall works properly, your system administrator must preconfigure the Transmission Control Protocol/Internet Protocol (TCP/IP) host on your network and put the required configuration files in the regenerator's nonvolatile random-access memory (NVRAM). It contains configuration information for Cisco IOS, ROM Monitor, and system information. You can use Cisco IOS commands to configure the memory partitions. The new configuration does not take effect until it is saved to NVRAM and the router is reloaded.
To enter Set-Up Configuration Mode and manually enter Cisco IOS commands, you must boot the regenerator without any default configuration settings. You can invoke Set-Up Configuration Mode when the regenerator is connected to the network through either the Ethernet port or the OC-48 regenerator ports.
The regenerator uses standard Cisco IOS software and standard configuration methods.
The Cisco Optical Regenerator is best used when two or more routers on a network are more than 50 miles apart in a remote area. You can connect a regenerator between two Cisco 12000 series routers to carry a signal up to 50 miles (80 km) with high quality single-mode long reach fiber.
The Cisco Optical Regenerator has the following restrictions.
Cisco product documentation that relates to the Cisco Optical Regenerator includes:
The Cisco Optical Regenerator is compatible with the following Cisco 12000 series routers:
The person(s) who will install, configure, and maintain the Cisco Optical Regenerator must be familiar with basic router configuration practices, and more specifically with Cisco 12000 series routers, so that they can connect the regenerator to system network devices. The person(s) must be familiar with optical and telecommunications networks, Cisco IOS software, and be able to perform software configuration and diagnostic procedures on the regenerator.
To ensure that AutoInstall works properly, your system administrator must preconfigure the TCP/IP host on your network and put the required configuration files in NVRAM. It contains configuration information for Cisco IOS, ROM Monitor, and system information. Cisco IOS software commands will be used to configure the memory partitions. The new configuration commands must be saved to NVRAM to take effect, using the copy run start command.
 | TimeSaver Ask your system administrator or review the network plan to verify network IP addresses before you begin to configure the Cisco Optical Regenerator. |
The Cisco Optical Regenerator supports the following MIBs and RFCs:
To configure the Cisco Optical Regenerator, perform the following tasks. The first or second task is required. The third task is required.
The following sections describe the how to configure the Cisco Optical Regenerator by.
Use AutoInstall to automatically enter the default interface configuration commands. To invoke AutoInstall, perform the following tasks, beginning at the user prompt.
| Step | Command | Task | ||
|---|---|---|---|---|
| Would you like to enter the initial configuration dialog? [yes/no]: y(es) | Enter y(es) to start AutoInstall. | ||
| Regen# copy running-config startup-config | Enter the copy running-config startup-config EXEC command to save the configuration to NVRAM. |
To manually configure the Cisco Optical Regenerator using the Set-Up Configuration Dialog, enter no at the set-up utility prompt to erase the default configuration. To invoke the Set-Up Configuration Dialog, perform the following tasks, beginning at the user prompt.
| Step | Command | Task | ||
|---|---|---|---|---|
| Would you like to enter the initial configuration dialog? [yes/no]: n(o) | Enter n(o) to erase the default configuration and start the System Configuration Dialog. | ||
| Regen# copy running-config startup-config Regen# | Enter the copy running-config startup-config EXEC command to save your configuration to NVRAM. |
The following sections describe tasks that include the following:
To create the LAN interface connections through two OC-48 regeneration ports, you must be sure that the two SDCC interfaces, SDCC0 and SDCC1 have sequential IP addresses. You may have to reconfigure the SDCC interfaces to achieve this. This is a required task. Follow the steps in this section to configure both the SDCC interfaces, beginning in privileged EXEC mode.
One of the following must be true for SDCC interfaces to work properly:
1. All SDCC interfaces can be on the same subnet. Routing Information Protocol (RIP) and IP routing must be enabled on each regenerator.
2. All SDCC interfaces can be on different subnets. IP routing and RIP must be enabled on each regenerator.
For example, when two routers that are on two different subnets are connected to the regenerator, you must enable RIP on each subnet.
To enable RIP on the SDCC interfaces, be sure that the IP address for each SDCC interface overlaps the networks configured for the RIP protocol. Complete the following tasks, beginning in privileged EXEC mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen# configure terminal Regen(config)# | Enter the configure terminal command to enter global configuration mode. | ||
| Regen(config)# router rip | Enter the router rip global configuration command. | ||
| Regen(config)# network 10.0.0.0 (subnet 1) | Enter the network global configuration command and specify the IP address and subnet mask of the router that is connected to the regenerator. | ||
| Regen(config)# interface SDCC0 Regen(config-if)# | Type the interface SDCC0 global configuration command. | ||
| Regen(config-if)# ip address 10.a.b.c 255.255.255.0 Regen(config-if)# | Enter the ip address interface configuration command and specify the IP address and subnet mask. | ||
| Regen(config-if)# keepalive Regen(config-if)# no shutdown Regen(config-if)# | Add the keepalive interface configuration command to keep the interface up. Enter a no shutdown interface configuration command to prevent data traffic shutdowns. | ||
| Regen(config-if)# end Regen# | Type end to return to privileged EXEC mode. | ||
| Regen# show interface SDCC0
interface SDCC0 bandwidth 192 ip address 10.a.b.c 255.255.255.0 ip directed-broadcast keepalive crc 32 ! | Enter the show interface SDCC0 EXEC command to verify the new SDCC0 interface configuration. |
To enable RIP and configure the SDCC1 interface, complete the following tasks, beginning in privileged EXEC mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen# configure terminal Regen(config)# | Enter the configure terminal command to enter global configuration mode. | ||
| Regen(config)# router rip | Enter the router rip global configuration command. | ||
| Regen(config)# network 11.0.0.0 (subnet 2) | Enter the network global configuration command and specify the IP address and subnet mask of each router that is connected to the regenerator. | ||
| Regen(config)# interface SDCC1 | Enter the interface global configuration command and specify the SDCC1 interface. | ||
| Regen(config-if)# ip address 11.x.y.z 255.255.255.0 Regen(config-if)# | Configure the SDCC1 interface using the ip address interface configuration command and enter the IP address and subnet mask. | ||
| Regen(config-if)# keepalive Regen(config-if)# no shutdown Regen(config-if)# | Add the keepalive interface configuration command to keep the interface up. Enter a no shutdown interface configuration command to prevent data traffic shutdowns. | ||
| Regen(config-if)# exit Regen(config)# exit Regen# | Type exit to return to the privileged EXEC mode. | ||
| Regen# show interface SDCC1
interface SDCC1 bandwidth 192 ip address 11.x.y.z 255.255.255.0 ip directed-broadcast keepalive crc 32 ! | Enter the show interface SDCC1 EXEC command to verify the new IP address for the SDCC1 interface. |
When you connect two OC-48 regeneration ports to a two-port OC-48 line card, you also connect the two regenerator controller module interfaces Regen 0 and Regen 1. When the connection occurs, the Regen controller module interfaces are automatically up. The Regen controllers monitor the SONET section overhead on incoming data.
Follow the configuration tasks in this section to configure the regenerator controller module interfaces, beginning in privileged EXEC mode. To access commands that will allow you to modify regen controller parameters, enter the regen controller configuration command and specify the command option.
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen# configure controller Regen(config-controller)# | Enter the configure controller EXEC command to enter controller configuration mode. | ||
| Regen(config-controller)# regen overhead j0 0x1 Regen(config-controller)# | To specify overhead, enter the regen overhead j0 controller configuration command and specify the range of values for j0. | ||
| Regen(config-controller)# regen framing sdh | To specify framing, enter the regen framing controller configuration command and specify the framer format. | ||
| Regen(config-controller)# regen report rxclk-fail Regen(config-controller)# | To enable the regenerator's alarms, enter the regen report controller configuration command and specify the alarm type. Enter the no regen report command to disable the regenerator's alarms. | ||
| Regen# show controller regen 0 Regen0 is up Error Count: RxClockFail = 0 SLOS = 1 SLOF = 1 BIP(B1) = 0
Active Defects: LOS LOF Active Alarms: SLOS Alarm reporting enabled for: RxClockFail SLOS SLOF B1-TCA
B1 TCA threshold: B1 = 10e-6
Framer 0, addr=0x68004000: Regen#
(Portion of displayed text omitted from example) | To verify controller status, enter the show controllers regen EXEC command and specify 0 or 1. | ||
| Regen# copy running-config startup-config Regen# | Enter the copy running-config startup-config privileged EXEC command to save your configuration changes to NVRAM. |
To create a LAN interface connection through the Ethernet port on the Cisco Optical Regenerator, you must configure the Ethernet interface. Ethernet0 is the only allowed value for the Ethernet interface. This is a required task. Follow these steps to configure the Ethernet interface beginning in privileged EXEC mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen# configure terminal Regen(config)# | Enter the configure terminal command to enter global configuration mode. | ||
| Regen(config)# interface ethernet0 Regen(config-if)# | Enter the interface Ethernet 0 global configuration command which puts you in interface configuration mode for the Ethernet interface. The prompt changes to interface configuration mode. | ||
| Regen(config-if)# ip address 20.15.5.9 255.255.255.0 Regen(config-if)# | Assign an IP address and subnet mask by entering the ip address interface configuration command. | ||
| Regen(config-if)# end Regen# | Type end to return to privileged EXEC mode. | ||
| Regen# copy running-config startup-config Regen# | Enter the copy running-config startup-config EXEC command to save your configuration changes to NVRAM. |
This concludes the Cisco Optical Regenerator configuration tasks with LAN-accessible interfaces.
The Cisco Optical Regenerator console port provides local access when it is connected to a terminal server, or a modem. You can communicate with the regenerator through a PC or VTY.
The following sections explain how to use the console port on the Cisco Optical Regenerator to:
To use the console port to download files, you may need to increase the baud rate. The console port baud rate speed determines the length of time it takes to download files to the regenerator. You can temporarily increase the console port baud rate to 115200 bps to decrease downloading time. The default console port parameters are 9600 bps, 8 data bits, no parity, 2 stop bits. The console port supports the following baud rates shown in Table 1.
1200 bps | 19200 bps |
2400 bps | 38400 bps |
4800 bps | 57600 bps |
9600 bps | 115200 bps |
For details on downloading files through the console port, see the section "Download Through the Console Port" section.
Table 2 shows the downloading speeds for the console port or the Ethernet port.
| Regenerator Interface | Baud Rate | Time Length |
|---|---|---|
9600 bps (default) | 30-40 minutes | |
Console port | 115200 bps | 6 minutes |
Ethernet port (configured) | 10Mbps | 5-10 seconds |
Once the Ethernet port is configured, it has a default baud rate of 10Mbps and takes only five to ten seconds to download the software using TFTP commands. For details on the Ethernet port, see the sections "Configure the Ethernet Interface" section, and "Download Through the Ethernet Port" section.
To change the console port baud rate, follow the configuration tasks in this section, beginning in ROM Monitor mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| rommon 1 > confreg Configuration Summary enabled are: break/abort has effect console baud:9600 boot:the ROM Monitor
do you wish to change the configuration? y/n [n]: y enable "diagnostic mode"? y/n [n]: enable "use net in IP bcast address"? y/n [n]: enable "load rom after netboot fails"? y/n [n]: enable "use all zero broadcast"? y/n [n]: disable "break/abort has effect"? y/n [n]: enable "ignore system config info"? y/n [n]: change console baud rate? y/n [n]: y change the boot characteristics? y/n [n]:
After you answer yes to the prompt to change the console baud rate, a list of different console baud speeds displays on the screen. Choose the 115200 bps baud rate.
Configuration Summary enabled are: break/abort has effect console baud:115200 boot:the ROM Monitor
do you wish to change the configuration? y/n [n]: | Enter the confreg command in ROM Monitor mode. | ||
| None. | Download a Cisco IOS software image using an option described in this section. | ||
| rommon 2 > confreg | Reset the baud rate to the default parameters by entering the previously shown confreg command. |
Cisco recommends using xmodem commands to download a Cisco IOS software image only as a disaster recovery mechanism, because you must be physically present at the regenerator to connect a PC to the console port.
In ROM Monitor mode, use the xmodem commands to download a Cisco IOS software image through the console port.
| Step | Command | Task | ||
|---|---|---|---|---|
| rommon 1 > xmodem <image name> (copy to flash)
or
rommon 2 > xmodem -r <image name> (run from RAM) | Use the xmodem filename command to begin receiving a Cisco IOS software image through the console port. where filename specifies the name of the Cisco IOS software image that will be written to Flash memory. | ||
| None | After you enter the xmodem command, a screen output displays. | ||
| rommon 3 > y(es) | Enter y(es) and start the xmodem transmission from within your terminal emulation software. |
System Bootstrap, Version 12.0(19990409:171649) [ROMMON_Apr9 102]
Copyright (c) 1994-1999 by cisco Systems, Inc.
REGEN48 platform with 16384 Kbytes of main memory
rommon 1 > xmodem regen-i4-mz.final
Do not start the sending program yet...
File size Checksum File name
1382456 bytes (0x151838) 0x5db4 regen-i4-mz.final
4 bytes (0x4) 0xceff snmpboots (deleted)
4 bytes (0x4) 0xcdff snmpboots
WARNING:All existing data in bootflash will be lost!
Invoke this application only for disaster recovery.
Do you wish to continue? y/n [n]: y
Ready to receive file regen-i4-mz.final ...
To download Cisco IOS software images through the configured Ethernet port, use one of the methods described in this section:
To download a Cisco IOS software image from Flash memory, follow the configuration tasks in this section, beginning in privileged EXEC mode.
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen# configure terminal | Type configure terminal to enter global configuration mode. | ||
| Regen (config)# boot system flash filename Regen (config)# | To download from flash memory, enter the boot system flash command, replace filename with the filename of the Cisco IOS image. | ||
| Regen (config)# end Regen# | When the download is completed, the global configuration prompt returns. Type end to return to privileged EXEC mode. | ||
| Regen# copy running-config startup-config Building configuration ... [OK] Regen# | Enter the copy running-config startup-config EXEC command to save your configuration changes to NVRAM. |
To quickly download a Cisco IOS software image from a local TFTP server, use the Ethernet port, beginning in privileged EXEC mode.
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen# configure terminal Regen (config)# | Enter the configure terminal command to enter global configuration mode. | ||
| Regen (config)# boot system tftp filename ipaddress Regen (config)# exit | To configure the regenerator to download images through the Ethernet port, enter the boot system tftp global configuration command and: Replace filename with the filename of the Cisco IOS software image. Replace ipaddress with the IP address of the TFTP server. | ||
| Regen# copy running-config startup-config Building configuration ... [OK] Regen# | Enter the copy running-config startup-config EXEC command to save your configuration changes to NVRAM. Using this command erases everything from Flash. If you boot from a TFTP server, you can reload files from the TFTP server. |
You can use the File Transfer Protocol (FTP) or Remote Copy Protocol (RCP) to download Cisco IOS software images to the regenerator. The regenerator controllers support FTP server software that resides in the system controller until it is notified that data is ready to be transferred to the regenerator controller in a specified file.
To transfer Cisco IOS software to the regenerator using FTP, follow the configuration tasks in this section, beginning in privileged EXEC mode.
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen# configure terminal Regen(config)# | Enter the configure terminal command to enter global configuration mode. | ||
| Regen(config)# ftp-server enable Regen(config)# | Enter the ftp-server enable command. | ||
| Regen(config)# end Regen# | Type end to return to privileged EXEC mode. | ||
| Regen# copy running-config startup-config Regen# |
You can copy a file from a network server to the regenerator using rcp, or by using one of the following copy rcp EXEC commands. The copy rcp running-config command replaces the configure network command in the command line. The copy rcp startup-config command replaces the configure overwrite-network command in the command line. To copy a file from a network server to the regenerator, follow the configuration tasks in this section, beginning privileged EXEC mode.
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen# configure terminal Regen(config)# | Enter the configure terminal command to enter global configuration mode. | ||
| Regen(config)# ip rcmd remote-username username | Enter the ip rcmd remote-username global configuration command and specify a username for all copies. You can also change the default remote username. | ||
| Regen(config)# end Regen# | Type end to return to privileged EXEC mode. | ||
| Regen# copy system:running-config rcp:[[[//[username@]location]/directory]/filename | |||
| Regen(config)# copy nvram:startup-config rcp:[[[//[username@]location]/directory]/filename | Enter the copy nvram: startup-config rcp EXEC command to copy the running configuration to NVRAM start-up configuration. |
You can download Cisco IOS software images from a TFTP server, using the copy command through the regenerator's Ethernet interface or the OC-48 regeneration interface, beginning in user EXEC mode.
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen> copy tftp flash | In ROM Monitor mode, enter the copy tftp flash EXEC command to download a Cisco IOS software image from a remote server accessible from an Ethernet network interface on a Cisco 12000 series router | ||
| Regen> filename | The system prompts you to type the filename. |
You must be in ROM Monitor mode to download a Cisco IOS software image using the following methods. The following sections describe the commands to:
You can configure Cisco IOS software to automatically enter the ROM Monitor mode the next time the regenerator boots by setting virtual configuration register bits 3, 2, 1, and 0 to zero. To configure the regenerator to automatically enter the ROM Monitor mode, enter the following commands beginning in user EXEC mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| Router> configure terminal Router(config)# | To configure Cisco IOS software to automatically enter ROM Monitor mode, type the config t EXEC command. the prompt changes to privileged EXEC mode. | ||
| Router(config)# config-register 0x0 | Enter the config-register EXEC command and set the virtual configuration register bits to 0x0. | ||
| Router(config)# exit | Type exit to return to privileged EXEC mode. | ||
| Router# copy running-config start-config |
You can manually enter the ROM Monitor mode by following the configuration tasks in this section, beginning with the regenerator in user EXEC mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| Router> ^ rommon 1 > | When you power-on the regenerator, press the Break key during the first 60 seconds while the system is booting to force the regenerator to stop booting and enter the ROM Monitor mode. The ROM Monitor mode returns in user EXEC mode. |
You can download a Cisco IOS software image through the Ethernet port by using the tftpdnld command to download the Cisco IOS software image into Flash memory. Follow the tasks in this section to download a Cisco IOS software image, beginning in ROM Monitor mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| rommon 1 > tftpdnld flash <filename> (copies to flash) or rommon 2 > tftpdnld -r (copies to RAM) | In ROM Monitor mode, enter the tftpdnld command to download a Cisco IOS software image from a remote server accessible from the Ethernet network. where h---Displays the tftpdnld command help screen. r---Loads the Cisco IOS software image only to DRAM and launches the image without writing the image into Flash memory. | ||
| rommon 3 > IP_ADDRESS=172.15.19.11 rommon 4 > IP_SUBNET_MASK=255.255.255.0 rommon 5 > DEFAULT_GATEWAY=172.16.19.1 rommon 6 > TFTP_SERVER=172.15.20.10 rommon 7 > TFTP_FILE=/tftpboot/regen-ih-mz rommon 8 > tftpdnld
IP_ADDRESS=172.15.19.11 IP_SUBNET_MASK=255.255.255.0 DEFAULT_GATEWAY=172.16.19.1 TFTP_SERVER=172.15.20.10 TFTP_FILE=/tftpboot/
Invoke this command for disaster recovery only. WARNING: all existing data in all partitions on flash will be lost! Do you wish to continue? y/n: [n]: | After you specify the variables, you must reenter the tftpdnld command. | ||
| rommon 9 > y rommon 10 > | Enter y(es) to begin downloading the Cisco IOS software image. When the process is complete, the ROM Monitor mode prompt appears on your screen. |
Use the following ROM Monitor commands to exit the ROM Monitor mode, and enter IOS mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| rommon 10 > boot | Enter the boot or (b) command to boot the first image in Flash memory. | ||
| rommon 11 > boot flash:[name] | Enter the boot or (b) command to boot the Cisco IOS software from the Flash memory. | ||
| rommon 12 > boot filename tftpserver
For example: rommon 7 > boot regenerator 172.15.19.11 | Enter the boot or (b) filename tftpserver command to boot from the specified file through the network from the specified TFTP server. For this command to work, there must be a Cisco IOS software image in Flash such that it can be used as a boot helper. |
This completes configuration tasks that describe downloading files.
To help identify and isolate the problem source, follow the steps in this section to:
To provide information about system processes, the Cisco IOS software includes an extensive list of EXEC commands that begin with the word show, which, when executed, display detailed tables of system information. Following is a list of some of the common show commands for the Cisco Optical Regenerator.
Regen# show interface SDCC0 interface SDCC0 bandwidth 192 ip address 171.71.100.67 255.255.255.0 ip directed-broadcast keepalive crc 32 ! Regen#
Regen# show ip interface brief Interface IP-Address OK? Method Status Protocol Ethernet0 10.1.0.2 YES NVRAM up up SDCC0 11.1.0.2 YES NVRAM up up SDCC1 12.1.0.2 YES NVRAM up up Regen#
Regen# show controller regen 0 Regen0 is up Error Count: RxClockFail = 0 SLOS = 1 SLOF = 1 BIP(B1) = 0 Active Defects: LOS LOF Active Alarms: SLOS Alarm reporting enabled for: RxClockFail SLOS SLOF B1-TCA B1 TCA threshold: B1 = 10e-6 Framer 0, addr=0x68004000: general_cntrl=0x0, active_led=0x1 ,gpio_port_mode=0x0, gpio_port_data=0x0, gpio_port_cntrl=0xF ,mask_3=0x0, mask_2=0xFF, mask_1=0xFF ,diag=0x0 , rsp_cntrl_1=0x10, ttog_cntrl=0x0 ,ttog_ovrhd_src_1=0x8C , Link Status=0xE0, LED control=0x80,regen_cntrl=0xA0, Regen#
Table 3 explains the output from the show controller regen command.
| Output Field | Explanation |
|---|---|
Regen0 is up | Regenerator 0 interface is administratively up. |
Error Count | Error Count on regenerator 0 interface. |
RxClockFail | Receive clock failed error. |
SLOS | Loss of signal. There must be a clear, unobstructed path between the transmitters and receivers. |
SLOF | Loss of frame. Indicates a SONET or SDH framing error. |
BIP(B1) | Bit Interleaved Parity. Bit errors in the payload can then be detected and reported as maintenance information. |
Active Defects: | Indicates which types of errors have active defects. |
Active Alarms: | Indicates which types of alarms are active. |
Alarm reporting enabled for: | Indicates which type of alarm reports you have selected. |
B1 TCA threshold: | B1 BER threshold crossing alarm. Reports B1 bit error rate (BER) threshold crossing alarm errors |
Framer 0, addr=0x68004000: | Describes the framer setting and the contents of the packet overhead. |
If you manually configure the regenerator and decide to return to using the default configuration, you can erase the configuration file and start again. Follow these steps to erase the configuration file, beginning in privileged EXEC mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen> enable Regen# | Type enable to enter privileged EXEC mode. | ||
| Regen# write erase Regen# Erasing the nvram filesystem will remove all files! Continue? [confirm] [OK] Erase of nvram: complete | Enter the write erase command. | ||
| Regen# | Enter the reload EXEC command to load the default configuration file. |
 | Caution The write erase EXEC command sequence will erase the entire configuration in NVRAM. |
To display the regenerator's startup configuration, follow these steps, beginning in user EXEC mode:
| Step | Command | Task | ||
|---|---|---|---|---|
| Regen> enable | Because the regenerator always starts in user EXEC mode, type enable to enter privileged EXEC mode. | ||
| Regen# show startup-config | Enter the show startup-config EXEC command. |
Before you call technical support, be sure to have the following information ready:
To isolate the problem to a specific subsystem, you must compare what the system is doing to what it should be doing. When problem solving, consider the following subsystems of the regenerator:
Instructions for troubleshooting these systems are covered in the following sections.
After you have installed and configured the Cisco Optical Regenerator, you can use the following commands in user EXEC mode to verify network connectivity:
If there is a problem with network connectivity, refer to the "Interpret Alarms and Alerts."
All status and alarm reports of the Cisco Optical Regenerator's receiving controller are from the receiving (Rx) fiber optic connector side; whereas, commands operating on the transmitting controller affect the transmitting (Tx) fiber-optic connector side. All of the error messages listed in this section are captured in the system log (Syslog) file as part of the console output. Alarm notifications are automatically sent to the network management system.
Error Message
SONET-4-ALARM: Regen 0: Rx Clock FailExplanation Framer does not see activity on the Rx clock extracted from the received signal.
Recommended Action Hardware failure. Replace the Cisco Optical Regenerator.
Error Message
SONET-4-ALARM: Regen 0: SLOSExplanation Framer does not detect a signal on receive fiber (all-ones/zeros).
Recommended Action Clean the fiber, check the power levels of the optical line and, if out of specified range, check the upstream equipment or fiber cable.
Error Message
SONET-4-ALARM: Regen 0: SLOFExplanation Framer can not lock onto incoming signal frame.
Recommended Action Clean the fiber, check the power levels of the optical line and, if out of specified range, check the upstream equipment or fiber cable.
Error Message
SONET-4-ALERT: Regen 0: B1 BER exceeds thresholdExplanation The B1 parity error count is higher than the provisioned threshold.
Recommended Action Clean the fiber, check the power levels of the optical line and, if out of specified range, check the upstream equipment or fiber cable.
Error Message
REGEN_ENV-2- WARNING: Hot sensor temperature at xx deg CExplanation The temperature sensor on the card indicates a temperature reading that is higher than 32-104ºF (0-40ºC).
Recommended Action Verify the environmental conditions of the regenerator and lower the temperature of the regenerator's surroundings.
Error Message REGEN_ENV-4-ALARM: xV PUP fail
Explanation Monitored power unit (x Volt) failed.
Recommended Action Hardware failure. Replace the Cisco Optical Regenerator.
This section documents the new or modified commands that are used to configure the Cisco Optical Regenerator. All other commands used with this feature are documented in the Cisco IOS Release 12.0 Command Summary.
Use the regen framing command in interface configuration mode to select SDH or SONET. Use the no form of this command to disable the regenerator's framing.
regen framing [sdh | sonet]
sdh | Select SDH framing and s1s0=2. |
sonet | Select SONET framing and s1s0=0 (default). |
sonet framing
Configuration controller
| Release | Modification |
|---|---|
12.0(6)S | This command was first introduced. |
To provision the framer format, use the regen framing configuration controller command.
Regen(config-controller)# regen framing sdh Regen(config-controller)#
| Command | Description |
None. |
|
To specify the Section Trace byte value, use the regen overhead configuration controller command. Use the no form of this command to disable the Section Trace byte value.
regen overhead j0 [0x01 | 0xCC]
no regen overhead j0 [0x01 | 0xCC]
0x01 | Specifies the byte value for compatibility |
0xCC | Specifies the default byte value. |
0xCC
Configuration controller
| Release | Modification |
|---|---|
12.0(6)S | This command was first introduced. |
Use the regen overhead configuration controller command to monitor and operate the SONET section overhead on incoming data. j0 equals the byte value in the range of 0x00 - 0xFF (0 - 255). j0 is the section trace byte, and value is 0x1 for interoperability with some SDH devices in Japan. The default value is 0xCC.
The following example shows how to assign the range of byte values for regen overhead that will monitor and operate the SONET section overhead on incoming data.
Regen(config-controller)# regen overhead j0 255 Regen(config-controller)#
| Command | Description |
None. |
|
To enable regenerator alarm reports, use the regen report command in regen configuration controller command. Use the no form of this command to disable the regen report alarm.
regen report {b1-tca | j0-mismatch | rxclk-fail | slof | slos}
b1-tca | B1 BER threshold crossing alert (TCA) |
j0-mismatch | Section Trace Mismatch |
rxclk-fail | Receive Clock failed |
slof | Section Loss of Frame |
slos | Section Loss of Signal |
No default behavior or values.
Controller configuration
| Release | Modification |
|---|---|
12.0(6)S | This command was first introduced. |
Use the regen report controller configuration command to specify the type of report you want to enable or disable. You can specify and enable multiple regen report commands.
The following example shows how to enable the regenerator controller to provide a section loss of frame report:
Regen(config-controller)# regen report slof Regen(config-controller)#
| Command | Description |
None. |
|
To specify the values of the regen B1-threshold for B1-TCA, use the regen threshold configuration controller command. Use the no form of this command to disable the regen threshold alarm.
regen threshold b1-tca 9 value
value | Value is an exponent value in the range of 3 - 9 to represent a bit error rate in the range of 10^-3 to 10^-9. |
No default behavior or values.
Configuration controller
| Release | Modification |
|---|---|
12.0(6)S | This command was first introduced. |
Use the regen threshold configuration controller command to determine the values of the regenerator's B1-threshold for (B1 TCA). b1-tca is an alarm with a value of 9. If the error rate exceeds 10, the bit error rate will be detected.
The following example shows how to enable a regen threshold b1-tca alarm with a value of 9:
Regen(config-controller)# regen threshold b1-tca 9 Regen(config-controller)#
| Command | Description |
None. |
|
To display information about the Regen 0 and Regen 1 controllers, use the show controller regen EXEC command.
show controller regen [0 | 1]
number | Identifies the Regen controller, either 0 or 1. |
No default behavior or values.
EXEC
| Release | Modification |
|---|---|
12.0(6)S | This command was first introduced. |
Be sure to specify the number of the regen controller when using the show controller regen command.
The following output from the show controller regen 0 EXEC command provides information about regenerator alarms and events:
Regen# show controller regen 0 Regen0 is up Error Count: RxClockFail = 0 SLOS = 1 SLOF = 1 BIP(B1) = 0 Active Defects: LOS LOF Active Alarms: SLOS Alarm reporting enabled for: RxClockFail SLOS SLOF B1-TCA B1 TCA threshold: B1 = 10e-6 Framer 0, addr=0x68004000: general_cntrl=0x0, active_led=0x1,gpio_port_mode=0x0, gpio_port_data=0x0, gpio_port_cntrl=0xF ,mask_3=0x0, mask_2=0xFF, mask_1=0xFF ,diag=0x0, rsp_cntrl_1=0x10, ttog_cntrl=0x0,ttog_ovrhd_src_1=0x8C , Link Status=0xE0, LED control=0x80,regen_cntrl=0xA0, Regen#
| Command | Description |
|---|---|
None |
|
To display information about a specific regenerator interface, use the show interface EXEC command.
show interfaces [ethernet | SDCC0 | SDCC1]
ethernet | Selects the Ethernet port interface statistics for display. |
SDCC0 | Selects the SDCC0 interface statistics for display. |
SDCC1 | Selects the SDCC1 interface statistics for display. |
No default behavior or values.
EXEC
| Release | Modification |
|---|---|
10.0 | This command was first introduced |
12.0(6)S | This command was modified. |
Applies to any interface that connects two systems or devices.
The following output provides information about the SDCC0 interface from the show interface EXEC command:
Regen# show interface SDCC0 interface SDCC0 bandwidth 192 ip address 171.71.100.67 255.255.255.0 ip directed-broadcast keepalive crc 32 !
| Command | Description |
|---|---|
show interface ip brief | Displays the IP addresses of all the network interfaces. |
To display the IP addresses of all the network interfaces on the regenerator, use the show interface ip brief EXEC command.
show interface ip brief
None |
|
No default behavior or values.
EXEC
| Release | Modification |
|---|---|
10.0 | This command was first introduced. |
12.0(6)S | This command was modified. |
The show interface ip brief EXEC command lists all of the interface IP addresses and shows the configuration method as NVRAM or manual.
The following example displays the output from the show interface ip brief EXEC command that lists all of default IP addresses assigned to the regenerator's interfaces during AutoInstall. Note that the Method field indicates that the IR addresses are from NVRAM configuration.
Regen# show ip interface brief Interface IP-Address OK? Method Status Protocol Ethernet0 10.1.0.2 YES NVRAM up up SDCC0 11.1.0.2 YES NVRAM up up SDCC1 12.1.0.2 YES NVRAM up up Regen#
The following example displays the output from the show interface ip brief EXEC command that lists all of the IP addresses for each regenerator interface. Note that the Method field indicates that the interfaces were configured manually.
Regen# show ip interface brief Interface IP-Address OK? Method Status Protocol Ethernet0 20.15.5.9 YES manual up up SDCC0 22.1.0.1 YES manual up up SDCC1 33.1.0.1 YES manual up up Regen#
| Command | Description |
|---|---|
show interfaces | Displays information about regenerator interfaces. |
The following are common terms and acronyms for your reference:
Posted: Tue May 9 18:54:30 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.