
File details 401
the [TlanConfig] section) still require a card reboot before the changes can
take effect. You can change the following sections without performing a
reboot:
• [snmp]
• [routes]
• [dsp0]
•
[tos]
• [ElanConfig]
• [Loss Plan]
• [firmware]
You can download the file through the VGMC shell by using the command
configFileGet.
Starting in Release 4.0, the following line is examined and compared
between the copy of the CONFIG.IN file stored on the Call Server and the
copy stored locally on the Signaling Server or VGMC:
#dateOfLastFileModification(dd/mm/yyyy hh:mm:ss)=21/08/2
003 01:45:12 i.
If the line is different, then the CONFIG.INI file on the Call Server is used.
The configuration file is self-explanatory. Each section begins with a
section identifier in brackets ([]).
Note: The [routes] section is for creating static route entries on the
ELAN interface only. The entry includes the destination IP address
and the subnet mask.
EM file
The following is an example of a CONFIG.INI file generated by the
Succession 4.0 Element Manager.
#version=VGMC4.0
#authoringApplication=EM
#dateOfLastFileModification(dd/mm/yyyy hh:mm:ss)=21/08/2
003 01:45:12
[keycode]
keycodeId=12345678-12345678-12345678
[Security]
ElanAccessOnly=0
[snmp]
Nortel Communication Server 1000
Troubleshooting Guide for Distributors
NN43001-730 02.02 31 December 2009
Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
.
Comentários a estes Manuais