-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Cisco Switch and IOS - More info #21
Comments
Cisco more than likely edited the structure of the CDP packets. If LDWin needs to show the information, it will need to be updated to parse the correct sections of the updated packets. If you're in immediate need, Wireshark can capture the full packet and you can parse it for the information you're looking for. |
OK thanks for the heads up.
I may have access to some 9300 switches over the next couple of months so
I'll take a look.
Chris
…On Wed, 6 Mar 2019, 01:03 cascadeth, ***@***.***> wrote:
Cisco more than likely edited the structure of the CDP packets. If LDWin
needs to show the information, it will need to be updated to parse the
correct sections of the updated packets. If you're in immediate need,
Wireshark can capture the full packet and you can parse it for the
information you're looking for.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABGubT4E-9X0esdWvHUyAvHriHp4iuzAks5vTwXbgaJpZM4beZy6>
.
|
I can send a copy of what the switches are sending out if it helps. |
Yes please. You can get the raw tcpdump output as shown
https://github.com/chall32/LDWin/wiki/What-To-Do-If-LDWin-Captures-No-Data
Thanks
…On Wed, 6 Mar 2019, 09:22 gdbz, ***@***.***> wrote:
I can send a copy of what the switches are sending out if it helps.
It appears I’m getting two broadcasts - CDPv2 and LLDP. When we get the
LLDP information, there’s a lot of information - it’s all there, just
doesn’t show in LDWIN.
When we get the CDPv2 version, it formats fine in LDWIN but loses info
like VLAN ID
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABGubRcoU4ard7N3Ap0rB6LKrOJViYdIks5vT3rHgaJpZM4beZy6>
.
|
Here are 2 results from the switches... Run1: Run 2 tcpdump: listening on \Device |
If i do a 'Save Link data', the save file does have some of the required information in the file, it just doesn't list in the GUI. The Switch port is listed twice, but different info. Switch Name: ma:ca:dd:re:ss:he:re Switch Port: HR DATA |
It looks like when it receives LLDP data, LDWIN writes the SwitchPort in two places on different results, possibly overriding the information. |
Hey @gdbz could you please share your changes with us? |
We've been using LDWin for a long time and it's been great.
We've just put some new switches in (Cisco C9300-48P) and the data LDWIN gets isn't the same.
Port Identifier and Switch model, they are reporting different fields such as the IOS version on the switch model and our own description field on the Port ID instead of the port interface.
However, if we keep running 'get link data' we can occasionally see the correct info under those fields, but the then other fields, like VLAN Identifier are blank.
I'm wondering if Cisco have changed/increaed what information they are sending but LDWIN can only read so much of it?
The text was updated successfully, but these errors were encountered: