Skip to content
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.

Sign up for GitHub

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

Jump to bottom

frrinit.sh - OSPF6 Unknown command: agentx #15896

Closed
vecinohk opened this issue May 1, 2024 · 4 comments · Fixed by #15980
Closed

frrinit.sh - OSPF6 Unknown command: agentx #15896

vecinohk opened this issue May 1, 2024 · 4 comments · Fixed by #15980

Comments

@vecinohk
Copy link

vecinohk commented May 1, 2024

It's more of a cosmetic issue, but I'm just pointing it out.

If I use this snmp configuration for both daemons everything is fine:

zebra_options="  -A 127.0.0.1 -s 90000000 -M snmp"
ospfd_options="  -M snmp"
ospf6d_options=" -A ::1 -M snmp"

But if I want to use snmp only for OSPFv2:

zebra_options="  -A 127.0.0.1 -s 90000000 -M snmp"
ospfd_options="  -M snmp"
ospf6d_options=" -A ::1"

I get this warning when FRR starts:

May 01 03:33:14 frrinit.sh[777]: % [OSPF6] Unknown command: agentx
May 01 03:33:14 frrinit.sh[777]: line 5: Failure to communicate[2] to ospf6d, line: agentx

Tested on Debian 12 + Arch Linux and FRR 10.0.

Thanks
@ton31337
Copy link
Member

ton31337 commented May 2, 2024

Do you have agentx in frr.conf? Or per-daemon (ospfd.conf, ...)?

@vecinohk
Copy link
Author

vecinohk commented May 2, 2024

in frr.conf

!
frr version 10.0
frr defaults traditional
hostname home
log syslog informational
agentx
service integrated-vtysh-config
!

@ton31337
Copy link
Member

ton31337 commented May 2, 2024

Have you tried adding agentx per-daemon configuration file and removing from frr.conf?

@vecinohk
Copy link
Author

vecinohk commented May 2, 2024

So I haven't tried that, but I thought that option would be cancelled. Plus I love the unified config - frr.conf. Otherwise everything works fine for me - I just wanted to point out that this is how it behaves on startup. Isn't the solution to address this in the source code?

https://github.com/FRRouting/frr/releases/tag/frr-10.0
per-daemon config files no longer supported
Writing configuration works only with the unified configuration file frr.conf. I.e, writing to per-daemon config files is no longer supported.

donaldsharp added a commit to donaldsharp/frr that referenced this issue May 9, 2024
@donaldsharp
*: Modify agentx to be allowed to be called
88d3912 
If you had a situation where an operator turned on
ospfd with snmp but not ospf6d and agentx was configured
then you get into a situation where ospf6d would complain
that the config for agentx did not exist.  Let's modify
the code to allow this situation to happen.

Fixes: FRRouting#15896
Signed-off-by: Donald Sharp <[email protected]>
@donaldsharp donaldsharp mentioned this issue May 9, 2024
Merged
donaldsharp added a commit to donaldsharp/frr that referenced this issue May 9, 2024
@donaldsharp
*: Modify agentx to be allowed to be called
300ca69 
If you had a situation where an operator turned on
ospfd with snmp but not ospf6d and agentx was configured
then you get into a situation where ospf6d would complain
that the config for agentx did not exist.  Let's modify
the code to allow this situation to happen.

Fixes: FRRouting#15896
Signed-off-by: Donald Sharp <[email protected]>
donaldsharp added a commit to donaldsharp/frr that referenced this issue May 10, 2024
@donaldsharp
*: Modify agentx to be allowed to be called
73ad64a 
If you had a situation where an operator turned on
ospfd with snmp but not ospf6d and agentx was configured
then you get into a situation where ospf6d would complain
that the config for agentx did not exist.  Let's modify
the code to allow this situation to happen.

Fixes: FRRouting#15896
Signed-off-by: Donald Sharp <[email protected]>
mergify bot pushed a commit that referenced this issue May 20, 2024
@donaldsharp @mergify
*: Modify agentx to be allowed to be called
10757fb 
If you had a situation where an operator turned on
ospfd with snmp but not ospf6d and agentx was configured
then you get into a situation where ospf6d would complain
that the config for agentx did not exist.  Let's modify
the code to allow this situation to happen.

Fixes: #15896
Signed-off-by: Donald Sharp <[email protected]>
(cherry picked from commit 73ad64a)

# Conflicts:
#	ldpd/ldpd.c
@mergify mergify bot mentioned this issue May 20, 2024
Closed
odd22 pushed a commit to Orange-OpenSource/frr-orange that referenced this issue May 22, 2024
@donaldsharp @odd22
*: Modify agentx to be allowed to be called
cd39f6d 
If you had a situation where an operator turned on
ospfd with snmp but not ospf6d and agentx was configured
then you get into a situation where ospf6d would complain
that the config for agentx did not exist.  Let's modify
the code to allow this situation to happen.

Fixes: FRRouting#15896
Signed-off-by: Donald Sharp <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

*: Modify agentx to be allowed to be called donaldsharp/frr
2 participants
@ton31337 @vecinohk