Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About UWE STEINHAU
UWE STEINHAU
Beginner
Over 38 years of experience in the
communications field including installation and maintenance of Local and Wide Area Networks;
installation, maintenance and repair of microcomputers and network related hardware; System Administration for a variety of platforms and Operation Systems, hardware design, software design and custom coding.
Recent Badges
Stats
Member since
01-25-2010
18
Posts
0
Helpful
0
Solutions
09-16-2016
04:42 PM
Kamil,
Looks pretty good but it probably won't run as is. You'll need to change:
my $sysUptime = '1.3.6.1.2.1.1.3;
to
my $sysUptime = '1.3.6.1.2.1.1.3.0';
and it should run fine.
= Uwe =
... View more
09-15-2016
10:07 PM
The exact code would depend on whether your ASA is configured for SNMPv2 or SNMPv3. Which SNMP version is configured on this device?
For a PERL script you would need some PERL modules or have the SNMP utilities installed, which you could then call from within the PERL script or simply call the SNMP client from a SHELL script. The exact syntax of the SNMP query depends on the installed SNMP package on the systems issuing the query. You could always read the man page (man snmpget) or run a query with the -h switch (snmpget -h) to find out how to build your query. I would need more info as to how the SNMPv3 agent on the ASA is configured to build a proper example of the SNMPv3 query.
This simple SNMPv2 example is for NetSNMP package version 5.6.2.1 with 'public' being the default read-only community string for SNMP queries:
snmpget -v2c -c public yourhostname .1.3.6.1.2.1.1.3 or snmpget -v2c -c public yourhostname .1.3.6.1.2.1.1.3.0
and should return the ASA's uptime since the last restart.
Inside the PERL script you would write the query to a string and then print the string to the screen:
$uptime = `snmpget -v2c -c public yourhostname .1.3.6.1.2.1.1.3.0`;
print $uptime;
Hope this gets you started.
= Uwe =
... View more
Created by
UWE STEINHAU
in Switching
in Switching
01-15-2013
09:23 PM
01-15-2013
09:23 PM
Hello, We have a series of 3750G access switches running 12.2(52)SE with IP SLA responder enabled. They are polled by a router outside a firewall. All switches reside on a Management VLAN using RFC1918 IPs with their default gateway address in the same Management VLAN. In order to allow router access to the IP SLA responder we provided the ability to route the packet back to the monitor by configuring an SVI. The SVI IP corresponds to the configured Host VLAN on these switches. This worked and still works great on the 3750G switches. When we upgraded some switches to 3750X platforms with IOS 15.0(2) the IP SLA monitor for the responders on the 3750X switches started timing out. As before, we see the router sending the IP SLA control packet to the SVI's IP address -- the response contains the switch's RFC1918 address rather than the SVI IP-address and therefore can't get back to the router. IP SLA functionality works fine on the 3750Xs as long as the queries stay on the Management VLAN. So, it's apparent that the issue seems to be with routing when sending the control packet to the SVI IP. Any ideas if there were changes in 15.0(2) that would induce this behavior? Do we have other options than to create a single-host static route for the router on the 3750Xs? Any help would be much appreciated. Thanks!! = Uwe =
... View more
Labels:
Created by
UWE STEINHAU
in Network Management
in Network Management
09-28-2010
05:07 AM
09-28-2010
05:07 AM
We wanted to see if there were any other solutions because we didn't want to lose the historical data but eventually deleted it and then let auto-discovery re-add it. That seems to have taken care of the problem. Thanks, Joseph!
... View more
Created by
UWE STEINHAU
in Network Management
in Network Management
09-24-2010
09:56 AM
09-24-2010
09:56 AM
NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/lib/pkgs are shown in attached file LMS_packages.txt NMSROOT/www/classpath/com/cisco/nm/xms/psu/pkgs/rme are shown in attached file RME_packages.txt
... View more
Created by
UWE STEINHAU
in Network Management
in Network Management
09-24-2010
06:23 AM
09-24-2010
06:23 AM
All device packages are up to date.
... View more
Created by
UWE STEINHAU
in Network Management
in Network Management
09-21-2010
07:39 AM
09-21-2010
07:39 AM
We just replaced some older routers with 1941's running the K9 of 15.0(1)M3 and "Sync on Device" no longer works in RME 4.2.0 and throws the following error: CM0100 Copy PRIMARY Running Config to PRIMARY Startup Config on device failed Cause: MgmtOperation RUNNING2STARTUP is not supported on automatically supported. However doing this manually on the router works just fine. #copy running-config startup-config Destination filename [startup-config]? Building configuration... [OK] The cause for the "out of sync" is shown below: Startup config: Using 5116 out of 262136 bytes Running config: Building configuration... Current configuration : 5116 bytes The "out of sync" errors persist even after manually doing a 'copy running-config startup-config`. Any help would be appreciated. Also, is there a list of exclude commands? Thanks...!!! = Uwe =
... View more
Labels:
Created by
UWE STEINHAU
in Network Management
in Network Management
06-15-2010
01:49 PM
06-15-2010
01:49 PM
I had the same problem and believe the issue is that you probably have a trap server configured and are using the same snmp-server group for the trap server and your queries. I created another group for SNMPv3 queries and the configuration no longer seems to get overwritten. Here's what I did. Go into config mode and create a group just for the trap server - let's call it TRAPS. I used priv and it looks like that's what you use. Don't worry about defining any MIB views as this group will automatically populate the notifyview once the trap servers below are added to the config. (...and will remove the readview and writeview entries after reboot - that's why a second group is needed). Remove your old trap server entries and set up the new trap server using the new group called TRAPS. snmp-server group TRAPS v3 priv snmp-server host version 3 priv TRAPS Now create another group for queries only - (let's call it QUERIES but you could just use your current group XXX since it's already set up) - I like the v1default MIB view for both reads and writes but you can limit the MIBs with the snmp-server view command. I am using md5 and des56 here - your case may be different - and set up the user (or keep the one you already have configured) snmp-server group QUERIES v3 priv read v1default write v1default access snmp-server user QUERIES v3 auth md5 priv des56 Exit and check the config. The group TRAPS should have the notifyview set. The group QUERIES should have the readview and writeview set to v1default (or whatever view you chose to enter here). The two SNMPv3 groups should look like this: #sh snmp group groupname: TRAPS security model:v3 priv readview : writeview: notifyview: *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.F row status: active groupname: QUERIES security model:v3 priv readview : v1default writeview: v1default notifyview: row status: active access-list: 4 The old trap server entry using the old group XXX should have been removed already. Verify that the user: entry says TRAPS #sh snmp host Notification host: xxx.xxx.xxx.xxx udp-port: 162 type: trap user: TRAPS security model: v3 priv Finally make sure the user is in the correct group (QUERIES): #sh snmp user User name: Engine ID: xxxxxxxxxxxxxxxxxxxxxxxxxx storage-type: nonvolatile active Authentication Protocol: MD5 Privacy Protocol: DES Group-name: QUERIES If all is well - write the config. You should now be able to perform a coldstart without losing your SNMPv3 config. Please, let me know if this worked for you.
... View more
Created by
UWE STEINHAU
in Network Management
in Network Management
06-14-2010
01:04 PM
06-14-2010
01:04 PM
Same issue here with a WS-C3750G-24PS running (C3750-IPBASEK9-M), Version 12.2(35)SE5.
... View more
Created by
UWE STEINHAU
in Network Management
in Network Management
05-20-2010
08:31 AM
05-20-2010
08:31 AM
One addition to this. Just noticed that the server having trouble displaying the Events Summary also won't run DFMCTMStartup. When starting it either from CLI with pdexec or from the GUI the process will only run for 1 second before it gets shut down with state: "Administrator has shut down this server".
... View more
Created by
UWE STEINHAU
in Network Management
in Network Management
05-20-2010
07:03 AM
05-20-2010
07:03 AM
Hi, we have two stand-alone LMS 3.1 boxes running Solaris 10 which are identically configured. Both recently began to have issues with the DFM. When refreshing the DFM window manually we see the following for the High Severity Alerts: High Severity Alerts An exception occurred. Please check the AAD.log file for further details. This is always followed ~45 seconds later by a normal refresh of the HSA portlet showing the High Severity alerts. When this occurs we also notice this problem: DFM Events Summary Cannot retrieve Device Summary, Please see the DeviceManagement.log file for more information. This behavior is observed on both servers. The issue below, however, is only seen on one of them. The DFM Events Summary portlet shows this when the above error isn't present: DFM Events Summary No Devices are encountered with Critical Events. There are Critical Events in the history for this server and they are shown in the High Severity Alerts portlet. When setting up the DFM Events Summary portlet to use identified critcal events (ie. HighUtilization, OperationallyDown, Flappeing etc) the portlet will always show a count of '0' for any and all selected events. We also noticed that the numbers in the CS Device Allocation Summary and the known hosts in DFM were off by one (555 vs 552, respectively). The identified host was removed from CS and manually re-added. However, the known hosts in DFM after rediscovery still only show 552. Don't know if these two issues are related but I thought I'd mention it since it needs to be fixed, as well Any help would be appreciated. Thanks!!! = Uwe =
... View more
Labels:
Created by
UWE STEINHAU
in Network Management
in Network Management
02-19-2010
12:40 PM
02-19-2010
12:40 PM
Yes, I did run it as root. I could download a different version of lsof (currently lsof 4.80).
... View more
Created by
UWE STEINHAU
in Network Management
in Network Management
02-19-2010
10:19 AM
02-19-2010
10:19 AM
The subscriber list is empty because we could not add the subscription after the swapping the certs. Sorry, was asked to obscure the host names - it shows host name only not FQDN. SyslogCollector - [Thread: main] INFO , 14 Feb 2010 10:37:33,198, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 14 Feb 2010 10:37:33,201, System Initialized. SyslogCollector - [Thread: main] INFO , 14 Feb 2010 10:37:36,694, Service started... SyslogCollector - [Thread: Thread-9] WARN , 14 Feb 2010 10:42:04,383, Unable to add monitor for SyslogCollector - [Thread: SyslogObjectForwarder] ERROR, 14 Feb 2010 11:07:42,369, Could not send syslogs, removing the subscriber...Connection refused SyslogCollector - [Thread: main] INFO , 14 Feb 2010 11:23:02,499, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 14 Feb 2010 11:23:02,501, System Initialized. SyslogCollector - [Thread: main] INFO , 14 Feb 2010 11:23:02,850, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 14 Feb 2010 11:23:06,047, Service started... SyslogCollector - [Thread: main] INFO , 14 Feb 2010 23:59:33,732, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 14 Feb 2010 23:59:33,735, System Initialized. SyslogCollector - [Thread: main] INFO , 14 Feb 2010 23:59:34,148, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 14 Feb 2010 23:59:37,352, Service started... SyslogCollector - [Thread: main] INFO , 15 Feb 2010 23:59:34,112, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 15 Feb 2010 23:59:34,115, System Initialized. SyslogCollector - [Thread: main] INFO , 15 Feb 2010 23:59:34,565, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 15 Feb 2010 23:59:38,168, Service started... SyslogCollector - [Thread: main] INFO , 16 Feb 2010 11:57:43,806, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 16 Feb 2010 11:57:43,816, System Initialized. SyslogCollector - [Thread: main] INFO , 16 Feb 2010 11:57:44,220, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 16 Feb 2010 11:57:47,493, Service started... SyslogCollector - [Thread: main] INFO , 16 Feb 2010 14:12:00,424, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 16 Feb 2010 14:12:00,427, System Initialized. SyslogCollector - [Thread: main] INFO , 16 Feb 2010 14:12:00,781, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 16 Feb 2010 14:12:04,007, Service started... SyslogCollector - [Thread: main] INFO , 16 Feb 2010 23:59:33,851, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 16 Feb 2010 23:59:33,854, System Initialized. SyslogCollector - [Thread: main] INFO , 16 Feb 2010 23:59:34,303, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 16 Feb 2010 23:59:37,834, Service started... SyslogCollector - [Thread: main] INFO , 17 Feb 2010 16:42:51,156, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 17 Feb 2010 16:42:51,166, System Initialized. SyslogCollector - [Thread: main] INFO , 17 Feb 2010 16:42:51,516, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 17 Feb 2010 16:42:54,734, Service started... SyslogCollector - [Thread: main] INFO , 17 Feb 2010 23:59:33,673, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 17 Feb 2010 23:59:33,676, System Initialized. SyslogCollector - [Thread: main] INFO , 17 Feb 2010 23:59:34,130, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 17 Feb 2010 23:59:37,759, Service started... SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:55:42,526, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:55:42,533, System Initialized. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:55:42,886, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:55:46,111, Service started... SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:34,144, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:34,147, System Initialized. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:34,604, Subscriber list is empty! SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:38,116, Service started... Our secondary host shows a subscriber, however no syslog packets are seen. Also, this subscriber can not be unsubscribed (deleted). SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:09:19,098, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:09:19,101, System Initialized. SyslogCollector - [Thread: main] WARN , 18 Feb 2010 16:09:22,723, Unable to resurrect connection to a subscriber. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:09:22,770, Service started... SyslogCollector - [Thread: Thread-11] WARN , 18 Feb 2010 16:14:07,828, Unable to add monitor for SyslogCollector - [Thread: Thread-13] WARN , 18 Feb 2010 16:14:08,008, Unable to add monitor for SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:32:29,557, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:32:29,560, System Initialized. SyslogCollector - [Thread: main] WARN , 18 Feb 2010 16:32:33,205, Unable to resurrect connection to a subscriber. SyslogCollector - [Thread: main] WARN , 18 Feb 2010 16:32:33,263, Unable to resurrect connection to a subscriber. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:32:33,277, Service started... SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:33,728, Logging System Initialized. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:33,733, System Initialized. SyslogCollector - [Thread: main] WARN , 18 Feb 2010 23:59:37,786, Unable to resurrect connection to a subscriber. SyslogCollector - [Thread: main] WARN , 18 Feb 2010 23:59:37,857, Unable to resurrect connection to a subscriber. SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:37,869, Service started...
... View more
Created by
UWE STEINHAU
in Network Management
in Network Management
02-19-2010
08:11 AM
02-19-2010
08:11 AM
lsof -i :3333 and :4444 return nothing on either host.
... View more
Created by
UWE STEINHAU
in Network Management
in Network Management
02-19-2010
07:58 AM
02-19-2010
07:58 AM
Thanks for the fast reply. Web access is working on port 443. The only problem that crept up is the syslog collector issue. Both collector and analyzer processes are running. I don't have lsof on the boxes but I'll try to get a version and install it today.
... View more
09-16-2016
Kamil, Looks pretty good but it probably won't run as is. You'll need to
change: my $sysUptime = '1....
09-15-2016
The exact code would depend on whether your ASA is configured for SNMPv2
or SNMPv3. Which SNMP versi...
Created by
UWE STEINHAU
in Switching
01-15-2013
01-15-2013
Hello,We have a series of 3750G access switches running 12.2(52)SE with
IP SLA responder enabled. Th...
Created by
UWE STEINHAU
in Network Management
09-28-2010
09-28-2010
We wanted to see if there were any other solutions because we didn't
want to lose the historical dat...
Created by
UWE STEINHAU
in Network Management
09-24-2010
09-24-2010
NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/lib/pkgs are shown in attached
file LMS_packages.txtNMSROOT/w...
Created by
UWE STEINHAU
in Network Management
09-24-2010
09-24-2010
All device packages are up to date.
09-21-2010
We just replaced some older routers with 1941's running the K9 of
15.0(1)M3 and "Sync on Device" no ...
06-15-2010
I had the same problem and believe the issue is that you probably have a
trap server configured and ...
Created by
UWE STEINHAU
in Network Management
05-20-2010
05-20-2010
One addition to this. Just noticed that the server having trouble
displaying the Events Summary also...
Created by
UWE STEINHAU
in Network Management
05-20-2010
05-20-2010
Hi,we have two stand-alone LMS 3.1 boxes running Solaris 10 which are
identically configured. Both r...
Created by
UWE STEINHAU
in Network Management
02-19-2010
02-19-2010
Yes, I did run it as root. I could download a different version of lsof
(currently lsof 4.80).
Created by
UWE STEINHAU
in Network Management
02-19-2010
02-19-2010
The subscriber list is empty because we could not add the subscription
after the swapping the certs....
Created by
UWE STEINHAU
in Network Management
02-19-2010
02-19-2010
lsof -i :3333 and :4444 return nothing on either host.
Created by
UWE STEINHAU
in Network Management
02-19-2010
02-19-2010
Thanks for the fast reply. Web access is working on port 443. The only
problem that crept up is the ...
Public Statistics
| Date Registered | 01-25-2010 07:08 AM |
| Date Last Visited | 04-21-2019 09:15 PM |
| Total Messages Posted | 18 |
