Hello,

in the Policy Manager xml file 
"$specroot/PolicyMgmt/Spectrum/policy-settings-spectrum.xml you can find some 
hints

The Port Fault Management Settings Template contains all attributes
that can be maintained by the Port Fault Management Policy.
        
PollPortStatus (0x1280a) - Controls status polling of a port
                                   whose connectivity is not modelled.
                                   Valid values are TRUE or FALSE.
        
ok_to_poll (0x11dd8) - Used to make the pipe associated with this
                               port "live".  The status of the port will
                               be polled.  Valid values are TRUE or FALSE.:

There are also some pre-defined policies, which explain this attributes a 
little bit:

<!--
        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" />
...

 <!--
        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" />
...

    <!--
        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" />
...

Maybe this helps a little bit.

Regards
--
Christoph Keßler
amasol AG                    [email protected]
Campus Neue Balan            Phone:+49 (89) 1894743-24
Claudius-Keller-Straße 3 B   Fax:  +49 (89) 1894743-99
81669 München, Germany       Web:  www.amasol.de

amasol Aktiengesellschaft für Informations- und Kommunikationstechnologie
Aufsichtsrat: Prof. Dr. Stephan Kaiser (Vorsitzender)
Vorstand: Wolfgang Bachmann, Stefan Deml, Thomas Dirsch, Frank Jahn, Johann 
Maurer
Amtsgericht München HRB 128327, Sitz der Gesellschaft München
________________________________________
Von: [email protected] [[email protected]]
Gesendet: Donnerstag, 21. Juli 2011 13:15
An: spectrum
Betreff: [spectrum] PollPortStatus & OKtoPoll attributes

Greetings

We are bringing up a new Spectrum 0.2 environment and I have noticed what
appears to be some differences in the way port polling is controlled -
compared to older releases.

In the past - I could control port level polling with the attribute
OKtoPoll.

In 9.2, I see there is another attribute - PollPortStatus.

This value is defaulting to TRUE on many of my discovered devices/ports.
Even though OKtoPoll is FALSE - the ports are still polled.

Can someone please tell me what the precedence between these two attributes
are?

Also - If I set all ports on a device to PollPortStatus == FALSE and allow
my Policy to set OKtoPoll to TRUE for selected ports - will these ports be
polled for status or do I need to also set PollPortStatus in the policy?

Thanks

Dan Ellsweig

Enterprise Management Systems
Avon Products
1 Avon Plaza
Rye, NY 10830

914-935-2723



---
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]

Reply via email to