Q: Why was the line protocol down on pos not reporting to logbuffer
NE40E version: V300R003C02B697
The STM-1 link went down at 14:13 Hrs but no alarm has been reported to logbuffer. But only the below logs appeared in log file of CFCard.
May 13 2011 14:13:09 SKR-NE80E-A2 %%01TRUNK/5/MEMBER_DOWN(l): The status of the trunk member turns Down. (TrunkName=Ip-Trunk6, PortName=Pos9/0/6)
A: But we can change the logbuffer configuration with notifications level(security 5) which including security 0-5 in info center configuration.
[NE40E-3]info-center source default channel 4 log level ?
alerts Immediate action needed (severity=1)
critical Critical conditions (severity=2)
debugging Debugging messages (severity=7)
emergencies System is unusable (severity=0)
errors Error conditions (severity=3)
informational Informational messages (severity=6)
notifications Normal but significant conditions (severity=5)
warnings Warning conditions (severity=4)
[NE40E-3]info-center source default channel 4 log level notifications
1. Line protocol up/down is reported only in IP-Trunk level not POS level while one pos port is the member of one IP-Trunk. Now the IP-Trunk was not down due to other member of it was alive which is according to VRP mechanism.
2. Physical interface up/down is reported to logbuffer while pos port not receive power or can receive the SDH alarm from transmission.
3. The above log about trunk member turns down mentioned in alarm information is from logfile of CFCard with security 5. By default only security 0-4 (0 is most critical) can report to logbuffer. So above log with level 5 can’t report logbuffer as well. By default logbuffer only records the logs up to warnings (security 4).