Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

IBM CIP Protocols

Debugging CSNA Events

Downloads

Document ID: 17535


Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
CSNA Events
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document provides reasons for Logical Link Control, type 2 (LLC2) session failure between Cisco Systems Network Architecture (CSNA) and end stations. This document is very useful during troubleshooting session/link failures.

Note: To turn on debug CSNA events on the Routing Processor (RP) console, issue the debug channel event sna command.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.

Conventions

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

CSNA Events

This is the list of CSNA events:

  • Open service access point (SAP) failed/Duplicate detected

  • Connection attempted failed/No connection resources

  • Connection failed/Link lost

  • Connection failed/Received Device Manager (DM) in Asynchronous Balanced Mode (ABM)

  • Connection failed/Received Set Asynchronous Balanced Mode Extended (SABME) while in ABM

  • Connection failed/Frmr rxd - invalid cmd/rsp

  • Connection failed/Frmr rxd - unexpected I-frame

  • Connection failed/Frmr rxd - invalid Nr

  • Connection failed/Frmr rxd - I-field too long

  • Connection failed/Frmr txd - invalid cmd/rsp

  • Connection failed/Frmr txd - unexpected I-frame

  • Connection failed/Frmr txd - invalid Nr

  • Connection failed/Frmr txd - I-field too long

The CSNA events are displayed in this syntax:

CIP LLC ALERT Channelx/2 - event_desciption_text
CSNA Port(n) Path(nnnn) Device(nn)
LAN:type_name(lan_id) ADAPTER:nnnn.nnnn.nnnn LSAP:nn
RMAC:nnnn.nnnn.nnnn RSAP:nn

For example:

CIP LLC ALERT Channel4/2 - Connection failed/Frmr rxd - I-field too long
CSNA Port(0) Path(0100) Device(42)
LAN:Token(0) ADAPTER:4000.7000.0001 LSAP:04
RMAC:4000.3270.0001 RSAP:08

When CSNA events are generated by the Channel Interface Processor (CIP) and sent to the RP via interprocess communications (IPC), they are converted into NetView alerts, Simple Network Management Protocol (SNMP) traps, and Console messages.

  • NetView alerts require that the Netview Service Point is configured.

  • SNMP traps require that SNMP is configured with the IP address of the remote SNMP station that traps are sent to, and that traps are enabled for SNMP.

  • Console display requires issuing the debug channel event sna command.

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 IBM
Network Infrastructure: Enterprise Data Centers

Related Information

Updated: Jun 01, 2006Document ID: 17535