Dell PowerConnect J-8208 Release Notes JUNOS version 10.3 - Page 16
Multilink, PoE, Security, The options to con the Custom Attacks, Custom Attack Groups
View all Dell PowerConnect J-8208 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 16 highlights
Junos 10.3 OS Release Notes • J-Web login page is updated with the new Juniper Networks logo and trademark. • The options to configure the Custom Attacks, Custom Attack Groups, and Dynamic Attack Groups are disabled because they cannot be configured from J-Web. Multilink • When data and LFI streams are present, we recommend the following configuration to get less latency for LFI traffic and to avoid out of order transmission of data traffic: Configure the following schedulers • set class-of-service schedulers S0 buffer-size temporal 20K • set class-of-service schedulers S0 priority low • set class-of-service schedulers S2 priority high • set class-of-service schedulers S3 priority high Configure the following scheduler map • set class-of-service scheduler-maps lsqlink_map forwarding-class best-effort scheduler S0 • set class-of-service scheduler-maps lsqlink_map forwarding-class assured-forwarding scheduler S2 • set class-of-service scheduler-maps lsqlink_map forwarding-class network-control scheduler S3 Attach scheduler map to all member links • set class-of-service interfaces t1-2/0/0 unit 0 scheduler-map lsqlink_map Even after this configuration, if Out-of-range sequence number drops are observed on reassembly side, please increase drop-timeout of the bundle to 200ms PoE • On J-SRX210 PoE devices, SDK packages might not work. Security • Any change in the Unified Access Control's (UAC) contact interval and timeout values in the J-SRX Series device will be effective only after the next reconnection of the J-SRX Series device with the Infranet Controller. • The maximum size of a redirect payload is 1450 bytes. The size of the redirect URL is restricted to 1407 bytes (excluding a few HTTP headers). If a user accesses a destination URL that is larger than 1407 bytes, the Infranet Controller authenticates the payload, the exact length of the redirect URL is calculated, and the destination URL is trimmed such that it can fit into the redirect URL. The destination URL can be fewer than 1407 bytes based on what else is present in the redirect URL, for example, policy ID. The destination URL in the default redirect URL is trimmed such that the redirect packet payload size is limited to 1450 bytes, and if the length of the payload is larger than 16