s not arrive in the input. A missing or lost packet can cause reassembling failure. ipInDiscards: This shows the number of packets discarded. Packets can be discarded due to internal problems in the system. ipOutDiscards: This variable gives a count of the output packets discarded. ipFragCreates: This variable keeps a count of the output packets with the fragmentation flag set. ipFragFails/ipFragOKs: Fragmentation can be either a success or it can fail. The count of fails in fragmentation is handled in ipFrag- Fails variable and the count of fragmentation success is maintained in ipFragOKs. There are few more read-only variables like ipInUnknownProtos, pInDelivers, ipOutRequests, and ipOutNoRoutes that have not been discussed in this section. Now let us look into the tables in an IP Group. The tables are: Fundamentals of EMS, NMS and OSS/BSS ipAddrTable: This is the IP address table. It has an index field (ifA- dEntIfIndex) and information like NetMask address that is used for classless interdomain routing. ipNetToMediaTable: This table uses ipNetToMediaIfIndex as the index field. It is used to map the physical address to a network address. A field ipNetToMediaType in this table can take values "static" when the address mapping is configured by an administrator, "dynamic" when it is automatically done using a protocol, or "in-valid." ipRouteTable: This table is used to give routing information including the route type and next hop or jump for a packet routing. The problem with this table is that its field ipRouteDest takes unique values, SO multiple routes to a destination cannot be configured using this table. Since there can be multiple routes to a destination in real-life scenar- ios, this table was depreciated and a new table named ipForwardTab was introduced. ipForwardTable: ipForward (24) was introduced to ensure that multiple routes can be set to a particular destination. This object has ipForward- Number (1) and ipForwardTable (2). The ipForwardNumb is an indi- cation of the number of entries in the ipFor