-
Notifications
You must be signed in to change notification settings - Fork 32
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
EtherChannel info is not consistent across platforms #193
Comments
Hi Can you please share the device output to debug this issue further along with os and platform used. |
Hi
|
One of the other issues I have is that the type is different on them. On the Cat9k the type is EtherChannel and on the ASR it is GEChannel or 10GChannel. But I guess that is the devices information about the hardware. |
In the device output which you had shared, I don't see the GEChannel or 10GChannel in the output. Please share the device output of the parser command which you are trying. So that I can verify the same and share how the type is being processed. Or you can search for the command which you are trying in the genieparser repository, and try adding print to see how it is done. |
I am not sure what you mean about the output from the parser command. Could you help me understand that?
|
Just to be clear, my main issue is not that the hardware type is different on the platforms as it shows the actual hardware type as reported by the network device. |
Can you elaborate on what you mean by |
Hi @Taarini,
Where as on the other device type it did:
|
Okay. I think it could be due to some regex related issue. Can you share the device output of |
Hi @Taarini
|
There isn't a information on other interface like below
That is the reason in some of the other interface output, you see something like below, |
Hi Did you understand the output info which I had shared you above |
So my issue is that the parent interface(PortChannel) contains information about the child interfaces in the configuration. This is true for both the Cat9k and ASR. But the child interfaces only contains information about the parent interface on the Cat9k but not the ASR.
|
Hi Sorry for the delay in responding, Right now we don't have support specific to platform ASR and CAT9K Since genieparser is community driven, request you to add support for the command in both the platform. Below is the link to the steps in creating a new parser, https://pubhub.devnetcloud.com/media/pyats-development-guide/docs/writeparser/writeparser.html If you need any assistance in creating a PR for the above, I'm very happy to assist you through the process of approval |
Hi May I know whether you will be contributing for the above |
Hi @Taarini |
Hi @fatman00, No issues we will add it in our backlog based on priority and let you know once we support them |
When looking at the EtherChannel info on two different platforms Cat9500 and ASR1001 the naming and information in the data is not consistent.
As shown in the snippet below on the CAT9K The PortChannel consists of the 2 member ports, and the member ports includes information about the Po.
On the ASR the PortChannel has information about the member ports, but the member ports does not include Po information.
The text was updated successfully, but these errors were encountered: