Specifications

for seq 1, return code: Egress-ok, time: 3993729.963 ms <--- Local transmit time:
2013-04-29 12:05:06 IST 873.491 ms Remote receive time: 2013-04-29 12:05:06 IST
3994603.454 <---- This is a cosmetic issue and current software limitation. PR891734
•
Although NSR does not support mplsoamd and it does not run on backup Routing
Engine, backup rpd is attempting to do task_connect to mplsoamd. This behavior
causes periodical message popping up on backup Routing Engine. rpd[2840]:
task_connect: task MPLSOAMD I/O./var/run/mplsoamd_control addr
/var/run/mplsoamd_control: No such file or directory. PR938284
•
If we set the following configuration and hit "show mpls admin-groups-extended"
command, we can see this issue. In this case, we don't set "admin-groups" for
"admin-groups-extended-range". << conifg >> set routing-options
admin-groups-extended-range minimum 50 set routing-options
admin-groups-extended-range maximum 300 set protocols mpls interface all <<
show command >> lab@cheese# run show mpls admin-groups-extended error:
timeout communicating with routing daemon <<<<<<<<<<<<<<<<<< we need to
wait this message about 30 seconds - 60 seconds. PR966613
•
When we set the following configuration, we can see this issue. << configuration >>
set routing-options admin-groups-extended-range minimum 2147483647 set
routing-options admin-groups-extended-range maximum 3500000000 set
routing-options admin-groups-extended test1 group-value 2147483647 set
routing-options admin-groups-extended test2 group-value 2147483648 set protocols
mpls interface all << show command >> lab@cheese# run show mpls
admin-groups-extended Group Value test1 2147483647 test2 -2147483648
<<<<<<<<<<<<<<<< Extended administrative groups range: [
2147483647..-794967296 ] <<<<<<<<<<<<<<< PR966615
Network Management and Monitoring
•
When syslog server is configured using hostname, after Routing Engine switchover
router stopped sending the syslogs to external syslog server. Immediately after
switchover, DNS was not accessible because it will take some time to learn route to
DNS. System stopped retrying DNS resolution and syslogging stopped. System was
running GRES (no NSR). PR947869
•
show snmp get/getnext for OID greater than 128B fails from router, the fix for this PR
adds support for "show snmp get/getnext" for OIDs greater than 128B. PR1063516
Platform and Infrastructure
•
Adaptive load-balance functionality is only supported for unicast traffic. If the aggregate
bundle contains logical interfaces for bridge or vpls domains, flooded traffic might get
dropped. PR821237
•
When scripts are synchronized from one Routing Engine to the other, the destination
for the scripts in the other Routing Engine should be based on the configuration on the
other Routing Engine. This issue prevents this from happening and destination for
scripts depends on the current Routing Engine from which the scripts was synchronized
instead of the configuration on the other Routing Engine. PR841087
75Copyright © 2015, Juniper Networks, Inc.
Known Issues