By default, the DHCP Scope option 150 for Cisco TFTP Server is not available on Windows Server. Below are the steps to add the configure the option 150:
1. First we need to define the option 150 so that it can be made available in the scope options list. For this, right click on the IPv4 and choose the option Set Predefined Options… (screenshot below)
image
2. Click on the Add… button and you will get another dialog box asking you the Option Type.
3. Fill the details as mentioned below and shown in the screenshot:
Name: Cisco TFTP Server
Data Type: IP Address
Array: Checked
Code: 150
Description: Used for Cisco Call Manager TFTP Server
image
4. Click OK and click Edit Array button to enter the IP address for the TFTP Server (Screenshot below). Once you are done, click OK to exit.
image
5. Now, to configure Option 150 for any scope, go to its Scope Options, right click on and choose Configure Options and select the Option 150 from the list. You can edit the IPs if you required.
image
When network service like telnet connection hangs, then it is possible the inetd subsystem is not working properly. # refresh -s inetd 0513-095 The request for subsystem refresh was completed successfully. If the refresh hangs for some time and comes back with 0513-056 time out waiting for command response, then the inetd subsystem may not be working correctly and should then be killed nicely. Run #ps -ef | grep inetd and do a kill -15 on the process ID on the line that has /usr/sbin/inetd. Once inetd has been killed, type startsrc -s inetd. If inetd starts, try to telnet into the machine. If inetd does not start up successfully, or if telnet still hangs indefinitely, run kill -15 on the PID of inetd again. Back up the original /etc/inetd.conf file to a new file name by typing: # mv /etc/inetd.conf /etc/inetd.conf.backup The original template is in /usr/lpp/bos.net/inst_root/etc/. You can copy it by typing: # cp /usr/lpp/bos.net/inst_root/etc/inetd.conf /etc/inetd.conf Run start...
Comments
Post a Comment