Repository navigation
AsterNOS support #308
Description
Hello!
Thank you for creating this project, it looks awesome. I intend to use it on Asterfusion's SONiC switches running AsterNOS. They have a CLI that mimics Cisco CLI, but they have some quirks (some from SONiC itself and some more introduced by Asterfusion).
In addition to that, I'm bypassing CLI for almost everything that can go directly to CONFIG_DB redis database, leaving actual running-config with only the basic interfaces definitions and everything FRR related. So the interfaces section should be ignored, for example.
Do you have any idea of how well it would run in suck scenario?
Thank you!
Activity
jtdub commentedon Oct 23, 2026
Thanks for the interest. hier_config should work for this today, without a new driver.
AsterNOS mimics Cisco CLI, so start with the GENERIC platform or subclass the Cisco IOS driver, then register it as a custom platform:
https://hier-config.readthedocs.io/en/latest/admin/custom-drivers/
To ignore the interfaces section, add a post-load callback to your driver that deletes every
interfacechild from the tree after parse. The remediation then never sees those lines. If you prefer to keep the lines but hide them from output, use tag rules withexclude_tagsinstead:https://hier-config.readthedocs.io/en/latest/user/tags/
For the FRR section, you will need the
exit-address-familyhandling that the Cisco IOS rules already have. Subclass HConfigDriverCiscoIOS, or copy its sectional-exiting rule into your driver.For the SONiC and Asterfusion quirks, the rule reference covers negation, ordering, idempotent commands and callbacks:
https://hier-config.readthedocs.io/en/latest/dev/rule-reference/
If you can share a sanitized running-config and a sample intended config, I can check the parse and remediation output. If the quirks turn out to be stable, a built-in AsterNOS driver is possible later.
token47 commentedon Oct 23, 2026
Awesome, I'll try it. Depending on how it goes I'll post the configs so you can take a look. Thank you very much for the response!