15.3 Perform a protocol analysis session; to examine the high-layer network frame communication processes. Have you verified that the 802.5 base frame communication processes are proper and fluent as to low-level protocol exchange? Go to S1. Go back to page 15.1 and troubleshoot the low-level 802.5 base communication processes. S1. First, perform a full-capture session. Next, view the high-layer protocol communication that occurs concurrently between the network components (the ring stations, network peripherals, gateways, bridges, routers, file servers, and so on) involved in the high-layer communication processes that you are troubleshooting. Closely examine the application and network operati ng system communication process between the respective network components. Keep in mind that certain applications may use multiple layers of the Token Ring protocol model for transmission. Check all the higher layers. Are the involved network components and their respective application/network operating system communication processes exchanging the correct assigned protocol? Reference the NOS and software application manufacturers' manuals and if necessary contact your NOS and software support channel for assistance with troubleshooting any suspected high-layer communication process. Continue. Does the incorrect protocol exchange appear to be related to some sort of file access process problem with a particular NOS or software application? Reference the NOS and software application manufacturers' manuals and if necessary contact your NOS and software support channel for assistance with troubleshooting any suspected high-layer communication process. Check the network components involved in the specific high-layer communication process that you are troubleshooting for a possible failure by going to the page for that particular specific network component (for example, 6 Ring Station Problems , 10 Network Peripheral Problems , 14 File Server Problems , and so on). If you are not completely conclusive as to a specific network component that may be related to the failure symptom, go to page 2 and troubleshoot the respective Token Ring addresses associated in the high-layer frames that appear to be involved with failure symptoms. If after going to the respective fault domain, network area, or network component you find a problem, resolve the problem and retest the ring by going back to page 15 and rerun another baseline session to test the ring. Then reexamine the high-layer communication processes for any deviations from the previous testing results. If everything appears normal, record the problem in the network maintenance and service log. If the problem still exists, contact your NOS and software support channel for assistance with troubleshooting any suspected high-layer communication process. November 15, 1996 Print This Page E-mail this URL