Thanks Phil Hopefully when we next upgrade, we'll end up with *both* of these fixes/PR resolutions.
Happy for it to be consistent one way or the other, but in the meantime, we're stuck with one of those PRs (PR 1383295), but not the other (PR 1384065). We have a dirty hack in the meantime of setting host-name as FQDN, and leaving domain-name blank. Best regards, James. On Tue, 15 Jan 2019 at 23:17, Phil Shafer <p...@juniper.net> wrote: > James Stapley writes: > >Not sure if we're the first people to notice this, but there seems to be a > >change in the way Junos deals with FQDN, host-name and domain-name with > our > >latest kit. > > These are the fixes for two PRs: > > PR 1383295 Domain name is not reported as part of the LLDP sysname > in "show lldp neighbor" command > PR 1384065 sysName of system mib does not include domain name > > The sysName brings up into conformance with the standard suggestion: > "By convention, this is the node's fully-qualified domain name", > while the LLDP fix brings up into conformance with "the rest of the > vendors". > > While backward compatibility is a priority, these were PRs and > intentional fixes to move toward standard behavior, and I'm told > they were in the release notes as customer visible changes. > > HTH > > Thanks, > Phil > > P.s.: No, I've no idea why 1384065 is marked confidential. > -- James Stapley Network Architect Information & Technology Services, Rhodes University t: +27 (0) 46 603 8849 PO Box 94, Grahamstown, 6140, South Africa www.ru.ac.za _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
