I can recommend to take a look into the default policy-settings that ship with
Spectrum.
The Policy Manager User Guide has some pretty good examples for port monitoring
on page 63
Choose one of the following configurations for your port models to define if
you want
alarms based on traps, alarms based on polling, live pipes or no alarms at all.
If I remember it correct, CA recommends not to use 0x12a54
GeneratePortStatusAlarms
but instead use the listed attributes and values.
Hope that helps.
Regards,
Jan
<!--
These settings enable port status monitoring using only
passive means. SPECTRUM will listen for Link Down traps
and generate alarms when needed. This is the most efficient,
yes least reliable, means of port status monitoring. This is
also the default SPECTRUM settings.
-->
<policy-settings name="Passive Port Monitoring">
<set-attr-value id="0x1280a" value="FALSE" />
<set-attr-value id="0x11dd8" value="FALSE" />
<set-attr-value id="0x11fc2" value="1" />
<set-attr-value id="0x12957" value="TRUE" />
</policy-settings>
<!--
These settings enable port status moniting using Live Pipes.
This means that SPECTRUM will actively poll the status of
ports involved in modeled connections. User will see colored
pipes in all UI applications displaying the status of the
connection. We also enable trap-based monitoring for
expedited fault detection.
-->
<policy-settings name="Live Pipes">
<set-attr-value id="0x1280a" value="FALSE" />
<set-attr-value id="0x11dd8" value="TRUE" />
<set-attr-value id="0x11fc2" value="1" />
<set-attr-value id="0x12957" value="TRUE" />
</policy-settings>
<!--
These settings enable port status moniting for ports whose
connectivity is not modeled in SPECTRUM.
This means that SPECTRUM will actively poll the status of
the port. We also enable trap-based monitoring for
expedited fault detection.
-->
<policy-settings name="Poll Unconnected Ports">
<set-attr-value id="0x1280a" value="TRUE" />
<set-attr-value id="0x11dd8" value="FALSE" />
<set-attr-value id="0x11fc2" value="1" />
<set-attr-value id="0x12957" value="TRUE" />
</policy-settings>
<!--
These settings disable all port status monitoring methods
and prevents any related alarms from being generated.
-->
<policy-settings name="Disabled Port Monitoring/No Alarms">
<set-attr-value id="0x1280a" value="FALSE" />
<set-attr-value id="0x11dd8" value="FALSE" />
<set-attr-value id="0x11fc2" value="0" />
<set-attr-value id="0x12957" value="FALSE" />
</policy-settings>
-----Ursprüngliche Nachricht-----
Von: Catalin Farcasanu [mailto:[email protected]]
Gesendet: Freitag, 8. Juli 2011 15:14
An: spectrum
Cc: spectrum
Betreff: Re: [spectrum] Silence Ports
Hi Ken,
As I remember from the previous versions, the combination between attributes
'ok_to_poll' and 'PortPollStatus' would conclude if a port is monitored or not.
IF you set those to 1 on a given device you would generically activate he
'LiveLinks' on the connection of that port.
However there are still the trap based events that you need to consider. There
are several attributes that relate to that on each model of the port. I suggest
to try all of them. As a last result you could disable the traps on the devices.
--
ok_to_poll No
PollPortStatus No
AlarmOnLinkDownTrap Check Status (1)
DisableTrapEvents No
DisableUnmanagedTraps No
ifLinkUpDownTrapEnable 1
OutstandingLinkDownTrap No
Processes_Traps No
--
Catalin Farcasanu
SOLVIT Networks
www.solvitnetworks.com
----- Original Message -----
> From: "Kenneth Kirchner" <[email protected]>
> To: "spectrum" <[email protected]>
> Cc: "Rajasekhar_Allala" <[email protected]>
> Sent: Friday, 8 July, 2011 5:50:20 AM
> Subject: Re: [spectrum] Silence Ports
>
> I finally got around to trying this. It does not seem to have any
> effect. Alarms continue to generate for these switch ports with
> polling=no and poll_port_status=no. Actually, I checked a few of the
> other ports on the switch and the poll port status attribute looks
> like it is no by default. What is the purpose of the polling
> toggle? It certainly does not seem intuitive. I could understand if
> polling was set to no, but a trap still caused an alarm (maybe
> "Disable trap-based events" would stop that! Naaaaaaah! Thats crazy
> talk!). That does not appear to be the case here. Spectrum is
> polling the device, seeing the port down, ignoring the poll status,
> and generating an alarm ("BAD LINK DETECTED"). I can't find anything
> in my 59 Spectrum documents that says what the "Generate Alarm on
> Port" and "Generate Alarm on Device" do.
>
> I have hyper-extended my middle finger in the direction of my
> Spectrum server.
>
> -Ken
>
> On Jun 19, 2011, at 11:03 PM, Rajasekhar_Allala wrote:
>
> > Hi Ken,
> >
> > Set polling status as well as poll port status (port) values to No.
> >
> > I hope, it helps.
> >
> > Regards
> > Rajashekar
> >
> >
> > -----Original Message-----
> > From: Kenneth Kirchner [mailto:[email protected]]
> > Sent: Monday, June 20, 2011 11:22 AM
> > To: spectrum
> > Subject: [spectrum] Silence Ports
> >
> > What is the best way to silence a port on a switch or router that
> > you never want to hear from again? Is it as simple as disabling
> > polling? Will that prevent traps on that interface from generating
> > alarms as well? We have a few ports with devices that we have no
> > control over and no responsibility to monitor, so we want to
> > remove that noise from our monitoring. We are currently stuffing
> > these in maintenance mode, but that does not appear optimal.
> >
> > -Ken
> > Spectrum 9.2 H03
> >
> >
> > ---
> > To unsubscribe from spectrum, send email to [email protected] with
> > the body: unsubscribe spectrum
> > [email protected]
> >
> >
> > ________________________________
> >
> > DISCLAIMER:
> > This email (including any attachments) is intended for the sole use
> > of the intended recipient/s and may contain material that is
> > CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or
> > reliance by others or copying or distribution or forwarding of any
> > or all of the contents in this message is STRICTLY PROHIBITED. If
> > you are not the intended recipient, please contact the sender by
> > email and delete all copies; your cooperation in this regard is
> > appreciated.
> >
> > ---
> > To unsubscribe from spectrum, send email to [email protected] with
> > the body: unsubscribe spectrum [email protected]
>
>
> ---
> To unsubscribe from spectrum, send email to [email protected] with the
> body: unsubscribe spectrum [email protected]
>
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]
