D-Link 1824i User Guide - Page 79

Boot Configuration File

Page 79 highlights

10BASE-T Stackable Hubs C CBOOT CONFIGURATION FILE The master hubs in the series support a powerful configuration file which allows many of the hub stack's configuration parameters to be stored on a centralized server. When the master hub starts up, it can be configured to read its configuration file from the server using the TFTP protocol. This can make it easier to manage a large number of hub stacks, since all of the configuration parameters for all of the hubs can be managed in a single place. The configuration file is a text file, usually stored on the server with a .CFG extension. It can be up to 10 kilobytes long. Lines beginning with # are considered comments which are ignored by the hub. All other lines are commands, which are interpreted by the master hub. The configuration file commands accepted by the hub are: ♦ sysdescr string Takes string as the System Name, corresponding to the SNMP MIB II variable system.sysName. This field is used to give a name to the hub for administrative purposes. The hub's fully qualified domain name is often used, provided a name has been assigned. The string can be up to 64 characters long. ♦ syscontact string Takes string as the System Contact, corresponding to the SNMP MIB II variable sysContact. This field is used to give the name and Boot Configuration File C-1

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87

10BASE-T Stackable Hubs
C
C
B
OOT
C
ONFIGURATION
F
ILE
The master hubs in the series support a powerful configuration file which
allows many of the hub stack’s configuration parameters to be stored on a
centralized server.
When the master hub starts up, it can be configured to
read its configuration file from the server using the TFTP protocol. This can
make it easier to manage a large number of hub stacks, since all of the
configuration parameters for all of the hubs can be managed in a single place.
The configuration file is a text file, usually stored on the server with a
.CFG
extension.
It can be up to 10 kilobytes long. Lines beginning with
#
are
considered comments which are ignored by the hub.
All other lines are
commands, which are interpreted by the master hub.
The configuration file commands accepted by the hub are:
sysdescr
string
Takes
string
as the System Name, corresponding to the SNMP MIB II
variable
system.sysName
.
This field is used to give a name to the
hub for administrative purposes.
The hub’s fully qualified domain name
is often used, provided a name has been assigned.
The
string
can be up to
64 characters long.
syscontact
string
Takes
string
as the System Contact, corresponding to the SNMP MIB II
variable
sysContact.
This field is used to give the name and
Boot Configuration File
C-1