G700 MGP Firmware Update Issues

[DTGMI]

In our lab - we are having a strange issue with upgrading G700 firmware.

A - Laptop IP is set to 192.11.13.5 as normal - SNM is 255.255.255.0
B - We are connected to the console port and connected via Putty - no problem.
C - We run the G700 initial setup routine .... P330 & MGP NVRAM INIT. Setup each interface 1 as 192.11.13.6 & 7 w/ correct SNM ... setup GW as 192.11.13.1
D - Start the Avaya TFTP server on our lab laptop - default config...
E - We can ping the P330 INTF 1 - 192.11.13.6 from the laptop and the laptop from the P330 ... but from the MGP - we can't ping the laptop or vice versa.
F - when we run the copy command - copy TFTP MGP-image A or B C:\TFTP\MGP_30_27_1.bin 192.11.13.5 ... Error - File Not Found

We have tried (3) G700s think it might be a NIC hardware issue for the MGP port ... but no change.

Any tricks in getting the firmware file to the G700 other than TFTP file transfer? There are no USB ports for a thumb drive transfer....

Any ideas?

 

[joe2938]

should be 192.11.13.5 255.255.255.252 not sure if this is your issue thou

 

[Arlo555]

Can you post a copy of the configuration?

 

[DTGMI]

This is my specific IP programming guide for the G700 ...

CONFIGURE STACK MASTER

Type 'session stack'

@P330(super)prompt
Type 'config'
Type 'nvram init'
Continue 'y'
Device resets.

@P330(super)prompt
Type 'config'
Type 'set interface inband 1 192.11.13.6 255.255.255.252
Type 'reset'
Continue 'y'
Device resets.

@P330(super)prompt
Type 'config'
Type 'set ip route 0.0.0.0 192.11.13.1
Type 'show interface' confirm ip address and subnet correct for stack master
Type 'show ip route' confirm ip address correct for default gateway

CONFIGURE MGP/VOIP

Type 'session mgp'
@MG-???(super)prompt
Type 'config'
Type 'nvram init'
Continue 'y'
MGP resets
Wait 30-45 seconds

Type 'session mgp'
@MG-???(super)prompt
Type 'config'
Type 'set interface mgp 1 192.11.13.7 255.255.255.252
Type 'reset mgp'
Continue 'y'
MGP resets
Wait 30-45 seconds

Type 'session mgp'
@MG-???(super)prompt
Type 'config'
Type 'set ip route 0.0.0.0 0.0.0.0 192.11.13.1
Type 'show interface mgp' confirm mgp ip address
Type 'show ip route mgp' confirm ip address of default gateway
Type 'set interface voip v0 192.11.13.8
Wait 30 seconds
Type 'show voip' confirm ip address

Our lab labtop's IP NIC address is - 192.11.3.5 .... 255.255.255.252

Our Fw files are in the TFTP file folder and the TradeWinds TFTP server is configured for that folder for routing.

 

[DTGMI]

Joe - Avaya's config docs show to use 255.255.255.0 for SNM as that allows for 254 endpoints as compared to 255.255.255.253 which only allows for 2 sessions.

 

[jimbojimbo]

Try putting your laptop on the network with the gateway and see if the tftp works. Most TFTP servers will have the ability to select a specific interface for service so you may simply have an issue where the TFTP server is not providing service on the 192.11.13.5 interface. You can try a netstat -a to see where your TFTP is listening.

 

[mattKnight]

Your IP addressing scheme is invalid....

I'd suggest that you don't use 192.11.13.x range at all as it clashes with the service port ranges. However.

192.11.13.5 and .6 are valid host addresses for a 255.255.255.252 (/30) network. 192.11.13.7 and .8 is not (.7 is the broadcast address for the previous /30 network and .8 is the network address of the next /30network)

In short, change the ip addresses to a rfc range and use a /24 (255.255.255.0) mask

This may not be the cause of you issue with tftp, but the g700 ain't gonna work!

Also, check your windows firewall... tftp is usually blocked



Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[joe2938]

no it needs to be 192.11.13.5 255.255.255.252, not sure what you are reading

 

[AvayaTier3]

Andy,

g700 uses an Avaya media-gateway console cable to rs232 or usb on your laptop.

Your lan on the pc is used with crossover cat 5 to services port of s8300 in slot v1 of the g700

stage your firmware file on the s8300 /tftpboot folder

http://www.tek-tips.com/viewthread.cfm?qid=1735642

md5sum mm711h20v73.fdl
b6fca3e92be6150645203d0ff20a742f

ls -l mm711h20v73.fdl
-rwxr-xr-x 1 craft susers 122539 Sep 9 2008 /tftpboot/mm711h20v73.fdl

What FW is on your g430?
Should be 25.43.0 - 07/11/2008

try this command from the media-gateway - 127.1.1.31 is always the internal
address for an 8300 in 01v1 - or use customer IP address for 8300 with /tftpboot

g430, g450, g350: (mm711 slot v2)
copy tftp module mm711h20v73.fdl 127.1.1.31 2
show download software status 2

for g700: (mm711 slot v2)
copy tftp mm-image v2 mm711h20v73.fdl 127.1.1.31

See this thread



A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[mattKnight]

no it needs to be 192.11.13.5 255.255.255.252, not sure what you are reading

To access a service port, yes I agree, the subnet mask needs to be /30 (255.255.255.252) and I'd also recommend setting the default gateway correctly and clearing the arp cache.

However DTGMI has configured the MGP interface as 192.11.13.7 on a /30 network. Which as I identified is an invalid host address (please feel free to check using an online subnet calculator)

Type 'session mgp'
 @MG-???(super)prompt
 Type 'config'
 Type 'set interface mgp 1 192.11.13.7 255.255.255.252
 Type 'reset mgp'
 Continue 'y'
 MGP resets
 Wait 30-45 seconds

While it is probably possible to configure a G700 P330 stack to use multiple /30 addresses for the interfaces, you'd need to be phenomenally adept at networks and subnetting. Even if you were, I'd strongly recommend that you don't for reasons of simplicity and ease of maintenance.

I stand by the original assertion that the IP configuration is invalid.



Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[DTGMI]

We figured out that we just couldn't use the 192.11.13 IP ranges.

We simply changed to another range ... 192.5.5.x and the MGP 192.5.5.7 could laptop 192.5.5.5 could ping each other ... so the MGP connected to the TFTP server and FW upgrade proceeded to completion.

Also used 255.255.255.0 .... but tried 252 also and it worked fine also.

Thanks for all the replies.