| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
| |
Now also populates snmpresults artificially with data from LLDP when
needed.
|
| |
|
|
|
|
|
| |
Still need to populate the ipmap with results from LLDP somehow.
E.g.: If we can't contact a switch over SNMP that we see over LLDP we know
the sysname and IP.
|
| |
|
|
|
|
|
| |
This removes the actual mapping, but introdcues crawling.
All the data for mapping is there, and now the collision detection and
fixing is starting to look actually sensible.
|
| | |
|
| | |
|
| |
|
|
|
| |
The lldp-only map ensures we aren't fooled by vlans and other logical
links, but if lldp is disabled it obviously doesn't tell the whole story.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
what?
lol...
just figure it out for me.
Ok, so the tool isn't entirely done, but it departs from the simple
lldpdiscver.pl method that was very limited when things weren't working as
they should.
The long-term idea of lolwhat is that it should be able to do all sorts of
discovery. Right now it just takes a list of IPs and figures out how things
are connected by SNMP. It uses LLDP info from SNMP, but it does not
_currently_ traverse new hosts based on what it finds.
|
| |
|
|
|
|
|
|
| |
Still needs lots of work, but mainly with regards to gluing it all
together.
Possibly populate a nice little "local macs" hash to map mac addresses to
systems/ports easily.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
moving things that need work into extras/
|
