|
Home > Archive > CCNP > February 2001 > CIT - token ring question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
CIT - token ring question
|
|
| The Reamer 2001-02-20, 7:57 pm |
| Question from another post.
3) On the output of the cisco IOS “show interface token ring” command, a large member of transition from up to down or vice versa can indicate a problem on the ring, what’s the problem for interface resets?
a) Lobe cable failure in ring
b) Multicast group address in transition
c) A station in the ring transmitting beacon frames
d) The ring speed set incorrectly (16mbps or 4mbps)
e) The class between an active monitor and a backup monitor | |
|
| I really suck at token ring, but I'm trying to improve my skills, so I'll venture a guess.
I want to say C, since beaconing tends to cause the interface to reset, right? But that beaconing could be caused by in incorrect ring speed set on a device somewhere. Still, that doesn't appear like the MOST correct answer, so I'll say C.
MadChef | |
|
|
|
| From http://www.cisco.com/univercd/cc/td...oc/tokenrng.htm
A Token Ring algorithm called beaconing detects and tries to repair certain network faults. Whenever a station detects a serious problem with the network (such as a cable break), it sends a beacon frame, which defines a failure domain. This domain includes the station reporting the failure, its nearest active upstream neighbor (NAUN), and everything in between. Beaconing initiates a process called autoreconfiguration, where nodes within the failure domain automatically perform diagnostics in an attempt to reconfigure the network around the failed areas. Physically, the MSAU can accomplish this through electrical reconfiguration.
MadChef | |
|
|
|
|
|