Guest

Cisco MGX 8800 Series Switches

MGX Network PNNI Connection Trace

Document ID: 26423



Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Problem
Solution
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document shows you how to trace the path of a Private Network-to-Network Interface (PNNI) connection in an MGX network.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on the MGX 8850 (PXM-45A/B/C) software release 3.0.00 and later.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Problem

The path of a connection in a PNNI network is unknown.

Solution

Use the command conntrace in order to trace the connection path.

Note: The command conntrace is not available in software releases earlier than 3.0.00.

Complete these steps:

  1. Issue the conntrace command on the connection.

    Note: Issue the command on the PXM. You can only issue the command on the master side of connections.

    Notice that the command does not have any output.

  2. Issue the dspconntracebuffer command to see the path of the connection.

    Here is an example:

    mgx1.7.PXM.a > conntrace 5:1.1:1 -vpi 1 -vci 100
    
    mgx1.7.PXM.a > dspconntracebuffer 5:1.1:1 1 100
    
    Last update time:Jul 9 2002 23:42:46 
    Result:SUCCESS     Reason:N/A
    
    Incoming Port:17111041   Physical PortId:5:1.1:1
    VPI   :1   VCI:100   CallRef:147019   
    Node Name:mgx1  NodeId:
    56:160:47.00918100000000016444456a.00016444456a.01 
    Outgoing Port:16914433   Physical PortId:2:1.1:1
     
    VPI   :1   VCI:47161   CallRef:72760   
    Node Name:mgx2  NodeId:
    56:160:47.009181000000000164444b71.000164444b71.01 
    Outgoing Port:16848897   Physical PortId:1:1.1:1
     
    VPI   :1   VCI:55482   CallRef:93315   
    Node Name:mgx3 NodeId:56:160:47.0091810000000004c113b985.0004c113b985.01 
    Outgoing Port:17045505   Physical PortId:4:1.1:1
     
    VPI   :1   VCI:47074   CallRef:36277   
    Node Name:MGX4 NodeId:56:160:47.009181000000000164444b35.000164444b35.01 
    Outgoing Port:16979969   VPI   :1   VCI:100   CallRef:142329   Physical
    PortId:3:1.1:1

    In this output, the Incoming Port is the master endpoint of the connection. The Outgoing Ports are the PNNI links over which the connection is routed. The last Outgoing Port in the output is the slave endpoint of the connection.

NetPro Discussion Forums - Featured Conversations

Networking Professionals Connection is a forum for networking professionals to share questions, suggestions, and information about networking solutions, products, and technologies. The featured links are some of the most recent conversations available in this technology.
NetPro Discussion Forums - Featured Conversations for WAN Switching
Network Infrastructure: WAN Routing and Switching

Related Information



Updated: Oct 04, 2005Document ID: 26423