cc/td/doc/product/rtrmgmt/tv/tv4
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Managing Ports

Managing Ports

This chapter provides information about using TrueView Catalyst 1600 Manager to configure Token Ring ports and FDDI ports on a Catalyst 1600.

Managing Token Ring ports

You can view and edit information about each Token Ring port, by right-clicking on the port and selecting a command from the pop-up menu that is displayed.

TrueView Catalyst 1600 Manager enables you to:

Configuring Token Ring Information

You can configure the node address, ring speed, and port type for a Token Ring port in the Token Ring Information dialog box.

The Token Ring Information dialog box displays the current and hard-wired addresses for each port on the Catalyst 1600. To assign a locally-administered port address, type a new address in the Current field. To restore the hard-wired address, click on the Reset button.

To configure Token Ring information:

Step 1 Double-click on a Catalyst 1600 icon, or double-click on an entry in the Catalyst 1600 Manager Table.

The Catalyst 1600 dialog box is displayed.


Step 2 Move the mouse pointer over a port.

The pointer changes to indicate the number of the port that is highlighted.


Step 3 Right-click on the port and click on the Token Ring command on the pop-up menu.

The Token Ring Information dialog box is displayed.



Table  4-1: Token Ring Information Dialog Box
Field Description
Ring number The number of the ring that is connected to the port.
Interface Whether the port is enabled.
Ring speed The speed of the attached ring (4- or 16Mbps).
Port type The port interface type that determines whether the port is a node or concentrator port, and whether the port is in classic or full duplex (FDX) mode. For more information about the port type, see "Configuring the Port Type".
Hard-wired The node address of the Catalyst 1600 port.
Current The current address of the port. A Locally Administered Address (LAA) must begin with the digit 4, 5, 6, or 7.
Neighbour The Nearest Active Upstream Neighbour (NAUN) of the port.
Adapter status The status of the Token Ring port.
Open status If the port is closed, the open status describes the reason the port closed. If the port is open, the open status describes the port interface mode.

The open status only applies to ports that have 'Adapter is open' or 'Adapter is closed' status. If the port is disabled, beaconing, unknown, or opening, the open status is always 'N/A'.

Understanding the Adapter Status

The adapter status describes the state of the Token Ring port.


Table  4-2: Adapter Status Messages
Message Description
Port is disabled The port interface is disabled.
Adapter has closed Either the adapter has been removed from the ring, or the duplex mode does not match the duplex mode of the device that is connected. For more information about the duplex mode, see "Configuring the Port Type".
Adapter is opening The adapter is opening onto the ring.
Adapter is open The Catalyst 1600 port is enabled. If the port is configured for node interface mode, it is only reported as normal if a device is inserted. If the port is configured for concentrator mode, it is reported as normal whether a device is inserted or not.
Ring is beaconing The ring to which the port is connected is beaconing. Check your network connections.
Unknown Catalyst 1600 Manager cannot determine the adapter status.

Understanding the Open Status

The open status describes the state of the Token Ring port. If the port is closed, the open status describes the reason the port closed. If the port is open, the open status describes the port interface mode.

The open status only applies to ports that have 'Adapter is open' or 'Adapter is closed' status. If the port is disabled, beaconing, unknown, or opening, the open status is always 'N/A'.


Table  4-3: Open Status Messages.
Message Description
N/A If the port is disabled, beaconing, unknown, or opening, the open status does not apply.

Port is closed:

Bad parameter on open This message should not occur during normal operation.
Lobe fault The port was removed from the ring because a problem exists between the Token Ring port and the device to which it is connected. Check the cable connections.
Signal loss The Catalyst 1600 failed to connect the port to the ring because the port is not receiving a valid Token Ring signal from the ring. Check that the cable is not disconnected or broken.
Insertion timeout The port timed out because it failed to receive a frame from the ring. To find the cause of the error, use a frame logging program or a ring management application.
Ring failure The port timed out because it failed to receive a frame from the ring after initiating a ring purge. To find the cause of the error, use a frame logging program or a ring management application.
Ring beaconing The ring to which the port is connected is beaconing. Check your network connections.
Duplicate MAC addresses The Catalyst 1600 failed to connect the port to the ring because there are two ports on the network with the same locally administered address (LAA). Check the node addresses of the port and nodes on the ring.
Request parameters failed The Catalyst 1600 failed to connect the port to the ring because there is no response from the Ring Parameter Server (RPS). To find the cause of the error, use a frame logging program or a ring management application.
MAC remove frame received A management program prevented a port from opening onto the ring.

Port is open:

Single station The Catalyst 1600 port is the only node on the ring. This message does not represent an error, unless you expect more nodes to be on the ring.
Auto node The port is in node interface mode. In node interface mode the port behaves like an adapter card, generating a phantom drive signal to insert into the connected device. The port determines whether to operate in classic or full-duplex mode by communicating with the connected device.
Auto concentrator The port is in concentrator interface mode. In concentrator interface mode the port behaves like a Lobe Attachment Module (LAM) and detects the phantom drive signal that is generated when the connected device attempts to insert. The port determines whether to operate in classic or full-duplex mode by communicating with the connected device.
Classic node The port is in classic mode and node interface mode.
Classic concentrator The port is in classic mode and concentrator interface mode.
Full duplex node The port is in full-duplex mode and node interface mode.
Full duplex concentrator The port is in full-duplex mode and concentrator interface mode.
Unknown Catalyst 1600 Manager cannot determine the open status.

Configuring the Port Type

The Catalyst 1600 supports full-duplex connections to other Catalyst 1600 devices. If you connect Catalyst 1600 devices using full duplex, the token-passing protocol can be omitted and the connection can operate as a full-duplex serial link running at 16Mbps in both directions at the same time, providing an effective aggregate bandwidth of 32Mbps.


Note The full-duplex capability is implemented according to draft specification IEEE 802.5r (draft 3). Future releases of Catalyst 1600 software will support full-duplex Dedicated Token Ring (DTR) connections to Token Ring adapters in servers and workstations.

The port type determines whether the port operates in classic or full-duplex mode, and whether the port operates in node or concentrator interface mode. In most conditions, configure the port type to be auto node or auto concentrator depending on the device that you connect to the port. A port in auto node or auto concentrator mode can determine whether to use full-duplex mode by communicating with the connected device.


Note To find out whether to use node or concentrator port interface mode for a Token Ring port, refer to the Catalyst 1600 Token Ring Switch User Guide.

TrueView Catalyst 1600 Manager also enables you to force the port type to be node or concentrator interface mode, and classic or full-duplex mode. You should only force the port type if, when the port is in auto node or auto concentrator mode, the port fails to resolve the port type through communicating with the connected device.

To configure the port type:

Step 1 Double-click on a Catalyst 1600 icon, or double-click on an entry in the Catalyst 1600 Manager Table.

The Catalyst 1600 dialog box is displayed.


Step 2 Move the mouse pointer over a port.

The pointer changes to indicate the number of the port that is highlighted.


Step 3 Right-click on the port and click on the Token Ring command on the pop-up menu.

The Token Ring Information dialog box is displayed.


Step 1 Select the port type and click on the OK button.

Managing FDDI Ports

You can view and edit information about each FDDI port, by clicking on the port and selecting a command from the pop-up menu that Catalyst 1600 Manager displays.

TrueView Catalyst 1600 Manager enables you to:

Enabling and Disabling the Interface

You can enable or disable the interface for a FDDI port.

To enable or disable the interface:

Step 1 Double-click on a Catalyst 1600 icon, or double-click on an entry in the Catalyst 1600 Manager Table.

The Catalyst 1600 dialog box is displayed.


Step 2 Move the mouse pointer over a FDDI port.

The pointer changes to indicate the number of the port that is highlighted.


Step 3 Right-click on the port and click on the FDDI Information command on the pop-up menu.

The FDDI Information dialog box is displayed. If the Interface check box contains a cross, the interface in enabled. If the Interface check box does not contain a cross, the interface is disabled.


Step 4 Click on the Interface check box to change the state of the port interface.

Step 5 Click on the OK button.

Configuring the Port Address

You can configure a Locally Administered Address (LAA) for a FDDI port, or reset the hard-wired address.

To change the address:

Step 1 Double-click on a Catalyst 1600 icon, or double-click on an entry in the Catalyst 1600 Manager Table.

The Catalyst 1600 dialog box is displayed.


Step 2 Move the mouse pointer over a FDDI port.

The pointer changes to indicate the number of the port that is highlighted.


Step 3 Right-click on the port and click on the FDDI command on the pop-up menu.

The FDDI Information dialog box is displayed.


Step 4 Enter text in the Current text box to set up an LAA, or click on the Reset button to reset the hard-wired address.

Step 5 Click on the OK button.

Setting the Token Rotation Timer (TRT)

On an FDDI network, a station can transmit different types of data. There are timers that determine how long a station can transmit each type of data. The Target Token Rotation Time (TTRT) is a time interval which is the same for all the stations on a network, within which each station expects to receive the token.

When the ring initializes, each station declares a TTRT value in a procedure known as 'bidding', and the lowest time is chosen. Each time a new station joins the network, the bidding procedure is repeated to determine whether the new station requests a lower TTRT than the negotiated time.

The Token Rotation Timer (TRT) measures the actual time it takes for the token to pass around the ring, by noting the time between successive appearances of the token. When a token passes a station, that station sets the TRT to the value of the negotiated TRT and then counts down the TRT as time passes. If the station does not receive the token by the time the count elapses, it increments the Late Counter (LC) and resets the value of the TTRT to the negotiated TRT. The station then starts counting down the TRT again. If the LC is greater than zero when the TRT expires, the token has been lost and the ring enters recovery mode.

The value of the LC is displayed in the FDDI Counters dialog box (see "Understanding FDDI Counters" for more information.)

To change the requested TRT:

Step 1 Double-click on a Catalyst 1600 icon, or double-click on an entry in the Catalyst 1600 Manager Table.

The Catalyst 1600 dialog box is displayed.


Step 2 Move the mouse pointer over a FDDI port.

The pointer changes to indicate the number of the port that is highlighted.


Step 3 Right-click on the port and click on the FDDI command on the pop-up menu.

The FDDI Information dialog box is displayed.


Step 4 Enter a value in the Requested check box to change the TRT.

Step 5 Click on the OK button.

Understanding FDDI Counters

Each FDDI station has Station Management (SMT) software, which manages the services performed by the Physical Medium Dependent (PMD), Physical (PHY), and Media Access Control (MAC) layers. Connection Management (CMT) is a component of SMT that controls the setup of the physical link to the FDDI network, the connections to other nodes on the ring, and the internal configuration of FDDI stations. Some management information provided by CMT is displayed in the FDDI Counters dialog box.


Table  4-4: FDDI Counters
Counter Description
CF state The configuration (CF) status of the FDDI port.
ECM state The status of Entity Co-ordination Management (ECM). ECM manages the media interface to the network.
RMT state The status of Ring Management (RMT). RMT receives status information from the MAC layer and CMT, and reports the status of the MAC.
PCM state The status of Physical Connection Management (PCM) for Port A and Port B. PCM manages the physical connection between the local port and another port in an adjacent station.
Neighbour type The type of the remote port that is connected to the FDDI port.
Error frames The number of error frames detected on the ring.
Lost frames The number of frames addressed to this MAC address, but not copied to the receive buffers.
LCT fail The number of times the ring has entered recovery mode because the Token Rotation Time (TRT) expired when the value of the Late Counter (LC) was greater than zero.

When a token passes a station, that station sets the TRT to the value of the negotiated TRT and then starts counting down the TRT. If the station does not receive the token by the time the count elapses, it increments the LC and resets the value of the TTRT to the negotiated TRT. The station then starts counting down the TRT again. If the LC is greater than zero when the TRT expires, the token has been lost and the ring enters recovery mode.

LER estimate The long term average of the Link Error Rate (LER). The LER is the number of errors per second on the ring.

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.