Model Interfaces: IP

The following sections discuss the topics necessary for interfacing with the IP model.

Packet Formats: IP

The IP model suite uses the following packet formats.

Table 111: IP Packet Formats

Packet Format Description
ip_dgram_v4 Represents an IPv4 datagram. It is used by IPv4 to encapsulate higher layer data. It carries control fields such as destination and source address, a reassembly identifier, and a time-to-live (TTL) counter.
ip_dgram_v6 Represents an IPv6 datagram. It is used by IPv6 to encapsulate higher layer data. It carries control fields such as destination and source address, a reassembly identifier, and a time-to-live (TTL) counter.
arp_v2 Represents an ARP packet. It is used to communicate address mappings between the host and the destination.
ip_igmp Represents an IGMP address packet. It includes fields for the IGMP version and type, a checksum, and a Class-D multicast group address.
ip_pim_sm Represents a PIM-SM message packet. It includes fields for data, message type, version, type, and checksum.

You can refer to the descriptions provided for each packet field to get more details about their importance.

ICI Formats: IP

The IP model suite uses the following interface control information (ICI) formats.

Table 112: IP ICI Formats

ICI Format Description
ip_arp_req_v4 Used with packet transfers from the IP layer to IP ARP layer, the role of this ICI is to specify the connection class and the IP address of the next hop in the packet's route. This information is used by ip_arp_v4 to determine a corresponding physical address. The IP datagram is passed to the DLL with this information.
ip_arp_ind_v4 Used with stream interrupts when an IP module receives a packet from the lower layer (applies to IPv4 or IPv6 packets). Also used with interrupts when an IP module receives a packet through an IP tunnel, removes the outer packet, and redelivers the inner packet back to itself for processing.
ip_encap_ind_v4 Used with packet transfers from IP Encap/Decap layer to the higher layers, this ICI carries the IP address of the source node and the IP address of the interface on which the datagram was received. This information is the only way for the higher level protocol to determine the source of the data, since the IP header is stripped by ip_encap_v4 before passing data upwards.
ip_encap_req_v4 Used with packet transfers from higher layers to the IP Encap/Decap layer, this ICI carries the IP address of the destination node, connection class, and a provision for specifying the IP address of the interface on which the multicast message should be sent.
ip_mac_req Used with packet transfers from IP ARP layer to the DLL, this ICI specifies the physical address of the next node in the packet's route. While each link layer protocol (e.g., FDDI, Ethernet.) can define its own ICI for requests that are supplied, ip3_mac_req attempts to unify these ICIs to simplify the design of the ip_arp_v4 process (i.e., ip_arp_v4 does not need to know what type of link layer it is connected to).
ip_rte_ind_v4 Used with packet transfers from the IP layer to IP Encap/Decap layer, this ICI carries the IP address of the interface on which the datagram arrived.
ip_rte_req_v4 Used with packet transfers from the IP Encap/Decap layer to the IP layer, this ICI carries the IP address of the interface on which the multicast message needs to be sent, if applicable.

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · Documentation compiled and provided by Beijing ZNetLink Technology Co., Ltd.

交流群 · QQ Group:OPNET/智网妙算网络仿真交流群(群号 486383494)

原文档 © 2017 Riverbed Technology · 本站为公益翻译,由 AI 辅助完成,请仔细甄别

Original documentation © 2017 Riverbed Technology. Community translation, AI-assisted. Contact: jiazequn@znetlink.com