Feature Requests

From Juniper Clue

While Juniper has produced some of the best router hardware and software available to date, there are still some areas which can be improved through innovative ideas and the practical experiences of network operators. Juniper accepts Feature Requests from its customers, but due to obvious business concerns will often give priority to requests which have significant revenue attached (for example, a large sale that is dependent on the implementation of a specific feature).

We hope that this list will both result in the adoption of the features listed, and inspire others to think of even more useful features. If you see a feature here which you think would be a good idea, please contact your Juniper representative and encourage them to open an enhancement request. The more companies that request a feature, and the more revenue that is associated with those requests, the more likely it is that the feature will be implemented.

Software-Only Feature Requests

• LNS capability on J series
• Default firewall filter term/action
• Disable command for BGP neighbors and groups
• Symbolic community definitions in static routes
• Unnamed AS-SET and Community references in policy-statements
• Automatic mapping of Ethernet unit numbers to VLAN ID
• Search and Sort options for the "show bgp summary" command
• Allow JunOS to be downloaded from Juniper from the router
• Configurable per-protocol default-actions
• Allow telnet to login without user/password, for route-server use
• BGP neighbor level prefix-list function, outside of policy-statements
• Issue warnings on console before rolling back a "commit confirmed"
• Reduce SNMP traps generated by BGP state changes
• Automatic sizing of policer burst values
• Enhance curses-interactive CLI "monitor" commands
• IS-IS overload wait-for-bgp (RFC3277)
• Implement a BGP "overload" setting
• Reduce IS-IS/PIM/Global restart-duration to more sensible values
• Optionally act as a stratum 10 local clock for NTP
• Backup REs should be able to do sane NTP clock sync without fxp0
• Default-originate mechanism for BGP neighbors
• Prefix-specific policer support for multiple, non-contiguous prefixes
• Implement buffering of syslog messages if there is no route to destination, similarly to SNMP trap buffering
• Ability to specify the filename for the automatic config upload feature
• Allow static routes to be set and configured via policy-statements or prefix-lists
• Option to set the channel numbering format
• CLI command to clear policer counters
• Enhance BFD Support
• Configuration auditing (count/find portions of configs referenced inside other configs)
• Rollback or undelete command for sub-sections of configurations
• Auto synchronization of commit/op/event scripts between Routing Engines
• Native BGP configuration for GTSM/TTL Security
• Archival of configuration in xml format
• Enhance BGP extended community features/support
• Configuration templating leveraging 'groups' using additional arguments
• Detect AS-PATH prepending

Possibly Hardware-affecting Feature Requests

• Maintain counters for the dsc discard interface.
• Add ability to record external power loss
• Ability to skip over IPv6 extension headers/hop-by-hop options when looking for UDP/TCP port numbers, flags, etc.

Resolved Feature Requests

• Add length modifiers to prefix-lists (Implemented in JUNOS 7.4)
• Allow empty BGP peer groups to exist (Implemented)
• Channelized DS3 config should be set separately from first CT3 channel
• Ability to filter on IPv6 TCP flags (Implemented in JUNOS 7.4)
• Allow automatic inclusion of external files into configuration (Implemented in JUNOS 7.4)
• Add "show route" flag for displaying active routes only (Implemented in JUNOS 8.0: show route active-path)
• Show ARP cache entry ages and incomplete entries in "show arp" (Implemented in JUNOS 8.1)
• Allow optional hiding of some configuration portions (Implemented in JUNOS 8.2)
• Command to generate test SNMP interface and BGP traps (Implemented in JUNOS 8.2)
• SNMP access filtering via prefix-list (Implemented in JunOS 8.5 with 'client-list-name')
• BGP prefix-limit on feasible routes, not just received routes (Implemented in JunOS 9.2 with 'accepted-prefix-limit')