RE: [EFM] RE: OAM functionals
Facilities Alarms are simple on/off condition points. Sometimes they are
brought out on a simple interface of the vendors equipment. Sometimes they
are internal. They always create "traps" to the EMS at condition crossing.
For active systems that are installed in un-manned locations, such as a
telephone pole, an external facility alarm interface required by the
service provider. This would be part of the implementation requirements of
the equipment vendors.
For active systems that are installed in a manned location, such as
someone's home, the alarms would likely be internal only. Things
like supply power "condition" (I do not mean "power supply".) and
environmental temperature "condition" would be classified a facility alarm.
The reason that these are simple on/off conditions is that the simpler the
technology it takes to get the alarm "condition" in a signal, the more
likely it will work as a system is "dying". The lower the technology layer
used to implement these alarms, the more likely they are to succeed. This
is equivalent to the "last gasp" alarm that is currently being discussed by
At 10:45 AM 9/25/01 -0700, Faye Ly wrote:
>Does facility alarm include:
>1. Chassis power supply status(in this case, CPE)
>2. Fan present/status
>Mechanical thing such as verifying if a box
>is fully closed is hard to implement. Does
>redundancy fault categorized as facility alarm
>From: Roy Bynum [mailto:rabynum@xxxxxxxxxxxxxx]
>Sent: Tuesday, September 25, 2001 7:32 AM
>Subject: [EFM] RE: OAM functionals
>These were not rhetorical questions. The issue of supporting far end
>active systems, and possibly active intermediate systems at "dark" sites
>has been a handicap for those service providers that are currently using
>GbE for service delivery.
>One of the presenters at the January 2001 meeting, John Moore,
>http://www.ieee802.org/3/efm/public/jan01/moore_1_01_2001.pdf, made the
>comment that he had to do a truck roll just to verify that the box cover
>was closed on the active demark system on the side of the customer's
>house. This is the sort of thing that "Facilities Alarms" are for.
>are a lot of other things that simple "alarms" are needed for. The
>as a whole needs to learn more about these types of issues that exist in
>service provider infrastructure, particularly at the very edge.
>At 10:38 PM 9/24/01 -0700, Andrew Smith wrote:
> >Assuming those weren't rhetorical questions - all I know on these
> >what I learnt from the presentation materials submitted so far to this
> >so: no, no, no and no.
> >Looking forward to learning more,
> >Andrew Smith
> >-----Original Message-----
> >From: Roy Bynum [mailto:rabynum@xxxxxxxxxxxxxx]
> >Sent: Monday, September 24, 2001 5:49 PM
> >To: ah_smith@xxxxxxxxxxx
> >Cc: stds-802-3-efm
> >Subject: OAM functionals
> >Lets start a new thread.
> >I would like for others, perhaps you, to be able contribute to some of
> >access edge OAM functional requirements.
> >Do you know what "Facilities Alarms" are? Do you know what they are
> >for? Do you know how they work? Do you know why they might be needed
> >Thank you,
> >Roy Bynum