How to log in to 8500

[jefflad]

Just playing about with our system which has 2 8700's in a remote site and 1 8500 locally. When I login and administer the system I log in via ASA to the 8700's, However if I lost them how would I administer the system on the 8500?

I've tried changing the ASA login IP's that relate to the 8500 but no joy... this has me worried now as if we lost the 8700's I'd have no access to adminster the system... help!

 

[kyle555]

Normally you wouldn't do much via ASA on it. Sounds like you've got a duplex pair of 8700s and a 8500 LSP or ESS. So, the 8700s run one instance of CM across them, and the 8500 runs a failover instance until you get the 8700s on their feet again.

If you can save trans all in the 8700 and pass and "list survivable" and see the 8500 up and happy, you're already in good shape.

CM does central call processing. So on a sunny day, that 8500 does a heartbeat to the 8700s and not much else. On a rainy day when it's working, you still can't "save translations" on it. If you were going to be down for a day or 3 you could make some changes, but you'd lose them when the 8700s came back. The user accounts on the 8700 are syncd to each other, but not to your 8500, so it's got whatever it's got.

Your choices are to find the password, get someone at Avaya to reset your password or reinstall. What version are you at? Old software isn't readily available from Avaya anymore. Something about ending their licensing agreement for certain packages so there's no more download link for CM2 or 3.

 

[jefflad]

Thanks for that, that is exactly the setup with an 8500 as the ESS... My problem is, if we lost network connectivity to the site where the 8700's are we'd lose our E1 circuits as that's the site they come in to. I'd want to then connect to the ESS and modify the routing so the inbound option would select local trunks to the ESS and route as per sunny day scenario.

I assumed that I could just punch the IP of the ESS into ASA and hey presto I'm up and running... this isn't the case. I've looked on the ESS via a web browser and can't see any IP addresses to try them in ASA so I assume I'm looking in the wrong location to see config... does that make sense of my problem?

 

[kyle555]

Generally the IP you'd pop in a web browser for the ESS is the same you'd use in ASA. You'd normally log in and see ***ESS TRANSLATIONS CANNOT BE SAVED***

I guess I'm not understanding your challenge. Generally speaking, Avaya's survivability design is such that you don't need to make changes on a ESS once it goes live to make it do what the main server was doing.

If buddy digs up the road and knock out the fiber to your main site with 8700s and say your E1s came from the carrier on that fiber, you're not exactly in a position to choose from your PBX how inbound calls will work.

In the world of SIP they have something called "call forward interface down". ISDN trunks can have something similar as well where if the interface to the circuit at 101 Main St is down, it can send the calls to a circuit on your 8500 at 555 Church St (some restrictions may apply, offer void where prohibited, batteries not included).

 

[AvayaTier3]

s8500, s8500B, s8500C may have RMB board or SAMP and usb modem connectivity.
IP address for your survivable s8500 server can be used to login to web browser port 80 or 443
to Linux port 23 or 22, SAT port 5023 or 5022.

With a laptop and crossover cable to s8500 services port you can use the same IP ports above.

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]

 

[jefflad]

Thanks for the input...

We did a quick test over the weekend and all working.

 

[kyle555]

Well, in the webpage, you define the ports it listens for telnet and ssh for linux and SAT (23/22, 5023/5022). Maybe your ASA is set for telnet, you have a newer CM where it's off by default and so telnet got turned on the 8700s but not the 85?

There was a bug in ASA 6.0 when it first came out that it wouldn't flush the key of the A server connecting to B. To say, with procr IP X, when the servers interchanged, ASA would have problems connecting to it. Its why some early R6 systems I see sometimes have telnet enabled. Just a thought.