Alarms on SONET Link

Hi experts,
We have a POS port going to our upstream provider. Recently we've noticed lots of errors on the port. We've tried changing the sfp and line cards to no avail. We have contacted our upstream provider, but they found nothing on there end...
Could it be a clocking issue?
See below logs:
Mar 22 12:58:31 SCT: %SONET-4-ALARM: POS3/0/1: PAIS declared
Mar 22 12:58:32 SCT: %SONET-4-ALARM: POS3/0/1: B3 declared
Mar 22 12:58:41 SCT: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS3/0/1, changed state to down
Mar 22 12:58:42 SCT: %SONET-4-ALARM: POS3/0/1: B3 cleared
Mar 22 12:58:43 SCT: %SONET-4-ALARM: POS3/0/1: PAIS cleared
Mar 22 12:59:03 SCT: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS3/0/1, changed state to up
Mar 22 13:03:32 SCT: %SONET-4-ALARM: POS3/0/1: PRDI declared
Mar 22 13:03:43 SCT: %SONET-4-ALARM: POS3/0/1: PRDI cleared
Mar 22 18:07:03 SCT: %SONET-4-ALARM: POS3/0/1: PRDI declared
Mar 22 18:07:03 SCT: %SONET-4-ALARM: POS3/0/1: B3 declared
Mar 22 18:07:04 SCT: %SONET-4-ALARM: POS3/0/1: PAIS declared
Mar 22 18:07:13 SCT: %SONET-4-ALARM: POS3/0/1: B3 cleared
Mar 22 18:07:15 SCT: %SONET-4-ALARM: POS3/0/1: PAIS cleared
Mar 22 18:07:16 SCT: %SONET-4-ALARM: POS3/0/1: PRDI cleared
Mar 22 18:07:24 SCT: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS3/0/1, changed state to down
Mar 22 18:07:45 SCT: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS3/0/1, changed state to up
Mar 23 14:36:36 SCT: %SONET-4-ALARM: POS3/0/1: PAIS declared
Mar 23 14:37:06 SCT: %SONET-4-ALARM: POS3/0/1: B3 declared
Mar 23 14:37:07 SCT: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS3/0/1, changed state to down
Mar 23 14:37:16 SCT: %SONET-4-ALARM: POS3/0/1: B3 cleared
Mar 23 14:37:17 SCT: %SONET-4-ALARM: POS3/0/1: PAIS cleared
Mar 23 14:37:28 SCT: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS3/0/1, changed state to up
Thanks to advise.
Regards Steve

The B3's indicate an issue between two PTE's (i.e. routers).
Here are some links to dive into:
http://www.cisco.com/c/en/us/support/docs/optical/synchronous-optical-network-sonet/16154-sonetalarms-16154.html
http://www.cisco.com/c/en/us/support/docs/optical/synchronous-optical-network-sonet/16149-biterrorrate-16149.html

Similar Messages

Timing over an ONS 15454 SONET link.

Hello,
Are there any provisioning restrictions on passing timing over a SONET link on the ONS 15454. Here is the senario; I have an OC-48 provisioned over Slot 4, port 1-1 on an MRC-12 card. On the Line provisioning tab, I am unable to set the ProvideSync check box. I need to use the link to time a distant end node. The far link is RX the STU SSM. The local Node is set for external timing with BITS 1 and 2 active and inservice w/PRS. Is there something I am missing?
TIA,
Steve

Steve,
The OC48 port is always providing timing information to the attached device in the S1 byte of the Line Overhead.
The ProvidesSync box is not an indication of whether the port is providing timing. Rather it is an indication that that port is being used as a timing source (Line Timing). If you go to Provisioning->Timing and select that slot/port as a Timing Reference the ProvidesSync box will be checked.
I will upload a Word document with screen shots. It should help clear things up.

What happens to SONET errors?

I'm not particularly strong with SONET and only have a small SONET network so any help with this question would be greatly appreciated. When line terminating equipment (SONET node) detects a section error what does it do with that frame when it switches it to the next section? Somehow it will not appear as an error on the next section and my group has some differing opinions on how this is accomplished. Any opinion and associated documentation you could provide would be great.

Hi,
SONET uses the layer model.
The overhead and transport functions are broken into layers: Physical, Section, Line and Path. The layers have a hierarchical relationship and are viewed from the top down.
The lowest layer is the physical layer, which represents the transmission medium. This is usually a fiber link. No overhead is associated with the physical layer. The main function of this layer is conversion between internal STS-N signals and external optical or electrical SONET signals
The Section layer deals with the transport of an STS-N frame across the physical medium. Functions of this layer include framing, scrambling, Section error monitoring and Section level communications overhead The Section overhead is interpreted and modified or created by Section Terminating Equipment.
The line layer is the part of the SONET link between multiplexers. The line overhead is used for the line layer. This layer provides synchronization and multiplexing functions for the Path layer. The overhead associated with these functions includes overhead for maintenance and line protection purposes
The Path Layer is the part of the SONET network from where the asynchronous digital signals enter and to where these signals exit the SONET network. (end-to-end). The Path layer maps the payloads into the format required by the Line layer. In addition, this layer communicates end-to-end via the Path Overhead. The POH is interpreted and modified or created by Path Terminating Equipment.
Each layer has its own set of overhead bytes that it uses for communication and monitoring purposes.
The information in the overhead bytes is interpreted and re-created at the corresponding terminating layer. For example, section overhead uses the B1 parity bit to monitor for section errors . This information is propagated separately for each section start/end point. When section terminating node sees B1 errors, it declares a section alarm or threshold crossing for that segment. The Section overhead and parity is then recalculated for the next segment of section overhead. Hence you will not see a section alarm or error propagated from segment to segment.
GR-253-CORE is the official industry standard for SONET transport systems. It is published by Telcorida Technologies. It described in-depth the generic criteria that all telecommunications equipment are supposed to conform to. Probably not the best place to start but it is an excelelnt source on SONET protocols.
There are some good on-line SONET tutorials that you can find using a GOOGLE search. Here are a few good links.
http://members.cox.net/michael.henderson/Papers/SONET-SDH.pdf
http://www.eetimes.com/electrical-engineers/education-training/tech-papers/4136556/A-Tutorial-on-ITU-T-G-709-Optical-Transport-Networks-OTN-
http://networking.ringofsaturn.com/Protocols/sonet.pdf

SONET and DS-1

Recently we just switch from CES over an ATM backbone to SONET (454s and 327s). We have a requirement for point-to-point T1 circuits. The circuits worked fine over CES and all we did was move the circuits to the SONET. The tail end of the circuit remained the same. My question is more on the timing of the actual T-1 circuit itself. Is timing for the individual DS-1 circuits provided by the SONET timing source or by the individual circuit itself? In other words do I set up the CSU devices connected to the SONET box to receive timing from the NI or do I need to set up the CSUs as if they are connected back-to-back (One as a master and one as a slave).
These circuits worked fine from the ATM/CES and the SONET boxes are in the same location as the ATM boxes. Timing issues for ATM/CES are more specific than the SONET and timing was clearly addressed. Provsioning of the circuit through SONET is correct (Line coding, framing etc.) No documentation that I have found addresses this question (at least not plainly) on the timing for individual DS-1 circuits. Cisco Support has said that each individual circuit must provide it's own timing. This is not working and even though there are no SONET alarms the WAN link is still lost intgermittently

SONET does NOT provide timing to the circuits it carries. In the case of your point-to-point circuit, set up the timing on your CSU's. On one end set it up for "master" or "internal" (or whatever sounds close, seems like they're all different), then set the other end up for "slave" or "line". Most CSU's will provide an internal clock; while it's not the best quality, as long as both DTE's are referencing the same source you shouldn't have a problem.

When will email alarms work in iCal 3.0 and Leopard?

I have been trying to follow the Apple discussions of some of the problems in iCal 3.0 under Leopard. Fortunately, I haven't experienced some of them. The one that is bothering me is the inability to send email alarms. This is a feature I used a lot in Tiger and want to use again. My iBook and iMac are syncing pretty well, and my calendars are, too. However, if I create a new iCal event on either computer and then try to set an email alarm, I get this response: "You must add your own card and email address in Address Book in order to be able to use mail alarms" with a link to open Address Book. When I open Address Book, there is no conceivable way to follow the above instruction. Either I am missing something very simple, or Apple has not fixed this bug in iCal 3.0 and Leopard, despite having stated in a knowledge base document on November 15, 2007, (http://docs.info.apple.com/article.html?artnum=306907) that as a result of the 10.5.1 update "iCal alarms are now more reliably delivered via email." Has anyone figured a go-around for this problem?

Well, here I am answering my own question. I went into Address Book preferences on my iBook, which was upgraded from Tiger to Leopard, and found that my own card in Address Book was no longer indicated as being "me". I checked the box to indicate that, and then--voilà!--my email alarms worked in iCal. I guess I should have realized that the upgrade to Leopard didn't necessarily create all the preferences that had previously existed in Tiger. Once I check the iMac, which came with Leopard, to ascertain that this fix works on the iMac, too, I will mark this question as answered.

Alarm clock & iphone

I looked through all the apps and it seems you need to have it running in the background ALL THE TIME for it to work which ends up using battery power...
Is there a way in which I can have my alarm clock somehow linked to an application so that it will run on a set schedule without me manually having to open it?

If your talking about the built in alarm clock in the "clock" app yes it does run in the background, though I would say the amount of battery drain this applies is miniscule.
If you set an alarm to a recurring event in a calendar it too is using a bit of battery power it just doesn't give you the little icon up the top to let you know it's doing something.
If it's just an alarm to get you up in the morning you could get one of the Clock app's like nightsand or the like so that way it's only running when it's opened, you just open the app before you go to bed and plug it into the power adaptor or dock, then it would only be running when the app is opened, this would chew more power as it has to run a full app but i would imagine you would have it on AC power during this time period so it wouldn't matter.
That's the only option i can think of

MPLS TE/FRR on ME 3600X

Hi,
Can ME 3600X provides 50-ms rerouting time upon link failure with MPLS TE/FRR?
There are many failure detection mechanisms cause the routers to switch LSPs onto their backup tunnels:
1.Interface Down Notification
(When a router’s link or neighboring node fails, the router often detects this failure by an interface down notification.
On a Packet over SONET (POS) interface, this notification is very fast.)
2.Loss of Signal
(Unlike POS interfaces, Gigabit Ethernet does not have any alarms to detect link failures. If a link is down
due to a cut cable or because the remote end shuts its laser, the optics module (GBIC or SFPs) on the
Gigabit Ethernet card detects a loss of signal (LOS). The LOS is used as a mechanism to detect the
failure and begin the switchover.)
3.Notification from the RSVP hello that a neighbor is lost
4.Notification from the Bidirectional Forwarding Detection (BFD) protocol that a neighbor is lost
5.Notification from the Interior Gateway Protocol (IGP) that the adjacency is down
6.For point-to-point link, PPP or HDLC keepalives
I know the 1st and 6th failure detection mechanism can't be applied with ME 3600X. Which failure detection mechanisms
cause ME 3600X to switch LSPs onto their backup tunnels to achieve 50-ms rerouting time upon link failure with MPLS TE/FRR?
My customer want to implement Ring Topology with ME 3600X to provide MPLS L2/L3 VPN services with MPLS TE/FRR.
What is the best pracetice design for Ring Topology with MPLS TE/FRR to provide link protection?
Regards,
Pipatpong

Hello Pipatpong
Below are the answers to your questions:
2. Should be able to detect and cutover.
3. Should be able to detect based on timer configuration. However the recommended value for RSVP hellos is 200 msec
From the config guide :
(http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/12.2_52_ey/configuration/guide/swmpls.html#wp1183359)
To prevent false detection of a down neighbor and unnecessarily triggering fast reroute, we recommend configuring a minimum frequency of 200 ms.
4. BFD support not yet available
5.Dont think IGP will be able to do 50ms on any platform.

Cisco Prime 1.3 and email alerts

I want to create some basic alarms on our infrastructure. I want to monitor only specific ports on specific switches. I do not want to monitor client ports, only uplinks to distribution/core and server ports. Is it possible to get alerts only from specific ports from specific switches ? If it is can you please tell me where exactly I have to look in the documentation of the PI.
Predrag Petrovic

Hi,
as far as I know, this is not possible.
We configured our core switches to send link-up-down events as traps to PI. With this configuration, we got alarms only for link-up-down events on our core switches. We could not restrict it to specific ports, but this worked for us.
Timo

15327 Version 06.01-005L-10.05 Software and XTC-14/XTC-28-3 Cards

I was wondering, if anyone has come across this. In service XTC-14 and XTC-28-3 Cards on the field in 15327 Switchs. Periodically they just drop communication. The Node's stay up (T1's and Ethernet/SONET links are still up) but the Communication to the box drops. The system is not Remote Pingable or Telnetable. BUT if you are able to log into a local internal Router, The box is pingable.
Has anyone come across these problems with the 6.01 Version of CTC Code? Or is it a Controller problem? Recently since switching from 4.01 to 6.01 We have had an increase if replacement XTC's Needed as well as RMA's for bad cards. I think this may be beyond the "Bad Recall Card" List.
Any Ideas?
[email protected]

Sorry - to add:
I don't think it's a question of WPA vs. WPA2, or even channel number - I have 2 identical routers here and neither work (both default to WPA Ch 11) but I changed one to WPA2, new SSID, various channels and still had the same problems.
Another thing to note that should be irrelevant, but who knows: the Firewire controller on my machine died back in Fall 2010 - to the point where the system won't start-up unless I remove the IOFirewire***.kext from /System/Library/Extensions , and as soon as I do that, it works flawlessly (minus Firewire). It meant I had a **** of a time installing Lion becuase I can't boot off the Recovery Partition (which has the drivers baked into it), but by cloneing my HD, installing Lion onto the clone via a borrowed machine, removing the .kext's and cloning back, I got it on and everything seems to be fine otherwise... I posted about that problem before, but never got any answers. And it wasn't just me, my father has a late 2007 MBP and the same firewire issue happened to his within 5 days of mine (not a power spike - I think it was shortly after some system update if I remember correctly).

Optical Networking Layer 2

I was having a discussion today about Global IP networks from AT&T, WorldCom, etc that are moving to the "IP+Optical" standard. From what I understand it fiber optic cable, MPLS and IP (OSPF, BGP, etc).
My question is what is the Layer 2 technology? I may be thinking of this from a TDM world (I work on several enterprise networks), but if it's not Ethernet everywhere (they're getting there), what is the Layer 2 technology the breaks the packets into frames and frames the 1's and 0's from the fiber network ?
I've read about RPR and DPT. Are these the Layer2 encapsulation used?
Thanks.

RPR and SRP (formerly called DPT) are Layer 2 MAC encapsulation protocols providing multiple access over Sonet. They virtually emulate a LAN environment.
On point-to-point Sonet links the choice of Layer 2 encapsulation is HDLC, PPP, Frame Relay. ATM is a special case, not fitting in the OSI layered model. ATM can also be a transport over Sonet, which is always Layer 1.

Cisco Prime infrastructure Change severity Switches and hubs - link down alarm

Hi, I want to change the severity of the link down alarm in the Cisco Prime Infrastructure 1.3, but in the menu Administration -> System Settings -> Severity Configuration i can not find the alarm. Some body knows where is it? o where i can change the severity of that alarm?
Thanks in advanced.

Hi Rollin and Daniel,
the first test i did changing the severity was with a new installation, with no devices added and it worked, when i did it in a Prime infrastructure with devices added it didn´t work, well, for this Prime with devices i upgraded it with the patch for 1.3 version and now it works too, the alarms is ok as the alarm severity, this is the link for the patch:
http://software.cisco.com/download/release.html?mdfid=284652876&flowid=38562&softwareid=284272933&release=1.3.0&relind=AVAILABLE&rellifecycle=&reltype=all
i hope this helps,
Regards,
Milton Tizoc.

Prime Infrastructure 2.0 Link-Down Alarm severity level

Hi,
i have been looking for a way to lower the severity level of link-down Alarms. I use the threshhold utilization feature and want to generate an alarm when CPU or Memory goes over 90%, this works fine. Problem is that when you enable "Switches and Hubs" or "Routers" category to receive alarms under: Operate -> Alarms & Events -> Email Notifications, you define only Critical alarms should generate an email and Link-down is by default Critical.
Well you figure that you should be able to change this, but i can't find anything to change the severity under: Administration -> System Settings -> Severity Configuration.
Do anyone know if this is even possible? If so please tell me how..

Hi,
Yes it is possible.
Changing Alarm Severities
You can change the severity level for newly generated alarms
Note Existing alarms remain unchanged.
To change the severity level of newly generated alarms:
Step 1 Choose Administration > System Settings .
Step 2 Choose Severity Configuration from the left sidebar menu.
Step 3 Select the check box of the alarm condition whose severity level you want to change.
Step 4 From the Configure Severity Level drop-down list, choose the new severity level ( Critical , Major , Minor , Warning , Informational , or Reset to Default ).
Step 5 Click Go, then click OK.
Check the attached screen shot ..
Thanks-
Afroz
***Ratings Encourages Contributors ***

False alarm error messages when Linking from e-mail to web

About 30-40% of the time that I try to link to the web from a URL embedded in an e-mail, an error message comes up saying that the program's unable to connect to that particular URL (which it cites). But then it almost always goes ahead and takes me to the right website. Why is this happening and is there a way I can stop it? It's a nuisance to always have to read the alarm and then needlessly worry that the connection to the website cannot be made. Thanks.

Hi,
you have something like:
end_of_data = ' '.
first_call = 'X'.
WHILE end_of_data = ' '.
        CALL FUNCTION 'RSDRI_INFOPROV_READ'
          EXPORTING i_infoprov             = ....
                     i_th_sfc               = ...
                     i_th_sfk               = ...
                     i_t_range              = ...
                     i_reference_date       = ...
                     i_save_in_table        = ....
                     i_save_in_file         = ....
                     I_USE_DB_AGGREGATION   = ...
                     i_packagesize          = 100000
                     i_authority_check      = ...
          IMPORTING e_t_data               = .....
                     e_end_of_data          = end_of_data
          CHANGING   c_first_call           = first_call
          EXCEPTIONS illegal_input          = 1
                     illegal_input_sfc      = 2
                     illegal_input_sfk      = 3
                     illegal_input_range    = 4
                     illegal_input_tablesel = 5
                     no_authorization       = 6
                     ncum_not_supported     = 7
                     illegal_download       = 8
                     illegal_tablename      = 9
                     OTHERS                 = 11.
ENDWHILE.
hope this helps...
Olivier.

Link Fail Alarm - SFP Ports

Hello,
I have been trying to configure the Link Fail Alarm on SFP ports for a Cisco CGS2520 (Cisco CGS-2520-16S-8PC).
SFP: GLC-FE-100FX-RGD (10-2360-02).
I can create a new Alarm Profile and attach it to the Ports that I want to monitor. The update Profile can then be saved to the startup-config and the configuration can be viewed as being correct.
If I then pull a fibre cable the Alarm is generated as expected.
However when I reboot the Switch the Alarm Profile is still within the configuration but it is no longer attached to the ports (i.e. the Alarm Profile configuration is shown on the startup-config however the running-config does not contain the alarm profile on the SFP port). Therefore when the Fibre Cable is removed no alarm is generated.
I have run through the procedure as defined in Chapter 7 of the Cisco CGS2520 Configuration Guide and as stated above copied the running-config to the startup-config.
Is anyone able to advise why the port attachment is lost when the switch is restarted – the Alarm Profile is retained.
Thank you,
Darsh

Hello,
I have been trying to configure the Link Fail Alarm on SFP ports for a Cisco CGS2520 (Cisco CGS-2520-16S-8PC).
SFP: GLC-FE-100FX-RGD (10-2360-02).
I can create a new Alarm Profile and attach it to the Ports that I want to monitor. The update Profile can then be saved to the startup-config and the configuration can be viewed as being correct.
If I then pull a fibre cable the Alarm is generated as expected.
However when I reboot the Switch the Alarm Profile is still within the configuration but it is no longer attached to the ports (i.e. the Alarm Profile configuration is shown on the startup-config however the running-config does not contain the alarm profile on the SFP port). Therefore when the Fibre Cable is removed no alarm is generated.
I have run through the procedure as defined in Chapter 7 of the Cisco CGS2520 Configuration Guide and as stated above copied the running-config to the startup-config.
Is anyone able to advise why the port attachment is lost when the switch is restarted – the Alarm Profile is retained.
Thank you,
Darsh

Sonet alarm problem on Cisco GSR

Hi,
I'm Peter working in an ISP network operations. I have problems understanding this alarm in Cisco GSR. July 15 04:44:55 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER exceeds threshold, TC alarm declared. How do I troubleshoot this problem? The interface is up but the line protocol went down because of it. What we did was we requested a loop from our international peering facing our side and we were able to see the loop. After releasing the loop and normalizing the line, line protocol went up and traffic started to flow. What's the first thing to do in problems like this?

Friend:
take a look to this:
http://www.cisco.com/en/US/tech/tk482/tk607/technologies_tech_note09186a0080094a79.shtml
http://www.cisco.com/en/US/tech/tk39/tk48/technologies_tech_note09186a00800c93c4.shtml
http://www.cisco.com/en/US/tech/tk482/tk607/technologies_tech_note09186a0080094522.shtml
I am actually getting same errors, i am triying to figure out what is going on, it looks like we are having problems with providor...

Alarms on SONET Link

Similar Messages

Maybe you are looking for