`Case 2:17-cv-00513-JRG Document 257-5 Filed 01/04/19 Page 1 of 5 PageID #: 16242
`
`
`
`
`
`EXHIBIT 5
`
`
`
`
`
`EXHIBIT 5
`
`
`
`
`
`
`
`
`Case 2:17-cv-00513-JRG Document 257-5 Filed 01/04/19 Page 2 of 5 PageID #: 16243
`Case 2:17-cv-00513-JRG Document 257-5 Filed 01/04/19 Page 2 of 5 PageID #: 16243
`
`Tl
`
`"'”1'|l
`
`SIEGEL000939
`
`
`
`Case 2:17-cv-00513-JRG Document 257-5 Filed 01/04/19 Page 3 of 5 PageID #: 16244
`Case 2:17-cv-00513-JRG Document 257-5 Filed 01/04/19 Page 3 of 5 PageID #: 16244
`
`D27080
`
`23 September 1998
`
`host’s queue waiting for the first unicast message to be delivered to its
`destination.
`
`3. Prior to sending a unicast message to the attached router, the local host
`sets up a TC P connection with the destination host. To set up the TC P
`connection, the following happens:
`
`a. The local host sends a TC P SYN message to the attached router. The
`router routes the TCP SYN message to the exit gateway IP address.
`
`b. At this point, the setup of the EPLRS point-to-point circuit is the same
`as described above, except that a SINCGARS stub net gateway router will
`proxy-ARP for the destination host based on its client list. Multiple
`gateway routers could not respond to the ARP, but the hardware address in
`the first response will be used.
`
`c. The destination exit gateway router will read the source IP address of
`the 1P header on the TCP SYN mes sage and add a return route to the
`source IP address into the routing table. The gateway router sends a RFC
`1256 advertisement onto the local SINCGARS net advertising the
`indicated source IP address.
`
`d. The destination gateway router then routes the TCP SYN message via
`the stub net to the router attached to the destination host.
`
`0. The destination router should install a route for the originator’s source
`IP address via the gateway router that has sent the RFC 1256
`advertisement referenced in paragraph c.
`
`1“. At this point, the originating and destination hosts have a TCP
`connection setup and start transmitting the message data.
`
`4. The termination of the TCP connection and EPLRS point-to—point circuit
`is the same deseribcd in Section 3.5,] 2.], paragraph A6.
`
`
`
`3-39
`
`SIEGEL001003
`
`
`
`Case 2:17-cv-00513-JRG Document 257-5 Filed 01/04/19 Page 4 of 5 PageID #: 16245
`Case 2:17-cv-00513—JRG Document 257-5 Filed 01/04/19 Page 4 of 5 PageID #: 16245
`
`23 September 1998
`
`
`D27080
`
`
`
`
`
`3-40
`
`SIEGEL001004
`
`
`
`Case 2:17-cv-00513-JRG Document 257-5 Filed 01/04/19 Page 5 of 5 PageID #: 16246
`Case 2:17-cv-00513-JRG Document 257-5 Filed 01/04/19 Page 5 of 5 PageID #: 16246
`
`D27080
`
`23 September 1998
`
`
`
`3.6
`
`NETWORK MANAGEMENT
`
`Network management consists of planning, changing monitoring, and corrective
`
`action.
`
`3.6.1
`
`Initial Planning
`
`TBS
`
`3.6.2 Configuration Changes
`
`TBS
`
`3.6.3 Network Monitoring
`
`3.6.3.1 EPLRS Network Monitoring
`
`TBS
`
`3.6.3.2 SINCGARS Network Monitoring
`
`TBS
`
`3.6.3.3 FBCBZ Network Monitoring
`
`FBCBZ will use a bottom-up, hierarchical approach to network monitoring.
`
`Every FBCBZ platform monitors its local router and radios via SNMP queries and
`traps for status i’ malfiinctions and provides this information to the host in the form of
`COMM Status. Additionally, SA client a“ sewer status and SA statistics are available to
`infer the health of the SA network. The host has the responsibility to monitor. fault
`isolate and repair (or call for repair of) the equipment associated with the platform.
`
`3-4]
`
`SIEGEL001005
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
