TFTP for MBG sets

[PureChimpie]

I have an issue whereby IP sets (5340's) are getting a lower firmware version when connecting in TW mode through the MBG, as opposed to the MCD.

The MCD is running MCD 5 SP2 PR2 and MBG is 7.0. MBG is running in server/gateway mode with 2 NIC's.

When an IP set boots on the customer LAN, the set gets a v5.1 via TFTP

When an IP set boots via the MBG / TW, the set is downgraded to v4.1 via TFTP

From the documentation, I believe that after the 1st IP set connects through the MBG and to the MCD, the MBG then takes a copy of the set firmware and caches it. The rest of the TW sets will get their TFTP from the MBG and NOT the MCD, therefore all sets should be on the same version.

Any ideas? Customer wants all sets on the same firmware version!

 

[PureChimpie]

Update from Mitel:

Last Troubleshooting Note:
---------------------------------------------------------------------------------------------
ActionPlan/Workaround:

this was an error in the rel 7.0 manuals which was rectified in the 7.1 eng guidelines page 22

Note: MBG's file downloader does not know about any ICPs until sets connect to MBG and thus get connected
to an ICP. This step happens after a set has already retrieved its firmware load via TFTP. Due to that, set
firmware loads are still bundled with MBG and are not fetched from the ICPs.


My suggestion is to upgrade the MBG to the latest version, this will keep the set firmware up to date and will also provide every security fix that has been applied to the MBG/MSL in the last 2 years since 7.0 was made available

 

[LoopyLou]

Interesting. Did not know MBG supplied firmware to sets.

The beatings will continue until morale improves.