Toke Høiland-Jørgensen <[email protected]> writes: > I think what's happening is a symbol collision: you've named your babel > instance 'babel', but the command line parser has 'babel' as a reserved > keyword, so it barfs.
Oh, fun. That'll be why I never noticed it before too, because I had multiple protocols called babel1, babel2, etc. > Or, given that you only have on instance, just run 'show babel > interfaces' with no arguments... When it's called 'babel', even that turns out to break: bird> show babel interfaces syntax error, unexpected CF_SYM_KNOWN All is fixed once I rename the protocol, as you say. Thanks! Best wishes, Chris.
