SMC 3.0 - Prob in acknowledging alarms

Hi,
I am using Sun Management Center 3.0, Solaris 8, E450 box. While tryin to acknowledge any alarms I am getting the below error.
"Exception occured while acknowledging alarm
Error in action on - acknowledging alarm
Agent is not responding"
It would be great if anyone can shed some light in it.
Thank you,
Manjunath

Hi Manjunath
Don't know whether you are still having the same problem, but mine was being caused by the fact that each agents hostname was not present in the Sun MC Servers hosts file. This I found annoying as I hadnt used hostnames when I setup the agents, and there is no mention of this in any of the documentation.
It actually took Sun over 2 months to spot it, they had me trying everything to get this sorted, but it was the hosts file that was the problem.
So make sure that the server can resolve the agents hostname correctly.
Hope this helps you are someone else.
Regards
Steve York

Similar Messages

Error acknowledging alarms 3.6.1

Hi everybody
I regularly (but not everytime) have the problem that I can't acknowledge an alarm in 3.6.1. SMC shows the alarm notification and I can also display the alarm in the hosts properties window . Howevery, when clicking the "Acknowledge Button" I just get this error window:
Exception occured while acknowledging alarms.
Set timeout for null socket
Any ideas?
Greetings
Dominik

I dont think I've ran into that exact error message before, but this could be some type of communication issue. BTW..I'm defintately not an expert and am just shooting in the dark here. If it is a communication problem there are many factors here that could come into play. Are you using the java console?..from where are you trying to ack them?..on the server the agent is running on themselves or connecting remotely?.. can you do an smnpwalk from the server to the agent and vice versa when this occurs? Have you been through all the logs on the agent/master server?..Does this always happen on the same agents?...

Can't acknowledge alarms on some clients

With certain clients, it appears there is full functionality (load/unload modules, monitor, etc.) with the exception of acknowledging alarms. When an attempt is made to acknowledge an alarm, the error message is "...No response from agent."
Any help is greatly appreciated!
J. Holly

Keep in mind when you click on the that alarm tab to are not talking to the agent, but the SunMC backend at the servber layer. Most of the time this issue is fixed by placing the server in the agent's host file and the agent in the server's host file and using files before nis on both....console as well.

Acknowledging alarms in remote server context

Hi there,
Just wondering.. If I have a local SunMC server and a remote SunMC server which is referenced to the local one, is it possible to acknowledge alarms without logging into the remote server console?
The error I'm getting is: "Exception occured while acknowledging alarms. The node is not in the current server context. No allowed action -- acknowledging alarm"
I know this is the default security policy, but is there any way to open this so I can just acknowledge alarms?
Communication between server contexts is done with the user "espublic", I tried adding this user, giving it access to SunMC and adding espublic to the group "esops" but that gives users access to almost everything on the remote server, even if they have read-only rights on the local server, .....not really an option ;-)
Edited by: Emerald on Sep 13, 2007 1:00 AM

Emerald wrote:
Just wondering.. If I have a local SunMC server and a remote SunMC server which is referenced to the local one, is it possible to acknowledge alarms without logging into the remote server console?As far as I know you can't ack it from the remote-server-context-Console unless you start playing it fast and loose with the security settings (as you've already noticed).
Are you trying to do this so you can "stack" SunMC Servers (i.e. have one Server that can see all the Agents in other Servers) or are you just trying to ack from another tool that isn't SunMC? If you're just looking for a way to ack from outside, EventAction can be configured to receive SNMP traps to ack alarms:
http://www.halcyoninc.com/products/EventAction/help/HALEventAction-remote-acknowledging-h.html
Regards,
[email protected]
http://www.HalcyonInc.com
New !! : http://forums.HalcyonInc.com !!

SMC 3.6 Cannot send email alarm

Dear All ,
I just try SMC 3.6 ,on the server i am configure sendmail and test send email working fine ,but when i try attribut set to send email outside ,script email.sh not send alarm notify to send out email , i try also email to localhost smc server but not yet working ? any idea ?
regards
hadi

Hi Hadi,
The Release Notes say the "usermod" command listed in your URL may not work: maybe you can make the file changes by hand?:
http://docs.sun.com/app/docs/doc/817-7553/6mms6q1ia?a=view
Regards,
[email protected]

Data Logging and Supervisory Control (DSC) Alarm Acknowledge / General Alarm Questions

Hi All -
I would like to know if anyone can help me with DSC and alarms. I have several shared variables that I have setup with alarms and logging with DSC. I can view them with the Shared Variable Manager, the value, status, alarm state, etc. So, I want to be able to view this info on my Front Panel and acknowledge alarms there - - Is that possible? I put "alarm and event display.vi" on my front panel and it shows when a variable goes to alarm state, but I don't see how to acknowledge the alarm once it enters the alarm state.
Other question, once a variable is in an alarm state, obviously it stays there until it is no longer in alarm, but if you acknowledge it - - what happens? does it stay 'red' color and remain in the alarm list - and what about logging, does the log indicate when the alarm was acknowledged any by whom?
So that is my next question, how do I setup and force a user to 'log-on' to be able to acknowledge alarms?
If anyone could point me at a document / tutorial / example I would really appreciate it!
Thanks!
Get Mystified

Mystic wrote:
Hi All -
I would like to know if anyone can help me with DSC and alarms. I have several shared variables that I have setup with alarms and logging with DSC. I can view them with the Shared Variable Manager, the value, status, alarm state, etc. So, I want to be able to view this info on my Front Panel and acknowledge alarms there - - Is that possible? I put "alarm and event display.vi" on my front panel and it shows when a variable goes to alarm state, but I don't see how to acknowledge the alarm once it enters the alarm state.
Other question, once a variable is in an alarm state, obviously it stays there until it is no longer in alarm, but if you acknowledge it - - what happens? does it stay 'red' color and remain in the alarm list - and what about logging, does the log indicate when the alarm was acknowledged any by whom?
So that is my next question, how do I setup and force a user to 'log-on' to be able to acknowledge alarms?
If anyone could point me at a document / tutorial / example I would really appreciate it!
Thanks!
Get Mystified
When your VI is running, you can right-click on the alarm & event display control and it will give you the option of acknowledging the alarm. Another option would be to use the Acknowledge Alarm.vi and create your own interface.
Once the alarm is acknowledged, the alarm color will change to magenta and the acknowledgement information will be displayed.
The acknowledgement information - user, time, comment - will be logged if logging alarms is enabled.
Regards,
Robert

LabVIEW DSC: How to get alarm status from the area?

Colleagues,
I have, lets say, 50 Shared Variables where alarming enabled. Some of these variables assigned to area, so I can get status of the entire area or acknowledge an entire area of alarms (prior to version 8.x there was groups of the tags).
Now I would like to get alarm status from the entire area. How can I do it?
In version 6 I was able to wire tag group to Get Alarm Summary Status. Now, in version 8, Alarm Status.vi can be wired to the array of the variables, but not to area. Is it possible to get all variables from the area?
regards,
Andrey.

I am not sure if I should be posting my problem under this particular topic. I am having trouble understanding acknowledge alarm vi and what this vi is supposed to do is not clear to me yet.
I have around 300 shared variables in my project and I have created a particular vi just to view the alarms that may pop up during runs. I created a main menu and this alarm vi can be accessed upon a button click in the main menu. Users get alarm alert based on sound configuration. Then he can navigate to the alarm vi and acknowledge the alarm. The alarm vi only contains alarm and event display found under DSC module.
The problem is everytime I click the alarm button in the main menu, it takes around 2 minutes for the alarm vi to update which is very annoying and unsatisfactory in the middle of run. I am not sure why it happens and I haven't got any response from support yet. These shared variables are managed under 10 different library files that are set up based on different loops of the process (flow, pressure and so on).
Then I looked into three alarm examples that ship with DSC module. None of these examples use acknowledge alarm vi. I implemented another vi similar to alarm demo vi in that example - containing multicolumn listbox. I created acknowledge event containing acknowledge button and used the acknowledge alarm vi under this event. Read vi alarm is under timeout event.
When I click the acknowledge button as soon as I see the alarm in multicolumn listbox, nothing happens - the color of font does not get changed to purple neither any alarms get acknowledged. I tried to aknowledge alarm by variable name or alarms or alarm area, it does not give me anything. What is this acknowledge alarm supposed to do? I tried to find examples everywhere in the web that uses this particular vi and haven't found one yet.

Problems with the Acknowledged propertie in the WCS

Hello,
I have a problem with the ACK propertie in the WCS. I check a logg entrie in the logg with the ACK, in few seconds/minute/hour this alarm disappear, and then if this alarm appear again, this message show the ACK marked.
Should not receive the message again without the ACK marking? what is the problem?
Thanks in advanced

Hello,
According also to what is stated in the official guides, this seems to be the expected behavior:
"You can acknowledge the alarm to prevent it from showing up in the Alarm Summary page. The alarm remains in WCS and you can search for all Acknowledged alarms using the alarm search functionality."
http://www.cisco.com/en/US/docs/wireless/wcs/7.0/configuration/guide/7_0event.html#wp1229996
So you can acknowledge that specific alarm once to not show it in the alarm page anymore, only for that occurrence. If however the alarm occurs again, the new occurrence will show up and let you know that you previously acknowledge a similar instance.
Hope this clarifies the behavior,
Fede
If this answers your question please mark the question as "answered" and rate it, so other users can easily find it.

Lookout 6.02 Hypertrend and Alarms only Issue

I recently upgraded from lookout 4.5 to 6.02. Since the upgrade I have seen two issues. The lookout 6.02 clients show all alarms and events even when the alarms only filter is selected. This only happens on the client application, the server / development server applications run fine.
The second and bigger issue is that my hypertrends are all over the place. I look at the trends on the server and they look correct. The same trend on the client application shows gaps on the trend where no data is plotted then the data continues. I have gone to several clients and I am seeing inconsistent trending on each client data just keeps disappearing in different places on the grid. I do have the 6.02 update files installed on the server. And the issue exists whether using the lookout hypertrend or the NI Active X hypertrend. It is almost like the client application needs to be updated as well. Reading other posts it appears that others have had similar hypertrend issues but I could not find that anyone had a resolution to the problem.
Has anyone else encountered/resolved these same issues? I am on the verge of trying to try rolling back to version 5.1 If I cant resolve this issue.

If you are using a free client software, not a server version, the client does not filter any alarms. It's a known issue in Lookout. There is a workaround right now, follow these steps to use NI AlarmEvent Browser ActiveX control.
Add the ActiveX object called NI AlarmEvent Browser to the Client Process.
On the Properties window for the ActiveX object, click on the Property Pages button.
Set the PopupMenu property to True and then set the Active property to True.
Exit and close out of the various property windows, saving the changes.
Drag the new ActiveX object onto the panel and size appropriately.
Go to Run Mode.
Right-click on the Alarm and Event Viewer and choose to Select Processes...
Select the server process you wish to monitor and click OK.
You should now see any active alarms and events. Right-click on the Alarm and Event Viewer again to set the Filter Options and acknowledge alarms.
The second question is also a know issue. Sometimes the hypertrend stops refreshing. It's maybe caused by a "missing data". This problem is to be fixed in the next version of Lookout.
Do you have a firewall enabled? If yes, I'd like you to disable it and see if hypertrend works.
Ryan Shi
National Instruments

"alarm and event display" crashes my application

Dear All,
I use the "alarm and event disply.vi" in my DSC application. It works fine: I can acknowledge alarms, events etc. BUT...
When I double click the alarm item (or press Alt-Enter) and watch the alarm properties in the Alarm Properties dialog, I can usually watch the properties for some time, selecting the next or previous alarm item, but most often than not, my application just crashes. I don't get any LabVIEW error dialogs. Only Windows is telling me that the application stopped working and it just closes giving me no explanation. Sometimes I don't even see the Windows message.
I've tried this on two different computers... same boat!
I'm using:
- LV2011
- Windows 7
In my application I create the shared variables programmatically, set alarm thresholds programmatically etc.
Anybody had the same problem?
regards
Witold Nocon

Well…I think I have isolated the problem, and I have recreated it in the Boiler example. Here’s what’s happening:
If you watch the properties of the alarm in the Alarm and Event Display, and if this alarm “disappears” at this time, the application will crash. This will happen for example when this variable is set to AUTO ACK.
You can try setting the R02 pump to zero. This will cause the L01 level to increase reporting an alarm. Now if you set the flows so that the level start decreasing (I set the outflow to max, and the inflow tozero), and immediately click the HI HI alarm and watch it’s properties, the application will crash at the time when this alarm is cleared due to the decreasing level (AUTO ACK).
It also seems a “little non-deterministic” but this may be my own impression.
Anybody had a similar problem or is able to recreate it?

Dsc 8.2 Acknowledge button...

Hi all,
1st problem:
Is this possible to use a button to acknowlege one alarm in the Alarm and event display (dsc 8.2) ? instead of using the right click on the selected alarm.
The idea is to select the alarm in the diplay and to use a button to acknowlege it.
2nd problem:
I'm able to generate an alarm in this diplay but not an event (green color). What is the way to do it ?
3rd problem:
Is this possible to disable the "Select processes" menu when you right click on the Alarm and event display ?
Thanks
Best Regards
Julien

Hi,
If you want to acknowledge an alarm using a boolean button on the front panel, I think you should use a LabVIEW function that install with the DSC module and called "acknowledge alarms.vi". To use this VI you have to connect the name of the shared you want to acknowlege alarms. You can use this function inside a case structure control by a boolean in the front panel.
For the other questions, I don't think it's possible since the "alarm and event display" is an activeX container for which we can't change the properties. We can access some properties and actions of the object using property and invoke nodes.
Regards,
ClémentG

Alarm and event notification DSC

I can't understand the functionality of these DSC VIs:
Acknowledge Alarms .vi
Set user Defined Alarms .vi
Request Alarm & Event Notifications .vi
I appreciate any guide.

Hi Maryam,
Acknowledge is where the sequence action that indicates recognition of a new alarm.
Where an alarm is an abnormal process condition. In the LabVIEW Datalogging and Supervisory Control (DSC) Module, an alarm occurs if a shared variable value goes out of its defined alarm limits or if a shared variable has bad status.
This is the URL of the DSC module Glossary:
http://zone.ni.com/reference/en-XX/help/370246D-01/lvdschelp/dsc_glossary/
If you want to know more about the general functionality of alarms and events and what to use specific VIs for.
The fisrst call as I said previously should be the context help, check the example library and the NI developer zone. Another reasource which you can check is the DCS module "VI, Function, & How-To Help".
Click on the "Help" then "VI, Function, & How-To Help", expand the following items in the tree structure "DSC Module"> "DSC Module VIs & Functions" > "Alarm & Events VIs".
For future reference it would be helpful in future if you gave more information in your posts eg what version of LabVIEW you are using - so can post back relevent versioned example code.
And what you are trying to do - why are you interested in the DSC alarm VIs, could make more specific replies given this information.
Sorry if my initial replies are basic but I had no way of knowing the level of information you were looking for and you did not say what you had already tried/ looked up.
Alarms can be used in many applications but as I said their basic functionality is to alert the user to an abnormal process condition eg sub/super limit values or bad status.
I hope the above helps but if you require more information please let me know what it is you specifically want to know.
Regards,
Emma Rogulska
NIUK & Ireland

DSC alarm set and cleared without operator ack - the variable should be not alarmed and not acked

We are deeply involved in porting our application from 7.1.1 to 8.6.1 under Windows XP.
Our application heavily depends on DSC and moving from 7.1.1 to 8.6.1 is actually much more than a simple porting....
here is our last problem:
it seems that there is no discrimination between 'active' alarms and 'acknowledged' alarms on a shared Variable in case the 'ack Type' is set to 'USER'.
Here is what happens:
1) a Boolean shared variable is defined to be alarmed when 'high' (TRUE) and its ack type is set to 'USER' (the operator at our application must ack alarms).
2) the Boolean var is set to TRUE -> it is declared alarmed (OK)  and not ack'ed (OK)
3) the operator ack the variable -> it is declared alarmed (OK)  and ack'ed (OK)
4) the Boolean var is set to FALSE -> it is declared not alarmed (OK)  and ack'ed (OK)
5) the Boolean var is set to TRUE -> it is declared alarmed (OK)  and not ack'ed (OK)
6) the Boolean var is set to FALSE -> it is declared alarmed (NOT OK!!!)  and not ack'ed (OK)
7) the operator ack the variable -> it is declared not alarmed (OK)  and ack'ed (OK)
This last case is the wrong situation: an alarm has been set and cleared without operator ack the variable should be not alarmed and not acked
Actually the variable returns OK only when ack'ed.
see the attached project in which a small vi and a small shared variable lvlib allows to repeat the above steps.
Note:
A) same situation applies to 'double' shared variable
B) under DSC version 7.1.1 everithing was OK
can anyone Help?
Thank You Guglielmo Rozera
Attachments:
AlmAckTest.zip ‏18 KB

Thank for your replay!
I have tried to undeploy and deploy the library with ack type set to 'User' by default, and then run the vi but the behavior is always the same.
The modification you suggest does not set 'User' ack type because data socket needs '2' as 'User ' setting while property node needs '1' or (better) its own enumerated type.
Anyway I've corrected the vi according to your suggestion and tried again but nothing changed...
Here I attach the project modified with property node and an indicator to show what is the actual ack type
I hope in your further investigations!
Thank You
Guglielmo
Attachments:
AlmAckTest_2.zip ‏20 KB

Site to Site VPN Problems With 2801 Router and ASA 5505

Hello,
I am having some issue setting up a site to site ipsec VPN between a Cisco 2801 router and a Cisco ASA 5505. I was told there was a vpn previously setup with an old hosting provider, but those connections have been servered. Right now I am trying to get the sites to talk to the 2801. Here ere are my current configs, please let me know if you need anything else. Im stumped on this one. Thanks.
IP scheme at SIte A:
IP    172.19.3.x
sub 255.255.255.128
GW 172.19.3.129
Site A Ciscso 2801 Router
Current configuration : 11858 bytes
version 12.4
service timestamps debug datetime localtime
service timestamps log datetime localtime show-timezone
service password-encryption
hostname router-2801
boot-start-marker
boot-end-marker
logging message-counter syslog
logging buffered 4096
aaa new-model
aaa authentication login userauthen group radius local
aaa authorization network groupauthor local
aaa session-id common
clock timezone est -5
clock summer-time zone recurring last Sun Mar 2:00 1 Sun Nov 2:00
dot11 syslog
ip source-route
ip dhcp excluded-address 172.19.3.129 172.19.3.149
ip dhcp excluded-address 172.19.10.1 172.19.10.253
ip dhcp excluded-address 172.19.3.140
ip dhcp ping timeout 900
ip dhcp pool DHCP
   network 172.19.3.128 255.255.255.128
   default-router 172.19.3.129
   domain-name domain.local
   netbios-name-server 172.19.3.7
   option 66 ascii 172.19.3.225
   dns-server 172.19.3.140 208.67.220.220 208.67.222.222
ip dhcp pool VoiceDHCP
   network 172.19.10.0 255.255.255.0
   default-router 172.19.10.1
   dns-server 208.67.220.220 8.8.8.8
   option 66 ascii 172.19.10.2
   lease 2
ip cef
ip inspect name SDM_LOW cuseeme
ip inspect name SDM_LOW dns
ip inspect name SDM_LOW ftp
ip inspect name SDM_LOW h323
ip inspect name SDM_LOW https
ip inspect name SDM_LOW icmp
ip inspect name SDM_LOW imap
ip inspect name SDM_LOW pop3
ip inspect name SDM_LOW netshow
ip inspect name SDM_LOW rcmd
ip inspect name SDM_LOW realaudio
ip inspect name SDM_LOW rtsp
ip inspect name SDM_LOW esmtp
ip inspect name SDM_LOW sqlnet
ip inspect name SDM_LOW streamworks
ip inspect name SDM_LOW tftp
ip inspect name SDM_LOW tcp
ip inspect name SDM_LOW udp
ip inspect name SDM_LOW vdolive
no ip domain lookup
ip domain name domain.local
multilink bundle-name authenticated
key chain key1
key 1
   key-string 7 06040033484B1B484557
crypto pki trustpoint TP-self-signed-3448656681
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3448bb6681
revocation-check none
rsakeypair TP-self-signed-344bbb56681
crypto pki certificate chain TP-self-signed-3448656681
certificate self-signed 01
3082024F
            quit
username admin privilege 15 password 7 F55
archive
log config
hidekeys
crypto isakmp policy 10
encr 3des
hash md5
authentication pre-share
group 2
crypto isakmp key XXXXX address 209.118.0.1
crypto isakmp key xxxxx address SITE B Public IP
crypto isakmp keepalive 40 5
crypto isakmp nat keepalive 20
crypto isakmp client configuration group IISVPN
key 1nsur3m3
dns 172.19.3.140
wins 172.19.3.140
domain domain.local
pool VPN_Pool
acl 198
crypto isakmp profile IISVPNClient
   description VPN clients profile
   match identity group IISVPN
   client authentication list userauthen
   isakmp authorization list groupauthor
   client configuration address respond
crypto ipsec transform-set myset esp-3des esp-md5-hmac
crypto dynamic-map Dynamic 5
set transform-set myset
set isakmp-profile IISVPNClient
qos pre-classify
crypto map VPN 10 ipsec-isakmp
set peer 209.118.0.1
set peer SITE B Public IP
set transform-set myset
match address 101
qos pre-classify
crypto map VPN 65535 ipsec-isakmp dynamic Dynamic
track 123 ip sla 1 reachability
delay down 15 up 10
class-map match-any VoiceTraffic
match protocol rtp audio
match protocol h323
match protocol rtcp
match access-group name VOIP
match protocol sip
class-map match-any RDP
match access-group 199
policy-map QOS
class VoiceTraffic
    bandwidth 512
class RDP
    bandwidth 768
policy-map MainQOS
class class-default
    shape average 1500000
service-policy QOS
interface FastEthernet0/0
description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-FE 0$$FW_INSIDE$
ip address 172.19.3.129 255.255.255.128
ip access-group 100 in
ip inspect SDM_LOW in
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
interface FastEthernet0/0.10
description $ETH-VoiceVLAN$$
encapsulation dot1Q 10
ip address 172.19.10.1 255.255.255.0
ip inspect SDM_LOW in
ip nat inside
ip virtual-reassembly
interface FastEthernet0/1
description "Comcast"
ip address PUB IP 255.255.255.248
ip access-group 102 in
ip inspect SDM_LOW out
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
crypto map VPN
interface Serial0/1/0
description "Verizon LEC Circuit ID: w0w13908 Site ID: U276420-1"
bandwidth 1536
no ip address
encapsulation frame-relay IETF
frame-relay lmi-type ansi
interface Serial0/1/0.1 point-to-point
bandwidth 1536
ip address 152.000.000.18 255.255.255.252
ip access-group 102 in
ip verify unicast reverse-path
ip inspect SDM_LOW out
ip nat outside
ip virtual-reassembly
frame-relay interface-dlci 500 IETF
crypto map VPN
service-policy output MainQOS
interface Serial0/2/0
description "PAETEC 46.HCGS.788446.CV (Verizon ID) / 46.HCGS.3 (PAETEC ID)"
ip address 123.252.123.102 255.255.255.252
ip access-group 102 in
ip inspect SDM_LOW out
ip nat outside
ip virtual-reassembly
encapsulation ppp
crypto map VPN
service-policy output MainQOS
ip local pool VPN_Pool 172.20.3.130 172.20.3.254
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 50.00.000.110 track 123
ip route 0.0.0.0 0.0.0.0 111.252.237.000 254
ip route 122.112.197.20 255.255.255.255 209.252.237.101
ip route 208.67.220.220 255.255.255.255 50.78.233.110
no ip http server
no ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip flow-top-talkers
top 20
sort-by bytes
ip nat inside source route-map COMCAST interface FastEthernet0/1 overload
ip nat inside source route-map PAETEC interface Serial0/2/0 overload
ip nat inside source route-map VERIZON interface Serial0/1/0.1 overload
ip nat inside source static tcp 172.19.3.140 21 PUB IP 21 extendable
ip access-list extended VOIP
permit ip 172.20.3.0 0.0.0.127 host 172.19.3.190
permit ip host 172.19.3.190 172.20.3.0 0.0.0.127
ip radius source-interface FastEthernet0/0
ip sla 1
icmp-echo 000.67.220.220 source-interface FastEthernet0/1
timeout 10000
frequency 15
ip sla schedule 1 life forever start-time now
access-list 23 permit 172.19.3.0 0.0.0.127
access-list 23 permit 172.19.3.128 0.0.0.127
access-list 23 permit 173.189.251.192 0.0.0.63
access-list 23 permit 107.0.197.0 0.0.0.63
access-list 23 permit 173.163.157.32 0.0.0.15
access-list 23 permit 72.55.33.0 0.0.0.255
access-list 23 permit 172.19.5.0 0.0.0.63
access-list 100 remark "Outgoing Traffic"
access-list 100 deny   ip 67.128.87.156 0.0.0.3 any
access-list 100 deny   ip host 255.255.255.255 any
access-list 100 deny   ip 127.0.0.0 0.255.255.255 any
access-list 100 permit tcp host 172.19.3.190 any eq smtp
access-list 100 permit tcp host 172.19.3.137 any eq smtp
access-list 100 permit tcp any host 66.251.35.131 eq smtp
access-list 100 permit tcp any host 173.201.193.101 eq smtp
access-list 100 permit ip any any
access-list 100 permit tcp any any eq ftp
access-list 101 remark "Interesting VPN Traffic"
access-list 101 permit ip 172.19.3.128 0.0.0.127 172.19.3.0 0.0.0.127
access-list 101 permit ip 172.20.3.128 0.0.0.127 172.19.3.0 0.0.0.127
access-list 101 permit ip 172.19.3.128 0.0.0.127 host 172.19.250.10
access-list 101 permit ip 172.19.3.128 0.0.0.127 host 172.19.250.11
access-list 101 permit tcp any any eq ftp
access-list 101 permit tcp any any eq ftp-data
access-list 102 remark "Inbound Access"
access-list 102 permit udp any host 152.179.53.18 eq non500-isakmp
access-list 102 permit udp any host 152.179.53.18 eq isakmp
access-list 102 permit esp any host 152.179.53.18
access-list 102 permit ahp any host 152.179.53.18
access-list 102 permit udp any host 209.000.000.102 eq non500-isakmp
access-list 102 permit udp any host 209.000.000.102 eq isakmp
access-list 102 permit esp any host 209.000.000.102
access-list 102 permit ahp any host 209.000.000.102
access-list 102 permit udp any host PUB IP eq non500-isakmp
access-list 102 permit udp any host PUB IP eq isakmp
access-list 102 permit esp any host PUB IP
access-list 102 permit ahp any host PUB IP
access-list 102 permit ip 72.55.33.0 0.0.0.255 any
access-list 102 permit ip 107.0.197.0 0.0.0.63 any
access-list 102 deny   ip 172.19.3.128 0.0.0.127 any
access-list 102 permit icmp any any echo-reply
access-list 102 permit icmp any any time-exceeded
access-list 102 permit icmp any any unreachable
access-list 102 permit icmp any any
access-list 102 deny   ip any any log
access-list 102 permit tcp any host 172.19.3.140 eq ftp
access-list 102 permit tcp any host 172.19.3.140 eq ftp-data established
access-list 102 permit udp any host SITE B Public IP eq non500-isakmp
access-list 102 permit udp any host SITE B Public IP eq isakmp
access-list 102 permit esp any host SITE B Public IP
access-list 102 permit ahp any host SITE B Public IP
access-list 110 remark "Outbound NAT Rule"
access-list 110 remark "Deny VPN Traffic NAT"
access-list 110 deny   ip 172.19.3.128 0.0.0.127 172.19.3.0 0.0.0.127
access-list 110 deny   ip 172.19.3.128 0.0.0.127 172.19.10.0 0.0.0.255
access-list 110 deny   ip 172.19.10.0 0.0.0.255 172.19.3.128 0.0.0.127
access-list 110 deny   ip 172.20.3.128 0.0.0.127 172.19.3.0 0.0.0.127
access-list 110 deny   ip 172.19.3.128 0.0.0.127 172.20.3.128 0.0.0.127
access-list 110 deny   ip 172.19.3.128 0.0.0.127 host 172.19.250.11
access-list 110 deny   ip 172.19.3.128 0.0.0.127 host 172.19.250.10
access-list 110 permit ip 172.19.3.128 0.0.0.127 any
access-list 110 permit ip 172.19.10.0 0.0.0.255 any
access-list 198 remark "Networks for IISVPN Client"
access-list 198 permit ip 172.19.3.0 0.0.0.127 172.20.3.128 0.0.0.127
access-list 198 permit ip 172.19.3.128 0.0.0.127 172.20.3.128 0.0.0.127
access-list 199 permit tcp any any eq 3389
route-map PAETEC permit 10
match ip address 110
match interface Serial0/2/0
route-map COMCAST permit 10
match ip address 110
match interface FastEthernet0/1
route-map VERIZON permit 10
match ip address 110
match interface Serial0/1/0.1
snmp-server community 123 RO
radius-server host 172.19.3.7 auth-port 1645 acct-port 1646 key 7 000000000000000
control-plane
line con 0
line aux 0
line vty 0 4
access-class 23 in
privilege level 15
transport input telnet ssh
line vty 5 15
access-class 23 in
privilege level 15
transport input telnet ssh
scheduler allocate 20000 1000
ntp server 128.118.25.3
ntp server 217.150.242.8
end
IP scheme at site B:
ip     172.19.5.x
sub 255.255.255.292
gw   172.19.5.65
Cisco ASA 5505 at Site B
ASA Version 8.2(5)
hostname ASA5505
domain-name domain.com
enable password b04DSH2HQqXwS8wi encrypted
passwd b04DSH2HQqXwS8wi encrypted
names
interface Ethernet0/0
switchport access vlan 2
interface Ethernet0/1
interface Ethernet0/2
interface Ethernet0/3
interface Ethernet0/4
interface Ethernet0/5
interface Ethernet0/6
interface Ethernet0/7
interface Vlan1
nameif inside
security-level 100
ip address 172.19.5.65 255.255.255.192
interface Vlan2
nameif outside
security-level 0
ip address SITE B public IP 255.255.255.224
boot system disk0:/asa825-k8.bin
ftp mode passive
clock timezone est -5
clock summer-time zone recurring last Sun Mar 2:00 last Sun Oct 2:00
dns server-group DefaultDNS
domain-name iis-usa.com
same-security-traffic permit intra-interface
object-group network old hosting provider
network-object 72.55.34.64 255.255.255.192
network-object 72.55.33.0 255.255.255.0
network-object 173.189.251.192 255.255.255.192
network-object 173.163.157.32 255.255.255.240
network-object 66.11.1.64 255.255.255.192
network-object 107.0.197.0 255.255.255.192
object-group network old hosting provider
network-object host 172.19.250.10
network-object host 172.19.250.11
access-list 100 extended permit ip 172.19.5.64 255.255.255.192 object-group old hosting provider
access-list 100 extended permit ip 172.19.5.64 255.255.255.192 172.19.3.128 255.255.255.128
access-list 10 extended deny ip 0.0.0.0 255.0.0.0 any
access-list 10 extended deny ip 127.0.0.0 255.0.0.0 any
access-list 10 extended deny ip 169.254.0.0 255.255.0.0 any
access-list 10 extended deny ip 172.16.0.0 255.255.0.0 any
access-list 10 extended deny ip 224.0.0.0 224.0.0.0 any
access-list 10 extended permit icmp any any echo-reply
access-list 10 extended permit icmp any any time-exceeded
access-list 10 extended permit icmp any any unreachable
access-list 10 extended permit icmp any any traceroute
access-list 10 extended permit icmp any any source-quench
access-list 10 extended permit icmp any any
access-list 10 extended permit tcp object-group old hosting provider any eq 3389
access-list 10 extended permit tcp any any eq https
access-list 10 extended permit tcp any any eq www
access-list 110 extended permit ip 172.19.5.64 255.255.255.192 172.19.3.0 255.255.255.128
access-list 110 extended permit ip 172.19.5.64 255.255.255.192 object-group old hosting provider
pager lines 24
logging enable
logging timestamp
logging console emergencies
logging monitor emergencies
logging buffered warnings
logging trap debugging
logging history debugging
logging asdm informational
mtu inside 1500
mtu outside 1500
ip verify reverse-path interface inside
ip verify reverse-path interface outside
ip audit name jab attack action alarm drop reset
ip audit name probe info action alarm drop reset
ip audit interface outside probe
ip audit interface outside jab
ip audit info action alarm drop reset
ip audit attack action alarm drop reset
ip audit signature 2000 disable
ip audit signature 2001 disable
ip audit signature 2004 disable
ip audit signature 2005 disable
icmp unreachable rate-limit 1 burst-size 1
icmp permit 75.150.169.48 255.255.255.240 outside
icmp permit 72.44.134.16 255.255.255.240 outside
icmp permit 72.55.33.0 255.255.255.0 outside
icmp permit any outside
icmp permit 173.163.157.32 255.255.255.240 outside
icmp permit 107.0.197.0 255.255.255.192 outside
icmp permit 66.11.1.64 255.255.255.192 outside
icmp deny any outside
asdm image disk0:/asdm-645.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 100
nat (inside) 1 0.0.0.0 0.0.0.0
access-group 10 in interface outside
route outside 0.0.0.0 0.0.0.0 174.78.151.225 1
timeout xlate 3:00:00
timeout conn 24:00:00 half-closed 0:10:00 udp 0:10:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 24:00:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
http 107.0.197.0 255.255.255.192 outside
http 66.11.1.64 255.255.255.192 outside
snmp-server host outside 107.0.197.29 community *****
snmp-server host outside 107.0.197.30 community *****
snmp-server host inside 172.19.250.10 community *****
snmp-server host outside 172.19.250.10 community *****
snmp-server host inside 172.19.250.11 community *****
snmp-server host outside 172.19.250.11 community *****
snmp-server host outside 68.82.122.239 community *****
snmp-server host outside 72.55.33.37 community *****
snmp-server host outside 72.55.33.38 community *****
snmp-server host outside 75.150.169.50 community *****
snmp-server host outside 75.150.169.51 community *****
no snmp-server location
no snmp-server contact
snmp-server community *****
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto map VPNMAP 10 match address 110
crypto map VPNMAP 10 set peer 72.00.00.7 old vpn public ip Site B Public IP
crypto map VPNMAP 10 set transform-set ESP-3DES-MD5
crypto map VPNMAP 10 set security-association lifetime seconds 86400
crypto map VPNMAP 10 set security-association lifetime kilobytes 4608000
crypto map VPNMAP interface outside
crypto isakmp identity address
crypto isakmp enable outside
crypto isakmp policy 20
authentication pre-share
encryption 3des
hash md5
group 2
lifetime 86400
telnet 172.19.5.64 255.255.255.192 inside
telnet 172.19.3.0 255.255.255.128 outside
telnet timeout 60
ssh 0.0.0.0 0.0.0.0 inside
ssh 0.0.0.0 0.0.0.0 outside
ssh timeout 60
console timeout 0
management-access inside
dhcpd dns 172.19.3.140
dhcpd wins 172.19.3.140
dhcpd ping_timeout 750
dhcpd domain iis-usa.com
dhcpd address 172.19.5.80-172.19.5.111 inside
dhcpd enable inside
threat-detection basic-threat
threat-detection scanning-threat shun except object-group old hosting provider
threat-detection statistics
threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200
ntp server 128.118.25.3 source outside
ntp server 217.150.242.8 source outside
tunnel-group 72.00.00.7 type ipsec-l2l
tunnel-group 72.00.00.7 ipsec-attributes
pre-shared-key *****
tunnel-group old vpn public ip type ipsec-l2l
tunnel-group old vpn public ip ipsec-attributes
pre-shared-key *****
tunnel-group SITE A Public IP type ipsec-l2l
tunnel-group SITE A Public IP ipsec-attributes
pre-shared-key *****
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect netbios
inspect tftp
inspect pptp
inspect sip
service-policy global_policy global
prompt hostname context
no call-home reporting anonymous
call-home
profile CiscoTAC-1
no active
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination address email [email protected]
destination transport-method http
subscribe-to-alert-group diagnostic
subscribe-to-alert-group environment
subscribe-to-alert-group inventory periodic monthly
subscribe-to-alert-group configuration periodic monthly
subscribe-to-alert-group telemetry periodic daily
Cryptochecksum:
: end

I have removed the old "set peer" and have added:
IOS router:
access-list 101 permit ip 172.19.3.128 0.0.0.127 172.19.5.64 0.0.0.65
ASA fw:
access-list 110 extended permit ip 172.19.5.64 255.255.255.192 172.19.3.128 255.255.255.128
on the router I have also added;
access-list 110 deny ip 172.19.3.128 0.0.0.127 172.19.5.64 0.0.0.63
Here is my acl :
access-list 110 remark "Outbound NAT Rule"
access-list 110 remark "Deny VPN Traffic NAT"
access-list 110 deny   ip 172.19.3.128 0.0.0.127 172.19.3.0 0.0.0.127
access-list 110 deny   ip 172.19.3.128 0.0.0.127 172.19.10.0 0.0.0.255
access-list 110 deny   ip 172.19.10.0 0.0.0.255 172.19.3.128 0.0.0.127
access-list 110 deny   ip 172.20.3.128 0.0.0.127 172.19.3.0 0.0.0.127
access-list 110 deny   ip 172.19.3.128 0.0.0.127 172.20.3.128 0.0.0.127
access-list 110 deny   ip 172.19.3.128 0.0.0.127 host 172.19.250.11
access-list 110 deny   ip 172.19.3.128 0.0.0.127 host 172.19.250.10
access-list 110 permit ip 172.19.3.128 0.0.0.127 any
access-list 110 permit ip 172.19.10.0 0.0.0.255 any
access-list 110 deny   ip 172.19.3.128 0.0.0.127 172.19.5.64 0.0.0.63
access-list 198 remark "Networks for IISVPN Client"
access-list 198 permit ip 172.19.3.0 0.0.0.127 172.20.3.128 0.0.0.127
access-list 198 permit ip 172.19.3.128 0.0.0.127 172.20.3.128 0.0.0.127
Still no ping tothe other site.

SCOM Internal Connector - Default Alert Format

Hi All,
We are having SCOM Probe, to Receive alarms from Netcool Connctor (Created at the time probe integration) and for that connector subscriptions are allowed to receive event
Post that, we are able to receive alarms of all them and all works fine.
But, For Service Availability Alarms,
Let Say: I have stopped one service , and got the alarm, but am not able to find exact service name and display name of service from raw data/event.
Further i have seen that , Monitoring Alert properties from below link
http://msdn.microsoft.com/en-us/library/microsoft.enterprisemanagement.monitoring.monitoringalert_properties.aspx
From above URL info, looks like by default am not getting Service Name and etc as like below.
URL : http://blogs.technet.com/b/kevinholman/archive/2007/12/12/adding-custom-information-to-alert-descriptions-and-notifications.aspx
Service Monitors:
Service Name                         $Data/Context/Property[@Name='Name']$
Service Dependencies             $Data/Context/Property[@Name='Dependencies']$
Service Binary Path                $Data/Context/Property[@Name='BinaryPathName']$
Service Display Name             $Data/Context/Property[@Name='DisplayName']$
Service Description                 $Data/Context/Property[@Name='Description']$
http://blogs.technet.com/b/kevinholman/archive/2007/12/12/adding-custom-information-to-alert-descriptions-and-notifications.aspx
How to get Service Name and others along with Monitoring Alert Props via connector to Netcool Event Mgmt Systems.
Is there any possibility to get Service Name and Display Name in Custom Fields Available in Default Monitoring Alert Properties ??
Thank you so much in advance.
Regards
Sekhara
9611200711

Hi Yan Li
Thanks for your reply.
Can you correct me in terms of syntax used in Custom Field
In your ex link i can see
<Property Name="CustomField9" NewValue="$PrincipalName$" GroupIdFilter=""
/>
        <Property Name="CustomField10" NewValue="$Severity$" GroupIdFilter=""
Above values taken from Monitoring Alert Class Members right ?
I wanted to store Service Name and Display Name as like above my query
As per my ex: Service Name = $Data/Context/Property[@Name='Name']$
CustomField1 = Here what value should i put here ??
Am pretty new to SCOM, am doing SCOM integration with Netcool.
So i need to know exact value , to propose right changes in SCOM to Client
Thanks
Sekhara
Sekhara Reddy

SMC 3.0 - Prob in acknowledging alarms

Similar Messages

Maybe you are looking for