Brocade Communications Systems Brocate Ethernet Access Switch 6910 - Manual (Page 71)

Brocade 6910 Ethernet Access Switch Configuration Guide 21
53-1002581-01
Basic Configuration
2
subnet 192.168.255.0 netmask 255.255.255.0 {
range 192.168.255.160 192.168.255.200;
option routers 192.168.255.101;
option tftp-server-name "192.168.255.100";#Default Option 66
option bootfile-name "bootfile"; #Default Option 67
}
class "Option66,67_1" { #DHCP Option 60 Vendor class one
match if option vendor-class-identifier = "es020000.cfg";
#option 43
option vendor-class-information code 43 = encapsulate dynamicProvision;
#option 66 encapsulated in option 43
option vendor-class-information.tftp-server-name "192.168.255.100";
#option 67 encapsulated in option 43
option vendor-class-information.bootfile-name "test1"
}
class "Option66,67_2" {#DHCP Option 60 Vendor class two
match if option vendor-class-identifier = "es020000.cfg";
option tftp-server-name "192.168.255.101";
option bootfile-name "test2";
}
NOTE
Use “es020000.cfg” for the vendor-class-identifier in the dhcpd.conf file.
Enabling SNMP Management Access
The switch can be configured to accept management commands from Simple Network
Management Protocol (SNMP) applications. You can configure the switch to respond to SNMP
requests or generate SNMP traps.
When SNMP management stations send requests to the switch (either to return information or to
set a parameter), the switch provides the requested data or sets the specified parameter. The
switch can also be configured to send information to SNMP managers (without being requested by
the managers) through trap messages, which inform the manager that certain events have
occurred.
The switch includes an SNMP agent that supports SNMP version 1, 2c, and 3 clients. To provide
management access for version 1 or 2c clients, you must specify a community string. The switch
provides a default MIB View (i.e., an SNMPv3 construct) for the default “public” community string
that provides read access to the entire MIB tree, and a default view for the “private” community
string that provides read/write access to the entire MIB tree. However, you may assign new views to
version 1 or 2c community strings that suit your specific security requirements (see
“Setting
SNMPv3 Views” on page 934).
Community Strings (for SNMP version 1 and 2c clients)
Community strings are used to control management access to SNMP version 1 and 2c stations, as
well as to authorize SNMP stations to receive trap messages from the switch. You therefore need to
assign community strings to specified users, and set the access level.
The default strings are:
• public - with read-only access. Authorized management stations are only able to retrieve MIB
objects.