CSM Serverfarm Status OID

Good afternoon
I need your help.
I´m trying to perform a snmp query to get the status of the reals of a serverfarm.
Basically I´m trying to get an output that tells me if the reals of a specific serverfarm are Operation or Probe_Failed.
What is the OID to get the reals status? And how do I translate the serverfarm name to its respective OID?
Best regards

Daniel
Thank you very much for your feedback. I´ve tried to perform the query and I get results but I´m not sure how to interpret them. For example:
:~$ snmpwalk -v 1 -c xxxxxx yyy.yyy.yyy.yyy 1.3.6.1.4.1.9.9.161.1.3.1 | grep 172.16.0.1
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.4.4.9.69.83.66.45.70.69.45.56.48.172.16.0.1.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.4.4.10.69.83.66.45.70.69.45.52.52.51.172.16.0.1.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.4.4.11.69.83.66.45.70.69.95.50.45.56.48.172.16.0.1.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.4.4.12.69.83.66.45.70.69.95.50.45.52.52.51.172.16.0.1.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.5.4.9.69.83.66.45.70.69.45.56.48.172.16.0.1.0 = Gauge32: 12
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.5.4.10.69.83.66.45.70.69.45.52.52.51.172.16.0.1.0 = Gauge32: 22
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.5.4.11.69.83.66.45.70.69.95.50.45.56.48.172.16.0.1.0 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.5.4.12.69.83.66.45.70.69.95.50.45.52.52.51.172.16.0.1.0 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.7.4.9.69.83.66.45.70.69.45.56.48.172.16.0.1.0 = Gauge32: 4294967295
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.7.4.10.69.83.66.45.70.69.45.52.52.51.172.16.0.1.0 = Gauge32: 4294967295
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.7.4.11.69.83.66.45.70.69.95.50.45.56.48.172.16.0.1.0 = Gauge32: 4294967295
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.7.4.12.69.83.66.45.70.69.95.50.45.52.52.51.172.16.0.1.0 = Gauge32: 4294967295
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.8.4.9.69.83.66.45.70.69.45.56.48.172.16.0.1.0 = Gauge32: 8
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.8.4.10.69.83.66.45.70.69.45.52.52.51.172.16.0.1.0 = Gauge32: 8
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.8.4.11.69.83.66.45.70.69.95.50.45.56.48.172.16.0.1.0 = Gauge32: 8
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.8.4.12.69.83.66.45.70.69.95.50.45.52.52.51.172.16.0.1.0 = Gauge32: 8
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.9.4.9.69.83.66.45.70.69.45.56.48.172.16.0.1.0 = Gauge32: 8
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.9.4.10.69.83.66.45.70.69.45.52.52.51.172.16.0.1.0 = Gauge32: 8
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.9.4.11.69.83.66.45.70.69.95.50.45.56.48.172.16.0.1.0 = Gauge32: 8
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.9.4.12.69.83.66.45.70.69.95.50.45.52.52.51.172.16.0.1.0 = Gauge32: 8
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.10.4.9.69.83.66.45.70.69.45.56.48.172.16.0.1.0 = Gauge32: 1
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.10.4.10.69.83.66.45.70.69.45.52.52.51.172.16.0.1.0 = Gauge32: 2
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.10.4.11.69.83.66.45.70.69.95.50.45.56.48.172.16.0.1.0 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.10.4.12.69.83.66.45.70.69.95.50.45.52.52.51.172.16.0.1.0 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.16.4.9.69.83.66.45.70.69.45.56.48.172.16.0.1.0 = Counter32: 347037
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.16.4.10.69.83.66.45.70.69.45.52.52.51.172.16.0.1.0 = Counter32: 29147
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.16.4.11.69.83.66.45.70.69.95.50.45.56.48.172.16.0.1.0 = Counter32: 20
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.16.4.12.69.83.66.45.70.69.95.50.45.52.52.51.172.16.0.1.0 = Counter32: 2
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.17.4.9.69.83.66.45.70.69.45.56.48.172.16.0.1.0 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.17.4.10.69.83.66.45.70.69.45.52.52.51.172.16.0.1.0 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.17.4.11.69.83.66.45.70.69.95.50.45.56.48.172.16.0.1.0 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.17.4.12.69.83.66.45.70.69.95.50.45.52.52.51.172.16.0.1.0 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.18.4.9.69.83.66.45.70.69.45.56.48.172.16.0.1.0 = Counter32: 200920621
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.18.4.10.69.83.66.45.70.69.45.52.52.51.172.16.0.1.0 = Counter32: 21553254
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.18.4.11.69.83.66.45.70.69.95.50.45.56.48.172.16.0.1.0 = Counter32: 109
SNMPv2-SMI::enterprises.9.9.161.1.3.1.1.18.4.12.69.83.66.45.70.69.95.50.45.52.52.51.172.16.0.1.0 = Counter32: 452
How can I determine which of these relates to the serverfarm I want, and how do I interpret the line to know if the real is operational or with a probe_failed status?

Similar Messages

Queuing/Retrying 'Rejected' status OID Process Tasks: OIM-OID provisioning

Hello Gurus,
I have already up and running environment with OIM, OID connector pack and OID as the target system. So when a user data (for e.g. a UDF) is being provisioned from OIM to OID target system; if a process task comes back with 'rejected' status due to target unavailability/OID down; then is there any settings that we can configure within OIM design console that queues up and retries these 'rejected' tasks related to each individual user?
Is there any setting within any of the OID lookups such that we can set a retry count for such process tasks?
The goal is without human intervention all these 'rejected' process tasks should run successfully and be set to 'completed' status. If the target system is unavailable then there should be a way to run all these failed tasks - is my assumption.
Is it by anyway related to 'Offline Provisioning'?
Please provide some guidelines.
Thanks,
- oidm.
Edited by: oidm on Mar 16, 2010 10:34 PM

But it'll only allow us to 'retry' those specific tasks for a limited number of times and limited period of time. And will this task be retried only if its 'rejected' or it'll be retried for whatever number of times we specified?
What if the target system doesn't come up for the whole day? Can we specify some value for the same in 'Duration' fields?
So all in all if we talk about retrying the failed/rejected tasks we just have these options in hand as far as task 'status' is concerned?
Thanks,
- oidm.

Bridge mode CSM - Serverfarm with hosts in different vlans

Hi,
I'm trying to answer a question while doing design. I am planning on deploying a CSM in bridge mode with multiple vlans. I need to create a serverfarm which has real servers in two separate server side vlans.
I would then present the Vserver on the client side only of one of the vlans (I always like to specify where I want the vserver). Whe traffic comes in to this vserver, will the CSM appropriately switch traffic to both vservers? I think it will but don't have access to a csm right now to mock it up.
Thanks
Adam

You cannot have 3 vlans configured in bridge mode with all vlans using same address space.
You can use mixed mode to achieve your goal.
It is possible to have Vlan 10 and Vlan 11 in bridge mode and at the same time have VLAN 12 (for example) in the routed mode.
- Traffic from vlan 10 to vlan 20 is bridged
- Traffic from vlan 10 to vlan 12 is routed
where Vlan 10&20 belong to same subnet and Vlan 12 is in different subnet.
Syed

CSM - serverfarms configured with multiple probes

Hi - If a serverfarm is configured with multiple probes, do the servers within the farm remain active if they respond positively to both probes or do they just need to respond to one of the configured probes?
Thanks in advance

Both probe must respond positively to make the server appears as OPERATIONAL.
If only one probe is responding positively then the server is considered DOWN
That is usefull for UDP test :
you need to check taht you don't have a RST when openning an UDP connection ( the UDP port is not closed) and you need to make ping (in order to be sure that there is a server ;-) )

How to start OID

Hi
When i issue the following command it shows
<infra_home>/opmn/bin opmnctl status
oid down
how to enable this OID.

Hi
I had issue the command as u people told still OID is not up.
log files shows date time and
dependency check
no error
thanks and regards
vishwa

Catalyst 6500 CSM-S Cookie stickiness timout ?

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Hi, anyone able to help with this ?
We have a CSM-S sitting in a 6513, at the moment we have IP stickiness applied for a Vserver/Serverfarm. The back end product vendor advises that cookie stickiness would be more appropriate for their application.
I have been scratching my head around the timeout of the inserted cookies; whatever I do they persist seemingly indefinitely, for example:
Just a test configuration with a 10minute sticky timout.
serverfarm applicationA
nat server
nat client applicationA_pool
failaction reassign
real 1.1.1.1
   inservice
real 1.1.1.2
   inservice
health retries 1 failed 120
probe applicationA_probe
sticky 1 cookie applicationA_sticky insert timeout 10
vserver applicationA-HTTP
virtual 2.2.2.10 tcp www
unidirectional
serverfarm applicationA
sticky 10 group 1
no persistent rebalance
inservice
Doing show mod csm 1 sticky
group   sticky-data              real                  timeout
1       cookie F5BF7115:F80EA688 1.1.1.1           0
1       cookie 4AFC972B:BB722437 1.1.1.2           0
Then a show mod csm 1 sticky config
Group NumEntries Timeout Type
1             82                           10        cookie-insert applicationA_sticky
When browsing to the VIP I see the application page via one of the reals. For the sake of the test I am using round-robin. Without cookies applied my browser will bounce between reals (I turned off persistent rebalance during testing) as expected.
With a sticky cookie inserted the browser stays on one of the real’s, however the timeout which I have applied does not work. The client will stay stuck to the real almost indefinitely (the actual cookie expiry is 2099!).
The online documentation advised that the method I am using should work as expected:
Quote
This example shows how to configure a virtual server named barnett, associate it with the server farm named bosco, and configure a sticky connection with a duration of 50 minutes to sticky group 12:
Router(config)# mod csm 2
Router(config-module-csm)# sticky 1 cookie foo timeout 100
Router(config-module-csm)# exit
Router(config-module-csm)#
Router(config-module-csm)# serverfarm bosco
Router(config-slb-sfarm)# real 10.1.0.105
Router(config-slb-real)# inservice
Router(config-slb-real)# exit
Router(config-slb-sfarm)#
Router(config-slb-sfarm)# vserver barnett
Router(config-slb-vserver)# virtual 10.1.0.85 tcp 80
Router(config-slb-vserver)# serverfarm bosco
Router(config-slb-vserver)# sticky 50 group 12
Router(config-slb-vserver)# inservice
Router(config-slb-vserver)# exit
Router(config-module-csm)# end
End Quote
I am guessing that sticky group 12 / 1 is a typo
Looking at the documentation, sticky can also be applied not in the vserver config but in a policy (this is how we are doing IP stickiness). I have tried both methods. Same result.
I am natting the client address to a private pool which then talks to the reals (and back). Would'nt expect this to be any issue.
The CSM is running Software version: 4.3(5).
Any help appreciated.

Good mornign Simon,
The behavior you are seeing is the expected one.
When the CSM is configured for cookie insertion, a static cookie value is created in the sticky table for each server. This is the cookie that is being inserted, using as expiration date the one defined in the COOKIE_INSERT_EXPIRATION_DATE variable.
With this stickiness method, there is no need to use a timeout, because, since the sticky table will only contain one entry for each server, it will never become full.
Quoting from the documentation:
Note     The
configurable timeout values are not applied when using cookie insert.
You can adjust the timeout value using the environment variables.
If you don't want to keep the cookies in the client for that long, another approach you can use is setting an empty date in the COOKIE_INSERT_EXPIRATION_DATE variable. When doing that, the cookie will be inserted without an expiration date, so it will be cleared when the browser is closed.
I hope this answers your question
Regards
Daniel

SNMP OIDs support in Netapp c-mode

Hi,I have been new to netapp devices. I have been working on a system which monitors the netapp devices. Till 7-mode my software monitors the netapp devices well. However after we have started working with c-mode devices we are encountering some problems:1. When we do snmpwalk for ndmp OIDs, it returns error: This may be that the OIDs(1.3.6.1.4.1.789.1.1.4.x) are not implemented on c-mode devices however at below link "http://people.teamix.net/~bu/81ClusterModeCLReference/CLI-Commands-NetApp-81-Cluster-Mode.pdf" I have seen that CLI exists.2. Simillar issue I am observing with snapvault, nfs, cifs and snapmirror OIDs.Do somebody have any idea about this or can somebody share any reason fro the above?Is there any document or some link where I can find the information?Thanks in advance.

I can add to this, working on this same issue now. We had a customer move from a FAS3020 in 7-mode to a 8020 in c-mode. Monitoring was working previously for the global status but since the cutover nagios was reporting OID not found. I was able to pull the MIB from the device by going to t http(s)://cluster-mgmt-ip/spi and downloading it. I imported this into a MIB browser and located the misc global status OID which is 1.3.6.1.4.1.789.1.2.2.4.0 however a snmpget to the cluster (both nodes and the VIP) results in a response of: Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.789.1.2.2.4.0 It's almost as if the filer has no idea that the OID exists. In fact I did a SNMPWALK on the device and output that to a file and don't find that OID at all. In fact there appears to be nothing under the .2 identifier yet it's listed in the MIB. (1.3.6.1.4.1.789.1.2.2) What gives? How do you measure anything in the misc category per the MIB as they are all 1.3.6.1.4.1.789.1.2.2.x.x? This is Ontap 8.3 btw. Any help on this would be appreciated. Thanks!

CSM HTTP return code checking

Hey again.
I have been looking into the CSM return code checking feature as suggested by this forum. This is a little closer to what I am looking for but I have question about what happens when there is a failure.
If a 500 code for HTTP is seen three times, for example, and the server is removed from the farm, is the original request from the client tried on the next server? Or is a reset sent back to the client, or the original code, and the client must try again.
I am trying to understand if the client will notice if the CSM noticed X number of a particular error and removed the server from the farm.
Thanks for any help!
/ahuffer/

I think you are mixing two things up(Inband health monitoring & HTTP return code checking).
The "Inband health monitoring" feature checks for both RSTs from a server and the failure of the server to respond to a SYN. If a SYN ACK response to a SYN is not received,the TCP portion of the code will perform several retries of a SYN before timing it out.
It is configured as follows
CSM(config-module-csm)# serverfarm xyz
CSM(config-slb-sfarm)# health retries 10 failed 50
(Retries are the number of abnormal end sessions that the CSM will tolerate before removing a real server from service. The failed time is the number of seconds that the CSM waits before reattempting a connection to a real server that was removed from service by inband health checking.)
"HTTP Return Code checking" is the CSM feature that can be configured to take a server out of use in response to receiving specific return codes.
When HTTP return code checking is configured, the CSM monitors HTTP responses from all balanced HTTP connections and logs the occurrence of the return code for each real server. The CSM stores return code counts. When a threshold for a return code is reached, the CSM may send syslog messages or remove the server from service.
Unlike "Inband Health monitoring", "Http Return code checking" feature has a small (estimated in 10-15%) impact on CPS setup rate, since it requires parsing L5 information in the server-to-client direction.
If the server is taken out of service, Client's request will be loadbalanced among available servers.
Syed
Syed

CSM: Sticky timeout parameter: difference between sticky group and vserver

Hi,
Concerning the example in the CSM manual about configuration of stickiness:
What (or why) is exactly the difference between the timeout parameter (100 minutes):
sticky 12 cookie foo timeout 100 AND the sticky 50 group 12 in the vserver.
The timeout parameter is overruled in the vserver configuration. (100 -> 50)
For what could this be usefull?
Thank you!
Kind regards,
Wim
This example shows how to configure a virtual server named barnett, associate it with the server farm
named bosco, and configure a sticky connection with a duration of 50 minutes to sticky group 12:
Router(config)# mod csm 2
Router(config-module-csm)# sticky 12 cookie foo timeout 100
Router(config-module-csm)# exit
Router(config-module-csm)#
Router(config-module-csm)# serverfarm bosco
Router(config-slb-sfarm)# real 10.1.0.105
Router(config-slb-real)# inservice
Router(config-slb-real)# exit
Router(config-slb-sfarm)#
Router(config-slb-sfarm)# vserver barnett
Router(config-slb-vserver)# virtual 10.1.0.85 tcp 80
Router(config-slb-vserver)# serverfarm bosco
Router(config-slb-vserver)# sticky 50 group 12
Router(config-slb-vserver)# inservice
Router(config-slb-vserver)# exit
Router(config-module-csm)# end

if you configure the group under a policy, there is no option for the timeout.
This is why the option exist under the stick-group.
In the vserver, you can overrid this timeout - so the timeout is per vserver.
If you want the same timeout, just configure the same value.
gdufour-cat6k-2(config-module-csm)#policy test1
gdufour-cat6k-2(config-slb-policy)#sticky-group ?
<1-255> sticky group ID
gdufour-cat6k-2(config-slb-policy)#sticky-group 12 ?
Gilles.

CSM reporting failed ARP request

Hi!!
We have a CSM on Catalyst 6509 SUP720, the IOS is 12.2(18)SXD7b.
We have a problem with load-balanced portal servers with the CSM. Checking Catalyst log we see the following messages:
Jun 7 06:17:42.145 UTC: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: Server [ip address] failed ARP request
Jun 7 06:17:43.505 UTC: %CSM_SLB-6-RSERVERSTATE: Module 4 server state changed: SLB-NETMGT: Server [ip address]now responding to ARP requests
Jun 7 06:19:23.445 UTC: %CSM_SLB-6-GATEWAYSTATE: Module 4 gateway state changed: SLB-NETMGT: Gateway [ip address]failed ARP request
Jun 7 06:24:12.241 UTC: %CSM_SLB-6-GATEWAYSTATE: Module 4 gateway state changed: SLB-NETMGT: Gateway [ip address]now responding to ARP requests
At the begining, the message were on refer to failed ARP for the real servers, but now the CSM reports failed ARP request on the Gateways (Vlan Interfaces) too.
Any idea?? We don?t now if the problem is the network, or is the CSM Card or the IOS version.
The Catalyst 6500 is on Distribution Layer, connecting 4 Access switches (Enterasys) and 2 Core Cat6500 switches. The balanced servers are on a Access Enterasys N7 Switch.
Thanks in advance...
Pedro

Hi Gilles, thanks for your quick response.
But, as well as the problem with missing ARP?s, we have very slow responses and sites pages are shown with missing objets every time we point to the CSM virtual address with 2 internet proxi servers on a CSM Serverfarm, while if we point to the Real IP Address of any proxi-sever, all is fine and fast.
Now we are pointing directly to real servers (not to the CSM virtual), and all is fine, but it is not the final idea.
It sounds like a problem with the Channel betwen the CSM and the Switch.
We made traces monitoring the PortChannel 260, and we saw very ARP request but just a few replys.
Is very strange that also the CSM is reporting missing ARP?s on Gateways, because this gateway is an interface Vlan into the MSFC!! The only way to disappear the log missing ARP messages is configuring static arp on CSM.
What you think about?.
The version on CSM is 4.2(2)
Thanks!!
Pedro.

Migrating Local Director to CSM - commands "name" "oos"

On a CSM v4.2(3) on a 6509: I'm trying to make the real servers have names (like on the local director) instead of IP addresses:
VOC-SW15#conf t
Enter configuration commands, one per line. End with CNTL/Z.
VOC-SW15(config)#mod csm 4
VOC-SW15(config-module-csm)#serverfarm TEST1
VOC-SW15(config-slb-sfarm)#real ?
A.B.C.D real server IP address
name use a named real server
VOC-SW15(config-slb-sfarm)#real name webtest
% Config not found for module real WEBTEST
VOC-SW15(config-slb-sfarm)#real name ?
WORD real server name
VOC-SW15(config-slb-sfarm)#real name webtest
% Config not found for module real WEBTEST
VOC-SW15(config-slb-sfarm)#
VOC-SW15(config-slb-sfarm)#real webtest
VOC-SW15(config-slb-module-real)#address 10.1.250.37
This is what I end up with (I want the real server under server farm test1:
real WEBTEST
address 10.1.250.37
serverfarm TEST1
nat server
no nat client
real 10.1.250.38
inservice
Also, if anyone has an easy way to take a box out of service (like on the local director) please let me know. On CSM we're having to do this:
VOC-SW15#conf t
VOC-SW15(config)#mod csm 4
VOC-SW15(config-module-csm)#serverfarm relays
VOC-SW15(config-slb-sfarm)#real 10.1.11.23
VOC-SW15(config-slb-real)#no inservice
on ld it was just: oos real relay-01
Thank you for all the posts. They have been tremendous help in getting the CSM in production.
ps (Gilles, My Christmas wish is that you're working on a CSS/CSM Book for Cisco Press. One is definately needed)
Thank you, Sheila

We figured out the name configuration.
real MLXWEBTEST
address 10.1.250.36
inservice
serverfarm TEST1
nat server
no nat client
real 10.1.250.38
inservice
real name MLXWEBTEST
no inservice
real server farm weight state conns/hits
10.1.250.38 TEST1 8 OPERATIONAL 0
MLXWEBTEST TEST1 8 OUTOFSERVICE 0
Is this the best configuration? We have to migrate
250+ servers over to the CSM. Thanks, sheila

How to configure SNMP on DMS or DMP?

for the first, English is not my mother tounge, so I may write a lot of mistake of my words.
One of my customer want to infomation of DMP that is down or up with SNMP tool.
I had download the tool named 'SNMP TESTER' and test with DMP, and DMS.
But the DMP has no SNMP configure set module or command. Only DMM has one sections of it's administrator - settings.
I changed the DMM setting like this
Queries
Query Operations : Enabled
Read Community : public
Notifications
Notification Operations : Enabled
Hostname or IP Address : 172.16.100.143
Port : 162
Trap Community : public
==========================================================
and my SNMP tester settings below.
Host name or address : 172.16.100.251
Community name : public
and these are logs of fail to test.
2012-11-07 17:27:04 - Starting SNMP test...
2012-11-07 17:27:04 - Connecting to
[email protected]
2012-11-07 17:27:05 - ERROR: Unable to complete the test.
2012-11-07 17:27:05 - ERROR: Data is incorrect (13)
2012-11-07 17:27:05 - [SNMP status] .1.3.6.1.2.1.1.1.0, .1.3.6.1.2.1.1.5.0, .1.3.6.1.2.1.4.1.0: No such name (#1)
==========================================================
My SNMP tester installed PC IP : 172.16.100.143
DMM : 172.16.100.251(Version 5.2)
DMP 4400 : 172.16.100.85 (UP status)
The SNMP service looks enabled. In fact, I'm not sure it's configure is right and working.
I'm not close to SNMP. So, I hope your experts will show me greatful kindness.
just two thing that the customer wants is simple.
OID number status 2 code and show them to within SNMP Tester. (UP & Down 2 status OID code needed)
How can I test the SNMP service is working and Showing the status of DMP within SNMP Tester?
P.S I attached the SNMP Tester program for your testing.

Hi Rafik, here is a basic snmp v1/v2 configuration
snmp-server server
snmp-server community test1234 rw view DefaultSuper
This is basically wide open to anyone who knows the password. This should be enough to get you started then you can tweak additional options as you go. Give this a test, see if you can do what you're trying to do then modify this sample to work for your security needs.
-Tom
Please mark answered for helpful posts

ERROR 1058 WHEN starting INFRASTRUCTURE

I am using Portal and Infrastructure 10g
metadatabase ASDB is 9.0.x
In order to use Oraacle Warehouse Builder(OWB) i had to have a 10.1 level runtime DB.
So I installed 10g oracle database and kept one listener at that level (10.1). Infrastructure listener has been deactivated.
Listener.ora and tsnames .ora where updated on INFRAstructure instance to be nearly identical to 10g DB instance (diference is one db definition)
However starting infrastructure and portal instances has become erratic and error prone:u
It takes about 20 minutes to start these two instances by hand has before i had only to start them and everything went smoothly (but took also a long time).
Now i get the following messages and have to use following opmnctl commands to have the whole thing running as follows:
==> start INFRASTRUCTURE
lancement de tnslsnr: veuillez patientez...
failed to start service, error 1058 ==> new message
TNS-12536: l'opÃ©ration provoquerait le blocage ==>new
TNS-12560 erreur d'adaptateur de protocole ==> not new and didn(t care
TNS-00506 l'opÃ©ration provoquerait un blocage ==> new
32-bits Windows Error: 997: Unknown error ==>not new and didn't care
I also get from SMTP the following mail:
Nom=LISTENER_ternes-1-81-57-68-1.fbx.proxad.net
Type=Listener
HÃ´te=ternes-1-81-57-68-1.fbx.proxad.net
Mesure=Status
Horodatage=2 nov. 2004 23 h 34 CET
GravitÃ©=Critique
Message=The listener is down: TNS-12541: TNS:no listener .
Nom de la rÃ¨gle=Listener Availability
PropriÃ©taire de la rÃ¨gle=SYSMAN
1-opmnctl status
opmnctl status
IAS-component process-type pid status
OID OID N/A Down
OC4J OC4J_SECURITY N/A Down
HTTP_Server HTPP_Server 1588 Alive
dsm-daemon dcm-daemon N/A Down
LogLoader logloaderd N/A Down
here its very erratic sometimes OID is in STOP status
2-opmnctl startall
opmnctl status
opmnctl status
IAS-component process-type pid status
OID OID 3504 Alive
OC4J OC4J_SECURITY 3416 Alive
HTTP_Server HTPP_Server 1588 Alive
dsm-daemon dcm-daemon N/A Down
LogLoader logloaderd N/A Down
3_opmnctl startproc ias-component=dcm-daemon
opmnctl status
IAS-component process-type pid status
OID OID 3504 Alive
OC4J OC4J_SECURITY 3416 Alive
HTTP_Server HTPP_Server 1588 Alive
dsm-daemon dcm-daemon 5524 Alive
LogLoader logloaderd N/A Down
At that point i can start Portal instance
Processes in Instance: PORTALBI.ternes-1-81-57-68-1.fbx.proxad.net
----------------------------------------------+---------
ias-component | process-type | pid | status
----------------------------------------------+---------
wireless | OC4J_Wireless | 5292 | Alive
wireless | messaging_server | 3456 | Alive
wireless | performance_server | 1364 | Alive
Discoverer | PreferenceServer | 2080 | Alive
Discoverer | OAD | 2124 | Alive
Discoverer | OSAgent | 1688 | Alive
OC4J | OC4J_WSRP | 820 | Alive
OC4J | OC4J_Portal | 4264 | Alive
OC4J | OC4J_BI_Forms | 5020 | Alive
OC4J | home | 4948 | Alive
WebCache | WebCacheAdmin | 1976 | Alive
WebCache | WebCache | 3500 | Alive
HTTP_Server | HTTP_Server | 1912 | Alive
dcm-daemon | dcm-daemon | 5048 | Alive
LogLoader | logloaderd | N/A | Down
What is the way to get the whole thing up at once and not in 20 minutes
Service OracleINFRAASControl takes about 10 minutes to start (INFRA name of infrastructure instance)
How is it possible to think of getting one day into production?
Thanks for help
jacques parisot

Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
*Don't make any changes on the Safe mode start window.
*https://support.mozilla.com/kb/Safe+Mode
*https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes
If it does work in Safe-mode then disable all extensions and then try to find which is causing it by enabling one at a time until the problem reappears.
*Use "Disable all add-ons" on the [[Safe mode]] start window to disable all extensions.
* Close and restart Firefox after each change via "File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit")

Mail.Dat Test Scenario

What are the following files they are requesting in Mail.Dat TEM?
(1) Reconcialiation Report including Container information
(2) Qualification Report
(3) Version Summary Report
I am having problems figuring out what are these files?

Hi Nash
What it means that the mail.dat you submit to PostalOne! should contain the information necessary to generate these documents.
For Example as mentioned in the TEM checklist if you submit an u2018original ready to payu2019 Mail.dat file (CSM Container status is u2018Ru2018 for original ready-to-pay) , you should be able to see the documents you mentioned on the dashboard.
Thanks
Anita

Using SNMP to monitor Nexus 7000 Series Supervisor Module

Hello,
I got a Nexus 7000 supervisor module recently, I met a SNMP problem for this module
I would like to know which specific OIDs to use to monitor the following using SNMP on a Nexus 7000 supervisor module:
- Port status
- CPU total utilization
- Power Supply status
- Chassis Fan status
etc.
The Nexus is quite different from other Cisco devices - any help will be appreciated!

hope help, and
port status OID is ifOperStatus
CPU total utilization OID is 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifDescr.83886080
.1.3.6.1.2.1.2.2.1.2.83886080 = STRING: mgmt0
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 ifOperStatus.83886080
.1.3.6.1.2.1.2.2.1.8.83886080 = INTEGER: up(1)
[root@NET-MONITOR-1 ~]#
[root@NET-MONITOR-1 ~]# snmpwalk -On -v 2c -c 360buy 172.17.0.253 1.3.6.1.4.1.9.9.109.1.1.1.1.6.1
.1.3.6.1.4.1.9.9.109.1.1.1.1.6.1 = Gauge32: 21
[root@NET-MONITOR-1 ~]#

CSM Serverfarm Status OID

Similar Messages

Maybe you are looking for