NBS-CMMC-MIB: View SNMP OID List / Download MIB

NBS object identifier definition

MIB for representing NBS CMMC information

all MIB objects in nbsCmmc MIB.

Objects systemic in scope

The description of the System Control Firmware.

The System Control Firmware version in the form Vmajor.minor.

This object is used to reset the system. Writing a coldRestart(2), causes the SNMP Agent CPU to be hardware reset, similar to a power-on cycle. Writing a warmRestart(3), causes only a restart of the System Control CPU operative software. Writing a upgrRestart(4), causes a total restart of the system software, but attempts to leave the hardware alone. Enumeration: 'running': 1, 'coldRestart': 2, 'upgrRestart': 4, 'warmRestart': 3.

Number of warmRestarts executed by the system, since the last coldRestart or power-on cycle. A warmRestart may be initiated by: - writing a warmRestart value in nbsCmmcSysRestart - a warmRestart command from the Command Line. - the SNMP Agent Firmware due to certain conditions.

The time (in hundredths of a second) since the last cold reset/power cycle when a fatal error occurred. This variable shows the system uptime from the last cold reset/power on cycle, unless a fatal error oc- curred.

Writing the value setDefaults to this objects will re- store the defaults in the NVRAM data base. These values will take effect after a system reset. For the Linux-based NM family, after restoring defaults, take care not to commit running changes with the nbsCmmcSysWriteConfig object. Doing so would undo the defaults, overwriting them with the running configuration. Enumeration: 'setDefaults': 1.

NVRAM based level of the system selftest. The values are : ststNone - meaning that no selftest will be executed upon boot-up ststShort- meaning that a short selftest, of approx 10-20 seconds will be executed upon boot- up ststLong - meaning that a long/extensive self-test will be executed upon boot-up ststDiagnostics - meaning that upon boot-up the di- agnostics mode is entered. In this mode it is possible to interactively select the test or the group of tests that will be executed. This value may not be set through a SNMP SET command. This object is deprecated. Enumeration: 'ststLong': 3, 'ststDiagnostics': 4, 'ststNone': 1, 'ststShort': 2.

The current time, expressed as the number of seconds since 00:00 (midnight) 1 January 1900 GMT. Obtained via Time Protocol (RFC 868) or set by user. Not supported value: 0

The current time, derived from nbsCmmcSysCurrentTime, adjusted to Agent's local time (nbsCmmcSysTimeZone), expressed in the format 'www mm dd hh:mm:ss yyyy'. If nbsCmmcSysCurrentTime is 0, this value should be 'unknown'.

Copy of Non-Volatile RAM kept in Agent, including all settings, configurations, and names for all cards managed by this Agent.

Represents a block of NVRAM

NVRAM Block number, starting with 1.

Bytes contained in this block of NVRAM.

This object is used to write the configuration file. If this returns supported, the SNMP Agent requires you to specifically write the configuration file. Any changes that are not written out will be lost on next reboot. Setting copyTempFile(4) will copy the file uploaded via nbsCmmcSysNvramTable into the non-volatile startup area. Enumeration: 'supported': 2, 'write': 3, 'notSupported': 1, 'copyTempFile': 4.

This object allows user to initiate a transfer of firmware from the NM file system to the cards in selected slots. Before using, user should ensure the proper files have been loaded (TFTP'd) onto the NM. This object has read-write access so it will be more universally compilable, but is intended only for writing. For reading, the contents are undefined. The string should contain a comma-separated list of slots to be reprogrammed, in the format chassis.slot, or chassis.* to load all cards. While the NM is reprogramming the line card, SNMP communication may be temporarily suspended.

This object is used to control the idle logout timer. This timer is in minutes. If a user logged into the CLI has not typed anything for this number of minutes, the session is automatically closed. Zero means no automatic timeout.

The Discovery protocol allows Linux NM cards to find each other on a single layer 2 network segment. By default it is enabled. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

Table that contains host information found using the L2 Discovery protocol

Represents a single host found using the L2 Discovery protocol

MAC address of discovered host

How many hops from me is this host?

IP address of discovered host

If the last SNMP SET was rejected, for example with SNMP Error: BadValue (SNMP Error 3), this object should explain why the SET failed. This string may be empty (size 0) if no explanation is available. If there have been no SET requests since boot-up, this string should be empty (size 0). In addition to this object, SET errors may also be found in the nbsCmmcSysRunningLogMessageTable.

Time Protocol (RFC 868) allows the managed device to synchronize its clock with a Time Server. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

The IP Address of the Time Server.

Table that lists firmware images loaded on NM.

Description of a firmware image

Unique Id for this row

Description of firmware image

The filename of the firmware package. If it is in the format scheme://host/path, it refers to nbsCmmcSysFirmwareURL.

The size (in bytes) of the firmware package file

The last modified time of the firmware package file itself.

The version of the firmware package

The date of release of the firmware package in RFC 2822 format

What kind of entity this package is for. Valid rev files have type chassis(2), slot(3), or port(4). invalid(1) indicates this entry is not a valid rev file. deleted(5) indicates this entry refers to a file that was deleted and is no longer in the management card storage area. This entry may be re-enabled if the identical file is again put on the management card. This way, indexes do not move around if files are deleted and subsequently restored. However, deleted slots may be reused by the system for new files at the system's descretion. Setting deleted(5) will delete this file permanently from the management card storage area. No values other than deleted(5) can be set. Enumeration: 'slot': 3, 'deleted': 5, 'chassis': 2, 'port': 4, 'invalid': 1.

A comma separated list of module versions supported by this firmware package

The checksum of the metadata. Used to uniquely identify this package file. Invalid package files have a zero Cksum. Not supported value: 0

User-configurable TimeZone or offset from GMT. Should be used to indicate the time local to the managed device. If the system supports nbsCmmcSysTimeZoneTableSize and it is non-zero, this object is the nbsCmmcSysTimeZoneIndex of nbsCmmcSysTimeZoneTable, which enumerates all the time zones that this system supports. Enumeration: 'gmtMinus0900': 5, 'gmtPlus0300': 17, 'gmtMinus0800': 6, 'gmtMinus0100': 13, 'gmtPlus0200': 16, 'notSupported': 1, 'gmtPlus0100': 15, 'gmtMinus1000': 4, 'gmtPlus0900': 23, 'gmtMinus0700': 7, 'gmtPlus0700': 21, 'gmtMinus1100': 3, 'gmtMinus0600': 8, 'gmtPlus0800': 22, 'gmtMinus0500': 9, 'gmtMinus0400': 10, 'gmt': 14, 'gmtPlus1000': 24, 'gmtMinus1200': 2, 'gmtMinus0300': 11, 'gmtPlus1100': 25, 'gmtPlus0500': 19, 'gmtPlus1200': 26, 'gmtPlus0400': 18, 'gmtPlus0600': 20, 'gmtMinus0200': 12.

This object enables or disables SNMPv1 protocol handling. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

This object enables or disables SNMPv2c protocol handling. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

This object enables or disables SNMPv3 protocol handling. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

This object enables or disables LMP protocol handling. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

If enabled, forces the system only to allow writes to slots/ports that are detected as the same type as the configured type. Use nbsCmmcSlotClearType to clear the configured type. When this object is enabled(3) and a module is inserted that is incompatible with the configured type, Agent should issue the notification nbsCmmcTrapSlotModuleLocked instead of nbsCmmcTrapSlotModuleIn. The notfication nbsCmmcTrapSlotModuleIn should be issued once the lock has been cleared (see nbsCmmcSlotClearType). Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

Name of terminal to use for the serial port, e.g. vt100, xterm, ansi.

For systems which have chassis/slots supporting cross-connect functionality, this object is used to reflect the operating state and clear the entire cross-connect map, including any independent maps of subordinate chassis and slots. If there are currently no cross-connect chassis or slots in this system, the Agent must report notSupported(1). Additionally, if this object reports notSupported(1), any SNMP SET to this object should return SNMP Error 3 (bad value). The Agent should report operating(2) under normal circumstances. If this object reports operating(2), SNMP Managers are allowed to set this object to clearing (3), which instructs the Agent to erase the cross-connect maps of all subordinate chassis and slots, so no circuits exist in the system. Enumeration: 'clearing': 3, 'notSupported': 1, 'operating': 2.

This object is used to reset all counters in this device. If agent does not have this feature, this object should be notSupported(1). In order to reset all counters to zero, set this object to clearing(3). If this feature is supported, the Agent may return the status clearing (3) during the interval in which it is resetting the counters, but otherwise should return the status counting(2). Enumeration: 'clearing': 3, 'notSupported': 1, 'counting': 2.

The number of entries in nbsCmmcSysProtoTable.

A table to report supportable data transmission protocols.

Describes a particular protocol or line rate.

Protocol number.

Family of this protocol. The following family names must be used exactly for machine-readability: SONET T-Carrier E-Carrier Ethernet FibreChannel DigitalVideo Other family names may be added as necessary.

Speeds or rates associated with this protocol.

The number of entries in nbsCmmcSysTimeZoneTable.

A table to report supportable timezones.

Describes a timezone.

TimeZone index corresponding to a nbsCmmcSysTimeZone setting. The first entry is reserved for 'notSupported'. The next 25 entries are reserved for GMT-12 (gmtMinus1200) through GMT+12 (gmtPlus1200) for compatibility with the older nbsCmmcSysTimeZone enumeration. Entries 27 and up are specific to the system.

Name of this timezone.

The maximum number of concurrent loader sessions.

A table to manage multiple loader (transfer from NM to blade or line card) sessions.

Describes a particular loader session.

Agent-determined session number.

The nbsCmmcSysFirmwareIndex value corresponding to the file being loaded.

Percentage of file transferred so far.

Status of this file transfer. The value idle (1) indicates this loader session is unused. The value transferring (2) indicates this transfer is underway. The value completed (3) indicates this transfer finished successfully. The value aborted (4) indicates the transfer was stopped before completion. Enumeration: 'idle': 1, 'transferring': 2, 'completed': 3, 'aborted': 4.

This object allows users to prematurely halt this loader session. If this loader session can not be aborted, the agent will report notSupported(1). If nbsCmmcSysLoaderStatus is transferring(2) and this feature is supported, the agent will report supported(2). When a GET on this object returns supported(2), a user may set this object to abort(3). Doing so will cause the agent to stop the transfer and change nbsCmmcSysLoaderStatus to aborted(4). The agent should report the values of nbsCmmcSysLoaderFileId and nbsCmmcSysLoaderProgress as the state they were in at the time of the abort. Please note that aborting a loader session will leave the destination memory bank with a corrupted, unusable firmware image. It is important for users to correct this promptly, by (re)transferring a good and complete firmware image. Enumeration: 'supported': 2, 'notSupported': 1, 'abort': 3.

This object allows users to ACKnowledge the termination of this loader session. If nbsCmmcSysLoaderStatus is idle(1) or transferring(2), the agent will report this object as notSupported(1). If nbsCmmcSysLoaderStatus is completed(3) or aborted(4), the agent should report supported(2). When a GET on this object returns supported(2), a user may set this object to acknowledge(3). Doing so will cause the agent to either: - delete this entire row of the nbsCmmcSysLoaderTable, or - reset this row to its idle state by clearing both nbsCmmcSysLoaderFileId and nbsCmmcSysLoaderProgress to zero, and changing nbsCmmcSysLoaderStatus to idle(1). Enumeration: 'supported': 2, 'notSupported': 1, 'acknowledge': 3.

A copy of nbsCmmcSysFirmwareFilename, for display.

Remote URL in the form: scheme://[username[:password]@]IP[:port][/path/]filename to use for the remote entry in FirmwareTable. When set, the remote URL will be retrieved and checked for compatability. If it is a valid firmware file, a row in FirmwareTable will be instantiated to represent this file. The corresponding FirmwareFilename will be set to the URL, and FirmwareType set accordingly. The file may or not be cached locally if this row is chosen for a Chassis or SlotFirmwareLoad. If the user has changed the remote file after FirmwareURL is set, but before a Chassis or SlotFirmwareLoad is initiated, the results are undefined. If the remote file has changed, setting this object again will 'refresh' its FirmwareTable entry. If a zero length string is set, the corresponding FirmwareType in the FirmwareTable row will be changed to 'deleted', and any local cache of the file deleted. If an invalid URL is set, or the remote file is invalid or does not exist, the corresponding FirmwareTable row will be changed to 'deleted'. If port is omitted, an appropriate port according to the scheme will be automatically selected Note that only numeric IPs are supported; there is no resolver. If a remote file fetch is in progress, or any Chassis or SlotFirmwareLoad involving a remote URL is in progress, sets to this object will be rejected. This object is not stored in the running configuration. It is an 'impulse' object.

The state of the URL fetch process initiated by a write to SysFirmwareURL. Setting the Chassis or SlotFirmwareLoad object to the URL index will be rejected unless this object returns completed(4). Enumeration: 'transferring': 3, 'failed': 5, 'idle': 2, 'notSupported': 1, 'completed': 4.

The number of non-volatile firmware flash image areas system wide

Table that lists firmware images loaded on a chassis, slot, or port.

Description of a firmware image

Interface index in the form CCSSPPP

Number of this memory bank / storage area. Numbering must start from one, and bank numbers must be contiguous.

invalid(1) indicates this entry is not a valid NV area. primary(2) indicates this entry is the primary NV area. The next time the hardware is reset, this image will be loaded. This setting may be changed via nbsCmmcChassisNVAreaAdmin or nbsCmmcSlotNVAreaAdmin. backup(3) indicates this entry is the backup NV area. The next time the hardware is reset, this image will be loaded if the primary image fails to load. This image is subject to being overwritten if a new image is downloaded and there are no other banks available. erased(4) indicates this entry refers to an area that was erased and is no longer in the NV storage area. busy(5) indicates this NV area is busy. Enumeration: 'erased': 4, 'busy': 5, 'backup': 3, 'primary': 2, 'invalid': 1.

Description of firmware image

The version of the firmware package

The checksum of the metadata. Used to uniquely identify this NV area. Invalid NV areas have a zero Cksum. Not supported value: 0

IP and SNMP configuration objects

The SNMP Agent Administrative value of the IP Address for the private in-band access. This value is stored in the system NVRAM. The current operational IP Address may be obtained by accessing the ipAdEntAddr entry in the ipAddrTable, for ipAdEntIfIndex equal to the private interface value. If the system has no current operational IP Address, meaning that, the access is done out-of-band, then this value takes effect immediately. In this case the NetMask and the BcastAddr will be automatically built. Otherwise it will take effect after a system reset.

The SNMP Agent Administrative value of the subnet mask for the private in-band access. This value is stored in the system NVRAM. The current operational IP Adress may be obtained by accessing the ipAdEntNetMask entry in the ipAddrTable, for ipAdEntIfIndex equal to the private interface value. If the system has no current operational IP Address, meaning that the access is done out-of-band, then this value takes effect immediately. Otherwise it will take effect after a system reset

The SNMP Agent Administrative value of the IP Broad- cast Address for the private in-band access. This value is stored in the system NVRAM. The current operational IP Adress may be obtained via the ipAdEntBcastAddr entry in the ipAddrTable for ipAdEntIfIndex equal to the private interface value. If the system has no current operational IP Address, meaning that the access is done out-of-band, then this value takes effect immediately. Otherwise it will take effect after a system reset

The SNMP Agent Administrative value of the IP Address for the system. This value is stored in the system NVRAM. The current operational IP Adress may be obtained by accessing the ipAdEntAddr entry in the ipAddrTable for ipAdEntIfIndex equal to the system interface value. If the system has no current operational IP Address, meaning that the access is done out-of-band, then this value takes effect immediately. In this case the NetMask and the BcastAddr will be automatically built. Otherwise it will take effect after a system reset.

The SNMP Agent Administrative value of the subnet mask for the system. This value is stored in the system NVRAM. The current operational IP Adress may be obtained by accessing the ipAdEntNetMask entry in the ipAddrTable for ipAdEntIfIndex equal to the system interface value If the system has no current operational IP Address, meaning that the access is done out-of-band, then this value takes effect immediately. Otherwise it will take effect after a system reset

The SNMP Agent Administrative value of the IP Broadcast Address for the system. This value is stored in the system NVRAM. The current operational IP Adress may be obtained by accessing the ipAdEntBcastAddr entry in the ipAddrTable for ipAdEntIfIndex equal to the system interface value. If the system has no current operational IP Address, meaning that the access is done out-of-band, then this value takes effect immediately. Otherwise it will take effect after a system reset

The SNMP Agent Administrative value of the IP Address for the out-band access. This value is stored in the system NVRAM. The current operational IP Adress may be obtained by accessing the ipAdEntAddr entry in the ipAddrTable, for ipAdEntIfIndex equal to the SLIP interface value. If the system has no current operational Out-Band IP Address, meaning that, the access is done in-band, then this value takes effect immediately. In this case the NetMask and the BcastAddr will be automa- tically built. Otherwise it will take effect after a system reset

The SNMP Agent Administrative value of the subnet mask for the out-band access. This value is stored in the system NVRAM. The current operational IP Adress may be obtained by accessing the ipAdEntNetMask entry in the ipAddrTable, for ipAdEntIfIndex equal to the SLIP interface value. If the system has no current operational Out-Band IP Address, meaning that, the access is done in-band, then this value takes effect immediately. Otherwise it will take effect after a system reset

The SNMP Agent Administrative value of the IP Broadcast Address for the in-band access. This value is stored in the system NVRAM. The current operational IP Adress may be obtained by accessing the ipAdEntBcastAddr entry in the ipAddrTable, for ipAdEntIfIndex equal to the SLIP interface value. If the system has no current operational Out-Band IP Address, meaning that, the access is done in-band, then this value takes effect immediately. Otherwise it will take effect after a system reset

The SNMP Agent Administrative value of the Default Gateway. This value is stored in the system NVRAM. The current operational Default Gateway IP Adress may be obtained by accessing ipRouteNextHop object of the 0.0.0.0 entry in the ipRouteTable. If the system has no current operational Default Gateway IP Address, then this value takes effect immediately. Otherwise it will take effect after a system reset.

This object indicates whether the NM should automatically retrieve its IP settings from its local network using BootP or DHCP. This setting will be stored in persistent memory, and thus preserved over system resets and power cycles. Enumeration: 'disabled': 1, 'enabled': 2.

This object indicates whether BootP or DHCP was enabled when the NM last booted. Enumeration: 'disabled': 1, 'enabled': 2.

The mode in which the serial line is used: by the local Administrative Interface, or as a SLIP line. Note that setting this object to adminIf(1) value while in SLIP mode will abort the serial connection between the SNMP Manager and the device. Setting this object to slipIf(2) while in Administrative Interface Mode will abort the local terminal connection. Enumeration: 'adminIf': 1, 'slipIf': 2.

The Serial Line Baud Rate when in SLIP Mode. This value is stored in the system NVRAM as well as in the SNMP Agent current configuration. Enumeration: 'b19200': 2, 'b9600': 1, 'b38400': 3.

The aging time for the ARP table.

The maximum number of entries in nbsCmmcSysTelnetTable.

A table describing the Telnet Sessions

Contains the information describing a Telnet Session

The index in the Telnet Table for this entry.

This object indicates if there is any TELNET session in progress. Enumeration: 'disconnect': 2, 'connected': 1.

This object indicates the remote IP host that connected to the local device. It is 0.0.0.0 if there is no active Telnet session

This object indicates the port number of the remote IP host.

This object indicates the IP address of the local device. It is 0.0.0.0 if there is no active Telnet session

This object indicates the local port number.

The internal session identifier for this entry.

This object indicates the length of time connected.

The maximum number of Ping Sessions allowed in this system.

A table describing the Ping Sessions

Contains the information describing a Ping Session

Index in the Ping Session Table.

This object controls the activity of the PING process progress. If GET idlePing(1) shows that the ping process is idle If SET idlePing(1) stops an active ping process, if any. If GET runPing(2) shows an active ping process. If SET runPing(2) starts an active ping process, if none active. This has to be the last SET in order to activate the PING process Enumeration: 'runPing': 2, 'idlePing': 1.

The IP Address to which the NM device will ping. Setting this variable initiates the ping sequence. The default value is the loopback address 127.0.0.1.

The number of ICMP echo packets (pings) to be sent. The default value is 1.

If a Ping Process is active, then the value of this object shows who activated it: the Administrative Interface, the SNMP Agent or a Web Based Manager. Enumeration: 'none': 1, 'adminInterface': 2, 'snmpAgent': 3, 'webManager': 4.

The number of ICMP echo request (pings) sent.

The number of ICMP echo response packets received.

The telnet server ships disabled by default on the NM2. Not supported means that the telnet server status cannot be changed from SNMP. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

The ssh server ships enabled by default on the NM2. Not supported means that the ssh server status cannot be changed from SNMP. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

The IP address actually being used by the Agent. The Agent's IP address may be assigned automatically by a bootp or DHCP server, or a static IP may be assigned via the nbsCmmcSysIpAddr object.

The subnet mask actually being used by the Agent. The Agent's subnet mask may be assigned automatically by a bootp or DHCP server, or may be assigned via the nbsCmmcSysNetMask object.

The IP Broadcast address actually being used by the Agent. The Agent's IP Broadcast address may be assigned automatically by a bootp or DHCP server, or may be assigned via the nbsCmmcSysBcastAddr object.

The Default Gateway actually being used by the Agent. The Agent's Default Gateway may be assigned automatically by a bootp or DHCP server, or may be assigned via the nbsCmmcSysBcastAddr object.

The web server ships enabled by default on the NM2. Not supported means that the web server status cannot be changed from SNMP. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

The TCP/UDP/IP port the Agent will listen on for web (HTTP) traffic when nbsCmmcSysWebServer is enabled(3). Not supported value: -1

The TCP/IP port the Agent will listen on for Telnet traffic when nbsCmmcSysTelnetServer is enabled(3). Not supported value: -1

The TCP/UDP/IP port the Agent will listen on for Secure Shell (SSH) traffic if nbsCmmcSysSshServer is enabled(3). Not supported value: -1

The SNMP Agent Administrative value of the write community string. This value is stored in the system NVRAM. It will take effect after a system reset. The object may not be read for obvious security reasons. A GET request will be answered by a zero length string.

The SNMP Agent Administrative value of the read community string. This value is stored in the system NVRAM. It will take effect after a system reset

The maximum size (number of rows) allowed in the trap table

A table of managers to whom will the traps generated by the SNMP agent will be sent. It represents the current operational table as well as the NVRAM saved table. The entries in the table are saved over system resets and power up cycles

Contains the information necessary to generate a trap to be sent to a particular manager. The object nbsCmmcSysTrapTblEntStatus, when written is used to create or delete an entry/row in nbsCmmcSysTrapTable. To create a new entry a SET PDU with the nbsCmmcSysTrapTblEntIpAddr, nbsCmmcSysTrapTblEntComm and nbsCmmcSysTrapTblEntStatus objects is required.

The index of the entry/row in the trap table in the range 1 to the value of nbsCmmcSysTrapTblMaxSize.

This object is used to get/set the validity of the information contained by nbsCmmcSysTrapEntry row. Setting this object to the value invalid(1) has the effect of deleting the corresponding nbsCmmcSysTrapTable entry. Deleting and entry has the effect of initializing it to default values : IpAddr = 0.0.0.0 & Comm = null string. Setting this object to the value valid(2) entry has the effect of creating a new row in the nbsCmmcSysTrapTable object, if an entry with the same nbsCmmcSysTrapTblEntIpAddr does not exist. If such an entry exists, then a 'badValue' error will be returned. The GET operations will receive a value of valid(2) for existing entries. An invalid(1) value indicates an entry that was deleted by a previous SET operation. Enumeration: 'active': 2, 'invalid': 1.

IP Address of a manager that is to receive the SNMP agent generated traps

Community string used by the SNMP agent in the traps generated to this SNMP manager/receiver.

Event severity level threshold for this SNMP manager. If the event severity level is at least nbsCmmcSysTrapTblEntLevel, the SNMP agent will generate a trap to this SNMP manager/receiver. Enumeration: 'alarm': 7, 'error': 3, 'disabled': 1, 'warning': 4, 'deprecated6': 6, 'deprecated5': 5, 'fatal': 2.

The UDP/IP port on the Manager to which the Agent will send SNMP traps/notifications. Not supported value: -1

Indicates whether powerSupplyAllarmOn and powerSupplyAllarmOff traps in this MIB should be generated. Enumeration: 'disabled': 1, 'enabled': 2.

Indicates whether moduleUp and moduleDown traps in this MIB should be generated. Enumeration: 'disabled': 1, 'enabled': 2.

Indicates whether newRoot and topologyChange traps in the BRIDGE-MIB should be generated. Enumeration: 'disabled': 1, 'enabled': 2.

Indicates whether IP access traps in this MIB should be generated. Enumeration: 'disabled': 1, 'enabled': 2.

The UDP/IP port the Agent will listen on for SNMP traffic after the next system restart. Not supported value: -1

The UDP/IP port the Agent is listening on for SNMP traffic now. Not supported value: -1

TFTP objects

This is the IP Address of the TFTP Server/Client serving the actual TFTP transfer. A TFTP transfer may mean a software/microcode/parameter/etc.. download/upload process, initiated by the SNMP agent, for one of the modules, including, but not only, the System Control Card. It is 0.0.0.0, if th TFTP host is undefined.

Maximum number of parallel TFTP sessions that are supported by the system

A table that describes the active TFTP sessions

Contains a description of a particular TFTP session

The index of the TFTP session (1..nbsCmmcTftpMaxSessionNum)

The status of this TFTP session Enumeration: 'underCreation': 3, 'active': 4, 'create': 2, 'inactive': 1, 'transferEnded': 5.

This is the IP Address of the TFTP Host (Server/Client) serving the TFTP session as a source/destination. An IP address of 0.0.0.0 signifies that no setup has been done. Setting the nbsCmmcTftpSessHostIp value will change also the the default of all the instances of nbsCmmcTftpSessHostIp that were not specifically initialized by a SET operation.

Deprecated. Module Id that owns this TFTP session (whose firmware/microcode/parameters/etc. are transferred

This object is used to initiate a TFTP file transfer. If nbsCmmcTftpSessStatus is not active (4), the Agent should report the value inactive (1). The Manager may initiate a session between the Agent and the host specified in nbsCmmcTftpSessHostIp by changing the value of this object. Setting the value downloadNM (2) tells the Agent to transfer its firmware image from the host to itself. Setting the value uploadNM (3) tells the Agent to transfer its firmware image from itself to the host. Setting the value downloadPar (4) tells the Agent to transfer a previous backup of its configuration from the host to itself. Setting the value uploadPar (5) tells the Agent to send a backup file of its current configuration to the host. For any other type of file, the Manager should set this value to downloadFile (6) to send a file from the host to the NM, and uploadFile (7) to transfer a file from the NM to the host. Enumeration: 'uploadFile': 7, 'uploadNM': 3, 'uploadPar': 5, 'downloadFile': 6, 'inactive': 1, 'downloadPar': 4, 'downloadNM': 2.

The name of the file to be transferred by this TFTP session.

The number of bytes in the file. Whichever side has the file being sent may report the file size here. Not supported value: -1

The number of bytes successfully transferred in this session. Not supported value: -1

Chassis objects

A table that describes the Chassis connected

Contains a description of a particular Chassis

The index of the Chassis.

The type of Chassis. Enumeration: 'virtual3': 15, 'bmc': 9, 'virtual1': 13, 'bu12': 21, 'virtual16': 10, 'bu2': 7, 'bu3': 6, 'bu16': 2, 'bu1': 4, 'bu3v': 19, 'bu4': 3, 'bu5': 5, 'virtual4': 16, 'fCpe': 8, 'other': 1, 'bu21': 11, 'bu82': 18, 'bu42': 12, 'bu22': 17, 'virtual2': 14, 'virtual3v': 20.

The model name of the chassis.

Object Id of chassis.

The number of slots in the Chassis.

The hardware revision of the chassis.

The status of Power Supply 1. Enumeration: 'acGood': 4, 'good': 7, 'dcBad': 3, 'notInstalled': 1, 'bad': 8, 'acBad': 2, 'dcGood': 5, 'notSupported': 6.

The status of Power Supply 2. Enumeration: 'acGood': 4, 'good': 7, 'dcBad': 3, 'notInstalled': 1, 'bad': 8, 'acBad': 2, 'dcGood': 5, 'notSupported': 6.

The status of Power Supply 3. Enumeration: 'acGood': 4, 'good': 7, 'dcBad': 3, 'notInstalled': 1, 'bad': 8, 'acBad': 2, 'dcGood': 5, 'notSupported': 6.

The status of Power Supply 4. Enumeration: 'acGood': 4, 'good': 7, 'dcBad': 3, 'notInstalled': 1, 'bad': 8, 'acBad': 2, 'dcGood': 5, 'notSupported': 6.

The status of Fan 1. Enumeration: 'bad': 2, 'notSupported': 1, 'notInstalled': 4, 'good': 3.

The status of Fan 2. Enumeration: 'bad': 2, 'notSupported': 1, 'notInstalled': 4, 'good': 3.

The status of Fan 3. Enumeration: 'bad': 2, 'notSupported': 1, 'notInstalled': 4, 'good': 3.

The status of Fan 4. Enumeration: 'bad': 2, 'notSupported': 1, 'notInstalled': 4, 'good': 3.

The temperature (degrees Celsius) of the Chassis. Not supported value: 0x80000000

The maximum safe temperature (degrees Celsius) of the Chassis. Not supported value: 0x80000000

The minimum safe temperature (degrees Celsius) of the Chassis. Not supported value: 0x80000000

The received signal strength.

The minimum recommended operational received signal strength.

Continuously monitor slots for module changes, and reset if new board installed. Deprecated. The response to any GET should be notSupported(1). Any SET attempt should be rejected with the SNMP error badValue(3). Enumeration: 'deprecatedon': 3, 'notSupported': 1, 'deprecatedoff': 2.

When set, send trap to report change in link status, up or down. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

When set, send trap to report chassis related events. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

When set, send trap to report change in loopback configuration. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

When set, send trap to report slot change related events. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

When set, send trap to report port change related events. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

Continuously monitor slots for module changes, and reset if new board installed. Deprecated. The response to any GET should be notSupported(1). Any SET attempt should be rejected with the SNMP error badValue(3). Enumeration: 'deprecatedReset': 3, 'notSupported': 1, 'deprecatedOperating': 2.

When set, send trap to report change in specific cards conditions Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

loopback timeout in minutes, zero indicates forever

Deprecated.

Deprecated.

Deprecated.

The user assigned name for this chassis

When off(2), suppresses any traps related to Link Integrity Notification. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

When off(2), suppresses any traps related to removable Ports being inserted or removed. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

When off(2), suppresses any traps related to SFP port diagnostics being outside of safe levels. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

The status of Fan 5. Enumeration: 'bad': 2, 'notSupported': 1, 'notInstalled': 4, 'good': 3.

The status of Fan 6. Enumeration: 'bad': 2, 'notSupported': 1, 'notInstalled': 4, 'good': 3.

The status of Fan 7. Enumeration: 'bad': 2, 'notSupported': 1, 'notInstalled': 4, 'good': 3.

The status of Fan 8. Enumeration: 'bad': 2, 'notSupported': 1, 'notInstalled': 4, 'good': 3.

When on, NM can send notifications whenever a self-healing card switches traffic from an active port to its redundant standby port. When off, NM will not send switchover notifications. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

For chassis housing cross-connect blades or slots, this object is used to reflect the operating state and to clear the entire cross-connect map, including any independent maps of subordinate slots. If there are currently no cross-connect blades or slots in this chassis, the Agent must report notSupported(1). Additionally, if this object reports notSupported(1), any SNMP SET to this object should return SNMP Error 3 (bad value). The Agent should report operating(2) under normal circumstances. If this object reports operating(2), SNMP Managers are allowed to set this object to clearing (3), which instructs the Agent to erase all this chassis' cross-connect maps, including any independent maps of subordinate slots. Enumeration: 'clearing': 3, 'notSupported': 1, 'operating': 2.

The maximum number of executable images that can be stored locally on this chassis. Not supported value: 0

This bitmask indicates which executable images this chassis can support. This object is mandatory for all chassis. Bit 0 is reserved. Subsequent bits refer to the nbsCmmcSysFirmwareTable. Bit 1 corresponds to the first table entry, Bit 2 to the second entry, and so on. A bit is set (1) if that image is appropriate for this chassis, cleared (0) otherwise. OCTET STRING bitmasks count the leftmost bit (MSB) as 0. A zero length OCTET STRING indicates that the nbsCmmcSysFirmwareTable is not supported by this agent.

This bitmask indicates which executable images this chassis has stored in its own NV area. This object is mandatory for all chassis. OCTET STRING bitmasks count the leftmost bit (MSB) as 0. Bit 0 indicates whether an executable image is loading. Subsequent bits refer to the nbsCmmcSysFirmwareTable. Bit 1 corresponds to the first table entry, Bit 2 to the second entry, and so on. A bit is set (1) if that image is stored on this chassis, cleared (0) if not. Clearing bits has no effect. To erase an NV area, use the nbsCmmcSysNVAreaTable. Users may transfer a file to an NV area by setting the appropriate file's bit and the loading (MSB) bit to one (1). Adding a file requires that the NM start a file transfer to this chassis, which is a lengthy operation. If a transfer session is already active (nbsCmmcChassisLoader is non-zero), writes to this object will be rejected. A zero length OCTET STRING indicates that the nbsCmmcSysFirmwareTable is not supported by this agent.

A SET on this object will force the corresponding nbsCmmcSysNvAreaStatus to primary, set this chassis' other memory banks to backup, and immediately load and execute the firmware image contained in the specified memory bank. A GET on this object will indicate the memory bank of this chassis that is currently designated as primary. Not supported value: -1

The nbsCmmcSysNVAreaBank of nbsCmmcSysNVAreaTable corresponding to the current operationally active firmware image. 0 indicates the current active image is NOT in the NVAreaTable. Not supported value: -1

The nbsCmmcSysLoaderIndex of nbsCmmcSysLoaderTable corresponding to the current loading session. 0 indicates no loading session is active.

SerialNumber of this chassis. If this object is not supported, this string should be empty.

ASCII string containing encoded summary of chassis front panel status. The encoding uses keywords and associated allowed values. Keyword:value pairs delimited by the pipe '|' symbol, and within a pair, a keyword should be separated from its associated value by a colon ':' character. Agent should provide the following info if available. If unknown, it should be omitted. Description Keyword Allowed Values --------------------------------------------------------- Protocol prot ether|slip Power Supply(X) psx [use nbsCmmcChassisPSxStatus] Temperature temp [use nbsCmmcChassisTemperature] Temperature Max tmax [use nbsCmmcChassisTemperatureLimit] Temperature Min tmin [use nbsCmmcChassisTemperatureMin] Type type [use nbsCmmcChassisType] RM/AH Peer Chas rmch [use nbsCmmcChassisIndex] An example string could be: |prot:ether|ps1:2|ps2:3|ps3:5|temp:20| If this object is not supported, this string should be empty.

This object allows user to reset MAC counters on all ports in this Chassis. Enumeration: 'clearing': 3, 'notSupported': 1, 'counting': 2.

The number of chassis currently plugged into the system.

Slot/Card/Blade objects

A table that describes the Slot connected

Contains a description of a particular Slot

The index of the Chassis to the Slot is connected.

The slot index.

The type of card in the slot. If the slot is empty and the chassis' color is black, this should be 0 or 1. If the slot is empty and the chassis' color is beige or gray, this should be 2. If a module is installed that the Agent does not support, this value should be 3. Values greater than 3 are used to indicate both the front panel and the functionality of the module.

Describes the model of card that is currently in the slot.

The description of the type of card in the slot.

Number of ports on the card.

This describes the hardware revision of the card

Operation of card.. Enumeration: 'optAmpPreampAGC': 23, 'repeater40G': 37, 'optAmpVariableGain': 29, 'fastRepeater': 7, 'optAmpBoosterAGC': 19, 'management': 2, 'monitor': 9, 'centralOffice': 13, 'splitterCombiner': 6, 'packetMux': 28, 'multiplexer4x10G': 38, 'deprecated16': 16, 'deprecated17': 17, 'physLayerSwitch': 27, 'deprecated18': 18, 'multiplexer': 15, 'optAmpBoosterAPC': 20, 'repeater': 4, 'multiCO1g': 32, 'addDropMux': 34, 'optAmpMidstageAGC': 30, 'coDualInactive': 26, 'optAmpMidstageAPC': 31, 'multiCO10g': 33, 'remote': 11, 'converter': 3, 'customerPremise': 14, 'optAttenuator': 36, 'optAmpInlineAPC': 22, 'optAmpInlineAGC': 21, 'coDualActive': 25, 'redundant': 12, 'switch': 5, 'multicast': 35, 'optAmpPreampAPC': 24, 'opticSwitch': 10, 'other': 1, 'gigabitRepeater': 8.

Current reset condition, and possible reset types. notSupported [1] - reported if feature unavailable. operating [2] - indicates normal operating status. phy [3] and queue [4] are deprecated. resetSlot [5] - cold restart, may impact traffic. initSlot [6] reverts to default settings; init-module. resetWarm [7] - soft restart, won't hurt traffic. The value operating [2] is normally returned by GET, but during a reset operation, the appropriate reset value [5, 6, or 7] may be returned. Enumeration: 'deprecatedQueue': 4, 'resetSlot': 5, 'initSlot': 6, 'operating': 2, 'notSupported': 1, 'deprecatedPhy': 3, 'resetWarm': 7.

The user assigned name for this slot.

Equivalent to nbsCmmcSlotType, except for modules that occupy more than one slot in a chassis. For such multi- slot modules, this ModuleType indicates the product this slot is a part of.

This indicates the position of this slot within its module. For one-slot modules this value is always one (1). For multi-slot modules, this is a positive integer between 1 and the number of slots spanned by this module. The numbering always begins with the leftmost slot as 1.

Indicates whether card is software configurable, usually based on hardware jumper/dip switch settings. If any changes to the hardware configuration are allowed, this value will be yes(3). If this is no(2), SNMP GETs will work but SETs will fail with an SNMP error. According to RFC 1157, that error should be noSuchName(2). Enumeration: 'yes': 3, 'other': 1, 'no': 2.

Bit stream containing current configuration of slot.

MAC Address of this card. If this object is not supported, this string should be empty.

For non-NM cards which feature independent IP stacks, this is the SNMP Agent Administrative value of the IP Address for the card in this slot.

For non-NM cards which feature independent IP stacks, this is the SNMP Agent Administrative value of the SubnetMask for the card in this slot.

For non-NM cards which feature independent IP stacks, this is the SNMP Agent Administrative value of the IP Broadcast Address for the card in this slot.

For non-NM cards which feature independent IP stacks, this is the SNMP Agent Administrative value of the Default Gateway for the card in this slot.

This object describes the cabling topology of CO / CPE pairs. It must be supported on the Customer Premises Equipment (CPE) slots. Any card that does not utilize this object should report notSupported(1). If one CO is redundantly cabled to one CPE, the pair is in singleCO(2) homing. If two separate CO cards are connected to the same CPE, the CPE is dually homed. Because neither CO has contact with the other CO, each CO should be told the CPE is in a dualCOs(3) homing configuration. If the card has a dual homing feature but does not know its current status, it defaults to singleCO(2). If that is incorrect, users should change the value to dualCOs(3) to inform the card of its network configuration. Enumeration: 'singleCO': 2, 'notSupported': 1, 'dualCOs': 3.

This object is used to disable redundancy on certain cards that support the 802.3ah standard, but if supported, the preferred method is to use the object nbsCmmcPortEnable to administratively disable redundant ports that shouldn't become active. This object may also be used to change the operating mode of 4 port crossbar cards that can be configured for redundancy. For cards that do not support this feature, any reads of this object should get the response notSupported (1). Writes to this object should be rejected with the SNMP error badValue (3). Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

Agent description of this slot.

This object indicates whether the card in this slot can now be reprogrammed. It should be used together with nbsCmmcSysUpgrade. Cards without reprogrammable firmware should always report notSupported (1). Reprogrammable cards should report supported(2) only if the NM has the appropriate firmware image already loaded and ready to send to the card. Enumeration: 'supported': 2, 'notSupported': 1.

For slots supporting cross-connect functionality, this object is used to reflect the operating state and clear the entire cross-connect map for this slot. If the slot is not of cross-connect type, the Agent must report notSupported(1). Additionally, if this object reports notSupported(1), any SNMP SET to this object should return SNMP Error 3 (bad value). The Agent should report operating(2) under normal circumstances. If this object reports operating(2), SNMP Managers are allowed to set this object to clearing (3), which instructs the Agent to erase the cross-connect map for this slot. Enumeration: 'clearing': 3, 'notSupported': 1, 'operating': 2.

When nbsCmmcSysLockTypes is enabled, use this object to clear the configured slot type. Issue a set command with a value of clearType(3). A read of this object will always return idle(2), or notSupported(1) if this feature is not supported. Enumeration: 'idle': 2, 'notSupported': 1, 'clearType': 3.

The maximum number of executable images that can be stored locally on this module. Not supported value: 0

This bitmask indicates which executable images this module can support. This object is mandatory for all modules. Bit 0 is reserved. Subsequent bits refer to the nbsCmmcSysFirmwareTable. Bit 1 corresponds to the first table entry, Bit 2 to the second entry, and so on. A bit is set (1) if that image is appropriate for this module, cleared (0) if unavailable. OCTET STRING bitmasks count the leftmost bit (MSB) as 0. A zero length OCTET STRING indicates that the nbsCmmcSysFirmwareTable is not supported by this agent.

This bitmask indicates which executable images this module has stored in its own NV area. This object is mandatory for all modules. OCTET STRING bitmasks count the leftmost bit (MSB) as 0. Bit 0 indicates whether an executable image is loading. Subsequent bits refer to the nbsCmmcSysFirmwareTable. Bit 1 corresponds to the first table entry, Bit 2 to the second entry, and so on. A bit is set (1) if that image is stored on this module, cleared (0) if not. Clearing bits has no effect. To erase an NV area, use the nbsCmmcSysNVAreaTable. Users may transfer a file to an NV area by setting the appropriate file's bit and the loading (MSB) bit to one (1). Adding a file requires that the NM start a file transfer to this module, which is a lengthy operation. If a transfer session is already active (nbsCmmcSlotLoader is non-zero), writes to this object will be rejected. A zero length OCTET STRING indicates that the nbsCmmcSysFirmwareTable is not supported by this agent.

A SET on this object will force the corresponding nbsCmmcSysNvAreaStatus to primary, set this module's other memory banks to backup, and immediately load and execute the firmware image contained in the specified memory bank. A GET on this object will indicate the memory bank of this module that is currently designated as primary. Not supported value: -1

The nbsCmmcSysNVAreaBank of nbsCmmcSysNVAreaTable corresponding to the current operationally active firmware image. 0 indicates the current active image is NOT in the NVAreaTable. Not supported value: -1

The nbsCmmcSysLoaderIndex of nbsCmmcSysLoaderTable corresponding to the current loading session. 0 indicates no loading session is active.

SerialNumber of this module. If this object is not supported, this string should be empty.

For crossbar products. Used to indicate the approximate rate, in microseconds, at which this card should toggle its transmitters on and off. Not supported value: 0

The temperature (in degrees celsius) of this slot. Not supported value: 0x80000000

This object allows user to reset MAC counters on all ports. Enumeration: 'clearing': 3, 'notSupported': 1, 'counting': 2.

This object reports the actual redundancy state of a card. For cards that do not support this feature, any reads of this object should get the response notSupported (1). Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

A table to report status of front panel LEDs

Indicates status of a particular LED

The index of the Chassis to the Slot is connected.

The slot index.

The index of the led. Index starts at 1.

Actual/current color of the LED. Enumeration: 'amber': 3, 'green': 2, 'other': 4, 'off': 1.

LED's label as on card and short description

A table that describes the front panel state of each slot

Contains a description of a particular Slot

The index of the Chassis housing this slot.

The slot index.

Row Number

ASCII string containing encoded summary of slot front panel status. The encoding uses keywords and associated allowed values. Keyword:value pairs delimited by the pipe '|' symbol, and within a pair, a keyword should be separated from its associated value by a colon ':' character. Agent should provide the following info if available. If unknown or inapplicable, it should be omitted. Description Keyword Allowed Values --------------------------------------------------------- Slot/SNMP Type slid [use nbsCmmcSlotType] LED ledx [use nbsCmmcLedColor] PortLink plnkx [use nbsCmmcPortLinked] PortOperational popx [use nbsCmmcPortOperational] PortSelectLink pselx actv|stdby PortConnector pconx [use nbsCmmcPortConnector] An example string could be: |slid:436|led1:2|plnk1:2|pop2:2|psel2:actv|pcon4:15| If this object is not supported, this string should be empty.

Port objects

A table that describes the Port connected

Contains a description of a particular Port.

The index of the Chassis for the Slot to which this port is connected.

The index of the Slot in the Chassis to which this port is connected.

The index of the Port in the Slot in the Chassis to which this port is connected.

The physical type of port. Valid port types are > 1.

Object Id of the port

The link status of the port. Enumeration: 'lock': 5, 'other': 1, 'link': 4, 'noSignal': 2, 'signalDetect': 3.

The AutoNegotiation status of a port. AutoNegotiation may affect the port's speed, duplex, and MDI/MDIX. If this port does not offer this feature, Agent should report the value notSupported(1). To disable this feature, set the value to off(2). To enable this feature, set the value to on(3). The value autoMDIXOnly(4) is deprecated. The value custom (5) is deprecated. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2, 'deprecated4': 4, 'deprecated5': 5.

The duplex mode of the port. Enumeration: 'notSupported': 1, 'full': 3, 'half': 2.

The line speed of the port. Enumeration: 'spd100Mbps': 3, 'spd10Gbps': 5, 'spd10Mbps': 2, 'other': 1, 'spdGigabit': 4.

The receive status of the port. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

The transmit status of the port. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

The collision status of the port. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

The loopback status of the port. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

Administratively desired operational status of the port. For the actual operational status, please see the related object nbsCmmcPortEnableOper. The value notSupported (1) indicates that the user has no ability to disable the transceiver. Users may set this value to disable (2) to turn off the port's transceiver so that no traffic will flow through this port. For traffic to be sent and received as normal, this object should be set to enable (3). The value auto (4) has been deprecated - older Agents might report it, and Managers may attempt to set it, but newer agents will neither report nor accept this value. Enumeration: 'deprecatedAuto': 4, 'enable': 3, 'notSupported': 1, 'disable': 2.

For ports in self-healing redundant groups, this object describes this port's redundant state. The value notSupported(1) indicates this object is unused for this port. The value standby(2) indicates that traffic is not currently routed through this port. The value active(3) indicates that this port is the selected channel for passing data traffic. This object may be used to choose which port in a redundant group is active. That selection may be overridden by the system as appropriate, such as the link going down, or a preferred port coming up. The values (4) through (6) are deprecated. They will no longer be reported by the Agent, and attempts to set them should be rejected with the SNMP error badValue(3). Enumeration: 'deprecatedStandbyPreferred': 5, 'standby': 2, 'deprecatedActivePreferred': 6, 'deprecatedAuto': 4, 'active': 3, 'notSupported': 1.

Line integrity check on or off. Enumeration: 'enable': 3, 'notSupported': 1, 'disable': 2.

Aging on or off. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

The Maximum Packet Size Allowed. Enumeration: 'max1536': 3, 'notSupported': 1, 'max1518': 2, 'max6k': 4.

Indicates whether port should perform Remote Loopback. When on (3), outbound traffic is returned to the ingress port. In other words, traffic comes from one of the module's other ports to get to this one, and upon arriving here gets sent back to that other port, from where it continues on back to the originator of the traffic. The related object nbsCmmcPortLoopback may be forced off(2) whenever this object is set to on(3). Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

The error activity of the port. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

The user assigned name for this port. This object is also used for the MIB2 object ifAlias.

Originally named nbsCmmcPortOpticalPower. Now usage may vary by card. For card 162, PortValue measures the Optical Power, or signal strength. For card 197, PortValue is a text string displaying signal strength in decibels. For cards 211 and 212, PortValue measures the current bandwidth level. Only one byte is used, and its value can be notSupported(1), under45Mbps(2), under155Mbps(3), under622Mbps(4), or under1Gbps(5)

Port Threshold - usage may be different for each card. For card 197, this indicates the minimum signal strength. Value ranges from -5 to -40 decibels. For card 211, valid values are: notSupported(1), speed45Mbps(2), speed155Mbps(3), speed622Mbps(4), speed1Gbps(5) For card 375, this indicates the rate limit and is expressed in units of Mbps. For cards 376 and 379, this indicates the rate limit and is expressed in units of Kbps. Not supported value: 0x80000000

Action to perform if threshold is crossed. Usage may be different for each card. For card 197, the allowable Actions are: notSupported(1), noAction(2), sendTrap(3) For cards 211 and 212, valid values are: notSupported(1), noAction(2), sendTrap(3), disablePort(4), disablePortAndSendTrap(5),disablePortPeriodically(6), disablePeriodicallyAndSendTrap(7) Not supported value: 1

This object indicates network topology. For ports with no remote peer, including ports on non-RM cards, this value is 0. For ports on Central Office RM cards [managed by a local NM Agent], this value will refer to a fictitious chassis for indexing remote [Customer Premise] RM cards. For ports on Customer Premise RM cards [managed by a remote peer], this value is the nbsCmmcPortChassisIndex of the host [Central Office] port.

This object indicates network topology. For ports with no remote peer, including ports on non-RM cards, this value is 0. For ports on Central Office RM cards [managed by a local NM Agent], this value is the nbsCmmcPortSlotIndex assigned to the remote [Customer Premise] card. For ports on Customer Premise RM cards [managed by a remote peer], this value is the nbsCmmcPortSlotIndex of the host [Central Office] port.

This object indicates network topology. For ports with no remote peer, including ports on non-RM cards, this value is 0. For ports on Central Office RM cards [managed by a local NM Agent], this value is the nbsCmmcPortIndex of the port on the remote [Customer Premise] card that hosts [is connected to] this port. For ports on Customer Premise RM cards [managed by a remote peer], this value is the nbsCmmcPortIndex of the host [Central Office] port.

Part Serial Number as reported by the component. Not supported value: 'N/A'

Vendor name as reported by the component. Not supported value: 'N/A'

The temperature (in degrees celsius) of this trans- ceiver. Not supported value: 0x80000000

The output power (in milli dBm) of this transmitter. Not supported value: 0x80000000

The received optical power (in milli dBm) of this receiver. Not supported value: 0x80000000

The bias current (in microAmps) of this transmitter. The reserved value -1 indicates that this object is not supported.

The supply voltage (in milliVolts) of this transmitter. The reserved value -1 indicates that this object is not supported.

The type of physical communications medium. Enumeration: 'twistedPair': 3, 'notSupported': 1, 'coax': 2, 'multiMode': 5, 'singleMode': 4.

The type of physical connector or jack. Enumeration: 'cxp': 32, 'foPigtail': 19, 'mpo': 30, 'foMtRj': 16, 'coax2BNC': 9, 'cuRj11': 11, 'coaxF': 7, 'cuRj45': 5, 'unknown': 1, 'cuRj48': 24, 'miniCoax': 29, 'cuPigtail': 20, 'foDSC': 3, 'sataHostPlug': 28, 'fo1LC': 25, 'smb': 21, 'foM': 17, 'coaxBNC': 8, 'cuHssdc': 13, 'miniSAS4x': 31, 'cuRj45wLEDs': 10, 'cuDb9': 12, 'foSC': 4, 'sataDevicePlug': 27, 'foLC': 6, 'foFiberJack': 15, 'removed': 2, 'firewireA': 22, 'firewireB': 23, 'fo2ST': 26, 'sg': 18, 'coaxHeader': 14.

The output wavelength (in nanoMeters) of this transmitter. The reserved value -1 indicates that this object is not supported. This object has been superseded by nbsCmmcPortWavelengthX, which supports floating point wavelengths, and lists of wavelengths.

Indicates whether Digital Diagnostics are supported by this port. If they are supported, this variable indicates the worst severity level among the measured diagnostic values. Enumeration: 'diagsAlarm': 4, 'notSupported': 1, 'diagsWarning': 3, 'diagsOk': 2.

For Fibre Channel products, this will be the Agent-assigned ZoneId of the zone this port belongs to. For products which allow dynamic configuration of converter circuits, this will be the Port number where data for this converter circuit will be received. If the chassis or slot is changing, they should be SET first, so ZoneIdAdmin is SET last. This signals the Agent to reconfigure the crossbar. The value 0 indicates that this port is not a part of any Fibre Channel Zone or converter circuit. In order for two ports to be in the same zone/circuit, each must be configured to the same PortSpeed or BitRate. If the Agent receives a request to set CircuitRxPort to a port with a different bit rate, the Agent will return SNMP error-status badValue (3).

This NominalBitRate variable exists for modules which support configurable speeds that may not be listed in PortSpeed. Here can be specified the raw bit rate desired, measured in decimal Mbps. The Agent may use exactly that rate, or may substitute it with a compatible rate within an appropriate range of speeds. If the Agent receives a request for a bitrate it cannot support, it should return the SNMP errorstatus badValue(3). For ports whose speed is unknown or not configurable, the Agent should report this value as -1. The reserved value 0 specifies that no speed is configured, and any clocking is bypassed. The following values are associated with specific protocols: 44 - DS3 51 - OC-1 77 - Telco bus 125 - Fast Ethernet (100 Mbps) 126 - FDDI 155 - OC-3 200 - ESCON 270 - SDI 270Mbps 540 - SDI 540Mbps 622 - OC-12 1063 - 1 Gig FibreChannel 1244 - OC-24 1250 - Gigabit Ethernet 1485 - HDTV 2125 - 2 Gig FibreChannel 2450 - OC-48 2500 - Infiniband 2666 - OC-48+FEC 9953 - 10 Gig Ethernet/WAN 10312 - 10 Gig Ethernet/LAN 10625 - 10 Gig FibreChannel For ports that support ProtoAdmin 'userDefined', writing this object will automatically set the ProtoAdmin to 'userDefined'.

Similar to SlotModuleSlot. Some modules occupy more than one slot of a chassis. For such products, this variable will report the port number from the Module perspective. In contrast, the PortIndex reports the port number from an individual slot's perspective. For modules that occupy only one slot, PortModulePort will be equivalent to PortIndex.

Part Number and Revision level as reported by the component. Not supported value: 'N/A'

The index to the MIB-II Interface table entry which represents this port. If there is no corresponding MIB-II interface entry, this value should be 0.

Simpler, one bit version of PortLink. The value no(1) means there is no signal detected or that signal is of poor quality. The value yes(2) indicates a good connection. Enumeration: 'yes': 2, 'no': 1.

Indicates whether the port is in a state appropriate for normal data communications. The value no(1) means that the port is disabled or in an abnormal state such as loopback. The value yes(2) indicates that the port is enabled and usable. Enumeration: 'yes': 2, 'no': 1.

For crossbar products, this is the Chassis housing the port shown in nbsCmmcPortZoneId.

For crossbar products, this is the Slot housing the port shown in nbsCmmcPortZoneId.

For Pluggable ports with Digital Diagnostics. If there is currently no alarm condition, this string should be empty. Otherwise, this should display the most severe actual alarm condition.

This object determines whether FlowControl should be used. If disabled(2), no FlowControl will be initiated by this port. Any FlowControl requests received will be dropped. If enabled(3), this port will initiate and observe FlowControl requests as specified by the objects nbsCmmcPortFCRecvOper and nbsCmmcPortFCSendOper. Those settings may be changed through the related nbsCmmcPortFCSendAdmin and nbsCmmcPortFCRecvAdmin objects. If notSupported(1), this object is not supported. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

This object determines which capabilities will be advertised during auto negotiation. Each capability is represented by one bit. Set bit to 1 to advertise capability, 0 to deny it. Capability Bit ---------------------- --- reserved 0 Flow Control 1 1000 Mbps Full Duplex 2 1000 Mbps Half Duplex 3 100 Mbps Full Duplex 4 100 Mbps Half Duplex 5 10 Mbps Full Duplex 6 10 Mbps Half Duplex 7 OCTET STRING bitmasks count the leftmost bit (MSB) as 0.

This object determines which AutoNegAd bits may be changed by the user. Bits set to 1 indicate user may choose whether to advertise the corresponding capability. Bits are cleared if user is not allowed to change the corresponding AutoNegAd bit. Capability Bit ---------------------- --- reserved 0 Flow Control 1 1000 Mbps Full Duplex 2 1000 Mbps Half Duplex 3 100 Mbps Full Duplex 4 100 Mbps Half Duplex 5 10 Mbps Full Duplex 6 10 Mbps Half Duplex 7 OCTET STRING bitmasks count the leftmost bit (MSB) as 0.

This objects supersedes the nbsCmmcPortWavelength object. The string format allows both whole numbers as in CWDM, or floating-point numbers as in DWDM. If there is more than one wavelength, as with WDM trunks, each color should be listed, separated by commas. Not supported value: 'N/A'

Operational version of nbsCmmcPortZoneIdAdmin

Operational version of nbsCmmcPortZoneSlotAdmin

Operational version of nbsCmmcPortZoneChassisAdmin

Some converter ports that are capable of autonegotiation (ANEG) may sometimes be between two end ports that would like to autonegotiate with each other. The Agent can ensure that both ports in the converter/circuit settle on the same autonegotiated settings. This feature is called LinkMatch. ANEG with LinkMatch can sometimes be a lengthy process. In order to streamline the ANEG process, users may manually configure the parameters that supporting ports will advertise during their independent autonegotiations. This involves two steps - first to change the nbsCmmcPortAutoNegAd object to reflect the outcome desired, then to set this nbsCmmcPortLinkMatch object to the value disabled(2). The default value for this object is enabled(3). Ports that do not support this feature should return the value notSupported(1). Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

Connecting twisted-pair ethernet ports originally required care in choosing either straight or crossover cables. Later, many ethernet ports added the feature that they could be configured to accept either cable pinout. Some ports are even smart enough to detect, or autosense, the pinout they should use. This Administrative object allows users to request the port adopt a specific pinout, or to have the port autosense it. The value notSupported(1) indicates that this port cannot dynamically alter its pinout through this object. The value mdi(2) is used to connect with a straight cable to mdix ports such as those found on hubs, switches and routers. The value mdix(3) is used to connect with a straight cable to mdi ports such as those found on workstations. The value autoSense(4) indicates this port should automatically detect and change to the necessary pinout. This object has a corresponding Operational value which reports the actual pinout state. In certain situations, the Operational value might differ from the Administrative. Enumeration: 'autoSense': 4, 'mdix': 3, 'notSupported': 1, 'mdi': 2.

This object reports the actual pinout state of an ethernet port. Enumeration: 'mdix': 3, 'notSupported': 1, 'mdi': 2.

This object allows user to specify what this port should do if it receives a flow control request. This object is ignored when nbsCmmcPortFlowControl is disabled. If this object reports notSupported(1), no changes to this object are allowed. Setting this object to drop(2) indicates that this port should ignore requests to control its flow. Setting this object to comply(3) means this port should grant flow control requests from the connected port, and buffer up traffic while the other side catches up. If this object is set to passthru(4), the port will not comply with the request, but will relay it along to the next port. The corresponding nbsCmmcPortFCRecvOper object indicates the setting that is actually in effect. Enumeration: 'passThr': 4, 'drop': 2, 'notSupported': 1, 'comply': 3.

This object indicates what this port will do with flow control requests it receives. Enumeration: 'passThr': 4, 'drop': 2, 'notSupported': 1, 'comply': 3.

This object specifies whether this port will send flow control requests when its in danger of dropping incoming packets. This object is ignored when nbsCmmcPortFlowControl is disabled. Setting this object to enabled(3) means this port may send flow control requests to the other port. Setting this object to disabled(2) indicates that this port should drop packets instead of sending flow control requests. If this object is set to notSupported(1), this object cannot be changed for this port. The corresponding nbsCmmcPortFCSendOper object indicates the setting that is actually in effect. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

This object is ignored when nbsCmmcPortFlowControl is disabled. This object indicates whether or not this port will send flow control requests. If it does, the value enabled(3) will be returned. If it does not, it reports disabled(2). If this object is not supported, device reports notSupported(1). Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

Sets the number of seconds a port should autonegotiate [ANEG] before deciding a link is down. This object is used by the NM when LIN and ANEG are both enabled. If the user knows that a particular end device needs extra time to complete autonegotiation, he should change this object to match the end device's needs. Not supported value: 0

This object indicates whether this port has a temperature problem. If this port does not support SFF-8472 Digital Diagnostics, this value should be notSupported(1). If Digital Diagnostics indicate temperature is below the low Alarm Threshold, this value should be lowAlarm(2). If Digital Diagnostics indicate temperature is above the low Alarm Threshold but below the low Warning threshold, this value should be lowWarning(3). If Digital Diagnostics indicate this port is within the recommended operating range, value is ok(4). If Digital Diagnostics indicate temperature is higher than the high Warning threshold, but has not crossed the Alarm threshold, this value should be highWarning (5),. If Digital Diagnostics indicate this port has crossed the high Alarm threshold, this value should be highAlarm(6). The related object nbsCmmcPortTemperature indicates what the current temperature is. Enumeration: 'lowWarning': 3, 'highAlarm': 6, 'ok': 4, 'highWarning': 5, 'lowAlarm': 2, 'notSupported': 1.

This object indicates whether this port has a problem with its transmitter power. If this port does not support SFF-8472 Digital Diagnostics, this value should be notSupported(1). If Digital Diagnostics indicate TxPower is below the low Alarm Threshold, this value should be lowAlarm(2). If Digital Diagnostics indicate TxPower is above the low Alarm Threshold but below the low Warning threshold, this value should be lowWarning(3). If Digital Diagnostics indicate this port is within the recommended operating range, value is ok(4). If Digital Diagnostics indicate TxPower is higher than the high Warning threshold, but has not crossed the Alarm threshold, this value should be highWarning (5),. If Digital Diagnostics indicate this port has crossed the high Alarm threshold, this value should be highAlarm(6). The related object nbsCmmcPortTxPower indicates what the current TxPower is. Enumeration: 'lowWarning': 3, 'highAlarm': 6, 'ok': 4, 'highWarning': 5, 'lowAlarm': 2, 'notSupported': 1.

This object indicates whether this port has a problem with the power of its received signal. If this port does not support SFF-8472 Digital Diagnostics, this value should be notSupported(1). If Digital Diagnostics indicate RxPower is below the low Alarm Threshold, this value should be lowAlarm(2). If Digital Diagnostics indicate RxPower is above the low Alarm Threshold but below the low Warning threshold, this value should be lowWarning(3). If Digital Diagnostics indicate this port is within the recommended operating range, value is ok(4). If Digital Diagnostics indicate RxPower is higher than the high Warning threshold, but has not crossed the Alarm threshold, this value should be highWarning (5),. If Digital Diagnostics indicate this port has crossed the high Alarm threshold, this value should be highAlarm(6). The related object nbsCmmcPortRxPower indicates what the current RxPower is. Enumeration: 'lowWarning': 3, 'highAlarm': 6, 'ok': 4, 'highWarning': 5, 'lowAlarm': 2, 'notSupported': 1.

This object indicates whether this port has a problem with the electric current going through the port. If this port does not support SFF-8472 Digital Diagnostics, this value should be notSupported(1). If Digital Diagnostics indicate BiasAmps is below the low Alarm Threshold, this value should be lowAlarm(2). If Digital Diagnostics indicate BiasAmps is above the low Alarm Threshold but below the low Warning threshold, this value should be lowWarning(3). If Digital Diagnostics indicate this port is within the recommended operating range, value is ok(4). If Digital Diagnostics indicate BiasAmps is higher than the high Warning threshold, but has not crossed the Alarm threshold, this value should be highWarning (5),. If Digital Diagnostics indicate this port has crossed the high Alarm threshold, this value should be highAlarm(6). The related object nbsCmmcPortBiasAmps indicates what the current amperage is. Enumeration: 'lowWarning': 3, 'highAlarm': 6, 'ok': 4, 'highWarning': 5, 'lowAlarm': 2, 'notSupported': 1.

This object indicates whether this port has a problem with the electric voltage across the port. If this port does not support SFF-8472 Digital Diagnostics, this value should be notSupported(1). If Digital Diagnostics indicate SupplyVolts is below the low Alarm Threshold, this value should be lowAlarm(2). If Digital Diagnostics indicate SupplyVolts is above the low Alarm Threshold but below the low Warning threshold, this value should be lowWarning(3). If Digital Diagnostics indicate this port is within the recommended operating range, value is ok(4). If Digital Diagnostics indicate SupplyVolts is higher than the high Warning threshold, but has not crossed the Alarm threshold, this value should be highWarning (5),. If Digital Diagnostics indicate this port has crossed the high Alarm threshold, this value should be highAlarm(6). The related object nbsCmmcPortSupplyVolts indicates what the current supply voltage is. Enumeration: 'lowWarning': 3, 'highAlarm': 6, 'ok': 4, 'highWarning': 5, 'lowAlarm': 2, 'notSupported': 1.

The current actual operational gain (in milli dB) of an optical amplifier. For nbsCmmcSlotType 503, this object only applies to AGC mode. The reserved value -1 indicates that this object is not supported.

The user configured administrative gain (in milli dB) of an optical amplifier. For nbsCmmcSlotType 503, this object only applies to AGC mode. The reserved value -1 indicates that this object is not supported.

The user configured desired output power (in milli dBm) of an optical amplifier. For nbsCmmcSlotType 503, this object only applies to APC mode. Not supported value: 0x80000000

This bitmask indicates which protocols this port can support. This object is mandatory for all ports in systems where the nbsCmmcSysProtoTable is supported. Bit 0 is reserved. Subsequent bits refer to the nbsCmmcSysProtoTable. Bit 1 corresponds to the first table entry, Bit 2 to the second entry, and so on. A bit is set (1) if that protocol is available for this port, cleared (0) if unavailable. Bit 1 always indicates 'custom' aka 'userDefined' is supported. Bit 2 always indicates 'bypass' aka 'transparent' is supported. OCTET STRING bitmasks count the leftmost bit (MSB) as 0. A zero length OCTET STRING indicates that this object is not supported.

The nbsCmmcSysProtoIndex of nbsCmmcSysProtoTable corresponding to the administratively desired family and rate of this port's protocol. The value 0 is reserved for 'notSupported' The value 1 is reserved for 'custom' aka 'userDefined'. If a PortNominalBitRate set is received, PortProtoAdmin will automatically change to 1. The value 2 is reserved for 'bypass' aka 'transparent'. Not supported value: 0

The nbsCmmcSysProtoIndex of nbsCmmcSysProtoTable corresponding to the current operational family and rate of this port's protocol. The value 1 is reserved for 'custom' aka 'userDefined'. If a PortNominalBitRate set is received, PortProtoAdmin will automatically change to 1. The value 2 is reserved for 'bypass' aka 'transparent'. Not supported value: 0

Defines the length of the transmitted ethernet preamble for every frame on this port. The value standard(2) indicates the standard 8 byte ethernet preamble should always be sent. The value variable(3) indicates longer preambles may be sent. The value notSupported(1) indicates preamble length is not configurable or not applicable for this port. Enumeration: 'variable': 3, 'notSupported': 1, 'standard': 2.

Among a group of ports this object per port says whether this ports is preferred or not. A preferred port in a redundant group (usually a pair of ports) will always be the active link if it has link, regardless of the link state of other ports in its group. Only one port in a redundant group may be preferred. If other ports in the same redundant group are already designated yes(1), the system should automatically set them to no(2). When a port is selected as preferred port, its redundant group is assumed to be in revertive mode. When no port is selected as preferred port, its redundant group is assumed to be in non-revertive (a.k.a. sticky) mode. Once selected, a port's actual active state be read via the SelectLink object. Use caution in designating Preferred ports, because on flaky/intermittent lines, this may result in excessive failovers. If read as notSupported(1), this port either does not belong to a redundant group, or its redundant group is always in non-revertive (a.k.a. sticky) mode. Enumeration: 'yes': 3, 'notSupported': 1, 'no': 2.

This object is used to specify the expected maximum cable length for copper DSX ports such as T1, E1, and T3. If a port does not use this feature, this object should be notSupported (1). T-carrier ports should specify a max cable length between 0 to 655 feet using values len133 (2) through len655 (6). E-carrier ports should use either the value shortHaul (7) or longHaul (8). Enumeration: 'len655': 6, 'len133': 2, 'len266': 3, 'shortHaul': 7, 'len399': 4, 'len533': 5, 'notSupported': 1, 'longHaul': 8.

This object determines whether or not a redundant port's transmitter should be shut down when that port is on standby. If both redundant ports are connected (via a Y cable) to the same remote port, use the setting oneColonOne (2). This 1:1 configuration will turn off the standby transmitter so it will not interfere with the active port. If each redundant port is connected to its own remote port, use the setting onePlusOne(3). 1+1 leaves both transmitters on, so the remote site can read its link status. Any changes to this object are automatically applied to this port's redundant pair. Enumeration: 'onePlusOne': 3, 'notSupported': 1, 'oneColonOne': 2.

Administrative setting for the line termination impedance of the port. The value disable (2) indicates that the line is to be terminated elsewhere. Enumeration: 'ohm100': 4, 'notSupported': 1, 'ohm75': 5, 'disable': 2, 'ohm120': 3.

A functional description of this port. May include port's role in the module, connector type, and other relevant info.

This object is for crossbar products. It allows the user to choose whether this port's transmitter should be enabled or disabled when this port is not mapped to another crossbar port. Setting the value disabled(2) will cause the transmitter to be disabled while the port is unmapped. Setting the value enabled(3) will cause this port to transmit even if unmappped, unless this entire port is disabled via the nbsCmmcPortEnable object. The agent will report this object as notSupported(1) if the feature is unavailable for this port. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

This object allows to the user to toggle the transmitter of this port. The value enabled(3) causes the transmitter to blink on and off at the rate specified in nbsCmmcSlotToggleRate. The value disabled(2) disables the toggle feature. The value notSupported(1) indicates that this port does not support the toggle feature. Enumeration: 'disabled': 2, 'notSupported': 1, 'enabled': 3.

For ports supporting cross-connect functionality, this object is used to reflect the operating state and clear this port from all cross-connect maps. If the port is not of cross-connect type, the Agent must report notSupported(1). Additionally, if this object reports notSupported(1), any SNMP SET to this object should return SNMP Error 3 (bad value). The Agent should report operating(2) under normal circumstances. If this object reports operating(2), SNMP Managers are allowed to set this object to clearing (3), which instructs the Agent to erase the cross-connect map for this port. Enumeration: 'clearing': 3, 'notSupported': 1, 'operating': 2.

Mib2 ifIndex of desired crossbar partner. Zero (0) indicates this port should be unmapped.

Mib2 ifIndex of actual crossbar partner. Zero (0) indicates this port is currently unmapped.

Actual current operational status of the port. This object is related to the nbsCmmcPortEnable object, where users specify the administrative operational status desired. The value notSupported (1) indicates that the port has no ability to disable the transceiver. The value disable (2) indicates that this port's transceiver is not allowing traffic to flow through this port. The value enable (3) indicates that this port's transceiver allows traffic flow. Enumeration: 'enable': 3, 'notSupported': 1, 'disable': 2.

Administrative crossbar mapping restrictions for this port. Non-crossbar ports must be reported as notSupported(1). If notSupported, any SET attempts will be rejected. Users may not set this object to notSupported(1). Users may mark the port as unavailable(2). If unavailable, the Agent will reject any attempts to map from or to this port. By default, each crossbar port is open(3). Open ports have no mapping restrictions. Ports that are set to source(4) may be used as the input (nbsCmmcPortZoneIfIndexAdmin) port by any other crossbar port. Their own input port may only be mapped to ports whose nbsCmmcPortMappingType is sourceHelper(6). Ports that are set to destination(5) may set their own input (nbsCmmcPortZoneIfIndexAdmin) port to any other crossbar port. They may not be used as the input port for other ports. A sourceHelper(6) port is used to provide whatever sort of link indication is needed by external traffic sources that are connected to a source(4) port. Ports set to interChasLink(7) are physically cabled to another crossbar port in a separate chassis. That connection should be entered by the user in the network topology objects nbsCmmcPortRMChassis, nbsCmmcPortRMSlot, and nbsCmmcPortRMPort for both those connected ports. Enumeration: 'unavailable': 2, 'interChasLink': 7, 'destination': 5, 'source': 4, 'sourceHelper': 6, 'notSupported': 1, 'open': 3.

This object allows user to reset MAC counters for this port. Enumeration: 'clearing': 3, 'notSupported': 1, 'counting': 2.

This object indicates (in millidecibels) the smallest gain user can set.

This object indicates (in millidecibels) the largest gain user can set.

Resolution (in millidecibels) of amplifier. Indicates the increment between amplifier gain settings.

Sniffing on or off. Enumeration: 'on': 3, 'notSupported': 1, 'off': 2.

NTP objects

SMTP objects

This entry contains the device's domain name. For example myDomain.com. It is used to identify the sender's domain.

Entry containing SMTP server's IP address.

Event severity level threshold for this SMTP receiver. If the event severity level is at least nbsCmmcSmtpRcvrLevel. the SNMP agent will generate an e-mail to this SMTP receiver.

Maximum number of SMTP receivers in nbsCmmcSmtpRcvrTable.

A list of SMTP receivers entries.

Entry containing SMTP information for a particular receiver entry.

The Email Recipient Index

Entry containing SMTP receiver's domain name (email address). The default is the device's domain name, if set.

To add a new entry to the nbsCmmcSmtpRcvrTable, set this object to valid(2) for an IP address which is not already in the table. To remove an entry from the table, set this object to invalid(1). Enumeration: 'valid': 2, 'invalid': 1.

SysLog objects

Indicates the level at which the system log message handler saves to a running message log. The level disabled(1) instructs the Agent to log nothing. This level may not be supported in some Agent versions. The level fatal(2) instructs Agent to log only events such as unplanned system shutdowns. The level error(3) includes fatal(2) events and events such as module failures. The level alarm(7) includes fatal(2), error(3), and other events that probably require immediate attention. The level warning(4) includes fatal(2), error(3), alarm(7), as well as events that probably need attention. The level info(5) includes all higher severities, plus events that indicate interesting but not necessarily problematic conditions. The level memo(6) includes all event notifications. Enumeration: 'info': 5, 'memo': 6, 'disabled': 1, 'warning': 4, 'error': 3, 'fatal': 2, 'alarm': 7.

Indicates the level at which the system log message handler saves in a non-volatile media(NVRAM,FLASH,etc.). For descriptions of each level, please see the DESCRIPTION for nbsCmmcSysLogRunningLevel. Enumeration: 'info': 5, 'memo': 6, 'disabled': 1, 'warning': 4, 'error': 3, 'fatal': 2, 'alarm': 7.

Indicates the level at which the system log message handler should generate a trap or SNMP notification. For descriptions of each level, please see the DESCRIPTION for nbsCmmcSysLogRunningLevel. Enumeration: 'alarm': 7, 'error': 3, 'disabled': 1, 'warning': 4, 'deprecated6': 6, 'deprecated5': 5, 'fatal': 2.

Indicates the level at which the system log message handler should generate an email message. For descriptions of each level, please see the DESCRIPTION for nbsCmmcSysLogRunningLevel. Enumeration: 'notSupported': 8, 'alarm': 7, 'error': 3, 'disabled': 1, 'warning': 4, 'deprecated6': 6, 'deprecated5': 5, 'fatal': 2.

This table defines a severity level for each type of message/event generated by the system.

A system log message control table entry.

System log message type. Enumeration: 'snmp': 2, 'dot1dBridge': 4, 'sysAuthentic': 5, 'sysReset': 1, 'physTraps': 3.

System log message severity. Enumeration: 'emergencies': 1000, 'debugging': 10000, 'errors': 100, 'informational': 1, 'warnings': 10.

Total number of messages in Running log table.

A table that describes the logged messages

Contains a description of a particular message entry

The index of the message entry.

The importance of this event.

Error code of the message.

Module Id of session causing the event.

Time of occurrence of the event.

The name of the module causing the event.

The actual event message.

Total number of messages in Nvram log table.

A table that describes the logged messages

Contains a description of a particular message entry

The index of the message entry.

Severity of the error.

Error code of the message.

Module Id of session causing the error.

Value of MIB-II sysUpTime (RFC 1213) at the time the error occurred. Note that sysUpTime resets to zero each time the agent is restarted.

The name of the module causing the error.

The actual error message.

The nbsCmmcSysCurrentTime at the moment this entry was made. This timestamp is derived from the Time Protocol (RFC 868), so it is independent of the system's UpTime. If the agent is unable to obtain the current time from a Time Protocol server, this value is 0. Not supported value: 0

The nbsCmmcSysCurrentDateTime at the moment this entry was made. This timestamp is derived from nbsCmmcSysNvramLogMessagePTime, so it is independent of the system's UpTime.

The number of entries in the audit log.

User activity log.

Contains a description of a particular message entry

The index of the message entry.

Value of MIB-II sysUpTime (RFC 1213) at the time the error occurred. Note that sysUpTime resets to zero each time the agent is restarted.

The nbsCmmcSysCurrentDateTime at the moment this entry was made. This timestamp is independent of the system's UpTime.

Log entry. Usually username:login or username:logout

The IP address that rsyslog messages should be sent to.

Indicates the level at which the system log message handler sends to remote syslog server. Enumeration: 'info': 8, 'notice': 7, 'alert': 3, 'disabled': 1, 'debug': 9, 'emerg': 2, 'error': 5, 'crit': 4, 'warning': 6.

This object is used to erase all entries from the Agent's internal Running Log. If the Agent does not support this feature, it must return the value notSupported(1), and any SNMP SET to this object should get an SNMP error badValue(3) in response. If this object is supported, the Agent normally should report the value operating(2). If it is actually deleting the log, it may report the value clearing(3). SNMP Managers may set this object to clearing(3), which indicates to the Agent that the log should be emptied. Enumeration: 'clearing': 3, 'notSupported': 1, 'operating': 2.

This object is used to erase all entries from the Agent's internal NVRAM (Persistent Memory) Log. If the Agent does not support this feature, it must return the value notSupported(1), and any SNMP SET to this object should get an SNMP error badValue(3) in response. If this object is supported, the Agent normally should report the value operating(2). If it is actually deleting the log, it may report the value clearing(3). SNMP Managers may set this object to clearing(3), which indicates to the Agent that the log should be emptied. Enumeration: 'clearing': 3, 'notSupported': 1, 'operating': 2.

This object is used to erase all entries from the Agent's internal Audit Log. If the Agent does not support this feature, it must return the value notSupported(1), and any SNMP SET to this object should get an SNMP error badValue(3) in response. If this object is supported, the Agent normally should report the value operating(2). If it is actually deleting the log, it may report the value clearing(3). SNMP Managers may set this object to clearing(3), which indicates to the Agent that the log should be emptied. Enumeration: 'clearing': 3, 'notSupported': 1, 'operating': 2.

How large the Nvram log is allowed to be (in kilobytes).

Trap objects

The last message sent by the system

ID of the power supply

ID of the fan

Index of the Port

Name of the Port

The reason for the last system shutdown

Brief explanation of the cause or nature of errors that triggered an nbsCmmcTrapPortErrorsDetected trap.

SNMP Traps

SNMP Traps

The last message sent by the system.

********* DEPRECATED ********** As of Agent version 4.14, this trap will not be sent.

Sent after device boots up. The cause of the last shutdown is indicated in nbsCmmcTrapShutdownReason. This Notification should be of Severity FATAL.

Sent when device detects restoration of network communications. This Notification should be of Severity WARNING.

Sent just before device shuts itself down. Reason for shutdown is indicated in nbsCmmcTrapShutdownReason. This Notification should be of Severity FATAL.

Unique trap for power supply failure events. This Notification should be of Severity ERROR.

Sent when power supply starts working again. This Notification should be of Severity ERROR.

Unique trap for fan failure events. This Notification should be of Severity WARNING.

Sent when fan starts working again. This Notification should be of Severity WARNING.

Sent when temperature rises above hottest permissible temperature. This Notification should be of Severity ERROR.

Sent when temperature falls under coldest permissible temperature. This Notification should be of Severity ERROR.

Sent when temperature returns to permissible range. This Notification should be of Severity ERROR.

Sent when card is physically inserted. This Notification should be of Severity ERROR.

Sent when card is physically removed. This Notification should be of Severity ERROR.

Sent after nbsCmmcPortEnableOper changes to enable(3). This Notification should be of Severity WARNING.

Sent after nbsCmmcPortEnableOper changes to disable(2). This Notification should be of Severity WARNING.

Sent when nbsCmmcPortLink transitions from noSignal(2) to a connected state. This Notification should be of Severity ERROR.

Sent when nbsCmmcPortLink transitions from a connected state to noSignal(2). This Notification should be of Severity ERROR.

Sent when Link Integrity Notification is turned on. This Notification should be of Severity WARNING.

Sent when Link Integrity Notification is turned off. This Notification should be of Severity WARNING.

Sent when Port is set to a Loopback state. This Notification should be of Severity WARNING.

Sent when Port returns from a Loopback state. This Notification should be of Severity WARNING.

Sent when PortValue exceeds PortThreshold. This Notification should be of Severity WARNING.

Sent when a hot-swappable port is removed. This Notification should be of Severity WARNING.

Sent when a hot-swappable port is inserted. This Notification should be of Severity WARNING.

Sent when transmitter temperature is too cold. For SFF Digital Diagnostics, this corresponds to the low temperature alarm. This Notification should be of Severity ERROR.

Sent when transmitter temperature is too hot. For SFF Digital Diagnostics, this corresponds to the high temperature alarm. This Notification should be of Severity ERROR.

Sent when received signal is too weak. For SFF Digital Diagnostics, this corresponds to the low RX power alarm. This Notification should be of Severity ERROR.

Sent when received signal is too powerful. For SFF Digital Diagnostics, this corresponds to the high RX power alarm. This Notification should be of Severity ERROR.

Sent when transmitter power is too weak. For SFF Digital Diagnostics, this corresponds to the low TX power alarm. This Notification should be of Severity ERROR.

Sent when transmitter power is too strong. For SFF Digital Diagnostics, this corresponds to the high TX power alarm. This Notification should be of Severity ERROR.

Sent when bias current is too small. For SFF Digital Diagnostics, this corresponds to the low bias current alarm. This Notification should be of Severity ERROR.

Sent when bias current is too large. For SFF Digital Diagnostics, this corresponds to the high bias current alarm. This Notification should be of Severity ERROR.

Sent when transceiver supply voltage is too low. For SFF Digital Diagnostics, this corresponds to the low supply voltage alarm. This Notification should be of Severity ERROR.

Sent when transceiver supply voltage is too high. For SFF Digital Diagnostics, this corresponds to the high supply voltage alarm. This Notification should be of Severity ERROR.

Sent when a self-healing (redundant ports) card switches traffic from an active port to a standby port. This Notification should be of Severity WARNING. The VARIABLE TrapLastMessage should specify the cause of the switchover, the PortName of the new Active port, and the PortName of the new Standby (formerely Active) port. The ChassisIndex and SlotIndex indicate the card that performed the switchover. The first PortIndex is the new Active port. The last PortIndex is the new Standby port. This trap should be accompanied by link up/down traps.

Sent when the slot/card is shutting down. This Notification should be of Severity WARNING if the shutdown is deliberate, or ERROR if shutdown because of module failure, i.e. last gasp. The VARIABLE nbsCmmcTrapShutdownReason should specify the reason the card is shutting down. To enable/disable this notification, use the object nbsCmmcChassisEnableModuleSpecificTraps.

Sent when CRC Error is received on this port. This Notification should be of Severity WARNING.

Sent when a module configured for customer premises is detected in a managed (central office) chassis. This Notification should be of Severity WARNING. To enable/disable this notification, use the object nbsCmmcChassisEnableModuleSpecificTraps.

Sent when a central office module has no link to a CPE module. This Notification should be of Severity WARNING. To enable/disable this notification, use the object nbsCmmcChassisEnableModuleSpecificTraps.

Sent when a central office module begins active management of a dual-homed CPE module. This Notification should be of Severity WARNING. To enable/disable this notification, use the object nbsCmmcChassisEnableModuleSpecificTraps.

Sent when a central office module ceases active management of a dual-homed CPE module. This Notification should be of Severity WARNING. To enable/disable this notification, use the object nbsCmmcChassisEnableModuleSpecificTraps.

Sent when one central office module is connected to another central office module. This Notification should be of Severity ERROR. To enable/disable this notification, use the object nbsCmmcChassisEnableModuleSpecificTraps.

Sent when a remote CPE module is detected. This Notification should be of Severity WARNING. To enable/disable this notification, use the object nbsCmmcChassisEnableModuleSpecificTraps.

Sent when SingleFiber port detects its own signal reflecting back on itself. This Notification should be of Severity WARNING.

Sent when SingleFiber port no longer detects its own signal returning. This Notification should be of Severity WARNING.

Sent when transmitter temperature returns to normal. For Agent's internal severity-based filtering. The severity of this NOTIFICATION must match the severity of the nbsCmmcTrapPortTempTooLow or nbsCmmcTrapPortTempTooHigh NOTIFICATION that this overrides.

Sent when received signal returns to normal. For Agent's internal severity-based filtering. The severity of this NOTIFICATION must match the severity of the nbsCmmcTrapPortRxPowerTooLow or nbsCmmcTrapPortRxPowerTooHigh NOTIFICATION that this overrides.

Sent when transmitter power returns to normal. For Agent's internal severity-based filtering. The severity of this NOTIFICATION must match the severity of the nbsCmmcTrapPortTxPowerTooLow or nbsCmmcTrapPortTxPowerTooHigh NOTIFICATION that this overrides.

Sent when bias current returns to normal. For Agent's internal severity-based filtering. The severity of this NOTIFICATION must match the severity of the nbsCmmcTrapPortAmpsTooLow or bsCmmcTrapPortAmpsTooHigh NOTIFICATION that this overrides.

Sent when transceiver supply voltage returns to normal. For Agent's internal severity-based filtering. The severity of this NOTIFICATION must match the severity of the nbsCmmcTrapPortVoltsTooLow or nbsCmmcTrapPortVoltsTooHigh NOTIFICATION that this overrides.

Sent when slot temperature is too cold. This Notification should be of Severity ERROR.

Sent when slot temperature is too hot. temperature alarm. This Notification should be of Severity ERROR.

Sent when slot temperature returns to normal. This Notification should be of Severity ERROR.

Sent when nbsCmmcPortErrorActivity changes to on(3). This Notification should be of Severity WARNING.

Sent when nbsCmmcPortErrorActivity changes to off(2). This Notification should be of Severity WARNING.