| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: commands, fiber, ipe, mmi, remote, troubleshooting |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Senior Member ![]() Rachelle is curious
Location: Lou, KY Rep Power: 9 ![]() | MMI commands and IPE Fiber Remote Troubleshooting????? I need some help interpreting the information below. I want to diag my IPE fiber remote but, the commands that are listed below only get me swartzed. If I don't need to be in a load why won't SUBM work? Can I not do this from the normal Maint Console? Help please!!!!! rachelle Fault isolation and correction using MMI maintenance commands You can perform some testing and troubleshooting of the Fibre Remote IPE from a local or a remote MMI terminal or TTY by typing MMI commands on the terminal without loading system diagnostic programs (overlays). These commands provide current equipment status, invoke card testing, check equipment performance, print messages from log files, and so on. Procedure 7 Checking Fibre Remote IPE using MMI commands This procedure uses MMI commands to maintain Fibre Remote IPE cards, and fibre-optic link status. You can send these commands from the local MMI terminal to be executed by the remote site MMI terminal and vice versa by executing the SUBM string command, where string is the actual command sent to the other side. For example, SUBM PLOG 10 entered at the local MMI terminal will request that the remote site prints 10 messages from the log file located in the Fibre Peripheral Controller card memory. To obtain the Fibre Superloop Network and Fibre Peripheral Controller cards status: 1 Log in on the MMI maintenance terminal. 2 Type STAT to check the status or the card connected to the MMI terminal. The response: The card is enabled by the CPU, when enabled. The phase-lock loop can be locked to the incoming signal or not, and the PLL may be locked on the primary or secondary packlet. Enabled/Disabled PLL: lock/unlock prim/sec Fibre Remote IPE maintenance Page 135 of 162 Fiber Remote IPE Description, installation, and maintenance 3 Type TEST P/S and press the Enter key, where P tests the primary packlet and S tests the secondary packlet. The response is one of the self-test messages listed in Appendix A. 4 Type QFIB and press the Enter key to query the status of the fibre-optic link. The response: PRIM physical/signal/direction SEC physical/signal/direction physical represents the status of the Electro-optical packlet, which can be equipped, unequipped, or faulty. signal represents the status of the incoming signal, which can be SF (signal failed), SD (signal degrade not implemented in Rev 1 H/W), or NA (no alarm). direction represents the direction of traffic on the link, which can be incoming, outgoing, bothways, or none. 5 Type QALM and press the Enter key to query the alarm status of the fibre-optic link. The response: PRIM alarm type SEC alarm type alarm on the Electro-optical packlet can be red (local alarm), yellow (remote alarm), or clear (no alarm). type indicate one of the following types of alarm when it exists: LOS, LOF, LOP, or FERF. Page 136 of 162 Fibre Remote IPE maintenance 553-3001-020 Standard 6.00 April 2000 6 Type PRPM {prim/sec} and press the Enter key to print the Performance Monitoring report for the primary and secondary fibre-optic links. The format of the response is shown in Table 13. Table 13 shows the format for the Performance Monitoring report. The report shows a matrix or fibre-optic link performance parameter values for different interval counters listed in the header and intervals listed in the first column. __________________ No matter where you go, there is the Ladies Love Marty Fan Club. :bow2: :bow2: :bow2: | ||||||||
| | |
| | #2 (permalink) | ||||||||
| Senior Member ![]() slagburn has no status.
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 ![]() | Not sure on the fiber remotes but on my carrier remotes the MMI connection is a separate serial connection - not sure if one can (with the proper connections) log into the local or remote interfaces via a TTY port on the switch but I'm pretty sure there is a setup that allows one to log into SL1 overlays from the MMI. | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Senior Member ![]() Rachelle is curious
Location: Lou, KY Rep Power: 9 ![]() | Here is what I am seeing, at least once a week, Tuesday nights, but twice this week: XMI000 8 : OIF: no active link XMI000 40 : OIF: no active link XMI000 8 : PLL lock lost XMI000 40 : PLL lock lost XMI000 8 : PLL locked XMI000 40 : PLL locked XMI000 8 : OIF: switched to prim XMI000 40 : OIF: switched to prim XMI000 8 : FPEC has requested Download XMI000 40 : FPEC has requested Download All of this is then followed by the XMI002 re-establishment codes for all of the line cards. I am leaning toward a power blink but, there aren't any PWR codes. I wouldn't know how the fiber to two separate modules could flake out at the exact same time. I need a cause. Any ideas???? rlc __________________ No matter where you go, there is the Ladies Love Marty Fan Club. :bow2: :bow2: :bow2: | ||||||||
| | |
| | #4 (permalink) | ||||||||
| Senior Member ![]() slagburn has no status.
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 ![]() | I'm with you on a power blink - the only time I see controller cards requesting a download is when they've lost power, if they remain powered up then everything should just come right back up... once again though no experience on the fiber controllers here just the standard and carrier remote controllers. Might be time to take a look at the UPS on the other side - bearing in mind that it doesn't have to be in alarm to not work. | ||||||||
| | |
| | #5 (permalink) | ||||||||
| Senior Member ![]() Rachelle is curious
Location: Lou, KY Rep Power: 9 ![]() | Everything on the UPS makes it look like it is fine. That just can't be the case. That unit is about 9 years old. It is possible that the batteries are the originals. So, I am sticking with the theory of power. I would feel so much better if there were a PWR code somewhere in the mix. rlc __________________ No matter where you go, there is the Ladies Love Marty Fan Club. :bow2: :bow2: :bow2: | ||||||||
| | |
| | #6 (permalink) | ||||||||
| Senior Member ![]() slagburn has no status.
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 ![]() | Most UPS batteries aren't rated past 5 years - 9 years is really pushing it even for ones that have been probably maintained. On the remote carrier setup there is a port on the LCI (local carrier interface) that is designed to interface with the host systems Sys monitor card - I have yet to see one actually hooked up and those are what generate the various PWR codes. Might want to look into this for the fiber setup and see if it applies. | ||||||||
| | |
| | #8 (permalink) | ||||||||
| Junior Member ![]()
Location: Terre Haute, IN Rep Power: 7 ![]() | I have seen this on several of our fiber remotes. We too thought it was a power problem but after replacing multiple ups's we still had the issue. In our case it has been bad cards(either end). A temporary fix was to disable and then re-enable but the problem always came back until the card was replaced. | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |