Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 03-SNMP Commands | 137.1 KB |
display snmp-agent local-engineid
snmp-agent trap if-mib link extended·
snmp-agent usm-user { v1 | v2c }
l Support of the H3C WA series WLAN access points for commands may vary by AP model. For more information, see Feature Matrix.
l The interface types and the number of interfaces vary by AP model.
l The models listed in this document are not applicable to all regions. Please consult your local sales office for the models applicable to your region.
SNMP Configuration Commands
display snmp-agent community
Syntax
display snmp-agent community [ read | write ]
View
Any view
Default Level
1: Monitor level
Parameters
read: Displays information about SNMP read-only communities.
write: Displays information about SNMP read and write communities.
Description
Use the display snmp-agent community command to display community information for SNMPv1 or SNMPv2c.
Examples
# Display the information for all the communities that have been configured.
<Sysname> display snmp-agent community
Community name: aa
Group name: aa
Acl:2001
Storage-type: nonVolatile
Community name: userv1
Group name: testv1
Storage-type: nonVolatile
Table 1-1 display snmp-agent community command output description
|
Field |
Description |
|
Community name |
Community name. l If a community name is created by using the snmp-agent community command, the community name will be displayed. l If a community name is created by using the snmp-agent usm-user { v1 | v2c } command, the user name will be displayed. |
|
Group name |
SNMP group name. l If a community name is created by using the snmp-agent community command, the group name and the community name are the same, which means the community name will be displayed. l If a community name is created by using the snmp-agent usm-user { v1 | v2c } command, the name of the group to which the user belongs will be displayed. |
|
Acl |
The number of the ACL in use After an ACL is configured, only the Network Management Station (NMS) with the IP address that matches the ACL rule can access the device. |
|
Storage-type |
Storage type, which could be: l volatile: Information will be lost if the system is rebooted l nonVolatile: Information will not be lost if the system is rebooted l permanent: Information will not be lost if the system is rebooted. Modification is permitted, but deletion is forbidden l readOnly: Information will not be lost if the system is rebooted. Read only, that is, no modification, no deletion l other: Other storage types |
display snmp-agent group
Syntax
display snmp-agent group [ group-name ]
View
Any view
Default Level
1: Monitor level
Parameters
group-name: Specifies the SNMP group name, which is a case-sensitive string of 1 to 32 characters.
Description
Use the display snmp-agent group command to display information for the SNMPv3 agent group, including group name, security model, MIB view, storage type, and so on. Absence of the group-name parameter indicates that information for all groups will be displayed.
Examples
# Display the information of all SNMP agent groups.
<Sysname> display snmp-agent group
Group name: groupv3
Security model: v3 noAuthnoPriv
Readview: ViewDefault
Writeview: <no specified>
Notifyview: <no specified>
Storage-type: nonVolatile
Table 1-2 display snmp-agent group command output description
|
Field |
Description |
|
Group name |
SNMP group name |
|
Security model |
Security model of the SNMP group, which can be: authPriv (authentication with privacy), authNoPriv (authentication without privacy), or noAuthNoPriv (no authentication no privacy). |
|
Readview |
The read only MIB view associated with the SNMP group |
|
Writeview |
The writable MIB view associated with the SNMP group |
|
Notifyview |
The notify MIB view associated with the SNMP group, the view with entries that can generate traps |
|
Storage-type |
Storage type, which includes: volatile, nonVolatile, permanent, readOnly, and other. For detailed information, see Table 1-1. |
display snmp-agent local-engineid
Syntax
display snmp-agent local-engineid
View
Any view
Default Level
1: Monitor level
Parameters
None
Description
Use the display snmp-agent local-engineid command to display the local SNMP agent engine ID.
SNMP engine ID identifies an SNMP entity uniquely within an SNMP domain. SNMP engine is an indispensable part of an SNMP entity. It provides the SNMP message allocation, message handling, authentication, and access control.
Examples
# Display the local SNMP agent engine ID.
<Sysname> display snmp-agent local-engineid
SNMP local EngineID: 800007DB7F0000013859
display snmp-agent mib-view
Syntax
display snmp-agent mib-view [ exclude | include | viewname view-name ]
View
Any view
Default Level
1: Monitor level
Parameters
exclude: Displays the subtrees excluded from any MIB view.
include: Displays the subtrees included in any MIB view.
viewname view-name: Displays information about the specified MIB view.
Description
Use the display snmp-agent mib-view command to display MIB view information.
If you do not specify any keyword or keyword and argument combination, the command displays all MIB views.
Examples
# Display all SNMP MIB views of the device.
<Sysname> display snmp-agent mib-view
View name:ViewDefault
MIB Subtree:iso
Subtree mask:
Storage-type: nonVolatile
View Type:included
View status:active
View name:ViewDefault
MIB Subtree:snmpUsmMIB
Subtree mask:
Storage-type: nonVolatile
View Type:excluded
View status:active
View name:ViewDefault
MIB Subtree:snmpVacmMIB
Subtree mask:
Storage-type: nonVolatile
View Type:excluded
View status:active
View name:ViewDefault
MIB Subtree:snmpModules.18
Subtree mask:
Storage-type: nonVolatile
View Type:excluded
View status:active
The output shows that the ViewDefault view has four subtrees. All MIB objects in the iso subtree are accessible except for the MIB objects in the snmpUsmMIB, snmpVacmMIB, and snmpModules.18 subtrees.
Table 1-3 display snmp-agent mib-view command output description
|
Field |
Description |
|
View name |
MIB view name |
|
MIB Subtree |
A MIB subtree covered by the MIB view |
|
Subtree mask |
MIB subtree mask |
|
Storage-type |
Type of the medium where the subtree view is stored |
|
View Type |
Access privilege for the MIB subtree in the MIB view: l Included – All objects in the MIB subtree are accessible in the MIB view l Excluded – None of the objects in the MIB subtree is accessible in the MIB view |
|
View status |
The status of the MIB view |
display snmp-agent statistics
Syntax
display snmp-agent statistics
View
Any view
Default Level
1: Monitor level
Parameters
None
Description
Use the display snmp-agent statistics command to display SNMP statistics.
Examples
# Display the statistics on the current SNMP.
<Sysname> display snmp-agent statistics
1684 Messages delivered to the SNMP entity
5 Messages which were for an unsupported version
0 Messages which used a SNMP community name not known
0 Messages which represented an illegal operation for the community supplied
0 ASN.1 or BER errors in the process of decoding
1679 Messages passed from the SNMP entity
0 SNMP PDUs which had badValue error-status
0 SNMP PDUs which had genErr error-status
0 SNMP PDUs which had noSuchName error-status
0 SNMP PDUs which had tooBig error-status (Maximum packet size 1500)
16544 MIB objects retrieved successfully
2 MIB objects altered successfully
7 GetRequest-PDU accepted and processed
7 GetNextRequest-PDU accepted and processed
1653 GetBulkRequest-PDU accepted and processed
1669 GetResponse-PDU accepted and processed
2 SetRequest-PDU accepted and processed
0 Trap PDUs accepted and processed
0 Alternate Response Class PDUs dropped silently
0 Forwarded Confirmed Class PDUs dropped silently
Table 1-4 display snmp-agent statistics command output description
|
Field |
Description |
|
Messages delivered to the SNMP entity |
Number of packets delivered to the SNMP agent |
|
Messages which were for an unsupported version |
Number of packets from a device with an SNMP version that is not supported by the current SNMP agent |
|
Messages which used a SNMP community name not known |
Number of packets that use an unknown community name |
|
Messages which represented an illegal operation for the community supplied |
Number of packets carrying an operation that the community has no right to perform |
|
ASN.1 or BER errors in the process of decoding |
Number of packets with ASN.1 or BER errors in the process of decoding |
|
Messages passed from the SNMP entity |
Number of packets sent by an SNMP agent |
|
SNMP PDUs which had badValue error-status |
Number of SNMP PDUs with a badValue error |
|
SNMP PDUs which had genErr error-status |
Number of SNMP PDUs with a genErr error |
|
SNMP PDUs which had noSuchName error-status |
Number of PDUs with a noSuchName error |
|
SNMP PDUs which had tooBig error-status (Maximum packet size 1500) |
Number of PDUs with a tooBig error (the maximum packet size is 1,500 bytes) |
|
MIB objects retrieved successfully |
Number of MIB objects that have been successfully retrieved |
|
MIB objects altered successfully |
Number of MIB objects that have been successfully modified |
|
GetRequest-PDU accepted and processed |
Number of get requests that have been received and processed |
|
GetNextRequest-PDU accepted and processed |
Number of getNext requests that have been received and processed |
|
GetBulkRequest-PDU accepted and processed |
Number of getBulk requests that have been received and processed |
|
GetResponse-PDU accepted and processed |
Number of get responses that have been received and processed |
|
SetRequest-PDU accepted and processed |
Number of set requests that have been received and processed |
|
Trap PDUs accepted and processed |
Number of traps that have been received and processed |
|
Alternate Response Class PDUs dropped silently |
Number of dropped response packets |
|
Forwarded Confirmed Class PDUs dropped silently |
Number of forwarded packets that have been dropped |
display snmp-agent sys-info
Syntax
display snmp-agent sys-info [ contact | location | version ] *
View
Any view
Default Level
1: Monitor level
Parameters
contact: Displays the contact information of the current network administrator.
location: Displays the location information of the current device.
version: Displays the version of the current SNMP agent.
Description
Use the display snmp-agent sys-info command to display the current SNMP system information.
If no keyword is specified, all SNMP agent system information will be displayed.
Examples
# Display the current SNMP agent system information.
<Sysname> display snmp-agent sys-info
The contact person for this managed node:
Hangzhou H3C Technologies Co., Ltd.
The physical location of this node:
Hangzhou, China
SNMP version running in the system:
SNMPv3
display snmp-agent trap queue
Syntax
display snmp-agent trap queue
View
Any view
Default Level
1: Monitor level
Parameters
None
Description
Use the display snmp-agent trap queue command to display basic information of the trap queue, including trap queue name, queue length and the number of traps in the queue currently.
Related commands: snmp-agent trap life and snmp-agent trap queue-size.
Examples
# Display the current configuration and usage of the trap queue.
<Sysname> display snmp-agent trap queue
Queue name: SNTP
Queue size: 100
Message number: 6
Table 1-5 display snmp-agent trap queue command output description
|
Field |
Description |
|
Queue name |
Trap queue name |
|
Queue size |
Trap queue size |
|
Message number |
Number of traps in the trap queue currently |
display snmp-agent trap-list
Syntax
display snmp-agent trap-list
View
Any view
Default Level
1: Monitor level
Parameters
None
Description
Use the display snmp-agent trap-list command to display the modules that can generate traps and whether their trap sending is enabled or not. If a module comprises multiple sub-modules, then as long as one sub-module has the sending of traps enabled, the whole module will be displayed as being enabled with the trap sending.
Related commands: snmp-agent trap enable.
Examples
# Display the modules that can generate traps and whether their trap sending is enabled or not.
<Sysname> display snmp-agent trap-list
configuration trap enable
flash trap enable
standard trap enable
system trap enable
wlan trap enable
Enable traps: 5; Disable traps: 0
If a module can generate traps, its trap function status is enable; if not, disable. You can enable or disable the trap function for a module at the command line interface (CLI).
display snmp-agent usm-user
Syntax
display snmp-agent usm-user [ engineid engineid | username user-name | group group-name ] *
View
Any view
Default Level
1: Monitor level
Parameters
engineid engineid: Displays SNMPv3 user information for a specified engine ID, where engineid indicates the SNMP engine ID. When an SNMPv3 user is created, the system records the current local SNMP entity engine ID of the device. If the engine ID is modified, the user becomes invalid and will become valid again if the engine ID is restored.
username user-name: Displays SNMPv3 user information for a specified user name. It is a case sensitive string of 1 to 32 characters.
group group-name: Displays SNMPv3 user information for a specified SNMP group name. It is a case sensitive string of 1 to 32 characters.
Description
Use the display snmp-agent usm-user command to display SNMPv3 user information.
Examples
# Display SNMPv3 information for all created users.
<Sysname> display snmp-agent usm-user
User name: userv3
Group name: mygroupv3
Engine ID: 800063A203000FE240A1A6
Storage-type: nonVolatile
UserStatus: active
User name: userv3code
Group name: groupv3code
Engine ID: 800063A203000FE240A1A6
Storage-type: nonVolatile
UserStatus: active
Table 1-6 display snmp-agent usm-user command output description
|
Field |
Description |
|
User name |
SNMP user name |
|
Group name |
SNMP group name |
|
Engine ID |
Engine ID for an SNMP entity |
|
Storage-type |
Storage type, which can be the following: l volatile l nonvolatile l permanent l readOnly l other See Table 1-1 for details. |
|
UserStatus |
SNMP user status |
enable snmp trap updown
Syntax
enable snmp trap updown
undo enable snmp trap updown
View
Interface view
Default Level
2: System level
Parameters
None
Description
Use the enable snmp trap updown command to enable the trap function for interface state changes on an interface.
Use the undo enable snmp trap updown command to disable the trap function for interface state changes on an interface.
By default, the trap function for interface state change is enabled.
For an interface to generate linkUp/linkDown traps when its state changes, you must also enable the linkUp/linkDown trap function globally by using the enable snmp trap updown command.
Related commands: snmp-agent target-host and snmp-agent trap enable.
Examples
# Enable port Ethernet 1/0/1 to send linkUp/linkDown SNMP traps in the community public.
<Sysname> system-view
[Sysname] snmp-agent trap enable
[Sysname] snmp-agent target-host trap address udp-domain 10.1.1.1 params securityname public
[Sysname] interface ethernet 1/0/1
[Sysname-Ethernet1/0/1] enable snmp trap updown
snmp-agent
Syntax
snmp-agent
undo snmp-agent
View
System view
Default Level
3: Manage level
Parameters
None
Description
Use the snmp-agent command to enable SNMP agent.
Use the undo snmp-agent command to disable SNMP agent.
By default, SNMP agent is disabled.
You can enable SNMP agent through any commands that begin with snmp-agent.
Examples
# Enable SNMP agent on the device.
<Sysname> system-view
[Sysname] snmp-agent
snmp-agent calculate-password
Syntax
snmp-agent calculate-password plain-password mode { 3desmd5 | 3dessha | md5 | sha } { local-engineid | specified-engineid engineid }
View
System view
Default Level
3: Manage level
Parameters
plain-password: Specifies a plain text authentication or privacy key.
mode: Specifies authentication and privacy algorithms. Select a mode option, depending on the authentication and privacy algorithm you are configuring with the snmp-agent usm-user v3 command. The three privacy algorithms Advanced Encryption Standard (AES), Triple Data Encryption Standard (3DES), and Data Encryption Standard (DES) are in descending order of security strength. Higher security means more complex implementation mechanism and lower speed. DES is enough to meet general requirements. The Message-Digest Algorithm 5 (MD5) and Secure Hash Algorithm (SHA-1) are the two authentication algorithms. MD5 is faster than SHA-1, while SHA-1 provides higher security than MD5.
l 3desmd5: Converts the plain text privacy key to an encrypted key for 3DES encryption used together with MD5 authentication.
l 3dessha: Converts the plain text privacy key to an encrypted key for 3DES encryption used together with SHA-1 authentication.
l md5: Converts the plain text authentication key to an encrypted key for MD5 authentication, or converts the plain text privacy key to an encrypted key for AES or DES encryption used in conjunction with MD5.
l sha: Converts the plain text authentication key to an encrypted key for SHA-1 authentication, or converts the plain text privacy key to an encrypted key for AES or DES encryption used in conjunction with SHA-1 authentication.
local-engineid: Uses the local engine ID to calculate the encrypted key. For engine ID-related configuration, see the snmp-agent local-engineid command.
specified-engineid: Uses a user-defined engine ID to calculate the encrypted key.
engineid: Sets the engine ID string, an even number of hexadecimal characters, which ranges from 10 to 64. Its length must not be an odd number, and the all-zero and all-F strings are invalid.
Description
Use the snmp-agent calculate-password command to convert a plain text key to an encrypted key for authentication or encryption.
This command helps you calculate encrypted authentication and privacy keys for SNMPv3 users that use encrypted authentication and privacy keys. To create an SNMPv3 user, see the snmp-agent usm-user v3 command.
Enable SNMP before you execute the snmp-agent calculate-password command.
The encrypted key converted for SHA authentication is a string of 40 hexadecimal characters. For an authentication key, all of the 40 hexadecimal characters are valid. For a privacy key, only the first 32 hexadecimal characters are valid.
The converted key is valid only under the specified engine ID.
Related commands: snmp-agent usm-user v3.
Examples
# Use local engine ID to convert the plain text key authkey to an encrypted key for MD5 authentication.
<Sysname> system-view
[Sysname] snmp-agent calculate-password authkey mode md5 local-engineid
The secret key is: 09659EC5A9AE91BA189E5845E1DDE0CC
snmp-agent community
Syntax
snmp-agent community { read | write } community-name [ acl acl-number | mib-view view-name ] *
undo snmp-agent community { read | write } community-name
View
System view
Default Level
3: Manage level
Parameters
read: Assigns the specified community the read only access to MIB objects. A read-only community can only inquire MIB information.
write: Assigns the specified community the read and write access to MIB objects. A read and write community can configure MIB information.
community-name: Sets a community name, a string of 1 to 32 characters.
acl acl-number: Applies a basic ACL to filter NMSs by source IP address. The acl-number argument represents a basic ACL number in the range of 2,000 to 2,999.
mib-view view-name: Specifies the MIB view available for the community. The view-name argument represents a MIB view name, which is a string of 1 to 32 characters. A MIB view represents a set of accessible MIB objects. If no MIB view is specified, the specified community can access the MIB objects in the default view ViewDefault. The system creates this default view when the SNMP agent is enabled. To create a MIB view, use the snmp-agent mib-view command.
Description
Use the snmp-agent community command to configure an SNMP community.
Use the undo snmp-agent community command to delete a specified community.
This command is for SNMPv1 and SNMPv2c.
A community comprises NMSs and SNMP agents, and is identified by a community name. When devices in a community communicate with each other, they use the community name for authentication. An NMS and an SNMP agent can access each other only when they are configured with the same community name. Typically, public is used as the read-only community name, and private is used as the read and write community name. To improve security, assign your SNMP communities a name other than public and private.
To ensure that the MIB objects are accessible only to a specific NMS, use a basic ACL to identify the source IP address of the NMS. To set the range of the MIB objects available for the community, use a MIB view.
Related commands: snmp-agent mib-view.
Examples
# Create a read-only community and name it readacess.
<Sysname> system-view
[Sysname] snmp-agent sys-info version v1 v2c
[Sysname] snmp-agent community read readaccess
l Set the SNMP version on the NMS to SNMPv1 or SNMPv2c
l Fill in the read-only community name readaccess
l Establish a connection, and the NMS can perform read-only operations to the MIB objects in the default view on the device
# Create a read and write community and name it writeaccess, allowing only the NMS with the IP address of 1.1.1.1 to configure the values of the agent MIB objects by using this community name; other NMSs are not allowed to perform the write operations by using this community name.
<Sysname> system-view
[Sysname] acl number 2001
[Sysname-acl-basic-2001] rule permit source 1.1.1.1 0.0.0.0
[Sysname-acl-basic-2001] rule deny source any
[Sysname-acl-basic-2001] quit
[Sysname] snmp-agent sys-info version v2c
[Sysname] snmp-agent community write writeaccess acl 2001
l Set the IP address of the NMS to 1.1.1.1
l Set the SNMP version on the NMS to SNMPv2c
l Fill in the write community name writeaccess; namely, the NMS can perform read-only operations to the MIB objects in the default view on the device
# Create a read and write community and name it wr-sys-acc. The NMS can perform the read and write operations to the MIB objects of the system subtree (with the OID of 1.3.6.1.2.1.1).
<Sysname> system-view
[Sysname] snmp-agent sys-info version v1 v2c
[Sysname] undo snmp-agent mib-view ViewDefault
[Sysname] snmp-agent mib-view included test system
[Sysname] snmp-agent community write wr-sys-acc mib-view test
l Set the SNMP version on the NMS to SNMPv1 or SNMPv2c
l Fill in the write community name wr-sys-acc
l Establish a connection, and the NMS can perform read and write operations to the MIB objects in system view on the device
snmp-agent group
Syntax
l SNMPv1 and SNMP v2c:
snmp-agent group { v1 | v2c } group-name [ read-view read-view ] [ write-view write-view ] [ notify-view notify-view ] [ acl acl-number ]
undo snmp-agent group { v1 | v2c } group-name
l SNMPv3:
snmp-agent group v3 group-name [ authentication | privacy ] [ read-view read-view ] [ write-view write-view ] [ notify-view notify-view ] [ acl acl-number ]
undo snmp-agent group v3 group-name [ authentication | privacy ]
View
System view
Default Level
3: Manage level
Parameters
v1: SNMPv1.
v2c: SNMPv2c.
v3: SNMPv3.
group-name: Group name, a string of 1 to 32 characters.
authentication: Specifies the security model of the SNMPv3 group to be authentication only (without privacy).
privacy: Specifies the security model of the SNMPv3 group to be authentication and privacy.
read-view read-view: Specifies a read-only MIB view. The read-view represents a MIB view, which is a string of 1 to 32 characters. The users in the specified group have read only access to the objects included in the MIB view. The default read view is ViewDefault.
write-view write-view: Specifies a read and write MIB view. The write-view argument represents a MIB view, which is a string of 1 to 32 characters. The users in the specified group have read and write access to the objects included in the MIB view. By default, no write view is configured, which means the NMS cannot perform the write operations to all MIB objects on the device.
notify-view notify-view: Specifies a trap MIB view. The notify-view argument represents a MIB view, which is a string of 1 to 32 characters. The system sends traps to the users in the specified group for the objects included in the MIB view. By default, no notify view is configured, which means the agent does not send traps to the NMS.
acl acl-number: Specifies a basic ACL by its number, which ranges from 2000 to 2999. This ACL filters NMSs by source IP address. In other words, you can configure to allow or prohibit SNMP packets with a specific source IP address to restrict the intercommunication between the NMS and the agent.
Description
Use the snmp-agent group command to configure an SNMP group and specify its access right.
Use the undo snmp-agent group command to delete an SNMP group.
By default, SNMP groups configured by the snmp-agent group v3 command use a no-authentication-no-privacy security model.
An SNMP group defines security model, access right, and so on. A user in this SNMP group has all these public properties.
Related commands: snmp-agent mib-view and snmp-agent usm-user.
Examples
# Create an SNMP group group1 on an SNMPv3 enabled device, no authentication, no privacy.
<Sysname> system-view
[Sysname] snmp-agent group v3 group1
snmp-agent local-engineid
Syntax
snmp-agent local-engineid engineid
undo snmp-agent local-engineid
View
System view
Default Level
3: Manage level
Parameters
engineid: Engine ID, an even number of hexadecimal characters, which ranges from 10 to 64. Its length must not be an odd number, and the all-zero and all-F strings are invalid.
Description
Use the snmp-agent local-engineid command to configure a local engine ID for an SNMP entity.
Use the undo snmp-agent local-engineid command to restore the default local engine ID.
By default, the engine ID of a device is the combination of company ID and device ID. Device ID varies by product; it could be an IP address, a MAC address, or a self-defined string of hexadecimal numbers.
An engine ID has two functions:
l For all devices managed by one NMS, each device needs a unique engine ID to identify the SNMP agent. By default, each device has an engine ID. The network administrator has to ensure that there is no repeated engine ID within an SNMP domain.
l In SNMPv3, the user name and cipher text password are associated with the engine ID. Therefore, if the engine ID changes, the user name and cipher text password configured under the engine ID become invalid.
If the newly configured engine ID is not the same as the one used for creating the USM user, the user is invalid.
Related commands: snmp-agent usm-user.
Examples
# Configure the local engine ID as 123456789A.
<Sysname> system-view
[Sysname] snmp-agent local-engineid 123456789A
snmp-agent log
Syntax
snmp-agent log { all | get-operation | set-operation }
undo snmp-agent log { all | get-operation | set-operation }
View
System view
Default Level
3: Manage level
Parameters
all: Enables logging of SNMP GET and SET operations.
get-operation: Enables logging of SNMP GET operation.
set-operation: Enables logging of SNMP SET operation.
Description
Use the snmp-agent log command to enable SNMP logging.
Use the undo snmp-agent log command to restore the default.
By default, SNMP logging is disabled.
If a specified SNMP logging is enabled, when NMS performs a specified operation on SNMP agent, the latter records the operation-related information and saves it to the information center. With parameters for the information center set, output rules of the SNMP logs are decided (that is, whether logs are permitted to output and the output destinations).
Examples
# Enable logging of SNMP GET operation.
<Sysname> system-view
[Sysname] snmp-agent log get-operation
# Enable logging of SNMP SET operation.
<Sysname> system-view
[Sysname] snmp-agent log set-operation
snmp-agent mib-view
Syntax
snmp-agent mib-view { excluded | included } view-name oid-tree [ mask mask-value ]
undo snmp-agent mib-view view-name
View
System view
Default Level
3: Manage level
Parameters
excluded: Denies access to any nodes in the specified MIB subtree.
included: Permits access to the nodes in the specified MIB subtree.
view-name: Specify a view name, which is a string of 1 to 32 characters.
oid-tree: Specifies a MIB subtree. It can only be an OID string, such as 1.4.5.3.1, or an object name string, such as system. An OID is made up of a series of integers. It marks the position of a node in the MIB tree and uniquely identifies a MIB object.
mask mask-value: Subtree mask, which ranges from 1 to 32 hexadecimal digits. It must be an even number. The subtree mask decides a view subtree, together with the MIB subtree.
Description
Use the snmp-agent mib-view command to create or update MIB view information.
Use the undo snmp-agent mib-view command to delete a MIB view.
By default, the system creates the ViewDefault view when the SNMP agent is enabled. This default view covers four MIB subtrees: the iso subtree is accessible, the snmpUsmMIB, snmpVacmMIB, and snmpModules.18 subtrees are inaccessible.
A MIB view presents a set of MIB objects (or MIB object hierarchies) with certain access privilege. Except the subtrees in the default MIB view, you can create up to 16 view-name oid-tree pairs, and define a MIB subtree in different views.
To display the default view, use the display snmp-agent mib-view command. In the default view, all MIB objects in the iso subtree but the snmpUsmMIB, snmpVacmMIB, and snmpModules.18 subtrees are accessible.
You can delete the default view with the undo snmp-agent mib-view command. However, be cautious with the operation, because it blocks access to any MIB object on the device from NMSs that use the default view.
Related commands: snmp-agent group.
Examples
# Include the mib-2 (OID 1.3.6.1) subtree in the mibtest view, exclude the ip subtree from the mibtest view.
<Sysname> system-view
[Sysname] snmp-agent mib-view included mibtest 1.3.6.1
[Sysname] snmp-agent mib-view excluded mibtest ip
[Sysname] snmp-agent community read public mib-view mibtest
An SNMPv1 NMS in the public community can query the objects in the mib-2 subtree, but not any objects (for example, the ipForwarding or ipDefaultTTL node) in the ip subtree.
snmp-agent packet max-size
Syntax
snmp-agent packet max-size byte-count
undo snmp-agent packet max-size
View
System view
Default Level
3: Manage level
Parameters
byte-count: Maximum number of bytes of an SNMP packet that can be received or sent by an agent, which ranges from 484 to 17,940 and defaults to 1,500 bytes.
Description
Use the snmp-agent packet max-size command to set the maximum size (in bytes) of SNMP packets that the SNMP agent can receive or send.
Use the undo snmp-agent packet max-size command to restore the default packet size.
By default, the maximum size of SNMP packets that the SNMP can receive or send is 1,500 bytes.
Use the snmp-agent packet max-size command to set the Maximum size (in bytes) of SNMP packets that the SNMP agent can receive or send.
Use the undo snmp-agent packet max-size command to restore the default packet size.
Examples
# Set the maximum size of SNMP packets that the SNMP agent can receive or send to 1,024 bytes.
<Sysname> system-view
[Sysname] snmp-agent packet max-size 1024
snmp-agent sys-info
Syntax
snmp-agent sys-info { contact sys-contact | location sys-location | version { all | { v1 | v2c | v3 }* } }
undo snmp-agent sys-info { contact | location | version { all | { v1 | v2c | v3 }* } }
View
System view
Default Level
3: Manage level
Parameters
contact sys-contact: A string of 1 to 200 characters that describes the contact information for system maintenance.
location sys-location: A string of 1 to 200 characters that describes the location of the device.
version: The SNMP version in use.
l all: Specifies SNMPv1, SNMPv2c, and SNMPv3.
l v1: SNMPv1.
l v2c: SNMPv2c.
l v3: SNMPv3.
Description
Use the snmp-agent sys-info command to configure system information, including the contact information, the location, and the SNMP version in use.
Use the undo snmp-agent sys-info contact and undo snmp-agent sys-info location command to restore the default.
Use the undo snmp-agent sys-info version command to disable use of the SNMP function of the specified version.
By default, the location information is Hangzhou China, version is SNMPv3, and the contact is Hangzhou H3C Technologies Co., Ltd.
The device can process the SNMP packets of the corresponding version only if SNMP of a specific version is enabled. If SNMPv1 is enabled, the device will drop the received SNMPv2c packets; if SNMPv2c is enabled, the device will drop the received SNMPv1 packets. To enable the device to communicate with different NMSs, you can enable SNMP of different versions on a device.
Related commands: display snmp-agent sys-info.
Network maintenance engineers can use the system contact information to get in touch with the manufacturer in case of network failures. The system location information is a management variable under the system branch as defined in RFC1213-MIB, identifying the location of the managed object.
Examples
# Configure the contact information as “Dial System Operator at beeper # 27345”.
<Sysname> system-view
[Sysname] snmp-agent sys-info contact Dial System Operator at beeper # 27345
snmp-agent target-host
Syntax
snmp-agent target-host trap address udp-domain { ip-address | ipv6 ipv6-address } [ udp-port port-number ] params securityname security-string [ v1 | v2c | v3 [ authentication | privacy ] ]
undo snmp-agent target-host trap address udp-domain { ip-address | ipv6 ipv6-address } params securityname security-string
View
System view
Default Level
3: Manage level
Parameters
trap: Specifies the host to be the target host which will receive traps and notifications from the device.
address: Specifies the destination IP address in the SNMP messages sent from the device.
udp-domain: Indicates that the trap is transmitted using UDP.
ip-address: The IPv4 address of the trap target host.
ipv6 ipv6-address: Specifies the IPv6 address of the trap target host.
udp-port port-number: Specifies the number of the port on the target host to receive traps.
params securityname security-string: Specifies the authentication related parameter, which is an SNMPv1 or SNMPv2c community name or an SNMPv3 user name, a string of 1 to 32 characters.
v1: SNMPv1. This keyword must be the same as the SNMP version on the NMS; otherwise, the NMS cannot receive any trap.
v2c: SNMPv2c. This keyword must be the same as the SNMP version on the NMS; otherwise, the NMS cannot receive any trap.
v3: SNMPv3. This keyword must be the same as the SNMP version on the NMS; otherwise, the NMS cannot receive any trap.
authentication: Specifies the security model to be authentication without privacy. Authentication is a process to check whether the packet is integral and whether it has been tampered. You need to configure the authentication password when creating an SNMPv3 user.
privacy: Specifies the security model to be authentication with privacy. Privacy is to encrypt the data part of a packet to prevent it from being intercepted. You need to configure the authentication password and privacy password when creating an SNMPv3 user.
Description
Use the snmp-agent target-host command to configure the related settings for a trap target host.
Use the undo snmp-agent target-host command to remove the current settings.
According to the networking requirements, you can use this command for multiple times to configure different settings for a target host, enabling the device to send trap messages to different NMSs.
l If udp-port port-number is not specified, port number 162 is used.
l If the key words v1, v2 and v3 are not specified, v1 is used.
l If the key words authentication and privacy are not specified, the authentication mode is no authentication, no privacy.
Related commands: enable snmp trap updown, snmp-agent trap enable, snmp-agent trap source, and snmp-agent trap life.
Examples
# Enable the device to send SNMPv1 traps to 10.1.1.1, using the community name of public.
<Sysname> system-view
[Sysname] snmp-agent trap enable standard
[Sysname] snmp-agent target-host trap address udp-domain 10.1.1.1 params securityname public
snmp-agent trap enable
Syntax
snmp-agent trap enable [ configuration | flash | standard [ authentication | coldstart | linkdown | linkup | warmstart ]* | system | wlan ]
undo snmp-agent trap enable [ configuration | flash |standard [ authentication | coldstart | linkdown | linkup | warmstart ]* | system | wlan ]
View
System view
Default Level
3: Manage level
Parameters
configuration: Configuration traps.
flash: FLASH-related traps.
standard: Standard traps.
l authentication: Authentication failure traps in the event of authentication failure.
l coldstart: Coldstart traps when the device restarts.
l linkdown: Linkdown traps when the port is link down. It should be configured globally.
l linkup: Linkup traps when the port is link up. It should be configured globally.
l warmstart: Warmstart traps when the SNMP restarts.
system: H3C-SYS-MAN-MIB (a private MIB) traps.
wlan: Traps of the WLAN module.
Description
Use the snmp-agent trap enable command to enable the trap function globally.
Use the undo snmp-agent trap enable command to disable the trap function globally.
By default, the trap function is enabled globally.
Only after the trap function is enabled can each module generate corresponding traps.
To enable an interface to generate linkUp/linkDown traps when its state changes, you need to enable the linkUp/linkDown trap function on the interface and globally. Use the enable snmp trap updown command to enable this function on an interface, and use the snmp-agent trap enable [ standard [ linkdown | linkup ] * ] command to enable this function globally.
Related commands: snmp-agent target-host and enable snmp trap updown.
Examples
# Enable the device to send SNMP authentication failure packets to 10.1.1.1, using the community name public.
<Sysname> system-view
[Sysname] snmp-agent target-host trap address udp-domain 10.1.1.1 params securityname public
[Sysname] snmp-agent trap enable standard authentication
snmp-agent trap if-mib link extended
Syntax
snmp-agent trap if-mib link extended
undo snmp-agent trap if-mib link extended
View
System view
Default Level
3: Manage level
Parameters
None
Description
Use the snmp-agent trap if-mib link extended command to extend the standard linkUp/linkDown traps defined in RFC. An extended linkUp/linkDown trap is the standard linkUp/linkDown trap appended with the interface description and interface type information.
Use the undo snmp-agent trap if-mib link extended command to restore the default.
By default, standard linkUp/linkDown traps defined in RFC are used.
l A standard linkUp trap is in the following format:
#Apr 24 11:48:04:896 2008 Sysname IFNET/4/INTERFACE UPDOWN:
Trap 1.3.6.1.6.3.1.1.5.4<linkUp>: Interface 983555 is Up, ifAdminStatus is 1, ifOperStatus is 1
l An extended linkUp trap is in the following format:
#Apr 24 11:43:09:896 2008 Sysname IFNET/4/INTERFACE UPDOWN:
Trap 1.3.6.1.6.3.1.1.5.4<linkUp>: Interface 983555 is Up, ifAdminStatus is 1, ifOperStatus is 1, ifDescr is Ethernet1/1, ifType is 6
l A standard linkDown trap is in the following format:
#Apr 24 11:47:35:224 2008 Sysname IFNET/4/INTERFACE UPDOWN:
Trap 1.3.6.1.6.3.1.1.5.3<linkDown>: Interface 983555 is Down, ifAdminStatus is 2, ifOperStatus is 2
l An extended linkDown trap is in the following format:
#Apr 24 11:42:54:314 2008 Sysname IFNET/4/INTERFACE UPDOWN:
Trap 1.3.6.1.6.3.1.1.5.3<linkDown>: Interface 983555 is Down, ifAdminStatus is 2, ifOperStatus is 2, ifDescr is Ethernet1/1, ifType is 6
The format of an extended linkup/ linkDown trap is the standard format followed with the ifDescr and ifType information, facilitating problem location.
After this command is configured, the device sends extended linkUp/linkDown traps. If the extended messages are not supported on NMS, the device may not be able to resolve the messages.
Examples
# Extend standard linkUp/linkDown traps defined in RFC.
[Sysname] snmp-agent trap if-mib link extended
snmp-agent trap life
Syntax
snmp-agent trap life seconds
undo snmp-agent trap life
View
System view
Default Level
3: Manage level
Parameters
seconds: Timeout time, in the range 1 to 2,592,000 seconds.
Description
Use the snmp-agent trap life command to configure the holding time of the traps in the queue. Traps will be discarded when the holding time expires.
Use the undo snmp-agent trap life command to restore the default holding time of the traps in the queue.
By default, the holding time of SNMP traps in the queue is 120 seconds.
The SNMP module sends traps in queues. As soon as the traps are saved in the trap queue, a timer is started. If traps are not sent out until the timer times out (namely, the holding time configured by using this command expires), the system removes the traps from the trap sending queue.
Related commands: snmp-agent trap enable and snmp-agent target-host.
Examples
# Configure the holding time of traps in the queue as 60 seconds.
<Sysname> system-view
[Sysname] snmp-agent trap life 60
snmp-agent trap queue-size
Syntax
snmp-agent trap queue-size size
undo snmp-agent trap queue-size
View
System view
Default Level
3: Manage level
Parameters
size: Number of traps that can be stored in the trap sending queue, in the range 1 to 1,000.
Description
Use the snmp-agent trap queue-size command to configure the size of the trap queue.
Use the undo snmp-agent trap queue-size command to restore the default queue size.
By default, up to 100 traps can be stored in the trap queue.
After traps are generated, they will be saved into the trap sending queue. The size of the queue determines the maximum number of the traps that can be stored in the queue. When the size of the trap sending queue reaches the configured value, the newly generated traps are saved into the queue, and the earliest ones are discarded.
Related commands: snmp-agent trap enable, snmp-agent target-host, and snmp-agent trap life.
Examples
# Set the maximum number of traps that can be stored in the trap sending queue to 200.
<Sysname> system-view
[Sysname] snmp-agent trap queue-size 200
snmp-agent trap source
Syntax
snmp-agent trap source interface-type interface-number
undo snmp-agent trap source
View
System view
Default Level
3: Manage level
Parameters
interface-type interface-number: Specifies the type and number of a Layer 3 interface.
Description
Use the snmp-agent trap source command to specify the source IP address contained in the trap.
Use the undo snmp-agent trap source command to restore the default.
By default, SNMP chooses the IP address of an interface to be the source IP address of the trap.
Upon the execution of this command, the system uses the primary IP address of the specified interface as the source IP address of the traps, and the NMS will use this IP address to uniquely identify the agent. Even if the agent sends out traps through different interfaces, the NMS uses this IP address to filter all traps sent from the agent.
Use this command to trace a specific event by the source IP address of a trap.
Before you can configure the IP address of a particular interface as the source IP address of the trap, ensure that the interface already exists and that it has a legal IP address. Otherwise, if the configured interface does not exist, the configurations will fail; if the specified IP address is illegal, the configuration will be invalid. After a legal IP address is configured for the interface, the configuration becomes valid automatically.
Related commands: snmp-agent trap enable and snmp-agent target-host.
Examples
# Configure the IP address of VLAN-interface 1 as the source address of traps.
<Sysname> system-view
[Sysname] snmp-agent trap source Vlan-interface 1
snmp-agent usm-user { v1 | v2c }
Syntax
snmp-agent usm-user { v1 | v2c } user-name group-name [ acl acl-number ]
undo snmp-agent usm-user { v1 | v2c } user-name group-name
View
System view
Default Level
3: Manage level
Parameters
v1: The configured user name should be applied in the SNMPv1 networking environment. If the agent and the NMS use SNMPv1 packets to communicate with each other, this keyword is needed.
v2c: The configured user name should be applied in the SNMPv2c networking environment. If the agent and the NMS use SNMPv2c packets to communicate with each other, this keyword is needed.
user-name: User name, a string of 1 to 32 characters. It is case sensitive.
group-name: Group name, a string of 1 to 32 characters. It is case sensitive.
acl acl-number: Associates a basic ACL with the user. acl-number is in the range 2000 to 2999. By using a basic ACL, you can restrict the source IP address of SNMP packets, that is, you can configure to allow or prohibit SNMP packets with a specific source IP address, so as to allow or prohibit the specified NMS to access the agent by using this user name.
Use the snmp-agent usm-user { v1 | v2c } command to add a user to an SNMP group.
Use the undo snmp-agent usm-user { v1 | v2c } command to delete a user from an SNMP group.
As defined in the SNMP protocol, in SNMPv1 and SNMPv2c networking applications, the NMS and the agent use community name to authenticate each other; in SNMPv3 networking applications, they use user name to authenticate each other. If you prefer using the user name in the authentication, the device supports configuration of SNMPv1 and SNMPv2c users. Creating an SNMPv1 or SNMPv2c user equals adding of a new read-only community name. After you add the user name into the read-only community name field of the NMS, the NMS can establish SNMP connection with the device.
To make the configured user take effect, create an SNMP group first.
Related commands: snmp-agent group, snmp-agent community, and snmp-agent usm-user v3.
Examples
# Create a v2c user userv2c in group readCom.
<Sysname> system-view
[Sysname] snmp-agent sys-info version v2c
[Sysname] snmp-agent group v2c readCom
[Sysname] snmp-agent usm-user v2c userV2c readCom
l Set the SNMP version on the NMS to SNMPv2c
l Fill in the read community name userv2c, and then the NMS can access the agent
# Create a v2c user userv2c in group readCom, allowing only the NMS with the IP address of 1.1.1.1 to access the agent by using this user name; other NMSs are not allowed to access the agent by using this user name.
<Sysname> system-view
[Sysname] acl number 2001
[Sysname-acl-basic-2001] rule permit source 1.1.1.1 0.0.0.0
[Sysname-acl-basic-2001] rule deny source any
[Sysname-acl-basic-2001] quit
[Sysname] snmp-agent sys-info version v2c
[Sysname] snmp-agent group v2c readCom
[Sysname] snmp-agent usm-user v2c userv2c readCom acl 2001
l Set the IP address of the NMS to 1.1.1.1
l Set the SNMP version on the NMS to SNMPv2c
l Fill in both the read community and write community options with userv2c, and then the NMS can access the agent.
snmp-agent usm-user v3
Syntax
snmp-agent usm-user v3 user-name group-name [ cipher [ ] authentication-mode { md5 | sha } auth-password [ privacy-mode { 3des | aes128 | des56 } priv-password ] ] [ acl acl-number ]
undo snmp-agent usm-user v3 user-name group-name { local | engineid engineid-string }
View
System view
Default Level
3: Manage level
Parameters
user-name: User name, which is a case sensitive string of 1 to 32 characters.
group-name: Group name, which is a case sensitive string of 1 to 32 characters.
cipher: Specifies that auth-password and priv-password are encrypted keys, which can be calculated by using the snmp-agent calculate-password command.
authentication-mode: Specifies an authentication algorithm. MD5 is faster than SHA, while SHA provides a higher security than MD5.
l md5: Specifies the MD5 authentication algorithm.
l sha: Specifies the SHA-1 authentication protocol algorithm.
auth-password: Authentication key. If the cipher keyword is not specified, auth-password indicates a plain text key, which is a string of 1 to 64 visible characters. If the cipher keyword is specified, auth-password indicates an encrypted key. If the md5 keyword is specified, auth-password is a string of 32 hexadecimal characters. If the sha keyword is specified, auth-password is a string of 40 hexadecimal characters.
privacy-mode: Specifies an encryption algorithm for privacy. The three encryption algorithms AES, 3DES, and DES are in descending order in terms of security. Higher security means more complex implementation mechanism and lower speed. DES is enough to meet general requirements.
l 3des: Specifies the 3DES algorithm.
l aes128: Specifies the AES algorithm.
l des56: Specifies the DES algorithm.
priv-password: The privacy key. If the cipher keyword is not specified, priv-password represents a plain text key, which is a string of 1 to 64 characters. If the cipher keyword is specified, priv-password represents an encrypted key. If the md5 keyword is specified, priv-password is a string of 32 hexadecimal characters. If the sha keyword is specified, priv-password is a string of 40 hexadecimal characters.
acl acl-number: Specifies a basic ACL. The acl-number argument takes an ACL number in the range of 2,000 to 2,999.ssociates a basic ACL with the user. acl-number is in the range 2000 to 2999. By using a basic ACL, you can restrict the source IP address of SNMP packets, that is, you can configure to allow or prohibit SNMP packets with a specific source IP address, so as to allow or prohibit the specified NMS to access the agent by using this user name.
local: Represents a local SNMP entity user.
engineid engineid-string: The engine ID string, an even number of hexadecimal characters, in the range 10 to 64. Its length must not be an odd number, and the all-zero and all-F strings are invalid.
Description
Use the snmp-agent usm-user v3 command to add an SNMPv3 user to an SNMP group.
Use the undo snmp-agent usm-user v3 command to delete an SNMPv3 user from an SNMP group.
This command is for SNMPv3. Create SNMPv3 users, if the agent and the NMS use SNMPv3 packets to communicate with each other.
Each SNMP user belongs to an SNMP group. Before creating a user, create an SNMP group first. Otherwise, the user can be created successfully but does not take effect. An SNMP group may contain multiple users. It defines SNMP objects accessible to the group of users in the MIB view and specifies whether to enable authentication and privacy functions. The authentication and encryption algorithms are defined when a user is created.
l If you specify the cipher keyword, the system considers the arguments auth-password and priv-password as encrypted keys, and does not encrypt them when executing this command.
l If you do not specify the cipher keyword, the system considers the arguments auth-password and priv-password as plain text keys, and encrypts them when executing this command.
Specify the cipher keyword when you roll back, copy or paste the running configuration. For example, assume that you have created SNMPv3 user A and configured both authentication and privacy keys of this user as xyz. To make the configuration of user A still effective after the configuration is copied, pasted, and re-executed, specify the cipher keyword when you create user A with this command. Otherwise, after you copy, paste, or re-execute the configuration, the device creates user A, but the corresponding keys are not xyz.
When you use the snmp-agent usm-user v3 cipher command, the pri-password argument in this command can be obtained by the snmp-agent calculate-password command. To make the calculated encrypted key applicable to the snmp-agent usm-user v3 cipher command and have the same effect as that in the snmp-agent usm-user v3 cipher command, ensure that the same encryption algorithm is specified for the two commands and the local engine ID specified in the snmp-agent usm-user v3 cipher command is consistent with the SNMP entity engine ID specified in the snmp-agent calculate-password command.
When you execute this command repeatedly to configure the same user (namely, the user names are the same, no limitation to other keywords and arguments), the last configuration takes effect.
A plain text password is required when the NMS accesses the device; therefore, please remember the user name and the plain text password when you create a user.
Related commands: snmp-agent calculate-password, snmp-agent group, and snmp-agent usm-user { v1 | v2c }.
Examples
# Add a user testUser to the SNMPv3 group testGroup. Configure the security model as authentication without privacy, the authentication algorithm as MD5, the plain-text key as authkey.
<Sysname> system-view
[Sysname] snmp-agent group v3 testGroup authentication
[Sysname] snmp-agent usm-user v3 testUser testGroup authentication-mode md5 authkey
l Set the SNMP version on the NMS to SNMPv3
l Fill in the user name testUser,
l Set the authentication algorithm to MD5
l Set the authentication key to authkey
l Establish a connection, and the NMS can access the MIB objects in the ViewDefault view on the device
# Add a user testUser to the SNMPv3 group testGroup. Configure the security model as authentication and privacy, the authentication algorithm as MD5, the privacy algorithm as DES56, the plain-text authentication key as authkey, and the plian-text privacy key as prikey.
<Sysname> system-view
[Sysname] snmp-agent group v3 testGroup privacy
[Sysname] snmp-agent usm-user v3 testUser testGroup authentication-mode md5 authkey privacy-mode des56 prikey
l Set the SNMP version on the NMS to SNMPv3
l Fill in the user name testUser
l Set the authentication algorithm to MD5
l Set the authentication key to authkey
l Set the privacy algorithm to DES
l Set the privacy key to prikey
l Establish a connection, and the NMS can access the MIB objects in the ViewDefault view on the device
# Add a user testUser to the SNMPv3 group testGroup with the cipher keyword specified. Configure the security model as authentication and privacy, the authentication algorithm as MD5, the privacy algorithm as DES56, the plain-text authentication key as authkey, and the plain-text privacy key as prikey
<Sysname> system-view
[Sysname] snmp-agent group v3 testGroup privacy
[Sysname] snmp-agent calculate-password authkey mode md5 local-engineid
The secret key is: 09659EC5A9AE91BA189E5845E1DDE0CC
[Sysname] snmp-agent calculate-password prikey mode md5 local-engineid
The secret key is: 800D7F26E786C4BECE61BF01E0A22705
[Sysname] snmp-agent usm-user v3 testUser testGroup cipher authentication-mode md5 09659EC5A9AE91BA189E5845E1DDE0CC privacy-mode des56 800D7F26E786C4BECE61BF01E0A22705
l Set the SNMP version on the NMS to SNMPv3
l Fill in the user name testUser,
l Set the authentication algorithm to MD5
l Set the authentication key to authkey
l Set the privacy algorithm to DES
l Set the privacy key to prikey
l Establish a connection, and the NMS can access the MIB objects in the ViewDefault view on the device
MIB Configuration Commands
display mib-style
Syntax
display mib-style
View
Any view
Default Level
3: Manage level
Parameters
None
Description
Use the display mib-style command to display the MIB style of the device.
Two MIB styles are available on the device: new and compatible. After obtaining the MIB style, you can select matched H3C network management software based on the MIB style.
Related commands: mib-style.
Examples
# After getting the device ID from node sysObjectID, you find that it is an H3C device, and hope to know the current MIB style or the MIB style after next boot of the device.
<Sysname> display mib-style
Current MIB style: new
Next reboot MIB style: new
The above output information indicates that the current MIB style of the device is new, and the MIB style after next boot is still new.
mib-style
Syntax
mib-style [ new | compatible ]
View
System view
Default Level
3: Manage level
Parameters
new: Specifies the MIB style of the device as H3C new; that is, both sysOID and private MIB of the device are located under the H3C enterprise ID 25506.
compatible: Specifies the MIB style of the device as H3C compatible; that is, sysOID of the device is located under the H3C enterprise ID 25506, and private MIB is located under the enterprise ID 2011.
Description
Use the mib-style command to set the MIB style of the device.
By default, the MIB style of the device is new.
The configuration takes effect only after the device reboots.
Examples
# Modify the MIB style of the device as compatible.
<Sysname> system-view
[Sysname] mib-style compatible
[Sysname] quit
<Sysname> display mib-style
Current MIB style: new
Next reboot MIB style: compatible
<Sysname> reboot
