Issues Fixed Since Last Release
Junos PRs That Affect AI-Scripts
Table 2: Junos PRs Affecting Devices Running AI-Scripts
PR/SUMMARY
Encoder error resulting in invalid JMBs
seen when performing API requests.
(PR 441511)
The AI-Scripts activation sequence
repeats every hour on EX platforms. (PR
440360)
Correct the transient-commit behavior.
(PR 386499)
AI-Scripts increase the commit time to
approximately 10 times, even with and
empty commit. (PR 294131)
The logger command causing an eventd
crash. (PR 428256)
©
Copyright
2010, Juniper Networks, Inc.
The following issues have been fixed in this AI-Scripts release:
Trim the link for the KB note for the event pfestat_req_receive. (PR 545464)
AI-Scripts workaround for JUNOS PR/520377, which generates duplicate chassis-module
subtags in Routing Engine section on M320 and some EX Series platforms. (PR 548758)
Modify the problem description field in problem-event-mrvl_brg_port_cist_init.slax to include
the related KB link. (PR 549035)
Trim the KB link for AI-Scripts problem-event-GenCfgBloberror.slax. (PR 551498)
AI-Scripts problem events for protocol-neighbor-related issues in BGP, OSPF, RSVP, and
ISIS have been removed. (PR 555122)
Modify attachments in AI-Scripts event-script problem-event-ichipregerr.slax. (PR 555489)
The following Junos PRs impact certain devices running AI-Scripts (See Table 2 on page 3).
FIX VERSIONS
•
Junos OS Release 9.3R4
•
Junos OS Release 9.4R3
•
Junos OS Release 9.5R2
•
Junos OS Release 9.6R1
•
Junos OS Release 10.0R1
•
Junos OS Release 9.6R1
•
Junos OS Release 9.5R3
•
Junos OS Release 10.0R1
•
Junos OS Release 9.5S1
•
Junos OS Release 9.5R1
•
Junos OS Release 9.6R1
•
Junos OS Release 9.3R1
•
Junos OS Release 9.0R4
•
Junos OS Release 9.4R1
•
Junos OS Release 9.2R3
•
Junos OS Release 9.1R4
•
Junos OS Release 9.5R1
•
Junos OS Release 9.5R2
•
Junos OS Release 9.4R3
•
Junos OS Release 9.6R1
Issues Fixed Since Last Release
IMPACT ON DEVICES RUNNING AI-SCRIPTS
All Junos platforms running Junos releases 9.3R1 –
R3. 9.4R1 – R2, or 9.5R1 can experience invalid or
incomplete JMBs generated when problem events are
detected.
Low-end devices without a hard drive may have
frequent log file rollovers, which signals eventd
internal times to reset, generating an iJMB.
Every commit signals eventd internal times to reset,
generating an iJMB, as well as extending the normal
commit time by approximately 20%.
Every commit time may be extended up to 10 times
the normal commit time.
Any event script that captures an event with two or
more attributes may cause eventd to crash.
31