| Author |
Message |
Colin (615498)
Guest
|
 Posted:
Fri Jan 07, 2005 11:13 am Post subject:
state alert properties |
|
|
Rule: The WMI Service is not running
How can the above rule be extended to resolve the alert when the service
returns to a running state? 'state alert properties' seems to be the right
place for such a feature.
This is the condition for a service started or starting:
AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "4" OR
AttributeValue(Parameter 9)= "2")
yet I cannot see how to set the alert severity correctly.
Colin. |
|
| Back to top |
|
 |
Mark
Guest
|
| Posted:
Fri Jan 07, 2005 7:53 pm Post subject:
RE: state alert properties |
|
|
I tried to modify this and also created a new rule to monitor all services
set to automatic, following the suggestions from a response to my question
and I get...
I created and also tried to modify the WMI event to have MOM alert when ANY
service set to Automatic has a state change from running to stop. When I
applied the rule I get slammed with emails/pages from every service on every
agent saying that the service has gone from unknown to running. I have to
disable the service to stop this.
did you have this problem when you modified WMI service state?
"Colin (615498)" wrote:
| Quote: | Rule: The WMI Service is not running
How can the above rule be extended to resolve the alert when the service
returns to a running state? 'state alert properties' seems to be the right
place for such a feature.
This is the condition for a service started or starting:
AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "4" OR
AttributeValue(Parameter 9)= "2")
yet I cannot see how to set the alert severity correctly.
Colin.
|
|
|
| Back to top |
|
|
Murugesan Vivekananthan [
Guest
|
| Posted:
Sat Jan 08, 2005 12:40 am Post subject:
Re: state alert properties |
|
|
Following Rule monitors the WMI Service.
Microsoft Operations Manager\Operations Manager 2005\Agents on all MOM
roles\The WMI Service is not running
Criteria:
Event Number equals '21207'
Source Name equals 'Microsoft Operations Manager'
Parameter 5 equals 'winmgmt'
State Alert Criteria:
If AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "1" OR
AttributeValue(Parameter 9)= "3") Critical Error
Else No Problem
Meaning:
When the service is set to "automatic" and state of service is in "stopped"
or "stopped pending", create a new alet and set the state of "WMI" component
to "Critical Error"
In all other conditions change the alert to "Inactive" and set the state of
"WMI Component" to "Success"
Conclusion:
This rule provides the functionality for alert status and state status.
Please note that an "Inactive" alert is similar to a "resolved" alert except
the fact that it changed some component to a "Green" state.
More Information:
State alerts use a "problem state" value which shows the current state of an
alert raised for state monitoring (traditional non-state based alerts use
the "investigate" value for the problem state field). The following values
are possible for problem state:
.. Active - A new (red- or yellow-based) state alert that is active. For
example, a service has stopped and state has been set red.
.. Inactive - An inactive (red- or yellow-based) state alert where the
problem has been resolved, as determined by state monitoring. For example, a
service has started running and state shows green for the alert. In this
case, the original alert will still be visible in the Operations console;
however, the problem state will show "Inactive".
.. Investigate - Used for non-state based rules.
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------
"Colin (615498)" <@.c> wrote in message
news:%23NyXeeH9EHA.2608@TK2MSFTNGP10.phx.gbl...
| Quote: | Rule: The WMI Service is not running
How can the above rule be extended to resolve the alert when the service
returns to a running state? 'state alert properties' seems to be the
right
place for such a feature.
This is the condition for a service started or starting:
AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "4" OR
AttributeValue(Parameter 9)= "2")
yet I cannot see how to set the alert severity correctly.
Colin.
|
|
|
| Back to top |
|
|
Colin (615498)
Guest
|
| Posted:
Mon Jan 10, 2005 6:22 am Post subject:
Re: state alert properties |
|
|
Mark,
Yes I did, however I think this is a once only occurance as the state of the
service is actually unknown, and once the state is known, which is 'running'
then it settles down and only alerts when it should. So you should allow a
period of time for all service states to become known before enabling your
production alert notification.
Colin.
"Mark" <Mark@discussions.microsoft.com> wrote in message
news:4ADDDB08-5C97-4005-9F40-BB7C96E8E38A@microsoft.com...
I tried to modify this and also created a new rule to monitor all services
set to automatic, following the suggestions from a response to my question
and I get...
I created and also tried to modify the WMI event to have MOM alert when ANY
service set to Automatic has a state change from running to stop. When I
applied the rule I get slammed with emails/pages from every service on every
agent saying that the service has gone from unknown to running. I have to
disable the service to stop this.
did you have this problem when you modified WMI service state?
"Colin (615498)" wrote:
| Quote: | Rule: The WMI Service is not running
How can the above rule be extended to resolve the alert when the service
returns to a running state? 'state alert properties' seems to be the
right
place for such a feature.
This is the condition for a service started or starting:
AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "4" OR
AttributeValue(Parameter 9)= "2")
yet I cannot see how to set the alert severity correctly.
Colin.
|
|
|
| Back to top |
|
|
Colin (615498)
Guest
|
| Posted:
Mon Jan 10, 2005 11:27 am Post subject:
Re: state alert properties |
|
|
I would like to check all automatic services with one rule, not just
winmgmt, however removing param5 from the criteria results in no seperation
of events for each service. How can this be achieved?
"Murugesan Vivekananthan [MSFT]" <vivekm@online.microsoft.com> wrote in
message news:uYSCdhO9EHA.3828@TK2MSFTNGP09.phx.gbl...
Following Rule monitors the WMI Service.
Microsoft Operations Manager\Operations Manager 2005\Agents on all MOM
roles\The WMI Service is not running
Criteria:
Event Number equals '21207'
Source Name equals 'Microsoft Operations Manager'
Parameter 5 equals 'winmgmt'
State Alert Criteria:
If AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "1" OR
AttributeValue(Parameter 9)= "3") Critical Error
Else No Problem
Meaning:
When the service is set to "automatic" and state of service is in "stopped"
or "stopped pending", create a new alet and set the state of "WMI" component
to "Critical Error"
In all other conditions change the alert to "Inactive" and set the state of
"WMI Component" to "Success"
Conclusion:
This rule provides the functionality for alert status and state status.
Please note that an "Inactive" alert is similar to a "resolved" alert except
the fact that it changed some component to a "Green" state.
More Information:
State alerts use a "problem state" value which shows the current state of an
alert raised for state monitoring (traditional non-state based alerts use
the "investigate" value for the problem state field). The following values
are possible for problem state:
.. Active - A new (red- or yellow-based) state alert that is active. For
example, a service has stopped and state has been set red.
.. Inactive - An inactive (red- or yellow-based) state alert where the
problem has been resolved, as determined by state monitoring. For example, a
service has started running and state shows green for the alert. In this
case, the original alert will still be visible in the Operations console;
however, the problem state will show "Inactive".
.. Investigate - Used for non-state based rules.
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------
"Colin (615498)" <@.c> wrote in message
news:%23NyXeeH9EHA.2608@TK2MSFTNGP10.phx.gbl...
| Quote: | Rule: The WMI Service is not running
How can the above rule be extended to resolve the alert when the service
returns to a running state? 'state alert properties' seems to be the
right
place for such a feature.
This is the condition for a service started or starting:
AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "4" OR
AttributeValue(Parameter 9)= "2")
yet I cannot see how to set the alert severity correctly.
Colin.
|
|
|
| Back to top |
|
|
Mark
Guest
|
| Posted:
Wed Jan 12, 2005 1:01 am Post subject:
Re: state alert properties |
|
|
Colin,
I accomplished this by coping the "WMI is not running" rule in Agents
on all mom roles" and modifying it. First i removed the WMI from the
advanced criteria and then enabled these state alert properites--
AttributeValue(Parameter 10)=2 AND AttributeValue(Parameter 9)="1"
This stopped my previous problem of getting slammed w. events that services
were started/stopped. However, I also wanted to know when the service that
stopped restarted so I had to create another rule, copied the one I just
created and set the state alert properties to----- AttributeValue(Parameter
10)=2 AND AttributeValue(Parameter 8)="1" AND AttributeValue(Parameter 9)=4
This is probably a dumb way of doing this but it seems to work for me!
"Colin (615498)" wrote:
| Quote: | I would like to check all automatic services with one rule, not just
winmgmt, however removing param5 from the criteria results in no seperation
of events for each service. How can this be achieved?
"Murugesan Vivekananthan [MSFT]" <vivekm@online.microsoft.com> wrote in
message news:uYSCdhO9EHA.3828@TK2MSFTNGP09.phx.gbl...
Following Rule monitors the WMI Service.
Microsoft Operations Manager\Operations Manager 2005\Agents on all MOM
roles\The WMI Service is not running
Criteria:
Event Number equals '21207'
Source Name equals 'Microsoft Operations Manager'
Parameter 5 equals 'winmgmt'
State Alert Criteria:
If AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "1" OR
AttributeValue(Parameter 9)= "3") Critical Error
Else No Problem
Meaning:
When the service is set to "automatic" and state of service is in "stopped"
or "stopped pending", create a new alet and set the state of "WMI" component
to "Critical Error"
In all other conditions change the alert to "Inactive" and set the state of
"WMI Component" to "Success"
Conclusion:
This rule provides the functionality for alert status and state status.
Please note that an "Inactive" alert is similar to a "resolved" alert except
the fact that it changed some component to a "Green" state.
More Information:
State alerts use a "problem state" value which shows the current state of an
alert raised for state monitoring (traditional non-state based alerts use
the "investigate" value for the problem state field). The following values
are possible for problem state:
.. Active - A new (red- or yellow-based) state alert that is active. For
example, a service has stopped and state has been set red.
.. Inactive - An inactive (red- or yellow-based) state alert where the
problem has been resolved, as determined by state monitoring. For example, a
service has started running and state shows green for the alert. In this
case, the original alert will still be visible in the Operations console;
however, the problem state will show "Inactive".
.. Investigate - Used for non-state based rules.
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------
"Colin (615498)" <@.c> wrote in message
news:%23NyXeeH9EHA.2608@TK2MSFTNGP10.phx.gbl...
Rule: The WMI Service is not running
How can the above rule be extended to resolve the alert when the service
returns to a running state? 'state alert properties' seems to be the
right
place for such a feature.
This is the condition for a service started or starting:
AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "4" OR
AttributeValue(Parameter 9)= "2")
yet I cannot see how to set the alert severity correctly.
Colin.
|
|
|
| Back to top |
|
|
Michiel Dulfer
Guest
|
| Posted:
Mon Jan 17, 2005 3:00 pm Post subject:
Re: state alert properties |
|
|
Yes!
### MOM Script
Dim TargetNetbiosComputer
TargetNetbiosComputer = "."
Dim WMIObject
Set WMIObject = GetObject("winmgmts:\\" & TargetNetbiosComputer &
"\root\cimv2")
Dim AutomaticServices
set AutomaticServices = WMIObject.ExecQuery("Select * from Win32_Service
where StartMode='Auto'",,48)
Dim AutomaticService
For Each AutomaticService In AutomaticServices
If AutomaticService.State <> "Running" then
CreateEvent AutomaticService
End If
Next
Set AutomaticServices = Nothing
Set WMIObject = Nothing
Sub CreateEvent(ServiceName)
Dim NewEvent
Set NewEvent=ScriptContext.CreateEvent
NewEvent.EventSource = "Check automatic services"
NewEvent.EventNumber = 1000
NewEvent.EventType = 1 ' ## ERROR
NewEvent.Message = "Service " & ServiceName & " is not running"
ScriptContext.Submit NewEvent
Set NewEvent = nothing
End Sub
### /MOM Script
"Colin (615498)" <@.c> wrote in message
news:ut0iJUt9EHA.2788@TK2MSFTNGP10.phx.gbl...
| Quote: | I would like to check all automatic services with one rule, not just
winmgmt, however removing param5 from the criteria results in no
seperation
of events for each service. How can this be achieved?
"Murugesan Vivekananthan [MSFT]" <vivekm@online.microsoft.com> wrote in
message news:uYSCdhO9EHA.3828@TK2MSFTNGP09.phx.gbl...
Following Rule monitors the WMI Service.
Microsoft Operations Manager\Operations Manager 2005\Agents on all MOM
roles\The WMI Service is not running
Criteria:
Event Number equals '21207'
Source Name equals 'Microsoft Operations Manager'
Parameter 5 equals 'winmgmt'
State Alert Criteria:
If AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "1"
OR
AttributeValue(Parameter 9)= "3") Critical Error
Else No Problem
Meaning:
When the service is set to "automatic" and state of service is in
"stopped"
or "stopped pending", create a new alet and set the state of "WMI"
component
to "Critical Error"
In all other conditions change the alert to "Inactive" and set the state
of
"WMI Component" to "Success"
Conclusion:
This rule provides the functionality for alert status and state status.
Please note that an "Inactive" alert is similar to a "resolved" alert
except
the fact that it changed some component to a "Green" state.
More Information:
State alerts use a "problem state" value which shows the current state of
an
alert raised for state monitoring (traditional non-state based alerts use
the "investigate" value for the problem state field). The following values
are possible for problem state:
. Active - A new (red- or yellow-based) state alert that is active. For
example, a service has stopped and state has been set red.
. Inactive - An inactive (red- or yellow-based) state alert where the
problem has been resolved, as determined by state monitoring. For example,
a
service has started running and state shows green for the alert. In this
case, the original alert will still be visible in the Operations console;
however, the problem state will show "Inactive".
. Investigate - Used for non-state based rules.
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no
rights.
---------------------------------------------------------
"Colin (615498)" <@.c> wrote in message
news:%23NyXeeH9EHA.2608@TK2MSFTNGP10.phx.gbl...
Rule: The WMI Service is not running
How can the above rule be extended to resolve the alert when the service
returns to a running state? 'state alert properties' seems to be the
right
place for such a feature.
This is the condition for a service started or starting:
AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "4" OR
AttributeValue(Parameter 9)= "2")
yet I cannot see how to set the alert severity correctly.
Colin.
|
|
|
| Back to top |
|
|
Blake Mengotto
Guest
|
| Posted:
Fri Jan 21, 2005 6:48 am Post subject:
Re: state alert properties |
|
|
This is awesome! Thanks Mike!
/salute
--
Regards,
Blake Mengotto
Email: mengotto@nospam.hotmail.com
"MOM 2000/2005 - The ultimate solution for monitoring/managing your Windows
OS and applications."
http://www.momanswers.com - MOM solution center resource
http://www.microsoft.com/mom - MOM Application site
http://www.silect.com - MOM Health Reporter
http://www.excsoftware.com - MOM solution provider
"Michiel Dulfer" <m.dulfer @ planettechnologies.nl> wrote in message
news:OMJ6uLH$EHA.3700@tk2msftngp13.phx.gbl...
| Quote: | Yes!
### MOM Script
Dim TargetNetbiosComputer
TargetNetbiosComputer = "."
Dim WMIObject
Set WMIObject = GetObject("winmgmts:\\" & TargetNetbiosComputer &
"\root\cimv2")
Dim AutomaticServices
set AutomaticServices = WMIObject.ExecQuery("Select * from Win32_Service
where StartMode='Auto'",,48)
Dim AutomaticService
For Each AutomaticService In AutomaticServices
If AutomaticService.State <> "Running" then
CreateEvent AutomaticService
End If
Next
Set AutomaticServices = Nothing
Set WMIObject = Nothing
Sub CreateEvent(ServiceName)
Dim NewEvent
Set NewEvent=ScriptContext.CreateEvent
NewEvent.EventSource = "Check automatic services"
NewEvent.EventNumber = 1000
NewEvent.EventType = 1 ' ## ERROR
NewEvent.Message = "Service " & ServiceName & " is not running"
ScriptContext.Submit NewEvent
Set NewEvent = nothing
End Sub
### /MOM Script
"Colin (615498)" <@.c> wrote in message
news:ut0iJUt9EHA.2788@TK2MSFTNGP10.phx.gbl...
I would like to check all automatic services with one rule, not just
winmgmt, however removing param5 from the criteria results in no
seperation
of events for each service. How can this be achieved?
"Murugesan Vivekananthan [MSFT]" <vivekm@online.microsoft.com> wrote in
message news:uYSCdhO9EHA.3828@TK2MSFTNGP09.phx.gbl...
Following Rule monitors the WMI Service.
Microsoft Operations Manager\Operations Manager 2005\Agents on all MOM
roles\The WMI Service is not running
Criteria:
Event Number equals '21207'
Source Name equals 'Microsoft Operations Manager'
Parameter 5 equals 'winmgmt'
State Alert Criteria:
If AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)=
"1"
OR
AttributeValue(Parameter 9)= "3") Critical Error
Else No Problem
Meaning:
When the service is set to "automatic" and state of service is in
"stopped"
or "stopped pending", create a new alet and set the state of "WMI"
component
to "Critical Error"
In all other conditions change the alert to "Inactive" and set the state
of
"WMI Component" to "Success"
Conclusion:
This rule provides the functionality for alert status and state status.
Please note that an "Inactive" alert is similar to a "resolved" alert
except
the fact that it changed some component to a "Green" state.
More Information:
State alerts use a "problem state" value which shows the current state
of
an
alert raised for state monitoring (traditional non-state based alerts
use
the "investigate" value for the problem state field). The following
values
are possible for problem state:
. Active - A new (red- or yellow-based) state alert that is active. For
example, a service has stopped and state has been set red.
. Inactive - An inactive (red- or yellow-based) state alert where the
problem has been resolved, as determined by state monitoring. For
example,
a
service has started running and state shows green for the alert. In this
case, the original alert will still be visible in the Operations
console;
however, the problem state will show "Inactive".
. Investigate - Used for non-state based rules.
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no
rights.
---------------------------------------------------------
"Colin (615498)" <@.c> wrote in message
news:%23NyXeeH9EHA.2608@TK2MSFTNGP10.phx.gbl...
Rule: The WMI Service is not running
How can the above rule be extended to resolve the alert when the
service
returns to a running state? 'state alert properties' seems to be the
right
place for such a feature.
This is the condition for a service started or starting:
AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "4"
OR
AttributeValue(Parameter 9)= "2")
yet I cannot see how to set the alert severity correctly.
Colin.
|
|
|
| Back to top |
|
|
Michiel Dulfer
Guest
|
| Posted:
Sun Jan 23, 2005 9:23 pm Post subject:
Re: state alert properties |
|
|
NP :-)
I use this script in a much more advanced version myself, including repair
actions, perfcounters, uptime reporting, backwards compatibility with MOM
2000 etc! (1500 lines!)
"Blake Mengotto" <mengotto@nospam.hotmail.com> wrote in message
news:OcJy762$EHA.4092@TK2MSFTNGP09.phx.gbl...
| Quote: | This is awesome! Thanks Mike!
/salute
--
Regards,
Blake Mengotto
Email: mengotto@nospam.hotmail.com
"MOM 2000/2005 - The ultimate solution for monitoring/managing your
Windows
OS and applications."
http://www.momanswers.com - MOM solution center resource
http://www.microsoft.com/mom - MOM Application site
http://www.silect.com - MOM Health Reporter
http://www.excsoftware.com - MOM solution provider
"Michiel Dulfer" <m.dulfer @ planettechnologies.nl> wrote in message
news:OMJ6uLH$EHA.3700@tk2msftngp13.phx.gbl...
Yes!
### MOM Script
Dim TargetNetbiosComputer
TargetNetbiosComputer = "."
Dim WMIObject
Set WMIObject = GetObject("winmgmts:\\" & TargetNetbiosComputer &
"\root\cimv2")
Dim AutomaticServices
set AutomaticServices = WMIObject.ExecQuery("Select * from Win32_Service
where StartMode='Auto'",,48)
Dim AutomaticService
For Each AutomaticService In AutomaticServices
If AutomaticService.State <> "Running" then
CreateEvent AutomaticService
End If
Next
Set AutomaticServices = Nothing
Set WMIObject = Nothing
Sub CreateEvent(ServiceName)
Dim NewEvent
Set NewEvent=ScriptContext.CreateEvent
NewEvent.EventSource = "Check automatic services"
NewEvent.EventNumber = 1000
NewEvent.EventType = 1 ' ## ERROR
NewEvent.Message = "Service " & ServiceName & " is not running"
ScriptContext.Submit NewEvent
Set NewEvent = nothing
End Sub
### /MOM Script
"Colin (615498)" <@.c> wrote in message
news:ut0iJUt9EHA.2788@TK2MSFTNGP10.phx.gbl...
I would like to check all automatic services with one rule, not just
winmgmt, however removing param5 from the criteria results in no
seperation
of events for each service. How can this be achieved?
"Murugesan Vivekananthan [MSFT]" <vivekm@online.microsoft.com> wrote in
message news:uYSCdhO9EHA.3828@TK2MSFTNGP09.phx.gbl...
Following Rule monitors the WMI Service.
Microsoft Operations Manager\Operations Manager 2005\Agents on all MOM
roles\The WMI Service is not running
Criteria:
Event Number equals '21207'
Source Name equals 'Microsoft Operations Manager'
Parameter 5 equals 'winmgmt'
State Alert Criteria:
If AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)=
"1"
OR
AttributeValue(Parameter 9)= "3") Critical Error
Else No Problem
Meaning:
When the service is set to "automatic" and state of service is in
"stopped"
or "stopped pending", create a new alet and set the state of "WMI"
component
to "Critical Error"
In all other conditions change the alert to "Inactive" and set the
state
of
"WMI Component" to "Success"
Conclusion:
This rule provides the functionality for alert status and state status.
Please note that an "Inactive" alert is similar to a "resolved" alert
except
the fact that it changed some component to a "Green" state.
More Information:
State alerts use a "problem state" value which shows the current state
of
an
alert raised for state monitoring (traditional non-state based alerts
use
the "investigate" value for the problem state field). The following
values
are possible for problem state:
. Active - A new (red- or yellow-based) state alert that is active. For
example, a service has stopped and state has been set red.
. Inactive - An inactive (red- or yellow-based) state alert where the
problem has been resolved, as determined by state monitoring. For
example,
a
service has started running and state shows green for the alert. In
this
case, the original alert will still be visible in the Operations
console;
however, the problem state will show "Inactive".
. Investigate - Used for non-state based rules.
--
---------------------------------------------------------
Murugesan Vivekananthan [MSFT]
MOM Test Team
This posting is provided "AS IS" with no warranties, and confers no
rights.
---------------------------------------------------------
"Colin (615498)" <@.c> wrote in message
news:%23NyXeeH9EHA.2608@TK2MSFTNGP10.phx.gbl...
Rule: The WMI Service is not running
How can the above rule be extended to resolve the alert when the
service
returns to a running state? 'state alert properties' seems to be the
right
place for such a feature.
This is the condition for a service started or starting:
AttributeValue(Parameter 10) = 2 AND (AttributeValue(Parameter 9)= "4"
OR
AttributeValue(Parameter 9)= "2")
yet I cannot see how to set the alert severity correctly.
Colin.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in