下载文档原格式
Net-Net® 9000 EMSConfiguration GuideRelease Version 6.0 Acme Packet, Inc.71 Third AvenueBurlington, MA 01803 USAt 781-328-4400f 781-425-5077Last Updated: July 16, 2008Document Number: 400-0084-60 Rev. 1.0.0Notices©2002—2008 Acme Packet, Inc., Burlington, Massachusetts. All rights reserved. Acme Packet®, Session Aware Networking®, Net-Net®, and related marks are registered trademarks of Acme Packet, Inc. All other brand names are trademarks, registered trademarks, or service marks of their respective companies or organizations. Patents Pending, Acme Packet, Inc.The Acme Packet Documentation Set and the Net-Net systems described therein are the property of Acme Packet, Inc. This documentation is provided for informational use only, and the information contained within the documentation is subject to change without notice.Acme Packet, Inc. shall not be liable for any loss of profits, loss of use, loss of data, interruption of business, nor for indirect, special, incidental, consequential, or exemplary damages of any kind, arising in any way in connection with the Acme Packet software or hardware, third party software or hardware, or the documentation. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above exclusions may not apply. These limitations are independent from all other provisions and shall apply notwithstanding the failure of any remedy provided herein.Copying or reproducing the information contained within this documentation without the express written permission of Acme Packet, Inc., 71 Third Avenue, Burlington, MA 01803, USA is prohibited. No part may be reproduced or retransmitted.Acme Packet Net-Net products are protected by one or more of the following patents: United States: 7072303, 7028092, 7002973, 7133923, 7031311, 7142532, 7151781. France: 1342348, 1289225, 1280297, 1341345, 1347621. Germany: 1342348, 1289225, 1280297, 1341345, 1347621. United Kingdom: 1342348, 1289225, 1280297, 1341345, 1347621. Other patents are pending.ContentsAbout this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Configuring Different Versions of Net-Net SBCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Configuration Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Who is Acme Packet?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Associated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Customer Questions, Comments, or Suggestions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Contact Us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 3Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 Using the Net-Net EMS to Configure the Net-Net SBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Configuration Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Filtering Configuration Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Installation and Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Hardware Installation Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Connecting to Your Net-Net SBC System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Local Connections and Time-outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Telnet Remote Connections and Time-outs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Connecting Using Telnet through Net-Net EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26SSH Remote Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27SSH Through Net-Net EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 System Boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Net-Net SBC Boot Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 Displaying Boot Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Changing Boot Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Using the ACLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Interrupting Boot in Progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Virtual IP Address for Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Setting Up System Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Version 6.0 Net-Net 9200 EMS Configuration Guide 3NTP Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Configuring the Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 About Your Net-Net SBC Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 Obtaining a New Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Using FTP to Copy an Image on Your Net-Net SBC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 System Image Filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Booting an Image on Your Net-Net SBC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Booting from Flash Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Booting from an External Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Software Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Unlicensed Net-Net SBCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Obtaining a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Trial Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Adding Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Deleting Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Expiration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Viewing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 RADIUS Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46PAP Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 PAP Client Request Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47PAP RADIUS Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 CHAP Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 CHAP Client Request Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48CHAP RADIUS Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 MS-CHAP-v2 Handshake. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 MS-CHAP-v2 Client Request Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49MS-CHAP-v2 RADIUS Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Management Protocol Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Configuring RADIUS Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 RADIUS Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .514System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49General System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Configuring General System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 System Description and Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Physical Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Types of Physical Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 4 Net-Net 9200 EMS Configuration Guide Version 6.0Slot and Card Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Before You Configure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Configuring Physical Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Configuring Physical Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Configuring the Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Network Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54VLAN Network Layer Segmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Overlapping Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55HIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Configuring Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Special Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Configuring the Network Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Configuring a HIP Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Enabling Management Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Basic SNMP Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58SNMP Community. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Trap Receivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 SNMP Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 SNMP Community Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Alarm Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Configuring Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 HDR Trap for Data Push Success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Configuring HDR Data Push Success Trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Persistent Protocol Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 About Persistent Protocol Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66About the Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Process Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Communication Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Protocol Trace Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Configuring Persistent Protocol Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Syslog and Process Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Overview of Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69Version 6.0 Net-Net 9200 EMS Configuration Guide 5Process Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69Syslog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Global Log Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Configuring a Process Log Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Task-Specific Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Facility Logging for Specific Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72General Management Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 Host Routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Configuring Host Routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Accounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 SIP Session Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Accounting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Accounting Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 Packet Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Packet Trace Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Packet Trace for One Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Packet Trace for Both Call Legs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Packet Trace for a Net-Net SBC Signaling Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Configuring Packet Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84System ACLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 Configuring System ACLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 Adding an ACL for the Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .865Realms and Nested Realms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 About Realms and Network Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78About the SIP Home Realm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78About Realms and Other Net-Net SBC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 Before You Configure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Configuration Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Configuring Realms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Creating the Realm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Configuring the Realm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 6 Net-Net 9200 EMS Configuration Guide Version 6.0Nested Realms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Configuring Nested Realms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Configuring Nested Realms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 Choosing the Parent Realm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Realm-Based Packet Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 About TOS/DiffServ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 ToS Byte. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88DiffServ Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Packet Marking for Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88Configuring Packet Marking by Media Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Creating the QoS Marking Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89Applying the QoS Marking Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Configuring Packet Marking for Signaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Creating a Class Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91Applying a Class Policy to a Realm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 Steering Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Configuring Steering Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Multiple Interface Realms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95Steering Pool Port Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Configuring Multiple Interface Realms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Media over TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 TCP Bearer Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99TCP Port Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 SDP Offer Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Timers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Configuring Media Over TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Media Management Behind the Same IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Additional Media Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104Configuring Media Management Behind the Same IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 6SIP Signaling Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105About the Net-Net SBC and SIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 Types of SIP Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Basic Service Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 About B2BUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106SIP B2BUA Peering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106B2BUA Hosted IP Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Version 6.0 Net-Net 9200 EMS Configuration Guide 7SIP B2BUA and L3/L5 NAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 About SIP Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 SIP Network Models and Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Network Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Network Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Default Network Model and Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Upgrade Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Configuring the Network Type and Network Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Configuring the Network Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Configuring the Network Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Configuring the Net-Net SBC for SIP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Using the Net-Net EMS to Configure the Net-Net SBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Configuration Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Configuring the Home Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 SIP NAT Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Home Realm’s Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Configuring the Home Realm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Configuring a SIP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114About SIP Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 Preferred SIP Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 Proxy Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114Redirect Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115Trust Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 About the Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 Configuring a SIP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116 Configuring SIP Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122Configuring Carriers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Configuring SIP Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Configuring SIP Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 Configuring SIP Options Tag Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Configuring SIP Options Tag Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 ENUM: Large UDP Datagram Support for DNS NAPTR Responses . . . . . . . . . . . . . . . . . .129 How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Configuring Large UDP Datagram Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 Configuring SIP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1308 Net-Net 9200 EMS Configuration Guide Version 6.0。
NM2‐xXx‐2230‐xx‐201Install Guide∙M.2 Gigabit Ethernet Fiber Network Interface Card (NIC)∙Provides a fiber optic interface for the Dell OptiPlex™ 7060, 5060, and 3060 Micro PCs∙PCI Express M.2 compliant∙A + E keyed M.2 interfaceContentsProduct Description (2)Ordering Information (2)Optional Accessories (sold separately) (2)Supported Fiber Connections (2)Driver Support (2)Features (3)Specifications (3)Regulatory Compliance (4)Declaration of Conformity (4)Package Contents (5)Reference Views (5)Product Views (5)OptiPlex Views (6)OptiPlex 7060 Micro Ports & Slots (7)Install the NM2‐xXx‐2230‐xx‐201 in the Dell OptiPlex (8)Installation Overview (8)Removing the Side Cover (9)Replacing the Side Cover (9)System Board / Layout (7060 Micro) (10)Installing the NM2‐xXx‐2230‐xx‐201 in the OptiPlex (11)Installed Views (12)Status LED (14)Troubleshooting (14)For More Information (14)Record Device and System Information (15)Contact Us (15)Record of Revisions (16)Product DescriptionTransition Networks NM2‐xXx‐2230‐xx‐201 M.2 Gigabit Ethernet or Fast Ethernet Fiber Network Interface Cards (NICs) provide a fiber optic interface for the Dell OptiPlex™ 7060, 5060, and 3060 Micro PCs. The NM2‐xXx‐2230‐xx‐201 consists of an M.2 NIC that installs into the OptiPlex PC’s M.2 “E key” interface, a fiber optic adapter that installs into the OptiPlex Micro PC’s Option port, and a 20‐pin Flat Flex Cable (FFC) that connects the NIC to the fiber adapter. The NICs are electro‐mechanically designed to be compatible (fit, form, function) with the Dell OptiPlex 7060 Thin Client PC through the use of its M.2 (E Key) slot.M.2 is known as the “next generation form factor” and is a specification for internally mounted computer expansion cards and associated connectors. Desktop PCs are being replaced by smaller computing devices (such as Thin Clients, Micro PCs, Ultrabooks, and Tablets) which typically have internal M.2 interfaces but do not have PCI or PCIe slots. Many users still need fiber Ethernet access, and without the external PCIe slot, there is no standard fiber interface on these devices.See the Dell OptiPlex manual for important notes, cautions, and warnings. Read the section “Before working inside your computer” before proceeding.Ordering InformationSKU DescriptionNM2‐GXE‐2230‐LC‐201 M.2 Gigabit Ethernet Fiber NIC (1000BASE‐SX, 850nm, MM, LC) (fixed optic). 1000Base‐SX 850nm multimode (LC) [62.5/125 μm fiber: 220 m/722 ft.] [50/125 μm fiber: 550 m/1804 ft.] Link Budget: 8.0 dBNM2‐GXE‐2230‐SFP‐201 M.2 Gigabit Ethernet Fiber NIC (1000Base‐X Open SFP Slot)NM2‐FXS‐2230‐SFP‐201 M.2 Fast Ethernet Fiber NIC. M.2 NIC, 100Base‐FX. M.2 NIC; 100Base‐FX to SGMII SFP media converter (included)Optional Accessories (sold separately)SFP Modules: Transition Networks offers a full line of small form factor pluggable (SFP) transceivers. See Transition Networks Optical Devices webpage for relevant SFP modules. See the related SFP manual for cautions and warnings.Supported Fiber Connections∙1000BASE‐SX, 850nm, MM, LC (fixed optic)∙1000BASE‐X, SFP Slot∙100BASE‐SGMII, SFP SlotDriver SupportWindows 10, 8.1, 8, and 7 (32 and 64 bit); LinuxFeatures∙IEEE 802.3‐2012 compliant∙PCI Express M.2 compliant (3.3V) ∙Full Duplex∙IPv6 Capable ∙A + E keyed M.2 interface∙Supports UEFI∙Jumbo frame support 9014 bytes ∙PXE Boot supportSpecifications•Standards: IEEE 802.3‐2012•Bus Slot: M.2 ‐ ‘2230‐D4‐A‐E’•Data Rate: 1000 Mbps (full duplex only)•Max Frame Size: 9014 bytes•Status LEDs: LINK/ACT ON = Link, Flashing = Activity•Dimensions (M.2 NIC) 2230‐D4‐A‐Eo Width: 0.87” [22 mm]o Depth: 1.18” [30 mm]o Height: 0.12” [3.08 mm]•Dimensions (Fiber Interface) Width: 1.65” [42 mm]o Depth: 2.05” [52 mm]o Height: 0.51” [13 mm]•Dimensions (FFC Cable) Length: 2.99” [76 mm]•Power Consumption (LC): 250mA @ 3.3V (0.8 Watts typical)•Power Consumption (SFP): 120mA @ 3.3V (0.4 Watts typical without SFP module) •Power Source M.2 interface connector: 3.3V (Refer to table 41 of M.2 Specification) •Environment:o Operating Temp: 0°C to +45°Co Storage Temp: ‐40°C to 85°Co Humidity: 5% to 95% (non‐condensing)o Altitude: 0 – 10,000 ft.•Weight: 0.1 lbs. [0.05 kg]•Warranty: LifetimeRegulatory ComplianceNote: Modification of NIC voids regulatory agency compliance.Compliance: CE Mark; Emissions: EN55032, FCC Part 15 Class A; Immunity: EN55024Emissions: EN 55032: 2012/AC: 2013; AS/NZS CISPR 32: 2013; VCCI V‐3/2015.04; ICES‐003, Issue 6: 2016; FCC Part 15 Subpart B.Immunity: EN 55024: 2010 (EN 61000‐4‐2: 2009; EN 61000‐4‐3: 2006 + A1: 2008 + A2: 2010; EN 61000‐4‐4: 2004 + AC: 2006 + A1: 2010; EN 61000‐4‐5: 2006; EN 61000‐4‐6: 2009; EN 61000‐4‐8: 2010; EN 61000‐4‐11: 2004).Declaration of ConformityHigh Risk Activities Disclaime r: Components, units, or third‐party products used in the product described herein are NOT fault‐tolerant and are NOT designed, manufactured, or intended for use as on‐line control equipment in the following hazardous environments requiring fail‐safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Support, or Weapons Systems ("High Risk Activities"). Transition Networks and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.Package ContentsVerify that you have received the following items. Contact your sales representative if any item is missing. Please save the packaging for possible future use.One TN‐SFP‐GE‐100FX SFP in anti‐static pouch (included with NM2‐FXS‐2230‐SFP‐01 version only).One M.2 NIC PCB attached to FFC Cable in anti‐static pouch.Parts in a 4x6 baggie (1 each): #4 Flat Head Screw, #4 Nylon Washer, #6 Black SEMS Screw.One NM2‐xXx‐2230‐xx‐01 Install Guide (this document).One Product Support Postcard.Reference ViewsProduct ViewsOptiPlex ViewsOptiPlex 7060 Micro Ports & SlotsDell OptiPlex 7060 Micro Front View: 1. Power button and power light. 2. Hard drive activity light.3. Headset/Universal audio jack port.4. Line‐out port.5. USB 3.1 Gen 2 Type‐C port with PowerShare.6. USB 3.1 Gen 1 port with PowerShare.Dell OptiPlex 7060 Micro Back View: 1. External antenna connectors (2) (optional). 2. DisplayPort/VGA/HDMI 2.0b/DP/USB Type‐C alt mode (optional). 3. USB 3.1 Gen 1ports (3). 4. Cable holder. 5. Padlock ring. 6. Network port. 7. USB 3.1 Gen 1 port (supports Smart Power On). 8. Service tag. 9. Kensington security cable slot. 10. DisplayPorts (2). 11. Power connector port.Dell Support for OptiPlex 7060: Diagnostics, Support topics & articles, Drivers & downloads, Manuals & documents, System configuration, and Parts & accessories.Install the NM2‐xXx‐2230‐xx‐201 in the Dell OptiPlexThe NM2‐xXx‐2230‐xx‐201 is designed to install in the Dell OptiPlex™ 7060, 5060, and 3060 Micro PCs.Caution: Only qualified persons should install the NIC. Failure to observe this caution could result in poor performance or damage to the equipment. Before installing the NIC, review the Pre‐Installation Checklist and Safety Precautions below.Caution: Wear a grounding device and observe electrostatic discharge precautions when installing the NIC in a system. Failure to observe this caution could result in damage to the NIC. Before installing the NIC, review the Pre‐Installation Checklist and Safety Precautions below. Before installing the NIC, ensure that system power is OFF, the power cord is unplugged from the power outlet, and that proper electrical grounding procedure has been followed.Warning: High voltage inside the system may present a safety hazard. Make sure that the system power is off before removing the cover. Unplug and disconnect the PC and then wait for 15‐20 seconds before plugging the NIC into the PC. When removing the NIC, unplug the Ethernet cable before removing the PC cover.Note: Refer to the Notes, Cautions, and Warnings in the Dell OptiPlex 7060 Service Manual. See Manuals & documents for details.Class I Laser Compliance: This product has been tested and found to comply with the limits for FDA Class I laser for IEC60825, EN60825, and 21CFR1040 specifications. Warning: Visible and invisible laser radiation when open. DO NOT stare into laser beam or view directly with optical instruments. Failure to observe this warning could result in damage to your eyes or blindness.Installation OverviewBefore installing your NIC, review the preceding sections, and then do the following:1.Verify that your system is using the latest BIOS.2.If you download the driver software, record the path where you saved the downloads.3.If your system is active, shut it down. Do not install the NIC until system power is completely removed.When system shutdown is complete, power OFF and unplug your system.4.Holding the NIC by the edges, remove it from its shipping package and place it on an antistatic surface.5.Check the NIC for signs of damage, particularly on the PCB edge connector. Caution: Never attempt to installa damaged NIC card. If the NIC is damaged, report it to Transition Networks.6.Remove the OptiPlex Side Cover. See Removing the Side Cover below.7.Gently remove the OptiPlex HDD.8.Remove the OptiPlex 15‐Pin DSUB Knockout.9.Insert the M.2 NIC into the OptiPlex Micro PC’s M.2 “E key” interface.10.Insert the fiber optic adapter into the OptiPlex Micro PC’s Option port.11.Replace the OptiPlex HDD.12.Replace the OptiPlex Side Cover.Removing the Side Cover1. Follow the procedure in “Before working inside your computer”.2. To remove the cover:a) Slide the release latch on the back side of the system until it gives a click sound to unlock the side cover [1].b) Slide and lift the side cover from the system [2].Replacing the Side Cover1. Place the cover on the system and slide the cover until it clicks into place [1].2. The release latch automatically locks the side cover to the system [2].System Board / Layout (7060 Micro)Installing the NM2‐xXx‐2230‐xx‐201 in the OptiPlexThe NM2‐xXx‐2230‐xx‐201 consists of a M.2 NIC that installs into the OptiPlex Micro PC’s M.2 “E key” interface, and a fiber optic adapter that installs into the OptiPlex Micro PC’s Option port.1.Remove PC cover.2.Gently remove the HDD Assembly. See the Dell documentation.3.Remove the 15‐Pin DSUB knockout.4.Insert the M.2 NIC into the OptiPlex Micro PC’s M.2 “E key” interface.5.Secure the M.2 NIC Assembly into place using the Securing Screw.6.Insert the fiber optic adapter into the OptiPlex Micro PC’s Option port.7.Attach to PC Case using Black SEMS Screw #6‐32x1/4”, and partially tighten to hold in place as shown below.8.Align #4 Standoff with Top Hole in PC Case.9.Slip #4 Nylon Washer on top of #4 Standoff and insert #4 Screw to secure.10.Tighten using Black SEMS Screw #6‐32x1/4”.11.Lift Locking Lever of FFC Connector on fiber optic adapter.12.Insert end of 20‐Position FFC Cable into fiber optic adapter, with Pins facing down.13.Push Locking Lever Down to Lock. Check that Cable is secure. See figure below for final placement.14.Gently replace the HDD Assembly.15.Replace PC cover.16.Install the SFP in the open SFP slot. On the fixed optic version, connect the fiber adapter/connector.17.Power up the PC.Installed ViewsPXE Boot Loader from PXE boot loader image pre‐loaded: https:///download/19186/Intel‐Ethernet‐Connections‐Boot‐Utility‐Preboot‐Images‐and‐EFI‐Drivers.Intel i210 PROSet Drivers from If your PC does not automatically detect the NM2‐xXx‐2230‐xx‐201 NIC, download and install the standard i210 PROSet drivers from Intel at /content/www/us/en/support/network‐and‐i‐o/ethernet‐products/000005686.html.The Intel® PROSet for Windows* Device Manager is an extension for Windows Device Manager. When you install the Intel PROSet software, tabs are automatically added to the supported Intel adapters in Windows Device Manager.These features allow you to test and configure wired Intel® Ethernet Adapters.The links below apply to the NM2‐GXE‐2230‐xx‐201, the NM2‐FXS‐2230‐SFP‐201, and –D versions. At each link, there is a 32‐bit and a 64‐bit download for each OS.Intel® Network Adapter Driver for Windows* 7.Intel® Network Adapter Driver for Windows* 8.1.Intel® Network Adapter Driver for Windows® 10.The full set of Intel Network Adapter Drivers for download (e.g., for Linux, Windows Server, etc.) is available. Transition Networks Resources page has Drivers (ZIP format) for Windows 10 32bit and 64bit Drivers, Windows 7 32bit and 64bit Drivers, and Windows 8 32bit and 64bit Drivers.Status LEDThe Media Converter has a status LED for checking Link/Activity:Link/ACTivity LED On = Link; Flashing = Activity. Color is amber when 100M.TroubleshootingThis section lists some common problems, their causes, and potential recovery steps.1. Confirm the Pre‐Installation Checklist items on page 8.2. Verify the Hardware Installation Procedure on page 9.3. Check that the cabling is securely attached. See the FOA troubleshooting guide or the SFP manual.4. Check for a mismatch of speed, duplex, protocol, or cable type.5. Make sure the SFP is plugged in to the open SFP slot before you power on the PC. Failure to do so will cause the device to fail, in which case you must shut down and restart the PC.6. Use the troubleshooting procedures in the Dell™ OptiPlex™ User’s Guide.7. Use the troubleshooting procedures on the PXE Boot Loader webpag e as required.8. Use the troubleshooting procedures on the Intel i210 PROSet Drivers webpage as required.9. Verify that the link partner is active and can send/receive traffic; make sure partner settings match; verify that the port is enabled; try connecting to another port or link partner. Check for incompatible or conflicting devices / settings.10. Run Windows Device Manager and scan for changes.11. Check if the PC’s BIOS version is appropriate and update to the latest. See the PC documentation.12. Run the PC diagnostics (e.g., Dell Quick Test or Dell pre‐boot diagnostics).13. Automatically detect and update drivers and software if you are connected to the Internet from the computer that needs updated drivers from /support/network/sb/CS‐031482.htm.14. Record information and contact TN Technical Support. See Recording Model and System Information below.For More InformationTo view the Dell™ OptiPlex™ User’s Guide at the Support Center web page:1.Click Start → Help and Support → Dell User and System Guides → System Guides.2.Click the User’s Guide for your computer.The User’s Guide is also available on the optional Drivers and Utilities media.Technical information in this document is subject to change without notice.See our SFP Products for more SFP information.The Fiber Optic Association, Inc. provides a Technical Bulletin on “Guidelines For Testing And Troubleshooting Fiber Optic Installations” at /tech/guides/TT3.pdf Other FOA Technical Bulletins to be used as references for the design and planning of the network can be downloaded from the FOA Tech Topics website.Record Device and System InformationAfter performing the troubleshooting steps, and before calling or emailing Technical Support, please record as much information as possible in order to help the TN Tech Support Specialist. Record the following information: 1. Product ID: ___________________________ MAC Address: ________________________________________ Serial #: _______________________________ Board Rev: ___________________________________________ LED status: __________________________________________________________________________________ 2. Record the System information: Check your computer documentation for support information.PC make and model: ________________________________________________________________________ Operating System: __________________________________________________________________________ BIOS version: ______________________________________________________________________________ Intel i210 Driver version: _____________________________________________________________________ PC’s Icon Tray indication: _____________________________________________________________________ Connected Device(s): ________________________________________________________________________3. Provide your TN service contract number: _______________________________________________________4. Describe the failure: _________________________________________________________________________ ___________________________________________________________________________________________ ___________________________________________________________________________________________5. Describe any action(s) already taken to resolve the problem: ________________________________________ ___________________________________________________________________________________________ ___________________________________________________________________________________________Contact UsTechnical Support: Technical support is available 24‐hours a dayUS and Canada: 1‐800‐260‐1312International: 00‐1‐952‐941‐7600Main Officetel: +1.952.941.7600 | toll free: 1.800.526.9267 | fax: 952.941.2322******************** | ************************** | ******************************AddressTransition Networks10900 Red Circle DriveMinnetonka, MN 55343, U.S.A.Web: https://Record of RevisionsRev Date NotesA 7/24/18 Initial release for production.B 11/14/18 Incorporate technical and editorial changes.Trademark notice: All trademarks and registered trademarks are the property of their respective owners. Copyright restrictions: © 2018 Transition Networks. All rights reserved. No part of this work may be reproduced or used in any form or by any means ‐ graphic, electronic or mechanical ‐ without written permission from Transition Networks.。
Network Working Group L. Dondeti, Ed. Request for Comments: 4909 QUALCOMM, Inc. Category: Informational D. Castleford France Telecom F. Hartung Ericsson Research June 2007 Multimedia Internet KEYing (MIKEY) General Extension Payloadfor Open Mobile Alliance BCAST LTKM/STKM TransportStatus of This MemoThis memo provides information for the Internet community. It doesnot specify an Internet standard of any kind. Distribution of thismemo is unlimited.Copyright NoticeCopyright (C) The IETF Trust (2007).AbstractThis document specifies a new Multimedia Internet KEYing (MIKEY)General Extension payload (RFC 3830) to transport the short-term key message (STKM) and long-term key message (LTKM) payloads defined inthe Open Mobile Alliance’s (OMA) Browser and Content (BAC) Broadcast (BCAST) group’s Service and Content protection specification.Table of Contents1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 22. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 23. MIKEY General Extension for OMA BCAST Usage . . . . . . . . . . 34. Interoperability Considerations . . . . . . . . . . . . . . . . 35. Security Considerations . . . . . . . . . . . . . . . . . . . . 46. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 47. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 48. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 8.2. Informative References . . . . . . . . . . . . . . . . . . 5 Dondeti, et al. Informational [Page 1]1. IntroductionThe Multimedia Internet Keying (MIKEY) protocol specification [1]defines a General Extension payload to allow possible extensions toMIKEY without having to allocate a new payload type. The GeneralExtension payload can be used in any MIKEY message and is part of the authenticated/signed data part. There is an 8-bit type field in that payload. The type code assignment is IANA-managed, and RFC 3830requires IETF consensus for assignments from the public range of0-240.The Open Mobile Alliance’s (OMA) Browser and Content (BAC) Broadcast (BCAST) group’s Service and Content Protection specification [2]specifies the use of a short-term key message (STKM) and a long-term key message (LTKM) that carry attributes related to Service andContent protection. Note that any keys associated with theattributes are part of the MIKEY KEMAC payload. This documentspecifies the use of the General Extension payload of MIKEY to carry the LTKMs or STKMs.RFC 3830 [1], the MIKEY General Extension payload defined in [3], and the 3rd Generation Partnership Project (3GPP)’s Multimedia Broadcast/ Multicast Service (MBMS) document [4] specify the transport of MIKEY messages via unicast or broadcast and the OMA specifications useeither for transport of MIKEY messages.2. TerminologyThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [5].OMA BCAST STKM/LTKM MIKEY General Extension: We refer to the General Extension type -- 5 -- as the OMA BCAST STKM/LTKM MIKEY GeneralExtension .Dondeti, et al. Informational [Page 2]3. MIKEY General Extension for OMA BCAST Usage1 2 30 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ! Next ! Type ! Length !+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ! OMA BCAST S/LTKM Subtype (variable length) ˜+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: OMA BCAST MIKEY General ExtensionSection 6.1 of RFC 3830 specifies the first three fields of theGeneral Extension Payload and defines a variable length Data field.This document specifies the use of Type 5 for OMA BCAST Service andContent Protection using the Smartcard Profile. The contents of the variable length data field are defined below.Subtype: 8 bits. This field indicates the type of the OMA BCASTpayload. In this specification, only two values are specified:LTKM (1), and STKM (2).Subtype Specific Data: Variable length. The contents of this field are defined in Section 6 of the OMA BCAST Service and ContentProtection specification [2].1 2 30 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+! Subtype ! Subtype specific data (variable length) ˜+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Figure 2: STKM/LTKM Subtype Payload4. Interoperability ConsiderationsThis document specifies the use of MIKEY General Extension PayloadType 5 and a couple of subtype values (1 and 2), one each for OMABCAST Service and Content protection’s STKM and LTKM payloads.Interoperability considerations span several standards bodies, withOMA BCAST 1.0 enabler compliance being the key aspect; as such, it is up to the OMA test planning to verify the interoperability andcompliance of OMA BCAST 1.0 implementations. This payload typeassignment does not change MIKEY beyond RFC 3830 [1] and RFC 4563[3].Dondeti, et al. Informational [Page 3]5. Security ConsiderationsAccording to RFC 3830, the general extension payload can be used inany MIKEY message and is part of the authenticated/signed data part. The parameters proposed to be included in the OMA BCAST MIKEY General Extension payload (listed in Section 3) need only to be integrityprotected, which is already allowed by the MIKEY specification. The OMA BCAST MIKEY General Extension Payload SHALL be integrityprotected. Furthermore, keys or any parameters that requireconfidentiality MUST NOT be included in the General ExtensionPayload. If keys or other confidential data are to be transportedvia the General Extension Payload, such data MUST be encrypted andencapsulated independently. Finally, note that MIKEY alreadyprovides replay protection and that protection covers the GeneralExtension Payload also.6. IANA ConsiderationsIANA has allocated a new General Extension Type from the "GeneralExtensions payload name spaces" in the IANA registry at/assignments/mikey-payloads for use by OMA BCAST. Furthermore, IANA maintains a list of corresponding subtypes (0-255) as follows:0 ... Reserved1 ... LTKM2 ... STKM3 ... 191 (maintained by IANA and assigned by IETF Review [6])192 ... 255 (Private use)7. AcknowledgmentsMany thanks to Jari Arkko, Piron Laurent, and Steffen Fries for their reviews and suggestions for improvement.Dondeti, et al. Informational [Page 4]8. References8.1. Normative References[1] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K.Norrman, "MIKEY: Multimedia Internet KEYing", RFC 3830,August 2004.[2] Open Mobile Alliance, "Service and Content Protection for Mobile Broadcast Services", OMA TS-BCAST_SvcCntProtection-V1_0-20070529-C, 2007, </release_program/bcast_v1_0.html>.[3] Carrara, E., Lehtovirta, V., and K. Norrman, "The Key IDInformation Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)", RFC 4563, June 2006.[4] 3GPP, "3G Security; Security of Multimedia Broadcast/MulticastService (MBMS)", 3GPP TS 33.246 6.6.0, March 2006.[5] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.8.2. Informative References[6] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANAConsiderations Section in RFCs", Work in Progress, March 2007. Dondeti, et al. Informational [Page 5]Authors’ AddressesLakshminath Dondeti (editor)QUALCOMM, Inc.5775 Morehouse DrSan Diego, CAUSAPhone: +1 858-845-1267EMail: ldondeti@David CastlefordFrance Telecom4, rue du Clos Courtel35512 Cesson Sevigne Cedex,FrancePhone: + 33 (0)2 99 12 49 27EMail: david.castleford@Frank HartungEricsson ResearchEricsson Allee 152134 Herzogenrath,GermanyPhone: +49 2407 575389EMail: frank.hartung@Dondeti, et al. Informational [Page 6]Full Copyright StatementCopyright (C) The IETF Trust (2007).This document is subject to the rights, licenses and restrictionscontained in BCP 78, and except as set forth therein, the authorsretain all their rights.This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual PropertyThe IETF takes no position regarding the validity or scope of anyIntellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described inthis document or the extent to which any license under such rightsmight or might not be available; nor does it represent that it hasmade any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can befound in BCP 78 and BCP 79.Copies of IPR disclosures made to the IETF Secretariat and anyassurances of licenses to be made available, or the result of anattempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of thisspecification can be obtained from the IETF on-line IPR repository at /ipr.The IETF invites any interested party to bring to its attention anycopyrights, patents or patent applications, or other proprietaryrights that may cover technology that may be required to implementthis standard. Please address the information to the IETF atietf-ipr@.AcknowledgementFunding for the RFC Editor function is currently provided by theInternet Society.Dondeti, et al. Informational [Page 7]。
