Hi. So, can we expect an answer ?
Thanks. With best regards, Dmitry S. Nikolaev Moscow, Russia phone: +7 (499) 678 8007 [ext. 6003] fax: +7 (499) 678 8007 [ext. 7777] www: http://www.mega-net.ru mail: dnikol...@mega-net.ru SIP URI: dnikol...@sip.mega-net.ru || d...@sip.mega-net.ru On 31.10.2017 13:39, Dmitry S. Nikolaev wrote: > Hi, hope you well. > > I also interested in this question. > Can someone from the developers say something about it ? > > Thanks. > > With best regards, Dmitry S. Nikolaev > Moscow, Russia > SIP URI: d...@sip.mega-net.ru > > On 26.10.2017 16:40, Mikhail Grishin wrote: >> Hi, >> >> 1) You also implemented >> enable bgp2 "enable message" >> This message currently seen only at local side and doesn't seen at >> remote peer. >> >> Scenario: You made maintenance work with the shutdown message "Session >> will be down from 13:00 till 14:00". >> Later session was established again. Days after at remote peer side >> still printed the same message. That's confusing. >> >> Suggestion: >> (May be) To show two different messages? Tx and Rx. >> To clear Rx message every time when BGP session state changed to >> established. >> >> >> 2) Is it possible to log such messages and see via syslog? >> >> P.S. For russian UTF8 text 128 bytes restriction (RFC) probably not >> always enough. >> >
