I can tell you're at the same point I was at one time. My advise for that is make sure you document everything, all your recommendation, alternatives, pricing, implementation schedule. And something to show that Management got a copy of it - either Email receipt or memo of why it was rejected.
Because when the "Defecation hits the rotatory oscillator" - you are going to be blamed!
When I worked at a major Utility I had made a recommendation to upgrade the network stability (old ChokenRing - with no management tools), we would get a beaconing node every couple of weeks which would cause an outage for 30 minutes or so until we found it (by hand - removing hubs).
Well, I put together a proposal, implementation schedule, recommended solution cost, alternates and costs, cost justification with ROI's and TCO (Cost of 1 day outage to corporation was over $2 mill - cost of fix $256K). The VP of IT turned it down, I asked him to please send me a memo about why just for my records - whether it was the solution or costs.
Six months later we got a beaconing node that we couldn't locate - took 2 days to recover. CEO was jumping Ugly - and the VP of IT blamed me and my boss. Oops magically the proposal and rejection memo were handed to the CEO..
Guess who was looking for a new job - and guess who got $500K to put in the solution in two weeks.
So - sounds like they have you lined up as a Duck and it's coming up on Duck Season... Get your CYA's lined up - for a just in case.
Do you have access to any Advisory services - Meta, Gartner, Faulkner, Giga - that would back your recommendation? As a place to find old equipment try AMVET's or Salvation Army or Good Will - I know in my area those outfits clean and sell them for $50 to $100 dollars...
Good Luck