|
|
This chapter offers troubleshooting steps to help you solve high-level problems while operating CTM, CTM GateWay, or CTM ConnectWay products.
Follow the troubleshooting procedures described in this chapter before contacting Cisco customer support.
For a list of error messages, see "Error Messages."
 |
Note For the purposes of this guide, we assume that the CTM server is installed under the default directory /opt/CiscoTransportManagerServer and the CTM client is installed under the default directory /opt/CiscoTransportManagerClient. If you specified a directory different from the default installation directory, replace the default paths with the installed path on your setup. |
This section describes troubleshooting procedures for CTM server-related problems. Complete the following steps in the order listed until you resolve the problem.
|
Note You must log in as root on the Sun Solaris machine where the CTM server has been installed to perform any operations on the Sun Solaris machine. |
If you suspect the CTM server is not running, complete the following steps.
Step 2 Enter the following command:
/bin/ps -aef | grep CTMServer
If you see a line containing /opt/CiscoTransportManagerServer/bin/CTMServer, it indicates that the CTM server is running.
If there is no line containing /opt/CiscoTransportManagerServer/bin/CTMServer, the CTM server is not running. Proceed to Step 3.
Step 3 Start the CTM server by using the script ctm-start located in the directory /opt/CiscoTransportManagerServer/bin.
a. Log in as the root user.
b. Change directories to /opt/CiscoTransportManagerServer/bin and enter the following command:
./ctm-start
If the connection state of an NE is listed as Unavailable in the Domain Explorer window, there is a connectivity or configuration problem. Wait 5 to 10 minutes after adding the NE to the CTM domain; then, complete the following steps.
Step 2 From the CTM server, enter the following command to verify connectivity between the CTM server and the NE:
ping IP address
Step 3 If the ping fails, there is a physical or configuration problem in the DCN.
a. If connectivity existed earlier:
b. If connectivity was never established:
section. If the entry is missing, the CTM server configuration file is corrupt. Reinstall the CTM server.
Step 2 Verify that the first entry in the file /var/opt/oracle/oratab looks similar to CTMS:/database/ora01/app/oracle/product/8.0.4:Y. If this entry is missing, the Oracle database might not be installed. The Oracle database is a prerequisite for installing the CTM server.
sqlplus ctmanager/visionway
If you log in successfully, an SQL> prompt appears, which indicates that the Oracle database has been installed and the database server is up and running. If you cannot log in, either the Oracle database has not been installed or the database server is not running.
Step 2 To start the Oracle database, log in to the Sun Solaris machine as the Oracle software owner user.
Step 3 Start the Oracle database by entering the following command at the shell prompt:
dbstart
Step 4 Start the Oracle listener by entering the following command at the shell prompt:
lsnrctl start
If you still have problems starting the Oracle database or the Oracle listener, refer to Oracle's documentation or contact Oracle support.
env
If you have sh as the shell, enter the following command:
set
Step 2 Find the value for the variable TFTPDIR. If the TFTPDIR variable does not exist, verify that TFTP service on Sun Solaris is enabled by looking up the inetd configuration file /etc/inetd.conf.
Step 3 Set the value of TFTPDIR to the location of the TFTP directory that is specified in /etc/inetd.conf.
Step 4 Restart the CTM server.
The CTM server requires exclusive access to the SNMP trap port to get SNMP traps from the NE.
netstat -a | grep 162
If you see the following line, it indicates that the SNMP trap port is being used by another application:
*.162 Idle
Step 2 Stop the other application.
Step 2 Change directories to /opt/CiscoTransportManagerServer/bin and enter the following command to start the CTM server:
./ctm-start
You might receive the following response:
Failed to start /opt/CiscoTransportManagerServer/bin/CTMServer as another copy is running or SNMP TRAP port 162 is taken by another process.
This message indicates that either another copy of the CTM server is running or there is another program on this computer running an SNMP application. If the CTM GateWay/TL1 OSS-MUX port number 26713 is in conflict, the message "bind: Address already in use" appears. Otherwise, check for a conflict with the JMOCO port number 27613.
Step 2 If the service NE Service 1 does not exist or if PM is enabled and the PM Service does not exist, check the corresponding error log files in /opt/CiscoTransportManagerServer/log.
If you see an Auth.ConnectionFailure error, the database listener might be configured incorrectly. Check the Oracle configuration to make sure the Oracle listener is listening on all IP interfaces on the Solaris server.
Step 3 View the files NEService1.log and PMService.log in the directory /tmp and the files NEService-1Error.log and PMServiceError.log in the directory /opt/CiscoTransportManagerServer/log. For Out of Memory errors, increase the swap space on the Solaris server.
If the CTM client cannot connect to the CTM server, verify that the database is available.
Step 2 Connect to the database by entering the following command:
sqlplus ctmanager/visionway
Step 3 If you get the error message "maximum processes exceeded," the maximum number of database connections have been reached. Close several clients or ask your database administrator to increase the maximum number of processes for the database.
Step 2 Choose Administration > Server Control Panel to see if PM is disabled for the selected interface or class of interfaces.
Step 3 Choose Administration > Audit Log to see if PM was ignored for the selected NE.
Step 4 Choose Administration > Server Control Panel > Performance Monitoring Service to see if the store nonzero values only option is enabled.
If you cannot change the NE operational state from preprovisioned or out of service to in service or under maintenance, the application has used all available NE licenses. Complete the following steps to add new licenses:
Step 2 After you receive your new licenses, log in to the CTM client with administrative privileges and choose Administration > Server Control Panel.
Step 3 Choose Administration > Add License.
Step 4 Enter the exact license string with hyphens and no spaces by using the format xxxx-xxxx-xxxx-xxxx; then, click OK.
 |
Tips Do not confuse the uppercase letter O with the number 0. |
Step 5 Verify that the additional license counts are reflected in the Server Control Panel > CTM Service property sheet > License Configuration tab.
Step 6 Return to the Domain Explorer or the Topology Explorer, select the NE, and change the NE operational state to in service.
|
Note You cannot add a new license if the license already exists in the file /opt/CiscoTransportManagerServer/license.dat. Increasing the license count requires a new license. |
If CTM cannot discover a Cisco ONS 15454 NE, complete the following steps:
Step 2 Verify that the NE IP address and default route are correctly configured.
Step 3 To verify that the NE is running the correct version of system software, open a CTC session to the NE and check the NE software version.
Step 4 Verify that the Cisco ONS 15454 that acts as the GNE (through which this node is discovered) is added to CTM and is available.
Step 5 Open CTC from the GNE and see if CTC can discover the NE.
If CTM cannot reach a Cisco ONS 15454 NE, complete the following steps:
Step 2 Verify that the NE IP address and default route are correctly configured.
Wait for 5 poll cycles while CTM reestablishes connectivity with the NE.
Step 3 To test IP connectivity to the NE from the CTM server, enter the following command from the Solaris machine running CTM:
ping NE IP address
Step 4 To verify that the NE is running the version of system software supported by CTM, open a CTC session to the NE and check the NE software version.
If CTM fails to display some circuits or if the information displayed by CTC and CTM differs, complete the following steps:
Step 2 Verify that the Circuit Table is opened from either the source or destination NE of the circuit that you want to see.
Step 3 Verify that the NEs that are part of the circuit (source, destination, or drop) are available in CTM.
Step 4 Open another CTC session and compare the circuit information in the newly opened CTC session with the circuit information displayed by CTM.
If you add an in service NE to the Domain Explorer, but the model type appears as "unknown," the software version of the NE might not be prepopulated in the database. In other words, CTM cannot match the NE with a recognizable version.
To determine the correct NE version and add it to the database, complete the following steps:
Step 2 Before adding a Cisco ONS 15454 to the CTM domain, verify that the NE software version string has been added to the CTM database. If you added an NE before adding the version string, complete the following steps:
a. Obtain the NE software version from CTC (similar to 02.10-001A-00.56).
b. Log in to the CTM UNIX server as root and enter the following commands:
su - oracle sqlplus ctmanager/visionway insert into pl_version_table values (3, '02.10-001A-00.56', 3, 'NN'); commit; quit
c. Reboot the NE.
If you cannot copy a CTC binary to the CTM server, the directory CTM install directory/cms/ might be missing or write-protected. Create a cms directory with write-access.
The CTM client may not be able to connect to the CTM server for various reasons. Complete the following steps in the order listed until you resolve the problem.
ifconfig -a
The command output looks similar to the following example:
hme0:flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST>mtu 1500 inet 192.168.120.93 netmask ffffff00 broadcast 192.168.120.255
The IP address is the address following the inet field.
Step 2 To verify that the physical connection between the CTM client and the CTM server has no problems, enter the following command from the CTM client:
ping IP address
where the IP address belongs to the Sun Solaris machine that runs the CTM server.
Step 3 If the ping command is not successful, fix the physical connectivity; then, log in to the CTM client.
Username: Administrator
Password: CTM-admin
Step 2 If you can log in as the administrator but could not log in as the operator earlier, verify that the operator exists and is not disabled. Choose Administration > CTM Users to view a table of all configured CTM users.
Step 3 (Optional) If you cannot see the operator in the CTM Users table, the user is not configured. Configure the operator; then, log in as the operator.
Step 4 (Optional) If you can see the operator, select the row corresponding to operator and click the Modify User toolbar button to bring up the Modify CTM User Properties wizard. Verify that the login state is enabled. If the login state is disabled, enable it and log in as the operator. The user might have been disabled due to the one of the following reasons:
Step 5 (Optional) If the password is not correct, set a new password for the user and log in again.
If you get a "Cannot authenticate user" error message when logging in to the CTM client, complete the following steps:
Step 2 You might have exceeded the maximum number of database connections. Contact your CTM administrator to check your CTM client license count.
If you add a new NE to the CTM domain and mark it in service, but the operational state remains unknown, complete the following steps:
Step 2 The CTM server might not be able to establish connectivity to the NE's GNE. Verify that the GNE for this NE is marked in service, and that the GNE is correctly populated in the CTM domain.
Step 3 Verify that the GNE is DCC connected to the CTM server by adding routes to the NE's GNE from the CTM server.
Step 4 In the Domain Explorer tree, select the NE and choose Fault > Test NE Connectivity.
Step 5 The CTM server might be configured to attempt communication with new NEs after a certain delay. To change the health poll frequency:
a. In the Domain Explorer window, choose Administration > Server Control Panel.
b. Select the CTM Service property sheet and view the Health Poll Frequency (secs) field. The default is 30 seconds. If the value is too large, there might be a delay in communicating with NEs. Under normal conditions, the CTM server attempts communication with new NEs at a maximum of twice the number of seconds specified in the Health Poll Frequency field.
Step 6 The CTM server might not recognize the NE's software version. In the Domain Explorer tree, select the NE and choose Fault > Test NE Connectivity. If the NE is available, contact Cisco Systems and verify that the version of the software on the NE is compatible with the CTM server being used. Use the Supported NE Table to provide the new NE software version that the CTM server will recognize.
If you cannot delete an NE, complete the following steps:
Step 2 Verify that the selected NE is not the last instance of the NE in the domain. You cannot delete the last instance of an NE from the database. You can delete only multiple instances of the NE. Choose Edit > Find and Edit > Find Next to see if other instances of the selected NE exist.
If you cannot start CTC to display the Cisco ONS 15454 shelf or provisioning view, complete the following steps:
a. Choose Administration > CTM Users.
b. In the CTM Users Table, choose Edit > Modify User.
c. In the Modify CTM User Properties wizard, change the CTC username and password to match those configured on the device.
Step 2 If the CTC progress screen idles for a long time before the login dialog appears, there might be network connectivity problems to the device.
a. From an MS-DOS command window or a Solaris terminal, ping the device.
b. If there is no response, set up routes so the device is available; then, restart CTC. If CTC does not start, your machine might have resource constraints.
c. Close some open applications and try again.
d. Close some instances of CTC that are managing another group of Cisco ONS 15454 devices and try again.
Step 3 If the GNE for the selected Cisco ONS 15454 was not found, there might be a mismatch between the GNE specified for the device and the available GNEs in the GNE Table. This means the data in the database is corrupt. Contact the Cisco TAC for further assistance.
If you cannot delete a GNE from the GNE Table, complete the following steps:
Step 2 Verify that the target GNE is not used by any NEs.
a. Select the entire domain in the Domain Explorer or the Topology Explorer; then, choose File > Domain Inventory Table.
b. Check the GNE ID column to see if the target GNE is assigned to any NEs. If so, assign a different GNE to the NEs; then, remove the target GNE.
If you cannot delete a subnetwork from the Topology Explorer, complete the following steps:
Step 2 Verify that the target subnetwork does not contain NEs. Move all NEs to another subnetwork before deleting the empty target subnetwork.
Step 3 Verify that the target subnetwork is not the last subnetwork for a GNE. You cannot delete the last instance of a subnetwork associated with a GNE.
Path_xterm=/usr/openwin/bin/
Path_xterm=path where your xterm program resides/
Step 2 If the connection state of the NE is listed as Unavailable in the CTM Domain Explorer window, see the "Checking Connectivity Between the CTM Server and the NE" section.
If the connection state of the NE is listed as Unavailable in the CTM Domain Explorer window, see the "Checking Connectivity Between the CTM Server and the NE" section.
You can use the CTM client to schedule three administrative tasks:
CTM maintains an error log and audit log to track potential problems. To view the error log or audit log:
Step 2 In the Domain Explorer window, choose Administration > Server Control Panel.
Step 3 To access the error log, choose Administration > Error Log in the Server Control Panel window.
To access the audit log, choose Administration > Audit Log in the Server Control Panel window.
Step 4 Look for errors related to software download, memory backup, or memory restore.
Common problems are described in the following sections.
Start the CTM server with the environment variable TFTPDIR set to the correct directory in which files can be transferred between the CTM server and the NE. Verify that the TFTPDIR variable is set correctly:
env
If you have sh as the shell, enter the following command:
set
Step 2 Find the value for the variable TFTPDIR. If the TFTPDIR variable does not exist, verify that TFTP service on Sun Solaris is enabled by looking up the inetd configuration file /etc/inetd.conf.
Step 3 Set the value of TFTPDIR to the location of the TFTP directory that is specified in /etc/inetd.conf.
Step 4 Restart the CTM server.
Bottlenecks in the DCN affect bandwidth-intensive operations, such as software download. Tune timeout and retry values to match DCN performance:
Step 2 Choose Configuration > NE Remote Console to access the cut-through session.
Step 3 To tune TFTP, log in to the NE and enter the following commands:
Because of DCN connectivity problems, the CTM server may not be able to retrieve the NE configuration file. Follow the steps in the "Performing Administrative Tasks" section.
If data is missing from any of the PM or FM tables, or if the data shows an incorrect time stamp, the problem is most likely an SNMP timeout on the CTM server. Complete the following steps in the order listed until you resolve the problem.
Step 2 Check the clock setting on the NE.
a. Telnet to the NE and log in.
b. Enter the following command:
show clock
c. Verify that the time shown is the correct GMT/UTC time and not the local time.
|
Tips If the time is set incorrectly, refer to the Cisco Optical Networking System 1530x Software Configuration Guide to change the clock setting. |
Step 3 Increase the SNMP timeout on the CTM server.
a. Choose Administration > Server Control Panel.
b. Click the NE icon to see the NE Poller Service property sheet.
c. In the SNMP Timeout (secs) field, increase the SNMP timeout value. Table 5-1 lists the recommended settings for SNMP timeout and retries.
| Line Speed | Timeout | No. of Retries |
|---|---|---|
9600 baud | 15 seconds | 2 |
19.2 to 56 kbps | 10 seconds | 2 |
56 kbps | 3 seconds | 3 |
|
Note The default setting for SNMP timeout and retries is 10 seconds, 2 retries. |
d. Click the Save button. The change takes effect immediately.
Step 4 Increase the SNMP queue size on the NE.
a. In the Domain Explorer tree, select the NE and choose Configuration > NE Remote Console to access the cut-through session.
b. Log in to the NE and enter the following command in configuration mode to tune the SNMP server:
snmp-server queue-length 100
If the NE displays incorrect CM data, complete the following steps:
Step 2 In the Domain Explorer window, choose Administration > Service Monitor Table and check if the NE Service is running. If it is not running, start the NE Service.
Step 3 Test NE connectivity.
a. In the Domain Explorer tree, select the desired NE and choose Fault > Test NE Connectivity. You should see a message saying NE name is available.
b. If the NE is unavailable, establish connectivity to the NE before retrieving CM data.
If you cannot view an image file while changing the Domain Map background or while changing a node icon, complete the following steps:
Step 2 Check the size of the image file. The image file might be larger than 100 KB, which is too big to load. If the file is too big, use a smaller image file.
If you plan to run the CTM client on a Sun Ultra 5 workstation, you must change the color map from 8 bit to 24 bit.
$ /usr/sbin/m64config -prconf
Command output looks similar to the following example:
--- Hardware Configuration for /dev/fbs/m640 --- ASIC: version 0x7c004750 DAC: version 0x0 PROM: version 104 Card possible resolutions: 720x400x88, 640x480x60, 640x480x72, 640x480x75, 800x600x56, 800x600x60, 800x600x72, 800x600x75, 1024x768x87, 1024x768x60, 1024x768x70, 1024x768x75, 1280x1024x75, 1280x1024x60, 1152x900x66, 1152x900x76, 1280x1024x67, 1280x800x76, 1280x1024x85 1280x1024x76, 1152x864x75, 1024x768x77, 1024x800x84, vga, svga, 1152, 1280, 800x600, 1024x768, 1280x1024, 1152x900 Monitor possible resolutions: 720x400x70, 720x400x88, 640x480x60, 640x480x67, 640x480x72, 640x480x75, 800x600x56, 800x600x60, 800x600x72, 800x600x75, 832x624x75, 1024x768x60, 1024x768x70, 1024x768x75, 1280x1024x75, 1152x870x75, 1152x900x66, 1152x900x76, 1280x1024x67, 1280x1024x76, vga, svga, 1152, 1280, 800x600, 1024x768, 1280x1024, 1152x900 Possible depths: 8, 24 Current resolution setting: 1280x1024x76 Current depth: 8
Step 2 Log in as the root user and enter the following commands:
$su
Password: password
# /usr/sbin/m64config -depth 24 -res 1152x900x76
Step 3 Reboot your machine for the new color settings to take effect.
|
Note The resolution in 24-bit depth is a little less than is possible with 8-bit depth (1152 x 900 x 76 versus 1280 x 1024 x 76), but the difference is hardly noticeable. |
If the OSS cannot connect to CTM GateWay/TL1, or if the OSS does not receive a response, complete the following steps in the order listed until you resolve the problem.
Step 2 Verify that the address bindings between the OSS and the Sun Solaris machine running the CTM GateWay/TL1 service are correct.
Step 3 Using the ping command, verify connectivity between the OSS and the Sun Solaris machine running the CTM GateWay/TL1 service.
Step 4 Verify that the TCP/IP socket connection is still up for the OSS-to-CTM GateWay/TL1 port.
Step 5 As the administrator, access the CTM Server Control Panel window and confirm that the CTM GateWay/TL1 service is running.
When CTM GateWay/TL1 receives a command, it immediately starts an independent task to send an In Progress (IP) response every IP-frequency seconds. The task stops when the output for the command is sent to the OSS. CTM GateWay/TL1 uses a database to retrieve information to transmit in a timely fashion; therefore, in most cases, you will not see a single IP message. If the database is large or many requests are being processed, you may see frequent IP messages. Alternately, CTM GateWay/TL1 may represent 200 NEs, each with 4 sessions to an OSS. It is possible that more than 800 requests are queued for processing with ongoing automatic messages. If so, the default 2-second IP frequency may be too short.
Step 2 Choose Administration > Server Control Panel.
Step 3 Click the GW icon.
Step 4 In the CTM GateWay/TL1 Service property sheet, enter the number of seconds between IP messages in the Progress Freq (secs) field.
Step 5 Click the Save button. The change takes effect immediately.
If an OSS cannot recognize the TL1 messages sent from CTM GateWay/TL1, it may not recognize positional-based TL1 messages (the default setting) and may only support name-value pair-based TL1 messages.
Step 2 Choose Administration > Server Control Panel.
Step 3 Click the GW icon to see the GateWay/TL1 Service property sheet.
Step 4 In the Response Parameters field, choose either Positional or Name-value.
Step 5 Click the Save button. The change takes effect immediately.
See the following example of a positional-based TL1 alarm message:
ONS1 99-06-01 15:30:45 * 999 REPT ALM ALL "T1-1:MN,GP, NSA,06-01,15-30-40,NEND,RCV,,,:/* DS1 Signal Degrade */" "T1-3:MN,GP,NSA,06-01,15-30-40,NEND,RCV,,,:/* DS1 Signal Degrade */" ;
See the following example of a name-value pair-based TL1 alarm message:
ONS1 99-06-01 15:30:45 * 999 REPT ALM ALL "T1-1:NFCNCDE=MN,CONDTYPE=GP,SRVEFF=NSA,OCRDAT=06-01, OCRTM=15-30-40,LOCN=NEND,DIRN=RCV,,,:/* DS1 Signal Degrade */" "T1-3:NFCNCDE=MN,CONDTYPE=GP,SRVEFF=NSA,OCRDAT=06-01, OCRTM=15-30-40,LOCN=NEND,DIRN=RCV,,,:/* DS1 Signal Degrade */" ;
Alarms may be allowed or inhibited according to the GR-833 specification. Parameters that affect this command are the access identifier (AID), severity (NFCNCDE), and service-affecting ability (SRVEFF). It may be extremely difficult for an OSS to handle these parameters on a case-by-case basis. Typically an OSS wants to see all alarms or only a few. Therefore, we added a parameter that allows the user to specify that alarms are assumed to be off or on.
If the OSS is receiving too many automessages from NEs or wants to receive only a specific set of automessages, complete the following steps:
Step 2 Choose Administration > Server Control Panel.
Step 3 Click the GW icon to see the GateWay/TL1 Service property sheet.
Step 4 In the Alarm Logic field, choose either Assume-allowed or Assume-inhibited.
Step 5 Click the Save button. The change takes effect immediately.
SR-1665 states that a session must time out if no commands are received in a 30-minute period. Accordingly, the CTM GateWay/TL1 default session timeout is 30 minutes. Programs other than OSSs may use TL1 for alarm management. If these programs send messages inconsistently to the CTM GateWay/TL1 interface, the CTM GateWay/TL1 session shuts down.
Step 2 To prevent sessions from timing out, either remove the line session-times-out = yes or enter session-times-out = no.
Step 3 To restore the timeout function, reenter session-times-out = yes in the file.
Step 4 (Optional) If you are viewing the Server Control Panel while you edit the configuration file, the Server Control Panel will not reflect the changes. Close, then reopen the Server Control Panel to see the changes.
If CTM ConnectWay/TL1 does not start, complete the following steps in the order listed until you resolve the problem.
/opt/CiscoConnectWayServer/cfg/CTMServer.cfg /opt/CiscoConnectWayServer/connectway.cfg
Step 2 Verify that the configuration files have the correct configuration parameters and are not corrupted.
For more information, see "Using Cisco Transport Manager ConnectWay."
/bin/ps -aef | grep Connectway
If you see a line containing /opt/CiscoConnectWayServer/bin/Connectway, it indicates that the CTM ConnectWay/TL1 server is running.
If there is no line containing /opt/CiscoConnectWayServer/bin/Connectway, the CTM ConnectWay/TL1 server is not running.
Step 2 Start the CTM ConnectWay/TL1 server by using the script cw-start located in the directory /opt/CiscoConnectWayServer/bin.
ifconfig -a
If you see information that looks similar to the following example, it indicates that the CTM ConnectWay driver is running:
connectwaydrv0 : flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 256 inet 10.5.20.100 netmask ffffff00 broadcast 10.5.20.255
Step 2 If the CTM ConnectWay driver is not running, verify that the driver connectwaydrv is present in the directory /usr/kernel/drv. Also, verify that the CTM ConnectWay/TL1 process is running.
netstat -a | more
Step 2 Verify that each GNE that was configured in the file /opt/CiscoConnectWayServer/cfg/connectway.cfg has a TCP connection in the ESTABLISHED state.
Step 3 If any TCP connection is not in the ESTABLISHED state, check the GNE configuration in the file /opt/CiscoConnectWayServer/cfg/connectway.cfg. Also, check the configuration of the router that is used to connect to the GNE.
Check the NE configuration and verify that the section DCC and TTunnel interfaces are configured correctly.
Refer to the Cisco Optical Networking System 1530x Software Configuration Guide to configure the section DCC and TTunnel interfaces.
If you are using a router between the element management system (EMS) and the GNE, verify that the WAN (for example, X.25, TCP/IP, OSI) link between the router and the GNE is up and running.
show interface sdcca0
Step 2 See if the GNE target identifier (TID) can be resolved from the NE by entering the following command on the NE console:
tarp resolv GNE TID
Posted: Wed Jun 28 10:42:23 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.