Sep 182009
 
We are happy to announce the release of Port Report 1.12. In this release, we can now follow CDP Neighbors while using the –report or -r options. Before when you used the –report option, the script will report on just that one switch. Now if you pass the –follow or -f option with the –report or -r option, port_report will follow the CDP neighbors and create multiple CSV files.
Release notes are below…. If you want to see an example of the Port Report output and how to run it, please check this link
Revision 1.12 09/18/09

  • The report option of the script can now follow cdp neighbors using the –follow option or -f.
    When you run the command below it will create ONE CSV file per cdp neighbor it scanned.
    I was able to scan from my core Switch down to the last neighbor in the line ( 44 Neighbors in just under 20 minutes. )
    Which equaled to a little over 4K Mac Addresses
    For instance…port_report.py -d 192.168.101.1 -c public -r -f

Continue reading “LD Port Report 1.12 update aka the Host and MAC Reporting tool” »

Sep 152009
 
We are happy to announce the release of Port Report 1.11. In this release, we have fixed quite a few bugs that were in the previous release. Included in this release is the ability to follow EtherChannel aka PortChannel Ports using the Port Agreggation Protocol.
Release notes are below…. If you want to see an example of the Port Report output and how to run it, please check this link
LD Port Report == Download
Revision 1.11 09/13/09

  • More code clean up and another increase in speed.
  • Also port_report can now follow EtherChannel
  • Fixed issue, where the matching of the cdp neighbor was not matching correctly
  • Added better verbosity
  • Added Sanity Checking for cdp neighbors

Revision 1.10 09/09/09

  • Code Clean up and a slight increase in speed ( by a few seconds ) during the search by mac or ip

Revision 1.9
Code changes and Added CDP Support

  • Detect CDP Neighbors during the scan for MAC Addresses or IP Addresses

Revision 1.8
Here is a quick update…..

  • I just add dns reverse lookups to the output of this script.

Revision 1.7
Adds support to the following devices..

  1. Cisco
    • Catalyst 6509 w/ Supervisor 720 running IOS
    • Catalyst 3560
    • Catalyst 3550 (SMI)
    • Cisco CIGESM series Chassis Blades
    • Cisco Catalyst 2960
  2. Foundry
    • Foundry Server Iron
  3. Nortel
    • Nortel Passport 8600
    • Nortel 5520 Ethernet Routing Switch
  4. HP
    • HP Procurve 5406xl

 

Revision 1.6
New additions to this revision ….

  • Support for HP Procurve Switches, ( Tested on the newer versions of HP )
  • combined switch_report.py in port_report.py.
  • Added –verbose flag

Previous Releases….

  • Search by MAC or IP or PORT

 

LD Port Reporter == Download

Feb 272009
 

Recently I had to input quite a few OID’s into Zenoss. This meant I had to create a Data Source for each OID I wanted to monitor as well as one Data Point.
Now I knew this was going to be a hassle!!! So I decided to write a custom Python script that uses pysnmp to essentially do a snmpwalk (nextCmd)
on a Branch of OID’s. This means that I can create one Data Source and Mutiple Data Points.
Which drops the amount of time that I have to input into the Zenoss GUI.

Please Post any questions about this script here http://www.linuxdynasty.org/forums/Scripting/scripting/snmp_branch_help
You can download the script snmp_branch.py

  • Update 1.0.10
    1. Fixed labeling bug, (Thanks Stephan26 for finding this)
    2. Added –fsearch option
      Thanks Stephan26 for suggesting to add a way to find OID’s by their begining Digits on their last Octect
    3. Added –length option
      This will allow you to search for an Index on the final Octect of the OID, when the final octect is not just the index.
      Example…. You want the index OID of 100 but the entire last octect of the OID is .6534389100)

 

So here is an example below of what the data looks like from SNMP..

UCD-SNMP-MIB::ssIndex.0 = INTEGER: 1UCD-SNMP-MIB::ssSwapIn.0 = INTEGER: 0UCD-SNMP-MIB::ssSwapOut.0 = INTEGER: 0UCD-SNMP-MIB::ssIOSent.0 = INTEGER: 0UCD-SNMP-MIB::ssIOReceive.0 = INTEGER: 1UCD-SNMP-MIB::ssSysInterrupts.0 = INTEGER: 3|UCD-SNMP-MIB::ssSysContext.0 = INTEGER: 19UCD-SNMP-MIB::ssCpuUser.0 = INTEGER: 7UCD-SNMP-MIB::ssCpuSystem.0 = INTEGER: 7UCD-SNMP-MIB::ssCpuIdle.0 = INTEGER: 84

 

Continue reading “HowTo monitor and add multiple Data Points the easy way in Zenoss” »

Jun 202008
 

Once we moved to VMWare ESX 3.+ we ran into a very annoying issue. The issue was that if you have multiple NICs from Multiple vendors, VMWare will reorder your NICs and cause havoc to you guys who use PXE boot/Kickstart. So I had to come with a work around that will alleviate this issue. I went ahead and created this script and I injected it in the post section of our kickstart profile and had it run after rebooting 3 times. Since After the third reboot the VMWare is done with its configuration, after the third reboot the script will run and then delete itself. Once all said and done your NICs will be in the proper order.

Some of you might just use it as a once shot deal manually and some of you might use it as I did, but I did not realize how many f you are having the same issue as I did. Since I posted this script it has ad close to 3000 hits. So for those of you who have used it and appreciated the work I have done or for those of you who have modified it and added to it. Please leave some feed back weather in the form of comments or in the forums.

Continue reading “Script to fix VMWare ESX 3.5 NIC Reordering after kickstart” »


Warning: fopen(/home/dynasty/linuxdynasty.org/wp-content/plugins/wp-google-plus-one/lib/standard.txt) [function.fopen]: failed to open stream: No such file or directory in /home/dynasty/linuxdynasty.org/wp-content/plugins/wp-google-plus-one/plusone.php on line 104

Warning: fread(): supplied argument is not a valid stream resource in /home/dynasty/linuxdynasty.org/wp-content/plugins/wp-google-plus-one/plusone.php on line 105

Warning: fclose(): supplied argument is not a valid stream resource in /home/dynasty/linuxdynasty.org/wp-content/plugins/wp-google-plus-one/plusone.php on line 106
.