ZHONE-SYSTEM-MIB: View SNMP OID List / Download MIB

The following variables are associated with the state of existence and connectivity with the Zhone Management System (ZMS).

Identifies whether or not this device is being managed by the Zhone Management System. This is only settable by the management system and NOT by the CLI as it indicates existence of the manager. Different operations are performed based on this setting (i.e. no configuration synchronization processing is performed if there is no Zhone Management System). Default value is 'false'.

The status of the connection between this device and the Zhone Management System, if one exists. This value can either be set directly by ZMS or by the device internally when a SNMP request is processed from the ZMS. For devices that are being proxied by another entity, since they are not being polled by ZMS, will set this state according to the communication channel state between this device and the connected entity. Default value is 'inactive'. Enumeration: 'active': 1, 'inactive': 2.

This is the ZMS IP address for which configuration synchronization messages and any other special handling is performed. This can be set either via CLI or ZMS.

If TRUE, CLI only allows 'show' commands and cannot modify/add any data records. This is used by ZMS to prevent race conditions and to allow only single access to system resources especially during problem analysis times. Default value is 'false'.

This is the trap information related to handling device to ZMS traps.

Zhone Traps Table

An entry per trap destination.

The location to be send traps.

Community name to be sent in all traps sent to this destination. This field is defaulted to NULL so a null string will be sent to the destination.

Next sequence number to be sent as part of a trap generated by the device. The sequence number has two uses. In one case,it is the sequence number of the non-acknowledge traps and has a range of 0-2147483647. While the acknowledge sequence number range is 2147483648-4294967295. This field wraps to the appropriate '0' value (0 or 2147483648) for it's range.

This is set by the ZMS in order to have the device resend saved traps because one or more were lost in transmission. The device will resend traps starting at this sequence number. Note that due to resource constraints not all traps may be available to be resent. The first trap resent will indicate that this is a resent and whether or not any traps were deleted/lost. This is used only on the unacknowledge trap flow. This is the only indication of whether or not any traps have been acknowledged. The value returned is always 0 as setting this field only causes restarting of the traps with this number.

Acknowledged trap sequence number. This field is set by the ZMS in order to acknowledge a trap sent by the device with the Request Acknowledge flag set to YES. There will be only one trap will be outstanding on this flow (acknowledged flow)at one time so this should be the last sequence number sent. If not, it is ignored.

The Trap severity level which at this level or higher, traps will be sent to this destination. Enumeration: 'severe': 2, 'critical': 1, 'moderate': 3, 'low': 4.

Array of allowed categories to be sent to this particular trap destination. This field is not currently implemented and is reserved for future use. Bits: 'catAdmin': 0, 'catVoice': 2, 'catRadio': 5, 'catIP': 3, 'catLine': 1, 'catRip': 4.

Whether traps should be enabled or disabled for this particular IP address. Enumeration: 'disabled': 2, 'enabled': 1.

Row status in order to create the entry for this destination. There are no required fields on a create besides the obvious index of the ip address of the destination.

The Gateway Trap Server Address is used to locate the Gateway. Trap Server. This field is defaulted 0,0,0.

Version number of the format of the trap. Any changes to the common area of a trap require a bump of this number. Enumeration: 'version1': 1.

This variable is sent with all traps and contains flags related to this trap. trapAcknolwedge: If this bit is set, it indicates to the ZMS that the trap must be acknowledged. Acknowledgement is accomplished by the ZMS sending a SET request to the variable zhoneTrapsAckedSequenceNumber in the zhoneTrapsTable. See the trap sequence number field description (value is 2147483648 and higher. trapOutOfSequence: If set, it indicates that this trap is being sent out of sequence from what the trap receiver is expecting. The specific occurence is when the trap receiver detects lost traps and requests resending of traps starting from a specific sequence number (see zhoneTrapsResendSequenceNumber) but the system does not have all these traps. Example: - traps 400-600 sent to the trap receiver. - trap 500 is lost - trap receiver requests resend of traps 500 and up. - system only has 550-600 saved in memory. - trap 550 resent with trapOutOfSequence set. - trap 551 and above resent with trapOutOfSequence reset. trapResetSequenceNumber: If set, the sender of this trap has reset the trap sequence number for this trap destination. It is indicating to the ZMS to also reset its sequence numbers. Bits: 'trapAcknowledge': 0, 'trapResetSequenceNumber': 2, 'trapOutOfSequence': 1.

This variable is sent with all traps. This contains the value of the shelf that originated the trap.

This variable is sent with all traps. This contains the value of the slot that originated the trap.

This variable is sent with all traps. This contains the value of the port that originated the trap. If this is a system or card level trap (no port is associated with the trap), this value is 0.

This variable is sent with all traps. This contains the value of the subport that originated the trap. If this is a system or card level trap (no port is associated with the trap), this value is 0. It may also be 0 if not subports are associated with this physical port such as in the case of an ethernet port.

Unique service provider ID. This value is used throughout the management system to link objects with customers or service providers.

Any text associated with this trap. NULL is allowed

This is the If Type. It is used to uniquely identify a port.

This is the If Type Extension. It is used to uniquely identify a port.

This is the alarm action type for products supporting the alarm manager functionality. Enumeration: 'clear': 2, 'set': 1, 'informational': 3.

For products supporting the alarm manager functionality, this is the alarm id a particular trap is setting or clearing.

For products supporting the alarm manager functionality, this is the alarm severity a particular trap is setting or clearing.

The ConfigSync reset check is run in 6 minute intervals. This object represents the interval number and starts with interval number 1 at system bootup and will reset to 1 whenever the sytem reboots.

This count is the number of times the device has had to reset ConfigSync. Resetting configsync on the device consists of closing the FTP data and control sockets, setting the configsyncstatus to syncerror, cleaning up any pending configsync records, resetting the ConfigSync state machine to the initial state, and throwing a ConfigSyncReset Trap.

Last time device sent a ConfigSync Ftp command to ZMS. Measured using the Unix time() function. The internal representation of time is the number of seconds elapsed since 00:00 Universal time on January 1, 1970 in the Gregorian calendar (Julian day 2440587.5), with time stored as a 32 bit signed integer (long in the original C implementation).

Current device time returned using Unix time() function. The internal representation of time is the number of seconds elapsed since 00:00 Universal time on January 1, 1970 in the Gregorian calendar (Julian day 2440587.5), with time stored as a 32 bit signed integer (long in the original C implementation).

Number of seconds since Jan. 1, 1970 GMT, when this trap was sent from the device.

Configuration Synchronization information.

Indicates whether or not there exists records to be sent to the ZMS config synch manager for changes that have been made by CLI/HTTP to the data base.

Indicates whether or not the device had to discard update data base records due to resource constraints. If TRUE, traps will be sent to the ZMS Config Synch Manager indicating a download of the entire data base is required.

Indicates the highest priority configuration synchronization trap outstanding. This flag is set to none at boot time and whenever a file of synchronization changes has been sent to ZMS. If a parameter change has been made to either the same or lower prioirty, the device does not have to send a change notification to ZMS. Higher priority fields must immediately cause traps to be sent to ZMS. Enumeration: 'high': 4, 'none': 1, 'medium': 3, 'low': 2.

Used by ZMS when it wants to create a list of config synch records. It must first write the filename expected and then set the action. The create_list action allows the device to determine whether the complete database (synchoverflow occured) needs to be sent or only those records that have been modified. create_full_list specifies that ZMS would like to receive the complete database. Enumeration: 'createFullList': 3, 'createList': 2, 'noAction': 1.

File Name to be used when creating the config synch records.

Used by Config Sync Acgent when processing a request to create a list of config synch records. Enumeration: 'syncError': 3, 'syncComplete': 1, 'syncPending': 2, 'syncInitializing': 4.

User Name to be used when sending the config synch records. When read, the last user name is returned.

Password to be used when sending the config synch records. For use in FTP authentication. When read, always returns the NULL string

Zhone Authorization parameters.

Zhone proprietary Community Table.

A community name access to this system.

The community name that has access to this system. Maximum length for community name string is 32 characters.

The Access Rights for this particular community name. An access of read-write-admin allows access to those tables with a higher level of security such as the community table. Gets to this table will return E_NOSUCHINSTANCE unless the accessrights is read-write-admin. noAccess - this community name does not have any access to this device. read - allows read access to all fields except admin access fields such as this community table. readAndWrite - allow read and write access to all fields except admin access fields such as this community table. admin - read and write access to all fields on this device. Enumeration: 'read': 2, 'readAndWrite': 3, 'admin': 4, 'noAccess': 1.

The AccessList Table index indicating which IP addresses are allowed to use this community name. If the value is 0, no address checking is performed and all SNMP requests are allowed with the access right as specified in this table.

Row status in order to create the entry for this destination.

The next available zhoneAdminAccessListIndex that can be used by the manager when creating a access list entry. A Get request to this field causes the current number to be returned and the value to be incremented for the next requester. Once this value reaches 50, processing examines the entire list for possible free entries and provides the lowest number available. If no entries are free, an error is returned.

Access List Table Definition.

Zhone Access List Entry Definition.

The index into this table. There is a maximum support of a total of 50 access lists. 0 is not supported as it indicates that no IP address validation should be performed.

The IP address is used as a index into this table and indicates whether SNMP requests originating from this address will be accepted.

Row status in order to create the entry for this destination.

Zhone User parameters.

The next available zhoneUserId that can be used by the manager when creating a user entry. A Get request to this field causes the current number to be returned and the value to be incremented to the next available ID for the next requester use. A maximum of 20 login accounts are allowed per system.

The number of failed logins performed by any user whether this be for invalid user id or valid user id but an invalid password.

ZLI user information.

A row exists for each user that can login on this system.

The id used to identify this particular user. This value is only used for access to this table and is not externally shown.

The user name allowed to login to this system.

The password to be used for logging in to the system. This field is returned as an encrypted field.

The prompt to be used after this user has logged in to the system.

Array of access levels that a user may have. This is an OR field where a user may have access to different subsystems. Only exception is Admin access level which allows access to all functions in the system. userAccessAdmin - allows access to all entities of the system. userAccessVoice - allows access to voice specific configuration and information. userAccessData - allows access to the data (i.e. IP) configuration and information. userAccessManuf - allows access to the manufacturing components of the system. userAccessDatabase - allows access to the database allowing write access. For any access except admin, this value must be set to allow any changes to be saved by this user. userAccessSystems - allows access to the system information. userAccessTool - allows access to system tools which help administer the system. userAccessDebug - allows access to Zhone Debug commands. This access should rarely be specified. There is No default value and a value must be specified for the user entry to be created. Bits: 'userAccessVoice': 1, 'userAccessTool': 6, 'userAccessDebug': 7, 'userAccessData': 2, 'userAccessDatabase': 4, 'userAccessManuf': 3, 'userAccessAdmin': 0, 'userAccessSystems': 5.

Whether this user is enabled (i.e. can login). Disabling the user will automatically cause an internal logout if the user is currently logged in. Enumeration: 'disabled': 2, 'enabled': 1.

The number of successful logins performed by this user.

The number of failed logins performed by this user. A user would have had entered a this user name but entered an invalid password. Invalid user names are not tracked but are included in the total count described above.

Row status in order to create the entry for this user. In order to successfully create a user record, the following variables are required: zhoneUserName zhoneUserPassword zhoneUserAccessLevel

System configuration parameters

The number of shelves physically in the system

Bit array from 0-255 (32 8-bit bytes) that are present in the system.

The total number of cards in the system (physcially). The number per shelf is defined in the shelf mib.

The IP address of this device. Independent of the different IP interfaces configured and what is active,a manager uses this address as how to address the device. This address may OR may not be an IP address of an existing IP interface. Deletion of a matching IP interface does not cause this address to be modified or deleted. A manager may communicate with the device using any of the configured IP interface addresses. However, any failures such as physical line outages or the card status is inactive, may result in failures to the manager requests (i.e. timeout). This value is defaulted to 0.

A second IP address of this device. Independent of the different IP interfaces configured and what is active,a manager uses this address as how to address the device. This address may OR may not be an IP address of an existing IP interface. Deletion of a matching IP interface does not cause this address to be modified or deleted. A manager may communicate with the device using any of the configured IP interface addresses. However, any failures such as physical line outages or the card status is inactive, may result in failures to the manager requests (i.e. timeout). This value is defaulted to 0 and in some cases, may never be configured.

The date and time of the system, specified in local time. Only a community name having 'admin' priviledges will be allowed to modify this value. Although any valid community name is allowed to read it. If an NTP server has been configured in zhoneSntpConfiguration, then manual setting of the date and time is not allowed, and a set attempt on zhoneSystemConfigurationDateAndTime will result in a generic error.

The country or region where this system is operating in. This variable is used to adjust system settings for different functional modules. For example, both DSP tones and TDM compounding are country-specific settings that can be determined by this variable. This value is defaulted to 'us'.

The ifIndex of the interface from which clock can be derived. Only oc3, ds1, and ds3 interfaces can be used for this. This interface will be used to drive the 8khz backplane signal. The interface must be set to loop or local timing in order for it to be considered as the primary clock source. It must also be administratively turned on and be in an operational state. Only one interface in the system can be the primary clock source at any given time. NOTE: This value has been deprecated and should not be used. If specified, the system will use this interface as the clock source and will ignore the provisioning specified in the zhoneSystemClockTable.

Ring voltage source selection (internal or external): (1)Select internal ring generator (located within TAC) as source for ring voltage to line cards. (2) Select external ring generator (input connector located on TAC) as source for ring voltage to line cards. Enumeration: 'externalRingSourceLabel': 2, 'internalRingSourceLabel': 1.

The current interface that is being used for the clock source. A value of 0 is returned if there are no available interfaces in the zhoneSystemClockTable that have a zhoneSystemClockAvailibilityStatus of active even the system clock table is not empty.

The interface that would next be used for the system clock source if the zhoneSystemCurrentClockSource becomes inactive, it's elgibility is changed,is being used for the clock source. A value of 0 is returned if there are no other available interfaces in the zhoneSystemClockTable that have a zhoneSystemAvailabilityStatus of active even the system clock table is not empty.

Table of physical ports that could be used as the clock source for other physical ports (i.e. DSL, DS1/DS3, and sonet). Entries are added to this table automatically by the system software whenever a card is activated for the first time. Ports that can supply clock will be added to this table with the default eligibility being set to FALSE (i.e not eligible to be a clock source). Current port types that will be added to this table are: DS1/E1, DS3/E3, and Sonet). Note that only physical ports are added so for example, a DS3 would be added but not any of the associated DS1 interfaces. A manager provisions entries in this table to be eligible to be a clock source and the associated weight that is provisioned is used to determine the preference order for the clock source. A manager which specifies the DEPRECATED zhonePrimaryClockSource overrides entries in this table and will be used as the system clock source as long as the interface is active.

A row in the system clock table. Each row represents a possible clock source by it's associated ifIndex.

The eligibility field indicates whether the system should include this physical port as a possible clock source.

The weight to be used to indicate the preference for each eligible port which is currently active (zhoneSystemClockElgibilityStatus = active) to be used as the system clock source. Multiple interfaces may have the same weight and if so, the system will choose which interface to be chosen as the clock source. Changing the weight will have an immediate affect. For example, changing an interface to the highest priority will immediately make the interface the zhoneSystemCurrentClockSource unless the weight of the current source has that same weight.

The status for whether this port can be usd as a clock source. A port can be active only on all of the following conditions are true: 1. zhoneSystemClockEligibility is true. 2. the interface is up and running (both ifAdminStatus and ifOperStatus are up). When this value is 'active', this port is included in a pool ordered by weights for whether it should be the clock source. Enumeration: 'active': 2, 'inactive': 1.

The transmit clock source is provisioned in the profile corresponding to the line type. The choices are loop, local, or through. zhoneSystemClockTxClockMode shows the current transmit clock source as possibly modified by the clock manager. If the line selected as system clock source is provisioned in through mode, its zhoneSystemClockTxClockMode value is set to loopTiming while it is the source. If there is no eligible clock source, zhoneSystemClockTxClockMode for all lines are set to localTiming. provisionedTiming is reserved for internal use and will never be seen as the status of transmit clock mode. localTiming indicates that a local clock source is used or that an external clock is attached to the box containing the interface. loopTiming indicates that the recovered receive clock is used as the transmit clock. throughTiming indicates that transmit clock is derived from the recovered receive clock of another interface. Enumeration: 'provisionedTiming': 2, 'loopTiming': 4, 'other': 1, 'localTiming': 3, 'throughTiming': 5.

An option to enable or disable logging of system messages onto the console. Enumeration: 'disabled': 2, 'enabled': 1.

Indicates whether revertive behavior of the system clock is desired. If set to TRUE, the system will automatically revert to the higher weighted clock when it becomes available again. Used by systems that have the Clock Manager enabled.

Turns ON (true) of OFF (false) ATM bandwidth checks for new voice calls going through the system. The bandwidth check is based on the configuration of the Rx and Tx traffic descriptors used for the ATM VC/CID that the call is going across. If rtVBR is being used then the SCR is used for the bandwidth calculation cell rate. If CBR is being used then the PCR is used for the bandwidth calculation cell rate. For any other service category, a call is always allowed and the voice quality is not guaranteed. The bandwidth calculation looks like this (assume approx 180 AAL2 cells used for a voice stream): if ((rxCellRate - (180 * numActiveCallsOn VC)) < 180) { /* reject call */ } else if ((txCellRate - (180 * numActiveCallsOnVC)) < 180) { /* reject call */ } else { /* proceed with call */ }

Bit field indicating which combination of the 4 alarm levels are enabled. User can disable alarms based on alarm severity level. Bits: 'major': 1, 'critical': 0, 'warning': 3, 'minor': 2.

This object determines how users access to the device is authenticated. A value of local indicates that user should be authenticated using locally provisioned user-profile profiles. A value of radius indicates that only RADIUS authentication should be used. A value of radiusThenLocal indicates that the user should be authenticated first by using RADIUS authentication and if that fails, then by local user-profile profiles. A value of radiusThenCraft indicates that the user should be authenticated first by using RADIUS authentication and if that fails, then only on the local craft port authentication by local user-profile profiles is allowed but all other ports will be denied access. Enumeration: 'radiusThenCraft': 4, 'radius': 2, 'radiusThenLocal': 3, 'local': 1.

This object contains the index of the Radius Server profile to be used if RADIUS authentication is desired.

Secure FTP (SFTP) control. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies whether the Web GUI Interface is enabled for this system. Enumeration: 'disabled': 2, 'enabled': 1.

System options in bit-mask format. Bits: 'disdefpktrules': 3, 'cfmon': 6, 'ipg88bits': 2, 'cvlanonly': 0, 'nol3bridgetable': 1, 'enablexcardlinkagg': 4, 'fiberlan': 5.

Starting VLAN ID of the reserved VLAN ID block. The reserved VLAN ID block starts with the reservedVlanIdStart and ends with reservedVlanIdStart + reservedVlanIdCount; No bridge, host, or IP can use a VLAN ID in the reserved VLANs.

Number of reserved VLAN IDs in the reserved VLAN ID block. A zero value disables these reserved VLANs and operation reverts to normal VLAN ID reservation. The reserved VLAN ID block starts with the reservedVlanIdStart and ends with reservedVlanIdStart + reservedVlanIdCount; No bridge, host, or IP can use a VLAN ID in the reserved VLANs. For GPON OLTs, the number of GEM Ports per OLT cannot exceed this number.

Version of SNMP the supported by the device. Enumeration: 'snmpv3includingZMS': 3, 'snmpv2': 1, 'snmpv3': 2.

An option to enable or disable persistent logging of system messages onto the console. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies the outlet sensor high temperature threshold. Minor, Major & Critical alarms will be raised when outlet sensor temperature reaches X, X+5 & X+10 respectively. X is the value of this field. Allowed range for MXK & MX1U products is 35 to 65 Allowed range for MX1U160Lt is 35 to 75

Specifies the outlet sensor low temperature threshold. Minor alarm will be raised when outlet sensor reaches the temperatue configured in this field

This table is used by the system to determine the default code image to load for each card type. Each card, when it requests a software load, will either receive an upgrade version of software, a specific version of software, or receive the known current version of the software. This table is used to determine the code image to load in the default case. This table is not used for non-BAN hardware.

Table of software code image names for each card type in a BAN.

Type of card requesting software load this card type the same used in the Card Resources MIB.

Name of code image to loaded by software load services for the card type requesting a load if a specific load version is not requested. Required for RowCreate

Row status in order to create the entry for this destination. zhoneCardSwFileName is required for row creation.

Zhone SNMP error information.

A single entry in the error table which describes an problem detected by the mib handler.

The IP address of the requesting station for which this error is applicable.

SNMP request ID of failed error.

The actual text string to show to the user.

System time that the error occurred. This is used so the system will remove any old entries (older than 2 minutes) as it is unlikely that the cli or management station will require errors after that long of a period.

Software Download information utilized by all Zhone devices in order to obtain software images on to local storage. In lower-end devices, the download itself may be stored directly into a boot area which is automatically used upon restart of the system. The login/password information may be ignored if the device only supports tftp. Sets to these fields will be accepted so the request may continue.

The login to be used on the remote system when downloading the image. This value is maintained throughout (i.e. persisted) and can be used for additional/future download requests. This login is used for both zli 'update-image' commands and snmp/zms requests using this mib. The login is defaulted to NULL the first time the system is booted and is maintained across sw download requests and reboots. That is, the value is not cleared upon completion and can be reused by the manager.. When read, the last value used is returned.

The password to be used on the remote system when downloading the image. This value is maintained throughout (i.e. persisted) and can be used for additional/future download requests. This password is used for both zli 'update-image' commands and snmp/zms requests using this mib. The password is defaulted to NULL the first time the system is booted and is maintained across sw download requests and reboots. That is, the value is not cleared upon completion and can be reused by the manager.. When read, a NULL value is always returned.

The IP address of the primary software load server. If the value of the zhoneSysSwPriLoadServer is set to 0.0.0.0 then no primary load server is available. If the system is unable to load the software file from the Primary Load Server, the system should attemmpt to load the software from the the Secondary Load Server (zhoneSysSecLoadServer). This value must be set on each download request.

The IP address of the secondary or back-up software load server, if there is no secondary server this should be set to 0.0.0.0

The path on the remote system for the image to be loaded.

The path on the system for the image to be stored.

(1) downloadSw: Download the image from the Primary load Server. If that fails, try to download from secondary load server. This value is only allowed if the zhoneSysSwStatus field is NOT downLoadSwInProgress. (2) abortDownLoadSw: abort an in-progress download. This value is only allowed if the zhoneSysSwStatus is downLoadSwInProgress. (3) delete: deletes the filename specified in zhoneSysSwLocalFilePath. This is used by the manager to manage the amount of storage space used by the system for sw load images. A delete will fail if the file is specified in either a: default sw entry, specific software entry, or an upgrade software entry. This is only supported on devices having a file-system. (4) imageFlashActive: flashes the raw file specified in the zhoneSysSwLocalFilePath. This is used to update the raw boot area of the flash of the active infoserver. (5) imageFlashStandby: flashes the raw file specified in the zhoneSysSwLocalFilePath. This is used to update the raw boot area of the flash of the active infoserver. (6) downLoadFile: Download a file from the Primary load Server. If that fails, try to download from secondary load server. This value is only allowed if the zhoneSysSwStatus field is NOT operationInProgress. (7) upLoadFile: Upload a file to the Primary load Server. The file must already exists on the load server This value is only allowed if the zhoneSysSwStatus field is NOT operationInProgress. (8) dumpFile: dump the database to a local file. (9) dumpNetwork: dump the database to the primary load server. The file must already exists on the load server This value is only allowed if the zhoneSysSwStatus field is NOT operationInProgress. (10) restore (11) configScriptActivate: activate the configuration script file specified in the zhoneSysSwLocalFilePath. This value is only allowed if the zhoneSysSwStatus is NOT operationInProgress nor downloadSwInProgress. (12) configDatabaseActivate: activate the contents of a database file specified in the zhoneSysSwLocalFilePath. This value is only allowed if the zhoneSysSwStatus is NOT operationInProgress nor downloadSwInProgress. Activation of a new database may result in a reset of the system. (13) backupDatabase: backup device by uploading database file to zhoneSysSwLocalFilePath. (14) restoreDatabase: restore device database from zhoneSysSwLocalFilePath. This command will reboot device with restored database. Enumeration: 'restore': 10, 'delete': 3, 'upLoadFile': 7, 'dumpFile': 8, 'dumpNetwork': 9, 'configDatabaseActivate': 12, 'backupDatabase': 13, 'downLoadFile': 6, 'imageFlashActive': 4, 'downLoadSw': 1, 'restoreDatabase': 14, 'abortDownLoadSw': 2, 'configScriptActivate': 11, 'imageFlashStandby': 5.

(1) downLoadSwUnknown: No state known. This is the value if no sw download had been requested since the system was initialized or a delete command is in progress. (2) downloadSwInProgres: Download currently in progress. (3) downLoadSwAborted: abort command processed. Sw not loaded. (4) downLoadSwFailed: FTP/TFTP request failed to both the primary and secondary server. (5) downLoadSwSuccessful: SW successfully downloaded from either the primary or secondary server. (6) deleteFileNotFound: The file specified in zhoneSysSwLocalFilePath cannot be found on the device. (7) deleteFileInUse: The file specified in zhoneSysSwLocalFilePath is currently specified in a sw configuration record. (8) deleteSuccessful: The file was successfully deleted. The following are the generic status for the imageFlash, uploadFile, downloadFile, dump and restore operations. (9) operationInProgres: operation currently in progress. (10) operationAborted: abort command processed. Sw not loaded. (11) operationFailed: operation failed (12) operationSuccessful: operation successfully Enumeration: 'deleteSuccessful': 8, 'downLoadSwSuccessful': 5, 'downLoadSwInProgress': 2, 'downLoadSwUnknown': 1, 'downLoadSwAborted': 3, 'deleteFileNotFound': 6, 'operationInProgress': 9, 'operationSuccessful': 12, 'operationFailed': 11, 'downLoadSwFailed': 4, 'deleteFileInUse': 7, 'operationAborted': 10.

Reboot for system or particular type of cards. Common use is after software downloads but can be used anytime. Initiating a reboot requires admin access level security.

systemReboot: reboot all the cards rebootByCardType : reboot all cards of a particular card Type (specified by zhoneSysRebootCardType). Enumeration: 'systemReboot': 1, 'rebootByCardType': 2.

The numerical representation of what unit/card type has to be rebooted.

The software configuration for this card. For every card (i.e. shelf/slot) in the system, an entry must be created in order for the card to get loaded with software along with the card software enable flag set to true. At a minimum, the system will check to see if the zhoneSysCardSwEnable value is TRUE to indicate the card can be loaded. If the value is true, the scenario to determine which software to load is: - if zhoneSysCardUpgradeFileName is set and the zhoneSysSwUpgradeEnable flag is set to true, load this software. - if zhoneSysCardSpecificFileName is set, load this software. - if a default file name is specified for this card type, the software specified in zhoneSwCardFileName will be used. - Otherwise, a trap is generated for the first time this error occurs.

An entry for a particular card. An entry is added by the manager in order for a card to be available for loading. If an entry does not exist for a card, no load is possible.

The file or code image name of the specific software version that should be loaded by the unit/card for operation. If a failure occurs when trying to boot an upgrade version, the system will automatically revert to a 'good' software version which is either the zhoneSysCardSpecificSwFileName if non-NULL or the default for this card type if it is NULL. The operation will vary if the unit is a BAN card or a standalone device. BAN: In the case of a BAN the card will load the indicated module and set cardSwStatus as appropriate. If the cardSpecificFileName is set to NULL then the card will load the image indicated by the zhoneSoftwareLoadTable in the system mib. STANDALONE: If the card is a Zedge,Sechtor, or similar device, the system will first check if there is a local copy of the code image indicated, if there is, the card will load from the local copy. If the local copy is not the same revision as zhoneSysCardSpecificSwFileName the card will load this file.

The software version of the file name specified in zhoneSysCardSpecificSwFileName. If the revision is not known or the file name is NULL, this should return an empty string.

The file name of the software version that should be loaded by the unit/card into the upgrade region of the card/unit memory or storage. This file takes precendence over the current sw file name and is used to attempt to upgrade the software on the system or card. If a user determines that the software upgrade version is acceptable, this value should be set in the CurrSwFileName.

The software version specified in the zhoneSysCardUpgrade FileName variable in this table that will be loaded on the next card reboot. This object complies to the Zhone software revision syntax.

The card type for the card in this shelf/slot. When initially created, this value is defaulted to 'unknown'. When the card requests a load, the value in this field is compared to the requesting card type. If the value is 'unknown' and a load can be serviced (i.e. the card is swenabled, and a sw is specified in either the upgrade, specific, or default for this type fields), the value is updated to the requesting card type. Otherwise, the type in this field is compared to the requesting card type. If it matches, a load based on the other parameters is attempted. Otherwise, the load request is rejected and the initial request causes a trap to be generated. This processing is provided to ensure a card is not accidentally installed which attempts to load or start provisioning for a non-matching card type. The user may switch to a different card type than currently executing by setting this value to the new card type after the old card has been removed.

Whether or not the card has been enabled to be loaded. If this value is false, no sw will be loaded, otherwise the logic flow defined in the table description will be exercised for determining which software to load.

This field indicates whether the zhoneSysCardUpgradeSwFileName should be used as the software image when the card requests a software load. This value can either be set directly or may be set indirectly via changes to the cardSwAdmin field in the card mib.

The row status used to create or delete an entry for a card (i.e. shelf/slot). No entries are required to be included in a table create as all entries have default settings.

This field is used to identify which line types for different cards For normal e1/t1 cards only t1 and e1 (uni mode) line types are supported. For MALC t1Ima Uplink card, e1, t1, e1-ima, and t1-ima line types are supported For MALC ds3 Uplink card, e3 and t3 line types are supported. For MALC t1e1tdm Uplink card, only t1UniGr303, t1ImaGr303, e1UniV52 and e1ImaV52 are supported. MalcT1E1Tdm cards have 16 T1/E1 ports. The first 8 ports are ATM, the second 8 are TDM. These 4 values indicate both the layer 1 line type (e1Uni, e1Ima, t1Uni, t1Ima) for the ATM ports and the layer 3 signalling (gr303 and V5.2) for the TDM ports. For malcXdsl48 with optional pots card, unknown, adsl-pots and adsl-pots-pv are allowed. For malcPots48 with unknown, pots and pots-pv are allowed. All other cards only support unknown. Default value for MALC t1Ima uplink will be t1 line type if the line type was not stored in the Real Time Clock (RTC). Otherwise it will be the value stored in the RTC. Default value for MALC ds3 Uplink will be t3 line type if the line type was not stored in the Real Time Clock (RTC). Otherwise it will be the value stored in the RTC. Default for MalcT1E1Tdm is t1UniGr303. This field is only set upon row-creation. Modifications to this value after row creation will only be allowed for packet voice capable cards.

This field specifies how internal resources are distributed between aal5 resources and aal2/cell relay resources based on the core use of this card. This field is applicable for BAN AtmTrnk, AtmAal25 and AtmTrnkCr Cards. For AtmAal25 card, it also specifies how much of the AAL2/Cell Relay BW will be utilized for RTVBR and UBR. For AtmTrnkCr card valid value is cellRelayOnly. It implies 100% BW is available for cellRelay and none for AAL5. All cell relay traffic is RTVBR. For AtmTrnk card valid values are cellRelayOnly, cellRelayAndManagement, dataTerm, hybridLowAal5Data, hybridDefault and hybridHighAal5Data. All cell relay traffic is RTVBR and all AAL5 traffic is UBR. Out of total available BW on AtmTrnk card: for cellRelayOnly Cell Relay BW is 100% and AAL5 BW is 0%. for cellRelayAndManagement Cell Relay BW is 95% and AAL5 BW is 5%. for dataTerm Cell Relay BW is 5% and AAL5 BW is 95%. for hybridLowAal5Data Cell Relay BW is 75% and AAL5 BW is 25%. for hybridDefault Cell Relay BW is 60% and AAL5 BW is 40%. for hybridHighAal5Data Cell Relay BW is 25% and AAL5 BW is 75%. For AtmAal25 card valid values are cellRelayOnly, cellRelayAndManagement, dataTerm, voiceGateway, hybridLowAal5Data, hybridDefault and hybridHighAal5Data. All AAL5 traffic is UBR and AAL2/Cell Relay traffic can be RTVBR or UBR. Out of total available BW on AtmAal25 card: for cellRelayOnly AAL2/Cell Relay BW is 100% and AAL5 BW is 0%. 50% of AAL2/Cell Relay BW is for RTVBR. for cellRelayAndManagement AAL2/Cell Relay BW is 95% and AAL5 BW is 5%. 50% of AAL2/Cell Relay BW is for RTVBR. for dataTerm AAL2/Cell Relay BW is 5% and AAL5 BW is 95%. 50% of AAL2/Cell Relay BW is for RTVBR. for voiceGateway AAL2/Cell Relay BW is 95% and AAL5 BW is 5%. 95% of AAL2/Cell Relay BW is for RTVBR. for hybridLowAal5Data AAL2/Cell Relay BW is 75% and AAL5 BW is 25%. 95% of AAL2/Cell Relay BW is for RTVBR. for hybridDefault AAL2/Cell Relay BW is 60% and AAL5 BW is 40%. 75% of AAL2/Cell Relay BW is for RTVBR. for hybridHighAal5Data AAL2/Cell Relay BW is 25% and AAL5 BW is 75%. 50% of AAL2/Cell Relay BW is for RTVBR. For malc uplink cards (t1/e1, t3/e3 ima), the following qos values and its associated BW can be configured: qos name ubr% vbr% vbrrt% vbnrt95rt5 0 95 5 vbnrt80rt15 5 80 15 vbnrt65rt30 5 65 30 vbnrt50rt45 5 50 45 vbnrt35rt60 5 35 60 vbnrt20rt75 5 20 75 vbnrt5rt95 5 5 95 vbnrt5rt95cbr 5 5 95 For all other cards valid value is notApplicable. This field cannot be updated after row creation. manual configuration is not supported in this release. Enumeration: 'voiceGateway': 5, 'vbnrt35rt60': 13, 'dataTerm': 4, 'hybridLowAal5Data': 6, 'cellRelayAndManagement': 3, 'vbnrt5rt95cbr': 16, 'vbnrt95rt5': 9, 'manual': 99, 'notApplicable': 1, 'vbnrt20rt75': 14, 'vbnrt50rt45': 12, 'hybridHighAal5Data': 8, 'cellRelayOnly': 2, 'vbnrt5rt95': 15, 'vbnrt65rt30': 11, 'hybridDefault': 7, 'vbnrt80rt15': 10.

Sepcifies the voltage supplied to all lines (ports) of this card, Used on ISDN line cards. Enumeration: 'lv-100-volts': 5, 'lv-60-volts': 2, 'not-used': 1, 'lv-110-volts': 6, 'lv-95-volts': 4, 'lv-68-volts': 3.

The maximum vpi and vci values that may be used for this card. Enumeration: 'vpi-7-vci-127': 3, 'vpi-15-vci-127': 4, 'vpi-15-vci-63': 2, 'not-applicable': 1.

Ascii string containing tokens separated by ',' or ' ' which is used to configure special non-standard operations. This string is blank for normal operation.

Sepcifies weather wetting current is disabled or enabled(standard). Enumeration: 'disabled': 1, 'standard': 2.

Returns the next unused card Redundancy Group Id.

This table is used to group redundant cards and provide a mechanism to indicate which card, if any, is preferred to be active. A weight is assigned to each card to indicate a preference for which card should be active. In the absence of any preference (e.g., weights for all cards are equal), then the card with the lowest shelf/slot number will become active. Notes: (1) A row for this table cannot exist without a corresponding entry in the zhoneSysCardSoftwareConfigTable. Thus, a row-create cannot occur on the this table until a corresponding row-create is performed on the zhoneSysCardSoftwareConfigTable. When a row-delete is performed on the zhoneSysCardSoftwareConfigTable, that action automatically performs a row delete on the relevant entry in this table. (2) Row deletes are disallowed on the zhoneCardRedundancy table.

An entry for a particular card.

The unique redundancy group to which the card is assigned.

A weight given to this card in determining whether this card should become Active on system boot.

When set to true, this indicates that the card, when Active, should remain in the Active state regardless of any system events. This effectively disables redundancy for the card group. Note the the holdActive attribute can be simultaneously set for multiple cards in the same redundancy group. Not supported in the initial release.

Indicates the status of the card. Note that a noStatus value means that the card is in a non-operational state, such as booting or fault. Enumeration: 'cardIsActive': 2, 'cardIsStandby': 3, 'cardIsStandbyWithActiveLinks': 5, 'noStatus': 1, 'cardIsNotRedundant': 4.

The row status used to create or delete an entry for card redundancy. No entries are required to be included in a table create as all entries have default settings.

Configuration of parameters for SNTP. The SLMS node will act as an SNTP Client and synchronize the time and date from the network as specified in this table. This table has one entry, which is automatically generated by the system at boot time.

The IP address of the Primary NTP Server from which the date/time will be synchronized.

The IP address of the Secondary NTP Server from which the date/time will be synchronized. Whenever the Primary NTP Server is not available, the Secondary NTP Server will be used.

Indicates the local time zone.

Indicates whether Daylight Savings time is currently in affect.

Indicates the daylight savings start time. The start time should be of the format mm:dd:hh:mm

Indicates the daylight savings end time. The start time should be of the fo rmat mm:dd:hh:mm

The objects contained in this ojbect identity are scalar objects used for provisioning and viewing the Adsl Pots LPF Bypass Relays.

Maximum number of Adsl Pots LPF Bypass Relays that can be active on any one card at any given time. This number is determined by the device and is calculated based upon power consumption of the relays. For example, if this value is set to 8, each Adsl Pots Splitter w/Bypass Relay card can have 8 relays set to closed at any given time. This object is only valid for Adsl Pots Splitter cards containing the Pots LBF Relays.

Enables the operator to force all Pots Bypass Relays in the system back to a normal state. This object is only valid for Adsl Pots Splitter cards containing the Bypass Relays. Enumeration: 'reset': 2, 'unchanged': 1.

System wide configuration of bulk statistics, including ftp parameters and enabling/disabling bulk statistics collection for the system.

Indicates whether bulk stats collection has been enabled for the system. If false, no collection is done. If true, the system will collect the stats identified in the zhoneBulkStatCollectionTable.

The IP address of the FTP Server to which the collected stats will be sent.

The FTP login name to be used for initiating the FTP file transfer of the collected bulk statistics.

The FTP password to be used for initiating the FTP file transfer of the collected bulk statistics.

This specifies the directory path on the FTP server into which the bulk statistics files will be transferred. The device will use this in a cd command, therefore a trailing '/' is not required. The ftp filename is constructed as follows: _ where timestamp is YYYY.DD.MM.HH.MM in device local time. For example: 172.16.80.291_2002.11.06.14.37

The operational status of the current collection interval. Valid values are: collectionInProgress: - Collection for the current interval has started collectionComplete: - Collection for the current interval has completed, and the resulting file has been transferred via ftp to the specified host. collectionPeriodOverrun: - Collection for the previous interval has not completed prior to the start of the current collection interval. In this case, the collection for the previous interval continues and the current interval is skipped. This is an indication that either the system/network is too busy and/or there are too many statistics being collected. collectionAbortedNoDiskSpace: - Collection for the current interval has been aborted due to insufficient disk space on the device. The current interval is skipped. collectionAbortedFileIoFailure: - Collection for the current interval has been aborted due to a file IO (write) error on the device. The current interval is skipped. collectionCompleteFtpFailure: - Collection for the current interval has completed, but the resulting file could not be transferred via ftp to the specified host. The file is queued for retry. The operStatus is only pertinent if bulk stats have been enabled. Enumeration: 'collectionComplete': 2, 'collectionAbortedNoDiskSpace': 4, 'collectionAbortedFileIoFailure': 5, 'collectionInProgress': 1, 'collectionCompleteFtpFailure': 6, 'collectionPeriodOverrun': 3.

Returns the next unused bulk statistics collection id.

This table is used to identify the statistics to be collected in bulk. Each row in the table represents a statistic to be collected.

Defines an entry in the zhoneBulkStatCollectionTable.

Unique identifier of the bulk statistic row.

Indicate whether collection in enabled for this statistic.

The OID of the statistic to be collected in bulk.

The Instance value for the zhoneBulkStatOID.

Indicates whether the statistic collection should include children. Using the zhoneAtmStatsExtTable (presently with 8 statistics in the table) as example, one could enable all stats for all 8 stats with one row entry by setting the includeChildren flag. The zhoneBulkStatOID leaf would contain the OID of zhoneAtmStatsExtEntry, the zhoneBulkStatInstance leaf would identify the specific VCL, and this leaf would be set to TRUE.

The collection interval for this statistic. Initially, all statistics will be collected on 15 minute intervals, and sets to this object are not supported.

The row status is used to create or delete an entry in this table.

Configuration information for the MALC video Head-End Server configuration. Managing the Head-End configuration requires provisioning the MALC with IP information as to the various server addresses.

This object contains an appropriate value to be used for zhoneVideoSystemConfigurationIndex when creating entries in the zhoneVideoSystemConfigurationTable. The value 0 indicates that no unassigned entries are available. To obtain the zhoneVideoSystemConfigurationIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.

This table is used to identify and manage the Head-End Video Servers. Each row in the table represents a Head-End Server.

Defines an entry in the Video System Configuration table.

A unique value to identify this video system profile entry.

This oid contains the IP address of the NTP Server for a particular Head-End.

This oid contains the IP adress of the EPG (Electronic Programming Guide) for a particular Head-End.

This oid contains the IP address of the set-top box head-end server.

his oid contains the multicast IP address of the channel chosen to be the default channel for a particular head- end provider.

This oid contains the multicast address of the channel appropriate to display when a user selects a channel that is not available or not in his channel profile.

zhoneVideoSystemConfigurationRowStatus is used to create/delete an entry in the zhoneVideoSystemConfigurationTable.

Indicates the type of EPG that we are talking to. Currently only Minerva, and Myrio are envisioned. Enumeration: 'minerva': 1, 'myrio': 2.

This oid contains the port number to use when talking with the EPG.

This oid is the IP address to use when FTP data to/from the EPP server.

System wide configuration of the Call Detail Recording.

Indicates whether CDR is enabled for this device. If false, the CDR is disabled. If true, the CDR is enabled, each call is recorded and a report is sent periodically to the most preferable and active ftp server.

If true, indicates the device to upload all pending call records and empty the CDR log. After the uploading is completed the flag is automatically set to false. In case of failure, the flag is also set to false but the OperStatus indicates an error.

Currently active FTP server. In case all FTP servers are not available the none(3) value is assigned. Enumeration: 'none': 3, 'primary': 1, 'secondary': 2.

IP address of the primary FTP server. If configured and available, it becomes the most preferable FTP server.

IP address of the secondary FTP server. This server is automatically selected when the primary FTP server is not configured or unavailable. The device will probe the primary FTP server and return to it automatically once it becomes available.

The FTP login name to be used by the device for initiating the transfer.

The FTP password to be used by the device during login to the FTP server.

The directory path on the FTP server where a file with CDR records is to be stored. The trailing '/' is not required. Within this directory, each device will have its subdirectory. The device subdirectory name is constructed from the device IP address as follows: '172-16-80-224'. The device subdirectory is created remotely from the device by using the FTP protocol. All call records from a device are stored in text files. All file names for a single device are unique and constructed as follows: YYYY-MM-DD-HH-MM-SN, where: YYYY - year MM - month DD - day HH - hour MM - minute SN - sequence number in case two subsequent raports are generated within the same minute.

This specifies the device reporting period in minutes. During this period a device is collecting CDR records and when this period elapses it triggers automatic uploading to the active FTP server. After successful transfer the CDR log is pruned. When the CDR log reaches its 'high water mark' before the end of the current reporting period, the transfer takes place immediately, then a new reporting period is commenced.

CDR Operational Status: active - CDR is enabled and working OK. ftpFailure - CDR cannot upload log due to lack of available FTP server. overrun - In result of FTP failure, CDR discards the oldest records. noConfig - CDR is disabled due to lack of correct configuration. Enumeration: 'active': 1, 'overrun': 3, 'ftpFailure': 2, 'noConfig': 4.

Used to upgrade device software during hitless upgrade.

Describes which software upgrade action to perform. Enumeration: 'swact-abort': 4, 'sw-upgrade-auto-swact': 2, 'swact': 3, 'sw-upgrade': 1.

Describes status of software upgrade. Enumeration: 'swact-aborted': 7, 'swact-complete': 6, 'swact-started': 5, 'standby-upgrade-aborted': 4, 'standby-upgrade-completed': 3, 'not-started': 1, 'standby-upgrade-started': 2.

Time software upgrade started.

Time software upgrade completed.

Represents SNMP view of Zhone File System available from Zhone Command Line Interface.

File Action: cd(1) - change directory command used in conjunction with zhoneDirectory location which specifies destination directory. dir(2) - listing of files within the directory specified by zhoneDirectoryPath. The generated file listing is written to zhoneFileTable. copy(3) - make a copy zhoneFileName1 and writes it to zhoneFileName2. User should prepend pathname to both filenames if not in default directory. rm(4) - removes file specified by zhoneFileName1. mkdir(5) - creates a subdirectory specified by zhoneFileName1. rmdir(6) - removes directory specified by zhoneFileName1. If directory not empty, returns error. mv(7) - moves zhoneFileName1 to zhoneFileName2. Enumeration: 'mkdir': 5, 'cd': 1, 'mv': 7, 'rmdir': 6, 'rm': 4, 'copy': 3, 'dir': 2.

Used when zhoneFileAction set to 'copy'. This will be the source filename of the file to be copied. Prepend a new path if you want to specify a file in a directory different from your current directory.

Used when zhoneFileAction set to 'copy'. This will be the resulting filename of the copied file. Prepend a new path if you want file to be written to a different directory, otherwise it will be written to same directory.

This is a read-write object. If read, it returns your current directory location. If written, it can be used by the 'cd' change directory command in order to specify the new directory, or by the 'dir' command to specify which directory from which to list files. NOTE: If it is written and a 'cd' or 'dir' command not performed, the next time it is read, it will return your current directory.

Total number of bytes available on the disk.

When in the 'datastor' directory, this object returns the number of bytes reserved for Zhone Provisioning. These are the number of bytes reserved for the database expansion.

Zhone File Listing Table. Used to view file information for files resident on Zhone Flash Memory Devices.

Zhone File Listing Entry. Used to view file information for files resident on Zhone Flash Memory Devices.

Index values of rows in this table. Positive ascending numbers starting at 1.

Directory path of file.

Filename.

File privileges.

File size in bytes.

Date and time file last modified.

Access, control and runtime details for managing CPEs connected to Zhone CO devices. Some of these objects will reside on CO devices, while others will reside on CPEs supporting CPE Manager controls.

Object Identity for Zhone Enhanced Status.

Table of Zhone Enhanced Status codes which are used to extend the current IETF definitions found in snmpdef.h. These status codes and corresponding text can be used by both SNMP and CLI. (see below for current error codes): /* Values for error_status */ #define NO_ERROR 0 #define TOO_BIG 1 #define NO_SUCH_NAME 2 #define BAD_VALUE 3 #define READ_ONLY 4 #define GEN_ERR 5 #define NO_ACCESS 6 #define WRONG_TYPE 7 #define WRONG_LENGTH 8 #define WRONG_ENCODING 9 #define WRONG_VALUE 10 #define NO_CREATION 11 #define INCONSISTENT_VALUE 12 #define RESOURCE_UNAVAILABLE 13 #define COMMIT_FAILED 14 #define UNDO_FAILED 15 #define AUTHORIZATION_ERROR 16 #define NOT_WRITABLE 17 #define INCONSISTENT_NAME 18 #define LAST_ERROR 19

Row in the table.

Entry index value.

Status code returned in SNMP packet as a result of issuing getproc_error, nextproc_error, testproc_error or setproc_error. Also used for reporting CLI errors.

Given the zhoneEnhancedStatusCode, this is the corresponding text to be displayed to user in either SNMP or CLI.

This is the Trap information related to the Zhone CPE polling task which exists on the BAN. This task polls all connected Zhone CPE devices by sending SNMP Set messages (zhoneZmsExists=TRUE and zhoneZmsConnectionStatus=ACTIVE) to each device. If a certain number of polls fails for a device, a Trap is sent to the ZMS indicating the Zhone CPE device whose connection has been lost.

This object identity adds a zero(0) for the next to last sub-identifier which should be used for new SNMPv2 Traps.

A Zhone CPE connection in down. The Trap objects specify the location of the Zhone CPE device.

A Zhone CPE connection that has previously been down is now up. The Trap objects specify the location of the Zhone CPE device.

The trap sent when an object in the device datastore is changed

This object identity adds a zero(0) for the next to last sub-identifier which should be used for new SNMPv2 Traps.

An object in the device datastore has changed

ConfigSync has timed-out on the device and has subsequently been reset to a nominal state by the device. Resetting configsync on the device consists of closing the FTP data and control sockets, setting the configsyncstatus to syncerror, cleaning up any pending configsync records, resetting the ConfigSync state machine to the initial state, and throwing a ConfigSyncReset Trap (this trap).

These are traps generated by SNMP, itself, when an error condition is detected.

This object identity adds a zero(0) for the next to last sub-identifier which should be used for new SNMPv2 Traps.

Trap occurs when an error condition is detected in sub agent, causing the Zhone SNMP Master agent to timeout. Shelf and slot in the trap will refer to the subagent card which caused the timeout.

Card Redundancy Traps

This object identity adds a zero(0) for the next to last sub-identifier which should be used for new SNMPv2 Traps.

Trap indicates that the specified card has become active.

Trap if system is provisioned for redundant uplinks but is not redundancy ready.

Bulk Statistics Traps.

This object identity adds a zero(0) for the next to last sub-identifier which should be used for new SNMPv2 Traps.

This notification alerts the manager that the device could not successfully complete the current collection interval. The zhoneBulkStatsSystemOperStatus is included in the trap to indicate the type of failure.

Object identifier under which Zhone ZMS related traps are defined.

The SNMPv2 zero(0) prefix for Zhone ZMS traps.

This is trap is generated when the value of zhoneZmsBlockCli is changed.

This module contains the system generic variables that are complete for the entire system. Note that some functional entities are maintained in their own mib as they will be included only when their functionality is included for that particular Zhone platform.

Description.

Description.

Description.

Description.