Managing a WCS by SNMP

Hello,
I'll need to supervise a WCS (release 4.2.) remotely through SNMP.
What mib can I use to get information such as CPU used on the WCS, free space HardDisc, number of AP, number of rogue AP, number of LWAPP tunnels , number of wifi users connected to all APs ?
regards,

Hello,
Thank you very much. I'll go on by polling the WLC.
reagrds,

Similar Messages

WLC failed to connect to WCS by snmp

Hi fellows,
I've a solution implemented that contains 1 WCS and 3 WLC.
For some unknown reason, started from some point, one of the WLC started to fail to connect by snmp to the WCS, given the next error "
%AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1037 Could not connect to LDAP server 2, reason: 49 (Invalid credentials)."
I've made upgrade for the last version of firmware on all WLC's, have rewritten the credentials of SNMP, but the problem remains with only one of the WLC's, all others are working fine.
The SNMP is v.3.
The version of WCS is 6.0.132.0.
Any ideias?
Best regards,
Luis Matos

Hi Scott Fella,
Thanks for your answer.
When the problem appears, the version of the wlc was 6.0.182. We 've made upgrade to version 7.0.116.0 to try to resolve the problem, but the problem remains.
The 2 others WLC that is working fine, have the version 6.0.182.
There isn't any FW between the WLC's and WCS.
Best Regards,
Luis Matos

Enterprise Manager Grid Control can send SNMP Traps to third-party?

GC 11.1
It looks like a simple config, but I've got into a confusion about it.
I'm trying to figure out the configuration to send SNMP traps to a third party server.
My scenario is:
Node A (managed, monitored) ---- GC box------ SNMP box (final destination).
My understanding is that the traps (notification methods) configured on GC box are generated by the Agent on Node A, then received by the GC and distributed as e-mails.
What is the config to set the traps from A to reach SNMP box?
There is the help page from the GC page (confused about interpretation):
"Add SNMP Trap pageThe Add SNMP Trap page enables you to provide the name of the host (machine) on which the SNMP Master Agent is running and other details so that SNMP traps can be sent through Notification Rules.
An example is shown below.
Name HP OpenView Console
Description Notification method to send trap to HP openview console
SNMP Trap Host Name litleguy.us.oracle.com
SNMP Host Port 162
SNMP Community public
This SNMP host will receive your SNMP traps.
Note: A Test Trap button exists for you to test your setup."
Any suggestions are highly appreciated.
Thx,

Please reply with the specific questions around this.
11.1
EM can send SNMP traps to specific designated receivers. You create an advanced notification method (of type SNMP Trap) with the appropriate details about the receiver.
(See Setup->Notification Methods)
In the notification rules UI, you specify the alerts you are interested in forwarding and select the SNMP trap advanced notification method you created earlier.
The SNMP receiver should be provided the correct MIB that defines the SNMP trap. There were some bugs with the MIB definition in one of the releases (don't recall which one off hand), so if the traps you are receiving don't match what the receiver expects - please let us know and we can point to the right one.
regards

Operations Manager 2012 doesn't listening SNMP Trap UDP port 162

hi,
SCOM 2012 SP1, how come the operations manager started but the SNMP Trap UDP port 162 not listening?
Without this port listening, I can't testing SNMP trap on SCOM.
Thanks...KEN

Hi,
As described in the following blog, the TRAP service should be installed but turned off, we could not get traps coming in until we turned the service back on.
So please verify if the service is on. You can continue audit the ports by running netstat –a.
System Center 2012 Notes From the Field
http://scom-2012.blogspot.in/2012/07/setting-up-snmp-monitoring-in-scom-2012.html
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Hope this helps.

WLSE manage AP using SNMP through xDSL line with an NAT router

Hi,
This is the deployment architecture that I had :
WLSE (Internet public add)--->xDSL----->NAT router---->BBSM--->APs
I had a problem in managing the APs which the ip address will be translated to a public ip addresses. When I use discovery options from my WLSE, it does not find any AP. I enable the CDP on my router and APs. There is only 1 ssid on all my APs.
Is it possible to manage the APs using snmp using this model?
regards,
Sam

Since you have NAT in between the WLSE and the APs, this will not work. SNMP does not work over NAT. To test this, try using the SNMP Reachable Tool under Administration->Connectivity Tools. enter the ip address and click on SNMP Reachable, you'll see that it will time out.

How can I apply existing WCS "WLAN Config" templates to a new WLC?

We've been running a pair of WLC 4402s managed by WCS, thus we are still on the older 7.0.235.0 (WCS) / 7.0.235.3 (WLC) release. I'm trying to add an additional WLC 4402-50 as a hot spare. I first ran the manual setup steps to give it an IP in our range, and used the WLCs web page to set our SNMP communities and such to the values used by our existing WLCs, then I added the new WLC in WCS.
At this point I could apply most of the "Controller Templates" from our existing configuration to the new unit. However, I can not get it to take our existing interfaces nor our WLAN Configurations. How do I avoid needing to recreate these from scratch on the new WLC?
We only have four dynamic interfaces, and each WLC needs its own IP address for each interface, so I did manually add these via the WLCs web page. However, now when I go to the WCS' "Configure > Contoller Templagte Launch Pad" page, then select "WLANs > WLAN Configuration", I see my usual list of WLANs, but can't figure how to push them to the new WLC.
For all of the other templates on the launch pad, I can select a template, click the "Apply to Controllers..." button, and I get a list that has my existing two and also the new controller. I can select the new controller, and apply the template, and it succeeds.
Yet if I select a specific WLAN config, and press "Apply to Controllers...", the list that appears has only my existing two WLCs, not the the new one.
In small green type at the top it says, "Controllers configured with Interface/Interface Group - 'w-restricted' and selected RADIUS server(s), LDAP servers, ACL Name with rules and Ingress interface are shown."
I have already manually added the interface "w-restricted" to the new controller, and have added the RADIUS servers via the template used by our other two WLCs. Not sure what to do about "LDAP servers, ACL Name with rules and Ingress interface", as we don't have any ACL rules, nor use LDAP directly from the WLCs (as all user ID stuff is via RADIUS).
Any hints on what manual setup I should add to get the new WLC in the list for these WLAN Configs?
Thanks,
Steve

To be honest, if your only adding another WLC, your better off creating the interface and WLAN's manually. I don't like pushing out templates to create new WLAN's. I would use it to adjust an existing WLAN, but that would be it. To me it's safer. Also your new WLC is on the same code? If you really want to figure it out, I would manually add the interfaces first then refresh the co fog from the new WLC and then push out the WLAN SSID and see if it takes. If not, don't waste your time anymore and create it manually.
Sent from Cisco Technical Support iPhone App

WCS MSE Help

I’m trying to synchronize one of our switches with the WCS/MSE (Version 6 on the WCS). I’ve added it onto the WCS and the MSE says it synchronizes properly but when I go into the SERVICES/MOBILITY SERVICES and look at the switch it is just showing the IP address. It’s not showing any of the ports or any information at all on the switch. I have the RW snmp string for the switch. Any ideas?

Well that is a complex question but let's start with making sure that you meet the requirements for it to work:
http://www.cisco.com/en/US/docs/wireless/wcs/6.0/configuration/guide/6_0admin.html#wpxref43135
Switch Port Trace
The Switch Port Trace page allows you to run a trace on detected rogue access points on the wire.
To correctly trace and contain rogue access points, you must correctly provide the following information.
•Reporting APs—A rogue access point has to be reported by one or more managed access points.
•AP CDP Neighbor—Access point CDP neighbor information is required to determine the seed switches.
•Switch IP address and SNMP credentials—All switches to be traced must have a management IP address and SNMP management enabled. You can add network address based entries instead of only adding individual switches. The correct write community string must be specified to enable/disable switch ports. For tracing, read community strings are sufficient.
•Switch port configuration—Trunking switch ports must be correctly configured. Switch port security must be turned off.
•Only Cisco Ethernet switches are supported.
•Switch VLAN settings must be properly configured.
•CDP protocol must be enabled on all switches.
•An Ethernet connection must exist between the rogue access point and the Cisco switch.
•You should have some traffic between rogue access points and the Ethernet switch.
•The rogue access point must be connected to a switch within the max hop limit. The default hop count is 2, and the maximum is 10.
•If SNMPv3 is chosen, use the context option and create one for each VLAN, in addition to the one for the main group (which is required for non-VLAN-based MIBs).
Follow these steps to specify options for switch port tracing.
Using switch port tracing:
http://www.cisco.com/en/US/docs/wireless/wcs/6.0/configuration/guide/6_0ctrlcfg.html#wpmkr1083367
After you meet all requirements the logs are your best bet for determining why it is not working. They are usually pretty good at leading you to the problem.
You would go to Administration > Logging and uncheck Status Polling, Configuration, SNMP Mediation, MSE/Location Servers, XML
Mediation, Navigator, Reports and Database Administration and change the message level to TRACE and click submit. Go back and recreate the issue
and then go back to the logging area and download the logs.
If you get the logs right after the test it should be in the wcs-0-0.log file and you will want to go from the bottom up and search for something like "
Switch port tracing failed". Around there will be why it failed.

WCS very sluggish

I'm working on a new installation of WCS (7.0.172) and it is extremely slow. I haven't got my permanent license (should be in by tommorow), so maybe it has something to do with the evaluation licenses. The server itself (Windows Server 2003 R2, 32 bit) is running very fast. (Single processor, 4GB of RAM). Memory utilization is fairly low. I have added an MSE to the system, the maps for 2 floors, and one controller, but other than that is it brand new. Any ideas? When I go to the server diags all of the pages there are quick.

No idea.
It could be the server itself being slow for some reason (check the process manager when WCS is being used to see any cpu usage) or it could be that snmp traffic is slow on the network because of high retransmissions or broadcast storm or whatever else.

Questions on Weblogic SNMP

Hi,
I have managed to start WLS snmp agent in Solaris2.7 but I have a couple
of questions on the following:
./snmpget stage57 public
.1.3.6.1.4.1.140.600.20.1.20.10.115.116.97.110.100.97.108.111.110.101.11.115.101.114.118.101.114.45.55.48.48.49
1) Why do I need to put in so many trailing numbers in order to snmpget
data from an object? What do these number mean? Any documnetation on
them? Based on the WLS MIB tree .1.3.6.1.4.1.140.600.20.1.20 is where
the serverState is located.
2) Why did serverState always return 1 (which means UP) even 2 minutes
after I brought down the server on port 7888 and ran the above on the
command line? In the startSNMPAgent.sh file, I have specify the port
number in this line "$JAVA weblogic.SNMPAgent -password 123 -serverURLs
t3://stage57:7888 -trapDestinations localhost:162".
enterprises.140.600.20.1.20.10.115.116.97.110.100.97.108.111.110.101.11.115.101.114.118.101.114.45.55.48.48.49
= 1
Any help is appreciated.
Jie Chen
http://home.cnet.com

Jie Chen <[email protected]> wrote in message news:[email protected]..
Hi,
I have managed to start WLS snmp agent in Solaris2.7 but I have a couple
of questions on the following:
./snmpget stage57 public
.1.3.6.1.4.1.140.600.20.1.20.10.115.116.97.110.100.97.108.111.110.101.11.115
.101.114.118.101.114.45.55.48.48.49
>
1) Why do I need to put in so many trailing numbers in order to snmpget
data from an object? What do these number mean? Any documnetation on
them? Based on the WLS MIB tree .1.3.6.1.4.1.140.600.20.1.20 is where
the serverState is located.- snmpget needs the OID of a specific instance of a Server in the
ServerTable. (see the SNMP RFCs for details on OID encoding - or i am sure i
have ans. this question in some other message in this newsgroup)
- or use snmpwalk with just '.1.3.6.1.4.1.140.600.20.1.20 ' . walk doesn't
need the specific OID.
>
2) Why did serverState always return 1 (which means UP) even 2 minutes
after I brought down the server on port 7888 and ran the above on the
command line? In the startSNMPAgent.sh file, I have specify the port
number in this line "$JAVA weblogic.SNMPAgent -password 123 -serverURLs
t3://stage57:7888 -trapDestinations localhost:162".
enterprises.140.600.20.1.20.10.115.116.97.110.100.97.108.111.110.101.11.115.
101.114.118.101.114.45.55.48.48.49
= 1the default refresh interval in the agent is 5 minutes. You can reduce that
if you want. See -refreshInterval @
http://www.weblogic.com/docs51/admindocs/snmpagent.html#use_agent
>
Any help is appreciated.
Jie Chen
http://home.cnet.com

WCS can't logon to ACS 3.3

Just fired up a new Windows WCS install and have been trying various optoins to get it to work with ACS (for admin only at this point). I've tried RADIUS (IETF) and tacacs+(Cisco IOS) with various failed attempts logged in ACS. Any ideas what I'm missing?
thanks

I've also been trying to use ACS to authenticate users to manage my WCS. I have not been able to make it work either. During my research I found this document which states it is no possible at this time. Not sure what version of ACS or WCS they are referring to.
http://www.cisco.com/en/US/products/ps6305/products_qanda_item09186a00807a60f0.shtml#apr6
I am using WCS 4.2.81 and ACS 4.1 (both on different servers) If this is possible I would like to know how I need to configure my ACS server.
regards,
cyril

LMS 4.0.1 and User tracking with SNMP v3

Hi! (again )
I've another problem with our new LMS 4.0.1.
We manage our devices with SNMP v3 but the user tracking don't want to work flawlessly.
I've attached an example from our SNMP configuration. Basicly it's the same in our devices.
1st the problem was that no matter what I did the User tracking didn't want to find any host. I left it and worked on something else. After 2 weeks suddenly appeard couple of thousand end host.
As earlier (LMS 2.6 or 3.2 with snmp v2) it is the same that LMS cannot differentiate normal end host and IP Phones although we have several thousand from both. But this is only one problem.
The other is that there are switches with the same IOS and SNMP configuration and from one I get the UT data and from another one I didn't get anything. Only from some 4506 (aprox. 12-15) and 6506 (2) works and we have 20+ 4506 and 10+ 6506. Not to mention the other switches (couple of houndred 2960 and 3750).
I'll be grateful if somebody could advice what to do.
Thanks
Gabor

Understanding Debugger Utility
The utility displays a report on the reasons why User Tracking failed to discover end hosts on specific ports.
In many cases, User Tracking may not perform as expected. This may be because of problems in other LMS applications. For instance LMS Server may have devices that are not discovered or inadequate VLAN discovery in Topology Services.
You can run the utility to troubleshoot problems, or provide the report and log generated by the utility when you contact TAC for help in diagnosing problems.
The debugger utility uses the data collected by LMS Server and reports the reasons for the missing ports in User Tracking.
This tool also has an SNMP component embedded which runs an SNMP query for the table as a part of verification for SNMP failure. For example, SNMP bugs in Catalyst operating system because of which User Tracking may fail to discover devices.
This generates an Action Report that you can use to analyze the data.
The Debugger Utility:
1. Checks the switch ports in a sequential order.
2. Reports violation of basic rules for each of the missing ports such as link ports and trunk ports.
3. Checks for SNMP retrieval of data, if the ports pass the validity check.
4. Generates an Action Report suggesting possible remedial actions to retrieve the valid missing ports.
Using Debugger Utility
The Debugger Utility is available at $NMSROOT/campus/bin/ (where $NMSROOT is the directory where you have installed CiscoWorks).
To run the Debugger Utility, run the command:
utdebug -switch switch-ip -port port1[,port2 ...] [-export filename]
where,
switch is the switch to which the end hosts are connected.
ports are the ports on the switch which have missing end hosts User Tracking.
-export filename specifies that the debug messages be stored in the file specified. If this option is not used, the messages are displayed on the console.
For example,
utdebug -switch 10.29.6.12 -port 5/12
utdebug -switch 10.29.100.10 -port Fa0/10
utdebug -switch 10.29.6.14 -port Gi6
Pretty sure you will find this and perhaps more in the build in help of LMS
Cheers,
Michel

ISE 1.1.1 cisco-av-pair:Wireless-WCS

Hello,
Has anyone configured ISE yet to authenticate WCS against ISE using RADIUS? I have created the Authorization Profiles with rule0=SuperUsers, tack0=...ect, but I am wondering how everyone has done the authentication and authorization rules. Any lessons learned would be great.
Kyle

Yes, I have patch 1 installed. I am trying to add the following cisco-av-pairs:
Wireless-WCS:role0=Admin
Wireless-WCS:task0=Users and Groups
Wireless-WCS:task1=Virtual Domain Management
Wireless-WCS:task2=Audit Trails
Wireless-WCS:task3=TACACS+ Servers
Wireless-WCS:task4=RADIUS Servers
Wireless-WCS:task5=Logging
Wireless-WCS:task6=License Center
Wireless-WCS:task7=Scheduled Tasks and Data Collection
Wireless-WCS:task8=User Preferences
Wireless-WCS:task9=System Settings
Wireless-WCS:task10=View Alerts and Events
Wireless-WCS:task11=Email Notification
Wireless-WCS:task12=Delete and Clear Alerts
Wireless-WCS:task13=Pick and Unpick Alerts
Wireless-WCS:task14=Ack and Unack Alerts
Wireless-WCS:task15=Configure Controllers
Wireless-WCS:task16=Configure Templates
Wireless-WCS:task17=Configure Config Groups
Wireless-WCS:task18=Configure Access Points
Wireless-WCS:task19=Scheduled Configuration Tasks
Wireless-WCS:task20=Migration Templates
Wireless-WCS:task21=Configure Choke Points
Wireless-WCS:task22=Configure Spectrum Experts
Wireless-WCS:task23=Configure ACS View Servers
Wireless-WCS:task24=Auto Provisioning
Wireless-WCS:task25=Monitor Controllers
Wireless-WCS:task26=Monitor Access Points
Wireless-WCS:task27=Monitor Clients
Wireless-WCS:task28=Monitor Tags
Wireless-WCS:task29=Monitor Security
Wireless-WCS:task30=Monitor Chokepoints
Wireless-WCS:task31=Monitor Spectrum Experts
Wireless-WCS:task32=RRM Dashboard
Wireless-WCS:task33=Mesh Reports
Wireless-WCS:task34=Client Reports
Wireless-WCS:task35=Performance Reports
Wireless-WCS:task36=Security Reports
Wireless-WCS:task37=Compliance Assistance Reports
Wireless-WCS:task38=Voice Audit Report
Wireless-WCS:task39=Config Audit Dashboard
Wireless-WCS:task40=Location Server Management
Wireless-WCS:task41=View Location Notifications
Wireless-WCS:task42=Maps Read Only
Wireless-WCS:task43=Maps Read Write
Wireless-WCS:task44=Client Location
Wireless-WCS:task45=Rogue Location
Wireless-WCS:task46=Planning Mode
Wireless-WCS:task47=High Availability Configuration
Wireless-WCS:task48=Health Monitor Details
Wireless-WCS:task49=Configure WIPS Profiles
Wireless-WCS:task50=Global SSID Groups
Wireless-WCS:task51=WIPS Service
Wireless-WCS:task52=Configure Lightweight Access Point Templates
Wireless-WCS:task53=Configure Autonomous Access Point Templates
Wireless-WCS:task54=Guest Reports
Wireless-WCS:task55=Handover Server Management
Wireless-WCS:task56=Monitor Handover Server
Wireless-WCS:task57=Configure Ethernet Switch Ports
Wireless-WCS:task58=Configure Ethernet Switches
Wireless-WCS:task59=Monitor Interferers
Wireless-WCS:task60=Device Reports
Wireless-WCS:task61=Network Summary Reports
Wireless-WCS:task62=Compliance Reports
Wireless-WCS:task63=CleanAir Reports
Wireless-WCS:task64=Report Launch Pad
Wireless-WCS:task65=Run Reports List
Wireless-WCS:task66=Saved Reports List
Wireless-WCS:task67=Report Run History
Wireless-WCS:task68=Automated Feedback
Wireless-WCS:task69=TAC Case Attachment Tool
Wireless-WCS:task70=Ack and Unack Security Index Issues
Wireless-WCS:task71=View Security Index Issues
Wireless-WCS:task72=Monitor Media Streams
Wireless-WCS:task73=Voice Diagnostics
Wireless-WCS:task74=ContextAware Reports
Thanks,
Kyle

Event manager script not working as expected

On a Cisco 4900M running Version 12.2(53)SG1, trying to capture certain information requested by Cisco TAC to troubleshoot periodic high cpu usage on the device causing it to momentarily not respond to HSRP packets from the HSRP partner.
This is the script in place today:
event manager applet capture_cpu_spike
event snmp oid 1.3.6.1.4.1.9.2.1.56 get-type next entry-op ge entry-val "80" exit-time 10 poll-interval 1
action 1.0 syslog msg "CPU Utilization is high"
action 2.0 cli command "en"
action 3.0 cli command "show proc cpu sort | redirect bootflash:cpuinfo1.txt"
action 3.1 cli command "show int summ | redirect bootflash:cpuinfo2.txt"
action 3.2 cli command "show proc cpu sort | redirect bootflash:cpuinfo3.txt"
action 3.3 cli command "show int summ | redirect bootflash:cpuinfo4.txt"
action 3.4 cli command "show platform cpu packet statistics | redirect bootflash:cpuinfo5.txt"
action 3.5 cli command "show platform health | redirect bootflash:cpuinfo6.txt"
action 4.0 cli command "end"
Problem is, when the cpu does spike, only action 3.1 is executed.
How do I modify this script to run all the commands listed?
TIA
dom

Let me first explain why your script is not working for you.
Basically, the problem you encounter is a result of a common misconception about copyin(). It is intended to be used to copy content of userspace memory into a scratch buffer so that it can be accessed directly from within kernel space (where the DTrace core executes). That said, it is often interpreted as somehow being equivalent to malloc() whereas in reality it actually works like alloca() instead. So, what you are seeing is basically the artefact of the scratch buffer being overwritten with other data. And unfortunately, that is perfectly legal.
The content of the scratch buffer pointed to by self->addr in your script is only valid for as long as the specific probe enabling is executing (it is clause-local). So, your clauses to print out the actual bytes in the buffer are looking at a buffer that is for all intends and purposes no longer reserved, and therefore you are looking at it after other data was written to the scratch space.
So... in order for this to work, you should do things a bit different. Rather than trying to get a copy of the buffer in one clause, and then read from it in following clauses, you can simply collect the buffer address in the entry read:entry clause, get the number of bytes read in the first read:return clause, and then for every clause in which you print 4 bytes do the following (example for bytes 4-7):
syscall::read:return
/execname == "foobar" && self->nbytes > 4/
this->addr = (char *)copyin((uintptr_t)self->bufferaddr + 4, 4);
printf(" 4- 7: %02x %02x %02x %02x\n", this->addr[0], this->addr[1], this->addr[2], this->addr[3]);
So basically, for every clause that print 4 bytes you copyin those bytes, and then print them out.

CSS 11501 - SNMP sysname

Hi All
Had a basic query on SNMP polling for CSS 11501..
Im polling a CSS through Ethernet Management Interface, and the SNMP servers are detecting the system name as "Support" instead of the hostname of the device..
SNMP get sysname from x.x.x.x with ****
.1.3.6.1.2.1.1.5.0 = Support
Is there a way to alter the SNMP sysname, to be identical to the hostname of the device ? I dont have issues with other components like routers, switches etc..
Raj

Hi Sachin,
Use the snmp name command to set or modify the SNMP name for this system.
You can specify only one name.
The syntax for this global configuration mode command is as follows:
snmp name "name"
Enter the SNMP name as the unique name assigned to a system by the administrator.
Enter a quoted text string with a maximum of 255 characters.
The standard name convention is the system's fully qualified domain name (for example, [email protected]).
For example:
(config)# snmp name "[email protected]"
To remove the SNMP name for a system and reset it to the default of "Support", enter:
(config)# no snmp name
Best regards,
Sachin Garg

Campus Manager

Hello,
I wonder if anyone can help, I have 7 Cisco 3750s that as soon as the Data Collection Schedule kicks in, every 4 hours, SNMP stops on the switches. The switches are still available on the network however Fault Manager and our separate SNMP monitoring tool flag up the issue.
I have other 3750 switches with the same IOS on them and they are not affected.
Has anyone seen this before?
Thanks in advance,
David.

Hi there,
Thanks for that d sorry for the late reply, I have been on holiday. Here is the output from sh stack PID
#sh stack 253
Process 253: IP SNMP
Stack segment 0x407A8B0 - 0x407D790
FP: 0x407D6C0, RA: 0x1254EE4
FP: 0x407D780, RA: 0xA6B34
FP: 0x407D788, RA: 0x941AF0
FP: 0x0, RA: 0x9387B8
#sh stack 253
Process 253: IP SNMP
Stack segment 0x407A8B0 - 0x407D790
FP: 0x407D6C0, RA: 0x1254EE4
FP: 0x407D780, RA: 0xA6B34
FP: 0x407D788, RA: 0x941AF0
FP: 0x0, RA: 0x9387B8
#sh stack 253
Process 253: IP SNMP
Stack segment 0x407A8B0 - 0x407D790
FP: 0x407D6C0, RA: 0x1254EE4
FP: 0x407D780, RA: 0xA6B34
FP: 0x407D788, RA: 0x941AF0
FP: 0x0, RA: 0x9387B8
#sh stack 255
Process 255: SNMP ENGINE
Stack segment 0x40806C8 - 0x40835A8
FP: 0x40831E8, RA: 0x1254EE4
FP: 0x4083220, RA: 0x51FC70
FP: 0x4083238, RA: 0x58AFB4
FP: 0x4083260, RA: 0x58B1B8
FP: 0x4083340, RA: 0x587E7C
FP: 0x4083360, RA: 0x5893F4
FP: 0x4083380, RA: 0x58978C
FP: 0x4083388, RA: 0x41D904
FP: 0x40833A0, RA: 0x94642C
FP: 0x40833B0, RA: 0x946584
FP: 0x40833C8, RA: 0x9468F8
FP: 0x40833D0, RA: 0x41D364
FP: 0x40833F0, RA: 0x117D5C0
FP: 0x4083428, RA: 0x117BDBC
FP: 0x4083470, RA: 0x115EAB0
FP: 0x40834D8, RA: 0x1135D78
FP: 0x4083540, RA: 0x1128B1C
FP: 0x4083598, RA: 0x114FFCC
FP: 0x40835A0, RA: 0x941AF0
FP: 0x0, RA: 0x9387B8
#sh stack 255
Process 255: SNMP ENGINE
Stack segment 0x40806C8 - 0x40835A8
FP: 0x40831E8, RA: 0x1254EE4
FP: 0x4083220, RA: 0x51FC70
FP: 0x4083238, RA: 0x58AFB4
FP: 0x4083260, RA: 0x58B1B8
FP: 0x4083340, RA: 0x587E7C
FP: 0x4083360, RA: 0x5893F4
FP: 0x4083380, RA: 0x58978C
FP: 0x4083388, RA: 0x41D904
FP: 0x40833A0, RA: 0x94642C
FP: 0x40833B0, RA: 0x946584
FP: 0x40833C8, RA: 0x9468F8
FP: 0x40833D0, RA: 0x41D364
FP: 0x40833F0, RA: 0x117D5C0
FP: 0x4083428, RA: 0x117BDBC
FP: 0x4083470, RA: 0x115EAB0
FP: 0x40834D8, RA: 0x1135D78
FP: 0x4083540, RA: 0x1128B1C
FP: 0x4083598, RA: 0x114FFCC
FP: 0x40835A0, RA: 0x941AF0
FP: 0x0, RA: 0x9387B8
I have also attached the switch config.
I really appreciate your hep with this.
Thanks,
David.

Managing a WCS by SNMP

Similar Messages

Maybe you are looking for