Re: [j-nsp] syslog is flooded with curious messages (MX5 / 14.2R2.8)

Same problem here... Jan 22 09:05:04 router chassisd[1546]: Cannot read hw.chassis.startup_time: No such file or directory Jan 22 09:05:14 router last message repeated 2 times Jan 22 09:07:14 router last message repeated 24 times Jan 22 09:08:59 router last message repeated 21 times --

Re: [j-nsp] syslog is flooded with curious messages (MX5 / 14.2R2.8)

14.2R5, had frequent /kernel: hw.chassis.startup_time update to 1449495334.808647 messages. I just did something like set sytem syslog file messages kernel warning to drop them... > Le 22 janv. 2016 à 12:12, Eduardo Schoedler a écrit : > > Same problem here... > > Jan 22

Re: [j-nsp] syslog is flooded with curious messages (MX5 / 14.2R2.8)

On Fri, Jan 22, 2016 at 09:12:01AM -0200, Eduardo Schoedler wrote: > Same problem here... > > Jan 22 09:05:04 router chassisd[1546]: Cannot read hw.chassis.startup_time: > No such file or directory > Jan 22 09:05:14 router last message repeated 2 times > Jan 22 09:07:14 router last message

Re: [j-nsp] Mixed vcf question

Hello The scalability levels and features in a mixed mode vcf (for all switches that are part of the vcf) will be lowered to the levels of the lowest switch model. This means that the numbers of ae's, mac address table size, routing tables size, cos features etc for the whole vcf will (in your

Re: [j-nsp] Mixed vcf question

Hi William For example for the layer3 (max routes supported, etc) why not the one of the QFX5100 acting as routing engine (and spine)? Is there something stated on the juniper.net site? Cheers James Il 23/Gen/2016 00:32, "William Johansson" ha scritto: > Hello >

Re: [j-nsp] Mixed vcf question

Hi James ! You wrote : "For example for the layer3 (max routes supported, etc) why not the one of the QFX5100 acting as routing engine (and spine)?" It would not help you at all if the routing engine can hold for example 300k routes and then only 100k can be downloaded to the forwarding