Cisco Headend System Release 2.5 Installation Guide
4-22
SR 2.5 and SR 3.5 Common Upgrade Procedures
78-738190-01 Rev B
Add an EAS Variable to the .profile File
Introduction
In order to make the EAS work properly, you may need to add the LOCAL_EAS_IP
variable to the .profile file. This procedure describes how to add the variable.
Adding an EAS Variable to the .profile File
Follow these instructions to add the LOCAL_EAS_IP variable, if necessary, to the
.profile file.
1.
If necessary, open an xterm window on the DNCS.
2.
Type cd /export/home/dncs and then press Enter.
Result: The /export/home/dncs directory becomes the working directory.
Result: The /export/home/dncs directory becomes the working directory.
3.
Type vi .profile and then press Enter.
Result: The .profile file opens for editing using the Unix vi text editor.
Result: The .profile file opens for editing using the Unix vi text editor.
4.
Does the .profile file contain an entry for the LOCAL_EAS_IP variable?
•
•
If yes, close the .profile file and go to Restart the System Components, next
in this chapter.
•
If no, continue with step 5.
5.
Append the following line to the .profile file:
export LOCAL_EAS_IP=[Ethernet address of the DNCS]
Note: Substitute the Ethernet address of the DNCS for [Ethernet address of
Note: Substitute the Ethernet address of the DNCS for [Ethernet address of
the DNCS].
6.
Save the file and close the vi text editor.
7.
Follow these instructions to activate the EAS variable.
a) Type cd /export/home/dncs and then press Enter.
b) Type . ./.profile and then press Enter.
a) Type cd /export/home/dncs and then press Enter.
b) Type . ./.profile and then press Enter.
8.
Type env | grep -i local and then press Enter.
Result: The system displays the value of environmental variables that
Result: The system displays the value of environmental variables that
contain the word “local.”
9.
Do the results from step 8 show that the LOCAL_EAS_IP variable has been
set properly?
•
•
If yes, go to Inspect the DNCS for BFS RPC Version 3 Support, next in
this chapter.
•
If no, repeat this procedure, or contact Cisco Services for assistance.