The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of RFC 1573's ifIndex.

A unique GUID ID from ncm.Interfaces table.

The media dependent `physical' address.

The IP address corresponding to the media dependent physical address.

A list of IP addresses sorted with octet markers (dots) omitted.

The type of IP address associated with an ARP operation and media dependent address.

Possible Values:

• Other (1)
• Invalid (2)
• Dynamic (3)
• Static (4)

Setting this object to the value invalid (2) has the effect of invalidating the corresponding entry in the ipNetToMediaTable. That is, it effectively disassociates the interface identified with said entry from the mapping identified with said entry. It is an implementation specific matter as to whether the agent removes an Invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipNetToMediaType object.

Result of DNS lookup on IPAddress.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of interfaces for which ARP data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

The value of the instance of the ifIndex object, defined in MIB-II, for the interface corresponding to this port.

The port number of the port for which this entry contains bridge management information.

The enabled/disabled status of the port.

Possible Values:

• Enabled (1)
• Disabled (2)

The port's current state as defined by application of the Spanning Tree Protocol. This state controls what action a port takes on reception of a frame. If the bridge has detected a port that is malfunctioning, it places that port into the broken(6) state. For ports that are disabled (see dot1dStpPortEnable), this object has a value of disabled(1).

The type of VLAN membership assigned to this port. A port with static VLAN membership is assigned to a single VLAN directly. A port with dynamic membership is assigned a single VLAN based on content of packets received on the port and through VQP queries to VMPS. A port with multiple VLAN membership may be assigned to one or more VLANs directly. A static or dynamic port membership is specified by the value of vmVlan. A multiVlan port membership is specified by the value of vmVlans.

Possible Values:

• Static(1)
• Dynamic(2)
• MultiVlan(3)

The VLAN id of the VLAN the port is assigned to when vmVlanType is set to static or dynamic. This object is not instantiated if not applicable.

The value may be 0 if the port is not assigned to a VLAN.

An indication of the current VLAN status of the port. A status of inactive(1) indicates that a dynamic port does not yet have a VLAN assigned, or a port is assigned to a VLAN that is currently not active. A status of active(2) indicates that the currently assigned VLAN is active. A status of shutdown(3) indicates that the port has been disabled as a result of VQP shutdown response.

Possible Values:

• inactive(1)
• active(2)
• shutdown(3)

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of interfaces for which bridge port data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

A unique value for each module within the chassis.

The type of module.

Possible Values:

(notdefined(0), version1(1), version2(2), version3(3),version4(4),version5(5),version6(6),version7(7),version8(8),version9(9),version10(10),vi2(11), vi4(12), vi30(13), s1b(14), sa2(15), as16(16), new8as(17), lsa(18), fxs2(19), fxo2(20), em2(21), fxs4(22), fxo4(23), em4(24), sab(25), e1vi(26), am12(27), am6(28), ndec(29), newsa2(30), aux(31), console(32), sic-wan(33), sic-1fe(34), sic-1sa(35), sic-3as(36), sic-1e1(37), sic-1t1(38), sic-1bu(39), sic-2bu(40), sic-1bs(41), sic-2bs(42), sic-1am(43), sic-2am(44), sic-1em(45), sic-2em(46), sic-1fxs(47), sic-2fxs(48), sic-1fxo(49), sic-2fxo(50), fcm6(51), sa8(52), t11(53), t12(54), t14(55), t1vi(56), fcm4(57), fcm2(58), rtb21ce3(59), ame6(60), ame12(61), wsx5162(62), e11-f(65), e12-f(66), e14-f(67), t11-f(68), t12-f(69), t14-f(70), e11-f-17(71), t11-f-17(72), rtb21ct3(73), atmadsl1(74), atmadsl2(75), atm155m(76), ase8(77), ase16(78), sae4(79), sae2(80), wsx5012a(81), wsx5167(82), wsx5239(83), wsx5168(84), wsx5305(85), wsx5550(87), wsf5541(88), atmshdsl1(90), atmshdsl2(91), atmshdsl4(92), atm25m(93), atme3(94), atmt3(95), xdsl-fec(96), xdsl-adsl(97), xdsl-gshdsl(98), xdsl-bri(99), xdsl-scc(100), ge1(101), pos155m(102), cpos(103), fe1op(104), sae8(105), atm155m-mm(106), atm155m-sm(107), atm155m-sml(108), fe1op-sfx(109), fe1op-mfx(110), cpos-t1(111), ge1-op(112), ge2-op(113), ge2(114),fix-1wan(115), fix-1sae(116), cavium(117), sic-1Eth(118), atm1ADSLI(119), atm2ADSLI(120), fix-e11(121), fix-t11(122), e18-75(123), e18-120(124), t18(125),  sic-1vifxs(126), sic-1vifxo(127), sic-2vifxs(128), sic-2vifxo(129), xdsl-fec-new(130), xdsl-sa(131), bs4(132), ima-8e175(133), ima-8e1120(134).ima-4e175(135),ima-4e1120(136), ima-8t1(137), ima-4t1(138), sic-1t1f(139), sic-1e1f(140). fe4(149), atm1shdsl4wire(151), atmIma4shdsl(152). ls4(153). ls8(154), ls16(155). sic-adls2plus-isdn(156). sic-adls2plus-pots(157), ft3(158), ce32(159), bsv2(160), bsv4(161). rpu(162). erpu(163). ssl(164), nsa(165), wsx6ksup12ge(200), wsx6408gbic(201). wsx6224mmmt(202). wsx6248rj45(203). wsx6248tel(204). wsx6302msm(206), wsf6kmsfc(207), wsx6024flmt(208), wsx6101oc12mmf(209), wsx6101oc12smf(210), wsx6416gemt(211), wsx61822pa(212), osm2oc12AtmMM(213), osm2oc12AtmSI(214), osm4oc12PosMM(216), osm4oc12PosSI(217), osm4oc12PosSL(218), wsx6ksup1a2ge(219), fe18-75(220). fe18-120(221). ft18(222), cf-card(223), bsv2-v2(224).  e1vi1-v2(225), e1vi2(226), t1vi1-v2(227), t1vi2(228). osm(229), sd707(230), dm-epri(231), dm-tpri(232), erpu-h(233), wsf6kmsfc2(234), wsx6324mmmt(235), wsx6348rj45(236), wsx6ksup22ge(237), wsx6324sm(238), wsx6516gbic(239), osm4geWanGbic(240), osm1oc48PosSS(241), osm1oc48PosSI(242), osm1oc48PosSL(243), wsx6381ids(244), wsc6500sfm(245), osm16oc3PosMM(246), osm16oc3PosSI(247), osm16oc3PosSL(248), osm2oc12PosMM(249), osm2oc12PosSI(250), osm2oc12PosSL(251), wsx650210ge(252), osm8oc3PosMM(253), osm8oc3PosSI(254), osm8oc3PosSL(255), wsx6548rj45(258), wsx6524mmmt(259), wsx6066SlbApc(260), wsx6516getx(261), osm2oc48OneDptSS(265), osm2oc48OneDptSI(266), osm2oc48OneDptSL(267), osm2oc48OneDptSSDual(268), osm2oc48OneDptSIDual(269), osm2oc48OneDptSLDual(270), wsx6816gbic(271). osm4choc12T3MM(272), osm4choc12T3SI(273), osm8choc12T3MM(274), osm8choc12T3SI(275), osm1choc48T3SS(276), osm2choc48T3SS(277). wsx6500sfm2(278). osm1choc48T3SI(279), osm2choc48T3SI(280), wsx6348rj21(281), wsx6548rj21(282), wsSvcCmm(284), wsx650110gex4(285), osm4oc3PosSI(286). osm4oc3PosMM(289), wsSvcIdsm2(290), wsSvcNam2(291), wsSvcFwm1(292), wsSvcCe1(293). wsSvcSsl1(294). osm8choc3DS0SI(295), osm4choc3DS0SI(296), osm1choc12T1SI(297). wsx4012(300). wsx4148rj(301). wsx4232gbrj(302), wsx4306gb(303), wsx4418gb(304), wsx44162gbtx(305), wsx4912gb(306), wsx2948gbrj(307), wsx2948(309), wsx4912(310), wsx4424sxmt(311). wsx4232rjxx(312). wsx4148rj21(313), wsx4124fxmt(317), wsx4013(318). wsx4232l3(319), wsx4604gwy(320). wsx44122Gbtx(321). wsx2980(322), wsx2980rj(323), wsx2980gbrj(324). wsx4019(325). wsx4148rj45v(326), wsx4424gbrj45(330), wsx4148fxmt(331), wsx4448gblx(332), wsx4448gbrj45(334), wsx4148lxmt(337), wsx4548gbrj45(339). wsx4548gbrj45v(340). wsx4248rj21v(341), wsx4302gb(342), wsx4248rj45v(343), wsx2948ggetx(345), wsx2948ggetxgbrj(346), wsx6516aGbic(502), wsx6148getx(503), wsx6148x2rj45(506), wsx6196rj21(507), wssup32ge3b(509), wssup3210ge3b(510), mec6524gs8s(511), mec6524gt8s(512), me6524msfc2a(598), osm12ct3T1(600), osm12t3e3(601). osm24t3e3(602), osm4GeWanGbicPlus(603), osm1choc12T3SI(604). osm2choc12T3SI(605), osm2oc12AtmMMPlus(606), osm2oc12AtmSIPlus(607), osm2oc12PosMMPlus(608), osm2oc12PosSIPlus(609). osm16oc3PosSIPlus(610), osm1oc48PosSSPlus(611), osm1oc48PosSIPlus(612), osm1oc48PosSLPlus(613), osm4oc3PosSIPlus(614). osm8oc3PosSLPlus(615), osm8oc3PosSIPlus(616), osm4oc12PosSIPlus(617), wsSvcIpSec1(903), wsSvcCsg1(911), wsx6148rj45v(912), wsx6148rj21v(913), wsSvcNam1(914), wsx6548getx(915), wsx6066SlbSk9(920), wsx6148agetx(921), wsx6148arj45(923), wsSvcWlan1k9(924), wsSvcAon1k9(925), ace106500k9(926). wsSvcWebVpnk9(927). wsx6148FeSfp(928), wsSvcAdm1k9(929), wsSvcAgm1k9(930), ace046500k9(936), wssup720(1001), wssup720base(1002). m7600Sip600(1004). wsx6748getx(1007). wsx670410ge(1008). wsx6748sfp(1009). wsx6724sfp(1010), wsx670810ge(1016). wsx65822pa(1101), m7600Sip200(1102). m7600Sip400(1103). c7600ssc400(1104). c7600ssc600(1105). esm2x10ge(1106), rsp720(1800). rsp720base(1801). c7600msfc4(1805)

A descriptive string used by the network administrator to name the module.

The manufacturer's model number for the module.

The serial number of the module. This MIB object returns the module serial number for any module that uses either a numeric or an alphanumeric serial number.

The hardware version of the module.

The firmware version of the module.

The software version of the module.

This value is determined by the chassis slot number where the module is located. Valid entries are 1 to the value of chassisNumSlots.

The value of the instance of the entPhysicalIndex object, defined in ENTITY-MIB, for the entity physical index corresponding to this module.

The operational status of the module. If the status is not ok, the value of moduleTestResult gives more detailed information about the module's failure condition(s).

Possible Values:

• other(1)
• ok(2)
• minorFault(3)
• majorFault(4)

The number of ports supported by the module.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of interfaces for which card data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

Index into cardTable (not physical chassis slot number).

Functional type of this card (integer value).

Functional type of this card (parsed from type name value).

Text description of this card.

The serial number of this card, or zero if unavailable.

Hardware revision level of this card, or an empty string if unavailable.

Version of the firmware or microcode installed on this card, or an empty string if unavailable.

Number of slots on this card, or 0 if no slots or not applicable, or -1 if not determinable.

cardIndex of the parent card that directly contains this card, or 0 if contained by the chassis, or -1 if not  applicable or determinable.

The operational status of the card. cardOperStatus is up when a card is  recognized by the device and is enabled for operation. cardOperStatus is down if the card is not recognized by the device, or if it is not enabled for operation. cardOperStatus is standby if the card is enabled and acting as a standby slave.

Possible Values:

• not-specified(1)
• up (2)
• down (3)
• standby (4)
• standbyMaster (5)
• activeMaster (6)
• outOfService (7)
• masterBooting(8)
• activeMasterBooting(9)
• standbyMasterBooting(10)
• slaveBooting(11)

Number of slots on this card, or 0 if no slots or not applicable, or -1 if not  determinable.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of interfaces for which card data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

An indication of the type of address contained in the corresponding instance of cdpCacheAddress (parse just ifIndex from value). For example 1,2,3.

An indication of the type of address contained in the corresponding instance of cdpCacheAddress (full value). For example 1.6, 2.108, 2.3.

The Device-ID string as reported in the most recent CDP message. A zero-length string indicates no Device-ID field (TLV) was reported in the most recent CDP message.

The (first) network-layer address of the device's SNMP-agent as reported in the most recent CDP message. For example, if the corresponding instance of cacheAddressType had the value 'ip(1)', then this object would be an IP address.

The Version string as reported in the most recent CDP message. A zero-length string indicates no Version field (TLV) was reported in the most recent CDP message.

The Port-ID string as reported in the most recent CDP message. This is typically the value of the ifName object (for example, 'Ethernet0'). A zero-length string indicates no Port-ID field (TLV) was reported in the most recent CDP message

The Device's Functional Capabilities as reported in the most recent CDP message. For latest set of specific values, see the latest version of the CDP specification. A zero-length string indicates no Capabilities field (TLV) was reported in the most recent CDP message.

The Device's Hardware Platform as reported in the most recent CDP message. A zero-length string indicates that no Platform field (TLV) was reported in the most recent CDP message.

The remote device's interface's duplex mode, as reported in the most recent CDP message. The value unknown(1) indicates no duplex mode field (TLV) was reported in the most recent CDP message.

Possible Values:

• unknown(1)
• halfduplex(2)
• fullduplex(3)

The remote device's interface's native VLAN, as reported in the most recent CDP message. The value 0 indicates no native VLAN field (TLV) was reported in the most recent CDP message.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of remote devices for which remote device data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

Chassis type (integer value).

Possible Values:

• unknown(1)
• multibus(2)
• agsplus(3)

Chassis type (parsed string value).

Possible Values:

• unknown(1)
• multibus(2)
• agsplus(3)

Chassis hardware revision level, or an empty string if unavailable.

Unique ID string. Defaults to chassis serial number if available, otherwise empty. Can also be set with 'snmp-server chassis-id'.

The serial number of the chassis. This MIB object returns the chassis serial number for any chassis that uses either a numeric or an alphanumeric serial number.

ROM monitor version.

ROM system software version or an empty string if unavailable.

Bytes of RAM available to CPU.

Bytes of nonvolatile configuration memory.

Bytes of non-volatile configuration memory in use.

Number of slots in this chassis, or -1 of neither applicable nor determinable.

This variable contains a printable octet string that contains the System Bootstrap description and version identification.

This variable contains a printable octet string that contains the reason why the system was last restarted.

Return the amount of free memory in bytes.

This MIB object is obsolete as of IOS release 11.1. IOS release 11.1 introduced the CISCO-MEMORY-POOL-MIB, which better instruments all of the memory pools.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of nodes for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

Total size of the Flash device. For a removable device, the size is zero if the device has been removed.

Flash device name. This name is used to refer to the device within the system. Flash operations get directed to a device based on this name. The system has a concept of a default device. This would be the primary or most used device in case of multiple devices. The system directs an operation to the default device whenever a device name is not specified. The device name is therefore mandatory except when the operation is being done on the default device, or the system supports only a single Flash device. The device name is always available for a removable device, even when the device has been removed.

Description of a Flash device. The description is meant to explain what the Flash device and its purpose is. Current values are: System flash - for the primary Flash used to store full system images. Boot flash: for the secondary Flash used to store bootstrap images. The ciscoFlashDeviceDescr, CiscoFlashDeviceController (if applicable), and ciscoFlashPhyEntIndex objects are expected to collectively give all information about a Flash device. The device description is always available for a removable device, even when the device has been removed.

Flash device partitions actually present. The number of partitions cannot exceed the minimum of ciscoFlashDeviceMaxPartitions and (ciscoFlashDeviceSize / ciscoFlashDeviceMinPartitionSize). This is equal to at least 1, in the case where the partition spans the entire device (actually no partitioning). A partition contains one or more minimum partition units (where a minimum partition unit is defined by ciscoFlashDeviceMinPartitionSize).

This object gives the minimum partition size supported for this device. For systems that execute code directly out of Flash, the minimum partition size needs to be the bank size. (Bank size is equal to the size of a chip multiplied by the width of the device. In most cases, the device width is 4 bytes, and so the bank size would be four times the size of a chip). This has to be so because all programming commands affect the operation of an entire chip (in our case, an entire bank because all operations are done on the entire width of the device) even though the actual command may be localized to a small portion of each chip. So when executing code out of Flash, one needs to be able to write and erase some portion of Flash without affecting the code execution. For systems that execute code out of DRAM or ROM, it is possible to partition Flash with a finer granularity (for example, at erase sector boundaries) if the system code supports such granularity.

This object lets a management entity know the minimum partition size as defined by the system. If the system does not support partitioning, the value is equal to the device size in ciscoFlashDeviceSize. The maximum number of partitions that could be configured is equal to the minimum of ciscoFlashDeviceMaxPartitions and (ciscoFlashDeviceSize / CiscoFlashDeviceMinPartitionSize).

Flash device controller. The h/w card that actually controls Flash read/write/erase. Relevant for the AGS+ systems where Flash may be controlled by the MC+, STR or the ENVM cards, cards that may not actually contain the Flash chips. For systems that have removable PCMCIA flash cards that are controlled by a PCMCIA controller chip, this object may contain a description of that controller chip. Where irrelevant (Flash is a direct memory mapped device accessed directly by the main processor), this object has an empty (NULL) string.

This object gives the state of a jumper (if present and can be determined) that controls the programming voltage called Vpp to the Flash device. Vpp is required for programming (erasing and writing) Flash. For certain older technology chips it is also required for identifying the chips (which in turn is required to identify which programming algorithms to use; different chips require different algorithms and commands). The purpose of the jumper, on systems where it is available, is to write protect a Flash device. On most of the newer remote access routers, this jumper is unavailable since users are not expected to visit remote sites just to install and remove the jumpers when upgrading software in the Flash device. The unknown(3) value is returned for such systems and can be interpreted to mean that a programming jumper is not present or not required on those systems. On systems where the programming jumper state can be read back through a hardware register, the installed (1) or notInstalled (2) value is returned. This object is expected to be used in conjunction with the ciscoFlashPartitionStatus object whenever that object has the readOnly(1) value. In such a case, this object indicates whether the programming jumper is a possible reason for the readOnly state.

Possible Values:

• installed(1)
• notInstalled(2)
• unknown(3)

Max number of partitions supported by the system for this Flash device. The default is 1, which actually means that partitioning is not supported. Note that this value is defined by system limitations, not by the flash device itself (for example, the system may impose a limit of 2 partitions even though the device may be large enough to be partitioned into 4 based on the smallest partition unit supported). On systems that execute code out of Flash, partitioning is a way of creating multiple file systems in the Flash device so that writing into or erasing of one file system can be done while executing code residing in another file system. For systems executing code out of DRAM, partitioning gives a way of sub-dividing a large Flash device for easier management of files.

System time at which device was initialized. For fixed devices, this is the system time at boot up. For removable devices, it is the time at which the device was inserted, which may be boot up time or a later time (if device was inserted later). If a device (fixed or removable) was repartitioned, it is the time of repartitioning. The purpose of this object is to help a management station determine if a removable device has been changed. The application should retrieve this object prior to any operation and compare with the previously retrieved value. Note that this time is not real time but a running time maintained by the system. This running time starts from zero when the system boots up. For a removable device that has been removed, this value is zero.

Whether Flash device is removable. Generally, only PCMCIA Flash cards are treated as removable. Socketed Flash chips and Flash SIMM modules are not treated as removable. Simply put, only those Flash devices that can be inserted or removed without opening the hardware casing are considered removable. Further, removable Flash devices are expected to have the necessary hardware support: 1) on-line removal and insertion; 2) interrupt generation on removal or insertion.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of Cisco devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

Flash file name as specified by the user copying in the file. The name should not include the colon (:) character as it is a special separator character used to delineate the device name, partition name, and the file name.

Size of the file in bytes. Note that this size does not include the size of the filesystem file header. File size is always non-zero.

File checksum stored in the file header. This checksum is computed and stored when the file is written into Flash. It serves to validate the data written into Flash. Whereas the system generates and stores the checksum internally in hexadecimal form, this object provides the checksum in a string form. The checksum is available for all valid and invalid checksum files.

Status of a file. A file could be explicitly deleted if the file system supports such a user command facility. Alternately, an existing good file would be automatically deleted if another good file with the same name were copied in. Note that deleted files continue to occupy prime Flash real estate.

A file is marked as having an invalid checksum if any checksum mismatch was detected while writing or reading the file. Incomplete files (files truncated either because of lack of free space or a network download failure) are also written with a bad checksum and marked as invalid.

Possible Values:

• deleted(1)
• invalidChecksum(2)
• valid(3)

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of Cisco devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

The string of this entry.

The string of this entry.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of Cisco devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

A textual name assigned to the memory pool. This object is suitable for output to a human operator, and may also be used to distinguish among the various pool types, especially among dynamic pools.

Indicates the number of bytes from the memory pool that are currently in use by applications on the managed device.

Indicates the number of bytes from the memory pool that are currently unused on the managed device. Note that the sum of ciscoMemoryPoolUsed and ciscoMemoryPoolFree is the total amount of memory in the pool.

Indicates the largest number of contiguous bytes from the memory pool that are currently unused on the managed device.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of Cisco devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

A textual description of the logical entity. This object should contain a string that identifies the manufacturer's name for the logical entity , and should be set to a distinct value for each version of the logical entity.

Indicates the kind of transport service by which the logical entity receives network management traffic. Possible values for this object are presently found in the Transport Mappings for SNMPv2 document (RFC 1906 [RFC1906]).

An indication of the type of logical entity. This is typically the OBJECT-IDENTIFIER name of the node in the SMI's naming hierarchy that represents the major MIB module, or the majority of the MIB modules, supported by the logical entity. For example: a logical entity of a regular host/router > mib-2 a logical entity of a 802.1d bridge -> dot1dBridge a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt If an appropriate node in the naming hierarchy of SMI cannot be identified , the value 'mib-2' should be used.

An SNMPv1 or SNMPv2C community-string that can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string that allows more privileges than the community string used to access this object.

The transport service address by which the logical entity receives network management traffic, formatted according to the corresponding value of entLogicalTDomain. For snmpUDPDomain, a TAddress is 6 octets long, the initial 4 octets containing the IP-address in network-byte order and the last 2 containing the UDP port in network-byte order. Consult 'Transport Mappings for Version 2 of the Simple Network Management Protocol' (RFC 1906 [RFC1906]) for further information on snmpUDPDomain.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of Cisco devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

The textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's 'console'. This might be a text name, such as 'console' or a simple component number (for example, port or module number) , such as '1' , depending on the physical component naming syntax of the device.

If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string.

The value of entPhysicalName for two physical entities is the same if the console interface does not distinguish between them (for example, slot-1 and the card in slot-1).

A textual description of physical entity. This object should contain a string that identifies the manufacturer's name for the physical entity, and should be set to a distinct value for each version or model of the physical entity.

An indication of the vendor-specific hardware type of the physical entity. Note that this is different from the definition of MIB-II's sysObjectID.

An agent should set this object to a enterprise-specific registration identifier value indicating the specific equipment type in detail. The associated instance of entPhysicalClass is used to indicate the general type of hardware device.

If no vendor-specific registration identifier exists for this physical entity, or the value is unknown by this agent then the value { 0 } is returned.

The value of entPhysicalIndex for the physical entity that 'contains' this physical entity. A value of zero indicates this physical entity is not contained in any other physical entity. Note that the set of 'containment' relationships define a strict hierarchy; that is, recursion is not allowed.

In the event a physical entity is contained by more than one physical entity (for example, double-wide modules) , this object should identify the containing entity with the lowest value of entPhysicalIndex.

An indication of the general hardware type of the physical entity. An agent should set this object to the standard enumeration value that most accurately indicates the general class of the physical entity or the primary class if there is more than one. If no appropriate standard registration identifier exists for this physical entity, then the value 'other(1)' is returned. If the value is unknown by this agent, then the value 'unknown(2)' is returned.

An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as entPhysicalEntries that share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects.

The vendor-specific hardware revision string for the physical entity. The preferred value is the hardware revision identifier actually printed on the component itself (if present).

Note that if revision information is stored internally in a non-printable (for example, binary) format, then the agent must convert such information to a printable format, in an implementation-specific manner. If no specific hardware revision string is associated with the physical component, or this information is unknown to the agent, then this object contains a zero-length string.

The vendor-specific firmware revision string for the physical entity.

Note that if revision information is stored internally in a non-printable (for example, binary) format , then the agent must convert such information to a printable format , in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or this information is unknown to the agent, then this object contains a zero-length string.

The vendor-specific software revision string for the physical entity.

Note that if revision information is stored internally in a non-printable (for example, binary) format, then the agent must convert such information to a printable format , in an implementation-specific manner. If no specific software programs are associated with the physical component, or this information is unknown to the agent, then this object contains a zero-length string.

The vendor-specific serial number string for the physical entity. The preferred value is the serial number string actually printed on the component itself (if present).

The name of the manufacturer of this physical component. The preferred value is the manufacturer name string actually printed on the component itself (if present).

The vendor-specific model name identifier string associated with this physical component. The preferred value is the customer-visible part number, which may be printed on the component itself. If the model name string associated with the physical component is unknown to the agent, then this object contains a zero-length string.

This object is an 'alias' name for the physical entity as specified by a network manager, and provides a non-volatile 'handle' for the physical entity.

This object is a user-assigned asset tracking identifier for the physical entity as specified by a network manager, and provides non-volatile storage of this information.

This object indicates whether or not this physical entity is considered a 'field replaceable unit' by the vendor. If this object contains the value 'true(1)' then this entPhysicalEntry identifies a field replaceable unit. For all entPhysicalEntries that represent components that are permanently contained within a field replaceable unit, the value 'false(2)' should be returned for this object.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of Cisco devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

[Swis]

A unique value, greater than zero, for each interface. SolarWinds recommends assigning values contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one reinitialization of the entity's network management system to the next reinitialization.

A textual string containing information about the interface. This string should include the name of the manufacturer, the product name, and the version of the interface hardware or software.

The set of the device's member ports that belong to the VLAN. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. Thus, each port of the VLAN is represented by a single bit within the value of this object. If that bit has a value of '1' then that port is included in the set of ports. The port is not included if its bit has a value of '0'. A port number is the value of dot1dBasePort for the port in the BRIDGE-MIB (RFC 1493).

An indication of the current VLAN status of the port. A status of inactive(1) indicates that a dynamic port does not yet have a VLAN assigned, or a port is assigned to a VLAN that is currently not active. A status of active(2) indicates that the currently assigned VLAN is active. A status of shutdown(3) indicates that the port has been disabled as a result of VQP shutdown response.

Possible Values:

• inactive(1)
• active(2)
• shutdown(3)

The type of this VLAN

The textual name of the interface. The value of this object should be the name of the interface as assigned by the local device and should be suitable for use in commands entered at the device's 'console'. This might be a text name, such as 'le0' or a simple port number, such as '1' , depending on the interface naming syntax of the device. If several entries in the ifTable together represent a single interface as named by the device, then each entry has the same value of ifName. If there is no local name, or this object is otherwise not applicable, then this object contains a 0-length string.

This object is an 'alias' name for the interface as specified by a network manager, and provides a non-volatile 'handle' for the interface.

The type of interface. Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA), through updating the syntax of the IANAifType textual convention.

The type of interface. Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA), through updating the syntax of the IANAifType textual convention.

The type of interface. Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA), through updating the syntax of the IANAifType textual convention.

An estimate of the interface's current bandwidth in bits per second. For interfaces that do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. If the bandwidth of the interface is greater than the maximum value reportable by this object then this object should report its maximum value (4, 294, 967, 295) and ifHighSpeed must be used to report the interface’s speed. For a sub-layer that has no concept of bandwidth, this object should be zero.

The interface's address at its protocol sublayer. The interface's media specific MIB must define the bit and byte ordering and format of the value contained by this object. For interfaces that do not have such an address (for example, a serial line), this object should contain an octet string of zero length.

The desired state of the interface. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, ifAdminStatus is then changed to either the up (1) or testing (3) states (or remains in the down (2) state).

The current operational state of the interface. The testing (3) state indicates that no operational packets can be passed. If ifAdminStatus is down (2) then ifOperStatus should be down (2). If ifAdminStatus is changed to up (1) then ifOperStatus should change to up (1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down (2) state if and only if there is a fault that prevents it from going to the up (1) state.

The size of the largest packet that can be sent or received on the interface, specified in octets. For interfaces that are used for transmitting network datagrams, this is the size of the largest network datagram that can be sent on the interface.

The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.

This object has the value 'true(1)' if the interface sublayer has a physical connector and the value 'false(2)' otherwise.

This object has a value of false(2) if this interface only accepts packets/frames that are addressed to this station. This object has a value of true(1) when the station accepts all packets/frames transmitted on the media. The value true(1) is only legal on certain types of media. If legal, setting this object to a value of true(1) may require the interface to be reset before becoming effective.

The value of ifPromiscuousMode does not affect the reception of broadcast and multicast packets/frames by the interface.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of Cisco devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

NCM.NodeHostsInterfaces (System.Hosting)

The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as  identified by the same value of RFC 1573's ifIndex.

The IP address to which this entry's addressing information pertains.

Store IP address in double representation.

The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

InterfaceId from interfaces table.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of Cisco devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

Either the value '0', or the port number of the port on which a frame having a source address equal to the value of the corresponding instance of dot1dTpFdbAddress has been seen. A value of '0' indicates that the port number has not been learned but that the bridge does have some forwarding/filtering information about this address (for example, in the dot1dStaticTable). Implementers are encouraged to assign the port value to this object whenever it is learned even for addresses for which the corresponding value of dot1dTpFdbStatus is not learned(3).

A unicast MAC address for which the bridge has forwarding and/or filtering information.

The status of this entry. The meanings of the values are: other(1) : none of the following. This would include the case where some other MIB object (not the corresponding instance of dot1dTpFdbPort, nor an entry in the dot1dStaticTable) is being used to determine if and how frames addressed to the value of  the corresponding instance of dot1dTpFdbAddress are being forwarded.

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of Cisco devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

IP address of the device entered manually by the user.

NCM-only specific status of the device:

• Unknown = 0 (not polled yet)
• Up = 1 (based on ICMP pool)
• Down = 2 (based on ICMP pool)
• Warning = 3 (based on ICMP pool)
• MonitoringDisabled = 10 (NCM node monitoring is disabled by user)
• UnManaged = 9 (device is unmanaged in NCM)

SNMP community string entered by the user.

DNS name of the device.

An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name.

A textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating-system, and networking software. It is mandatory that this contains only printable ASCII characters.

The textual identification of the contact person for this managed node, together with information on how to contact this person.

The physical location of this node (for example, 'telephone closet, 3rd floor').

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining 'what kind of box' is being managed. For example, if vendor 'Flintstones , Inc.' was assigned the subtree 1.3.6.1.4.1.4242 , it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its 'Fred Router'.

Vendor of device- determined based on SystemOID.

Vendor icon of device- determined based on SystemOID.

Machine Type - determined based on SystemOID.

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

Determined based on SysDescr.

Determined based on SysDescr.

SNMP version selected by the user (1,2 or 3).

SNMPv3 credentials entered by the user.

SNMPv3 credentials entered by the user.

SNMPv3 credentials entered by the user.

SNMPv3 credentials entered by the user.

SNMPv3 credentials entered by the user.

SNMPv3 credentials entered by the user.

The status of SNMP connection to the device (OK, No SNMP support, SNMP error description if any).

A SWIS-generated unique identifier of a network node in the current inventory. (Instances of this property recur in this table according to the number of devices for which data is reported.)

A SWIS-generated date and time marker for when NCM last discovered the device during inventory.

NCM.NodeHostsInterfaces (System.Hosting)

NCM.NodeHostsMacForwarding (System.Hosting)

NCM.NodeHostsVLANs (System.Hosting)

NCM.NodeHostsBridgePorts (System.Hosting)

NCM.NodeHostsArpTables (System.Hosting)

NCM.NodeHostsCiscoCards (System.Hosting)

NCM.NodeHostsCiscoCdp (System.Hosting)

NCM.NodeHostsCiscoChassis (System.Hosting)

NCM.NodeHostsCiscoFlash (System.Hosting)

NCM.NodeHostsCiscoFlashFiles (System.Hosting)

NCM.NodeHostsCiscoImageMIB (System.Hosting)

NCM.NodeHostsCiscoMemoryPools (System.Hosting)

NCM.NodeHostsEntityLogical (System.Hosting)

NCM.NodeHostsEntityPhysical (System.Hosting)

NCM.NodeHostsPortsTcp (System.Hosting)

NCM.NodeHostsPortsUdp (System.Hosting)

The unique identifier of a network node subject to configuration actions.

Date and time NCM last discovered the device during inventory.

Date and time NCM first discovered the device during inventory.

The local IP address for this TCP connection. In the case of a connection in the listen state that is willing to accept connections for any IP interface associated with the node, the value 0.0.0.0 is used.

The local port number for this TCP connection.

Port description based on TCPLocalPort value.

The remote IP address for this TCP connection.

The remote port number for this TCP connection.

The state of this TCP connection.

The only value that may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a 'badValue' response if a management station attempts to set this object to any other value.

If a management station sets this object to the value deleteTCB(12) , then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection.

As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).

The unique identifier of a network node subject to configuration actions.

Date and time NCM last discovered the device during inventory.

Date and time NCM first discovered the device during inventory.

The local IP address for this UDP listener. In the case of a UDP listener that is willing to accept datagrams for any IP interface associated with the node, the value 0.0.0.0 is used.

The local port number for this UDP listener.

The unique identifier of a network node subject to configuration actions.

Date and time NCM last discovered the device during inventory.

Date and time NCM first discovered the device during inventory.

The index value that uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.

Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipRouteDest field. For those systems that do not support arbitrary subnet masks , an agent constructs the value of the ipRouteMask by determining whether the value of the correspondent ipRouteDest field belong to a class-A , B , or C network , and then using one of:

• mask network
• 255.0.0.0 class-A
• 255.255.0.0 class-B
• 255.255.255.0 class-C

If the value of the ipRouteDest is 0.0.0.0 (a default route), then the mask value is also 0.0.0.0. Note that all IP routing subsystems implicitly use this mechanism.

The type of route. Note that the values direct(3) and indirect(4) refer to the notion of direct and indirect routing in the IP architecture. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipRouteTable object. That is, it effectively disassociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table.

Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipRouteType object.

Possible Values:

• other(1)
• invalid(2)
• direct(3)
• indirect(4)

The routing mechanism through which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.

Possible Values:

• other(1)
• local(2)
• netmgmt(3)
• icmp(4)
• egp(5)
• ggp(6)
• hello(7)
• rip(8)
• is-is(9)
• es-is(10)
• ciscoIgrp(11)
• bbnSpfIgp(12)
• ospf(13)
• bgp(14)

The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of 'too old' can be implied except through knowledge of the routing protocol by which the route was learned.

The IP address of the next hop of this route. (In the case of a route bound to an interface that is realized via a broadcast media, the value of this field is the agent's IP address on that interface.)

The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

The index value that uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.

Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipRouteMask by determining whether the value of the correspondent ipRouteDest field belong to a class-A, B, or C network, and then using one of:

• mask network
• 255.0.0.0 class-A
• 255.255.0.0 class-B
• 255.255.255.0 class-C

If the value of the ipRouteDest is 0.0.0.0 (a default route) , then the mask value is also 0.0.0.0. Note that all IP routing subsystems implicitly use this mechanism.

The unique identifier of a network node subject to configuration actions.

Date and time NCM last discovered the device during inventory.

Date and time NCM first discovered the device during inventory.

The set of the device's member ports that belong to the VLAN. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. Thus, each port of the VLAN is represented by a single bit within the value of this object. If that bit has a value of '1' then that port is included in the set of ports ; the port is not included if its bit has a value of '0'. A port number is the value of dot1dBasePort for the port in the BRIDGE-MIB (RFC 1493).

The name of this VLAN. This name is used as the ELAN-name for an ATM LAN-Emulation segment of this VLAN.

The MTU size on this VLAN, defined as the size of largest MAC-layer (information field portion of the) data frame that can be transmitted on the VLAN.

The type of this VLAN