-12 dBm shouldn't melt anything. Check for dirty conectors and the
usual schmear. A while back someone forwarded info specifically
about which Bn error levels indicate which kind of problems.
Use fiber to loopback/test your card so you can make assertions about
it's innocence in this matter.
If this is dark fiber, make sure that both ends are set to supply
clock, if it's managed fiber make sure that the provider is providing
clocking...
George
> From cisco-nsp-request@puck.nether.net Thu Oct 19 11:14:41 2000
> Resent-Date: Thu, 19 Oct 2000 11:11:27 -0400
> Received-Date: Thu, 19 Oct 2000 11:09:22 -0400
> Date: Thu, 19 Oct 2000 10:29:32 -0400 (EDT)
> From: Mike Gibbs <gibbs@servint.com>
> To: cisco-nsp@puck.nether.net
> Subject: Problems with a PA-POS card
> In-Reply-To: <003601c03834$9ca22220$ee08ca18@videotron.ca>
> Resent-From: cisco-nsp@puck.nether.net
> X-Mailing-List: <cisco-nsp@puck.nether.net> archive/latest/4078
> X-Loop: cisco-nsp@puck.nether.net
> Precedence: list
> Resent-Sender: cisco-nsp-request@puck.nether.net
>
>
> What would cause these errors? I assumed it was light intensity too high,
> since the telco sent us -12.2 dBm so we built it out to -23 dBm and are
> getting the same errors.
>
>
> *Oct 18 17:32:38: %SONET-4-ALARM: POS8/0/0: B3 BER exceeds threshold, TC alarm declared
> *Oct 18 17:32:48: %SONET-4-ALARM: POS8/0/0: B3 BER below threshold, TC alarm cleared
> *Oct 18 17:40:46: %SONET-4-ALARM: POS8/0/0: B3 BER exceeds threshold, TC alarm declared
> *Oct 18 17:40:56: %SONET-4-ALARM: POS8/0/0: B3 BER below threshold, TC alarm cleared
> *Oct 18 17:46:48: %SONET-4-ALARM: POS8/0/0: B3 BER exceeds threshold, TC alarm declared
> *Oct 18 17:46:58: %SONET-4-ALARM: POS8/0/0: B3 BER below threshold, TC alarm cleared
> *Oct 18 18:04:09: %SONET-4-ALARM: POS8/0/0: B3 BER exceeds threshold, TC alarm declared
>
>
> Cisco Internetwork Operating System Software
> IOS (tm) RSP Software (RSP-K3PV-M), Version 12.0(9)S, EARLY DEPLOYMENT
> RELEASE SOFTWARE (fc1)
> Copyright (c) 1986-2000 by cisco Systems, Inc.
> Compiled Fri 04-Feb-00 20:18 by htseng
> Image text-base: 0x60010908, data-base: 0x60D2E000
>
> ROM: System Bootstrap, Version 11.1(8)CA1, EARLY DEPLOYMENT RELEASE
> SOFTWARE (fc1)
> BOOTFLASH: GS Software (RSP-BOOT-M), Version 11.1(22)CA, EARLY DEPLOYMENT
> RELEASE SOFTWARE (fc1)
>
> Telephonica uptime is 1 week, 1 day, 20 hours, 1 minute
> System returned to ROM by reload
> System image file is "slot0:rsp-k3pv-mz_120-9_S.bin"
>
> cisco RSP4 (R5000) processor with 262144K/2072K bytes of memory.
> R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache
> Last reset from power-on
> G.703/E1 software, Version 1.0.
> G.703/JT2 software, Version 1.0.
> X.25 software, Version 3.0.0.
> Chassis Interface.
> 1 GEIP controller (1 GigabitEthernet).
> 1 VIP2 R5K controller (1 POS).
> 1 GigabitEthernet/IEEE 802.3 interface(s)
> 1 Packet over SONET network interface(s)
> 123K bytes of non-volatile configuration memory.
>
> Mike Gibbs
>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:19 EDT