If the SNMP version on the NMS is set to SNMPv1, when the NMS uses the community name public to
access the device, it cannot access all objects of the ip subtree (such as the ipForwarding node, the
ipDefaultTTL node, and so on), but it can access all objects of the mib-2 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, in
the range 484 to 17,940. The default value is 1,500 bytes.
Description
Use the snmp-agent packet max-size command to configure the maximum size of the SNMP packets
that can be received or sent by the agent.
Use the undo snmp-agent packet max-size command to restore the default packet size.
By default, the maximum size of the SNMP packets that can be received or sent by the agent is 1,500
bytes.
If devices not supporting fragmentation exist on the routing path between the NMS and the agent, you
can use the command to configure the maximum SNMP packet size, and thus to prevent giant packets
from being discarded.
Typically, you are recommended to apply the default value.
Examples
# Configure the maximum number of bytes that can be received or sent by an SNMP agent as 1,042
bytes.
<Sysname> system-view
[Sysname] snmp-agent packet max-size 1042
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
1-19
Need help?
Do you have a question about the S7906E and is the answer not in the manual?
Questions and answers