Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Trouble Changing FW on J179s - R11.1 SW 1

Status
Not open for further replies.

DTGMI

Vendor
Jun 1, 2006
236
US
So - we have spent more time on this HTTP FW upgrade lab server.
Here is an update.
A - new IP500 V2 CU
B - SD card is created with R11.1.1 SW load
C - License is valid and has all the licenses required for this test lab system - IP Endpoints ad SIP licenses etc.
D - Downloaded the 96x1-IPT-H323-R6_8_5_4-022123.zip file
That is the HTTP FW we need to load on the new J179s and all J179 FW H.R.6.8.5.4.10 and JEM24 1.0.0.16 Bin files are in the Primary directory on SD card
E - Created the J100SUPDATE.txt file and 46XXSETTINGS.TXT files and added them to the primary folder on the SD card
F - From Manager - Set DHCP to SERVER ... H.323 Gatekeeper Enabled
G - CU is set at 192.168.42.1 and FILE SERVER field is set to 192.168.42.1 also
H - First DHCP IP address is set to start at 192.168.42.5
I - CU is connected to an 8 port POE switch - Laptop is connected to the POE switch and connectivity to CU is good
J - All ports are open
K - (2)test extensions are setup as HTTP - 209 - 210
L - J179 is configured as DHCP ... signaling to H.323
M - J179 - on powerup - sees the CU as it gets the 192.168.42.5 IP assigned to it and shows in the IP4 config screen - but the shows "Waiting on DHCP"

The problem we are having is no matter what we try - the J179s won't start the upgrade process and pull the H323 upgrade 6.8.5.4.10 BIN file

Anyone having this problem and have any tips :)

ALSO - we are having a time issue on the CU - it is stuck at 2014 and we tried all the tricks we know and can't resolve it. Ended up setting it to NONE as it is only a lab CU - not IN-Service
 
We figured it out .... a file name of the FW file was one issue and some settings in the 96z1Supgrade.txt file was anohter.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top