Hi all, has anyone ever seen the behaviour below? I've been going back and forth with JTAC for months now without any result (which seems to be the norm nowadays...). We just upgraded a few M-series boxes from 9.3 to 9.5R3 and the issue still persists. It seems the issue was introduced in one of the earlier 9.x releases.
dan...@xxxxx> show route advertising-protocol bgp <ipv6 neighbor> error: timeout communicating with routing daemon Dec 16 16:20:23.671 2009 XXXXX mgd[73749]: %INTERACT-6-UI_CMDLINE_READ_LINE: User 'daniel', command 'show route advertising-protocol bgp <ipv6 neighbor> ' Dec 16 16:21:23.659 2009 XXXXX mgd[73749]: %DAEMON-5-UI_READ_TIMEOUT: Timeout on read of peer 'routing' It's most obvious with IPv6 neighbors receiving a full feed (+/- 2400 prefixes) from us, whereas the same command with an IPv4 neighbor receiving a full feed (>300k prefixes) is almost instantaneous. Cheers, Daniel. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
