Netgear XSM4324FS Product Data Sheet - Page 46

Other fields in PTPv2 packets Announce, Delay_Resp, Pdelay_Req and Pdelay_Resp are

Get Netgear XSM4324FS PDF manuals and user guides View all Netgear XSM4324FS manuals
Add to My Manuals
Save this manual to your list of manuals

Page 46 highlights

Data Sheet | M4300 series Intelligent Edge Managed Switches COS Queue Config Queue Parms configurable per-interface Yes Drop Parms configurable per-interface Yes Interface Traffic Shaping (for whole egress interface) Yes Minimum Bandwidth Yes Weighted Deficit Round Robin (WDRR) Support Yes Maximum Queue Weight 127 WRED Support Yes PTP - PTPv2 Feature Support PTPv2 All M4300 models, except 48-port 10G models (M4300-24X24F, M4300-48X, M4300-48XF) IEEE 1588 PTPv2 Section 10 and 11.5 Yes Implementation Limitations Transparent Clock (TC) End-to-End implementation considering the residence time of PTPv2 packets from ingress to egress Standalone mode, or Stack Master only. On M4300-52G and M4300-52G-PoE+ models, PTPv2 is supported between port 1 and port 24, and between port 25 and port 48. PTPv1 packets are forwarded but not processed (no PTPv1 support). Method Residence time of the PPTPv2 packet at the egress port level PTPv2 packet fields that are updated PTPv2 packet fields that are NOT updated The "Sync & Delay_Req" field of passing/egressing out PTPv2 packets is updated with the residence time in the switch Other fields in PTPv2 packets ("Announce", "Delay_Resp", "Pdelay_Req" and "Pdelay_Resp") are not updated Functional Summary - IETF RFC Standards and IEEE Network Protocols Core Management RFC 854 - Telnet RFC 855 - Telnet option specifications RFC 1155 - SMI v1 RFC 1157 - SNMP RFC 1212 - Concise MIB definitions RFC 1867 - HTML/2.0 forms with file upload extensions RFC 3414 - User-Based Security Model RFC 3415 - View-based Access Control Model RFC 3416 - Version 2 of SNMP Protocol Operations RFC 3417 - Transport Mappings RFC 3418 - Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) Configurable Management VLAN RFC 1901 - Community-based SNMP v2 RFC 1908 - Coexistence between SNMP v1 and SNMP v2 SSL 3.0 and TLS 1.2 - RFC 2246 - The TLS protocol, version 1.0 RFC 2068 - HTTP/1.1 protocol as updated by draft-ietf-http-v11-spec-rev-03 - RFC 2346 - AES cipher suites for Transport layer security RFC 2271 - SNMP framework MIB RFC 2295 - Transparent content negotiation - RFC 2818 - HTTP over TLS SSH 2.0 - RFC 4253 - SSH transport layer protocol RFC 2296 - Remote variant selection; RSVA/1.0 state management cookies - draft-ietf-http-state-mgmt-05 - RFC 4252 - SSH authentication protocol RFC 2576 - Coexistence between SNMP v1, v2, and v3 - RFC 4254 - SSH connection protocol RFC 2578 - SMI v2 - RFC 4251 - SSH protocol architecture RFC 2579 - Textual conventions for SMI v2 RFC 2580 - Conformance statements for SMI v2 RFC 3410 - Introduction and Applicability Statements for Internet Standard Management Framework - RFC 4716 - SECSH public key file format - RFC 4419 - Diffie-Hellman group exchange for the SSH transport layer protocol RFC 3411 - An Architecture for Describing SNMP Management Frameworks HTML 4.0 specification, December 1997 RFC 3412 - Message Processing & Dispatching RFC 3413 - SNMP Applications Java Script™ 1.3 PAGE 46 of 60

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
COS Queue Config
Queue Parms configurable per-interface
Drop Parms configurable per-interface
Interface Traffic Shaping (for whole egress interface)
Minimum Bandwidth
Weighted Deficit Round Robin (WDRR) Support
Maximum Queue Weight
WRED Support
Yes
Yes
Yes
Yes
Yes
127
Yes
PTP - PTPv2 Feature Support
PTPv2
All M4300 models, except 48-port 10G models (M4300-24X24F, M4300-48X, M4300-48XF)
IEEE 1588 PTPv2 Section 10 and 11.5
Yes
Implementation
Transparent Clock (TC) End-to-End implementation considering the residence time of PTPv2 packets from
ingress to egress
Limitations
Standalone mode, or Stack Master only. On M4300-52G and M4300-52G-PoE+ models, PTPv2 is
supported between port 1 and port 24, and between port 25 and port 48. PTPv1 packets are forwarded
but not processed (no PTPv1 support).
Method
Residence time of the PPTPv2 packet at the egress port level
PTPv2 packet fields that are updated
The "Sync & Delay_Req" field of passing/egressing out PTPv2 packets is updated with the residence time
in the switch
PTPv2 packet fields that are NOT updated
Other fields in PTPv2 packets ("Announce", "Delay_Resp", "Pdelay_Req" and "Pdelay_Resp") are not
updated
Functional Summary - IETF RFC Standards and IEEE Network Protocols
Core Management
RFC 854 — Telnet
RFC 3414 — User-Based Security Model
RFC 855 — Telnet option specifications
RFC 3415 — View-based Access Control Model
RFC 1155 — SMI v1
RFC 3416 — Version 2 of SNMP Protocol Operations
RFC 1157 — SNMP
RFC 3417 — Transport Mappings
RFC 1212 — Concise MIB definitions
RFC 3418 — Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)
RFC 1867 — HTML/2.0 forms with file upload extensions
Configurable Management VLAN
RFC 1901 — Community-based SNMP v2
SSL 3.0 and TLS 1.2
–
RFC 2246 — The TLS protocol, version 1.0
– RFC 2346 — AES cipher suites for Transport layer security
– RFC 2818 — HTTP over TLS
SSH 2.0
RFC 1908 — Coexistence between SNMP v1 and SNMP v2
RFC 2068 — HTTP/1.1 protocol as updated by draft-ietf-http-v11-spec-rev-03
RFC 2271 — SNMP framework MIB
RFC 2295 — Transparent content negotiation
–
RFC 4253 — SSH transport layer protocol
–
RFC 4252 — SSH authentication protocol
–
RFC 4254 — SSH connection protocol
–
RFC 4251 — SSH protocol architecture
– RFC 4716 — SECSH public key file format
– RFC 4419 — Diffie-Hellman group exchange
for the SSH
transport layer protocol
RFC 2296 — Remote variant selection; RSVA/1.0 state management cookies — draft-ietf-http-state-mgmt-05
RFC 2576 — Coexistence between SNMP v1, v2, and v3
RFC 2578 — SMI v2
RFC 2579 — Textual conventions for SMI v2
RFC 2580 — Conformance statements for SMI v2
RFC 3410 — Introduction and Applicability Statements for Internet Standard Management Framework
RFC 3411 — An Architecture for Describing SNMP Management Frameworks
HTML 4.0 specification, December 1997
RFC 3412 — Message Processing & Dispatching
Java Script™ 1.3
RFC 3413 — SNMP Applications
Intelligent Edge Managed Switches
Data Sheet |
M4300 series
PAGE 46 of 60