Key Features in Junos OS Release 22.1

Start here to learn about the key features in Junos OS Release 22.1. For more information about a feature, click the link in the feature description.

• Perpetual PoE (EX4400-24MP, EX4400-24P, EX4400-48MP, and EX4400-48P)—Starting in Junos OS Release 22.1R1, you can configure perpetual PoE on EX4400 switches that support Power over Ethernet (PoE). Perpetual PoE provides uninterrupted power to connected powered devices even when the power-sourcing equipment switch is rebooting.

  [See Configuring Perpetual PoE and Fast PoE.]

• Support for GeoIP filtering, global allowlist, and global blocklist with Juniper ATP Cloud (MX240, MX480, and MX960)—Starting in Junos OS Release 22.1R1, you can configure the Security Intelligence process (IPFD) on MX Series routers to fetch the GeoIP feeds from Juniper ATP Cloud. You can then use the feeds to prevent devices from communicating with IP addresses belonging to specific countries.

  You can define:

  • A profile to dynamically fetch GeoIP feeds. Include the geo-ip rule match country country-name statement at the [edit services web-filter profile profile-name security-intelligence-policy] hierarchy level.
  • A template to dynamically fetch GeoIP feeds. Include the geo-ip rule match group group-name statement at the [edit services web-filter profile profile-name url-filter-template template-name security-intelligence-policy] hierarchy level.

  You can configure a global allowlist by configuring the white-list (IP-address-list | file-name) statement at the edit services web-filter profile profile-name security-intelligence-policy hierarchy level. You can configure a global blocklist by configuring the black-list (IP-address-list | file-name) statement at the edit services web-filter profile profile-name security-intelligence-policy hierarchy level. Here, IP-address-list refers to the name of the list specified at the [edit services web-filter] hierarchy level. The file-name option refers to the name of the file where the list of the IP addresses to be allowed or blocked is specified. The file must be in the /var/db/url-filterd directory and must have the same name as in the configuration.

  [See Integration of Juniper ATP Cloud and Web filtering on MX Routers .]

• Avoid microloops in OSPFv2 segment routing networks (ACX5448, ACX6360, MX Series, PTX Series, and QFX10002) —Starting in Junos OS Release 22.1R1, you can enable post-convergence path calculation on a device to avoid microloops if a link or metric changes in an OSPFv2 segment routing network. Note that microloop avoidance is not a replacement for local repair mechanisms such as topology-independent loop-free alternate (TI-LFA), which detects local failure very fast and activates a precomputed loop-free alternative path.

  To configure microloop avoidance in an OSPFv2 segment routing network, include the maximum-labels and delay milliseconds statements at the [edit protocols ospf spf-options microloop avoidance post-convergence-path] hierarchy level.

  [See How to Configure Microloop Avoidance for OSPFv2 SR Networks.]