[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | atm |
|
| Moderator: | NPSS::WATERS |
|
| Created: | Mon Oct 05 1992 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 970 |
| Total number of notes: | 3630 |
829.0. "topology change requests?" by TKOV51::HAYAKAWA (Kouhei Hayakawa, NPB/MS, Osaka HUB6F) Tue Feb 18 1997 06:07
What does topology changes mean?
My customer has 4 GS/ATMs and 15 AlphaServers connected to GS/ATM.
They use LAN Emulation and one of them work as LAN Emulation Server.
Then "topology change requests" counter of GS/ATM is increasing.
And "Time in state" is reset to zero sometime.
What happen?
Regards,
Kohei
<<< NOTED::NOTES$9:[NOTES$LIBRARY]ATM.NOTE;3 >>>
-< atm >-
================================================================================
�Ρ��� 563.0 When is a topology change not a topology change? ��ץ饤�ʤ�
STEVMS::PETTENGILL "mulp" 110 �� 18-JUN-1996 16:27
--------------------------------------------------------------------------------
I'm trying to figure out how there can be topology changes happening very
frequently from the GS/ATM standpoint, but not happening for days from the
standpoint of the DS400s that are connected to it. There are two vms lane
clients attached, but I don't understand how they could be generating
topology changes.
All three components were last reset about the same time several days ago.
GIGAswitch/ATM-> les 1 -ct
LAN Emulation Server 1 Topology Change Status
Topology change state: FALSE
Time in state: 1322 seconds
Topology change requests
received: 175091
forwarded: 175091
discarded
receive queue full: 0
no resources: 0
generated: 0
generation failures: 0
GIGAswitch/ATM->
-----------------
Main File Summary VLAN Networking
Interface Security System Services Help
/VLAN/Bridge % sts
Spanning Tree Parameters for Group 1 (Default GROUP (#1))
Spanning Tree Status : ON
Bridge Protocol Used : IEEE 802.1D
Priority : 32768 (0x8000)
Bridge ID : 8000-0020DA:073120
Designated Root : 007F-08002B:17E5BB
Cost to Root Bridge : 124
Root Port : Slot 3 Interface 5 Brg/1
Hold Time : 1
Topology Changes : 7
Last Topology Change : 1 days, 13 hours, 28 minutes, 26 seconds ago
Bridge Aging Timer : 300
Parameters system uses when
Current Parameters attempting to become root
-------------------------------- --------------------------------
Max Age 15 secs System Max Age 20 secs
Forward Delay 15 secs System Forward Delay 15 secs
Hello Time 1 secs System Hello Time 2 secs
/VLAN/Bridge % stps
Spanning Tree Port Summary for Group 1 (Default GROUP (#1))
Slot Service Path Desig Des Rt Swt Fw Root Bridge ID
Intf Inst Pri State MAC Cost Cost Pt Pt Pt Tx Desig Bridge ID
---- ----------- --- ----- ------ ----- ----- --- --- --- -- ------------------
2/ 1 Lne/ 1 128 FORWD 073120 8 124 Yes No No 2 007F-08002B:17E5BB
8000-0020DA:073120
3/ 2 Brg/ 1 128 FORWD 074391 100 124 Yes No No 0 007F-08002B:17E5BB
8000-0020DA:073120
3/ 3 Brg/ 1 128 FORWD 074392 100 124 Yes No No 0 007F-08002B:17E5BB
8000-0020DA:073120
3/ 5 Brg/ 1 128 FORWD 074394 100 24 No Yes No 1 007F-08002B:17E5BB
0080-08002B:B25580
3/ 6 Brg/ 1 128 FORWD 074395 100 124 Yes No No 0 007F-08002B:17E5BB
8000-0020DA:073120
/VLAN/Bridge %
-------------------
/VLAN/Bridge % sts
Spanning Tree Parameters for Group 1 (Default VLAN (#1))
Spanning Tree Status : ON
Bridge Protocol Used : IEEE 802.1D
Priority : 32768 (0x8000)
Bridge ID : 8000-0020DA:06F970
Designated Root : 007F-08002B:17E5BB
Cost to Root Bridge : 132
Root Port : Slot 2 Interface 1 Lne/1
Hold Time : 1
Topology Changes : 13
Last Topology Change : 1 days, 10 hours, 57 minutes, 30 seconds ago
Bridge Aging Timer : 300
Parameters system uses when
Current Parameters attempting to become root
-------------------------------- --------------------------------
Max Age 15 secs System Max Age 20 secs
Forward Delay 15 secs System Forward Delay 15 secs
Hello Time 1 secs System Hello Time 2 secs
/VLAN/Bridge % stps
Spanning Tree Port Summary for Group 1 (Default VLAN (#1))
Slot Service Path Desig Des Rt Swt Fw Root Bridge ID
Intf Inst Pri State MAC Cost Cost Pt Pt Pt Tx Desig Bridge ID
---- ----------- --- ----- ------ ----- ----- --- --- --- -- ------------------
2/ 1 Lne/ 1 128 FORWD 06F970 8 124 No Yes No 2 007F-08002B:17E5BB
8000-0020DA:073120
3/ 2 Brg/ 1 128 FORWD 074311 100 132 Yes No No 0 007F-08002B:17E5BB
8000-0020DA:06F970
3/ 3 Brg/ 1 128 FORWD 074312 100 132 Yes No No 0 007F-08002B:17E5BB
8000-0020DA:06F970
3/ 5 Brg/ 1 128 FORWD 074314 100 132 Yes No No 0 007F-08002B:17E5BB
8000-0020DA:06F970
3/ 6 Brg/ 1 128 FORWD 074315 100 132 Yes No No 0 007F-08002B:17E5BB
8000-0020DA:06F970
/VLAN/Bridge %
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 829.1 | Topology Change is there for 802.1D Spanning Tree | NPSS::NEWTON | Thomas Newton | Tue Feb 18 1997 17:59 | 35 |
|
LANE V1.0 Specification
7.1.19 Generation of LE_TOPOLOGY_REQUESTS
An (sic) LE Client that is acting as an IEEE 802.1D transparent bridge
MUST send one LE_TOPOLOGY_REQUEST to its LE Server for every Configuration
BPDU it sends ot the BUS. The Topology Change bit in the FLAGS field in
the LE_TOPOLOGY_REQUEST MUST be set to the same value as the Topology
Change bit in the Configuration BPDU.
7.1.20 Local Management Directives
A LE Client MAY send LE_TOPOLOGY_REQUESTs to its LE Server in response
to local management directives or network management directives. However,
such LE_TOPOLOGY_REQUESTs MAY be sent while bridge clients are still
active, and MAY have either value for the Topology Change bit. Note that
adverse operation may result in all LE Clients when more than one LE
Client generates LE_TOPOLOGY_REQUESTs and the topology change status
values do not agree.
7.2.10 Forwarding LE_TOPOLOGY_REQUESTs
The LE Server MUST send one LE_TOPOLOGY_REQUEST to all LE Clients for
each valid LE_TOPOLOGY_REQUEST received from any client. The Topology
Change bit in the FLAGS field in the LE_TOPOLOGY_REQUEST SHOULD match
that of the LE_TOPOLOGY_REQUEST last received by the LE Server.
7.2.11 Initiating LE_TOPOLOGY_REQUESTs
An (sic) LE Server MAY issue LE_TOPOLOGY_REQUESTs without receiving any
LE_TOPOLOGY_REQUESTs. For example, an (sic) LE Server may wish to clear
the LE Clients' Topology Change flags if all its transparent bridge LE
Clients cease operations while the other LE Clients' Topology Change
flags are set.
|
| 829.2 | | TKOV51::HAYAKAWA | Kouhei Hayakawa, NPB/MS, Osaka HUB6F | Tue Feb 18 1997 21:03 | 4 |
|
Thank you for your helpful reply.
Kohei
|