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!

Control Networks and IPSI's

Status
Not open for further replies.

dmthames

Technical User
Jan 11, 2006
96
US
Hi All,

I posted a similar version of this question on avaya users, but wanted to drop it here as well...

Is there a mutually exclusive relationship between control networks and ipsi's? That's to say, does control network a operate exclusively on the a ipsi's (in a duplicated environment) and does control network b operate exclusively on the b ipsi's?

Thanks!
 
Server A has a Control A and B port for connectivity to IPSI's.
Server B has a Control A and B port for connectivity to IPSI's.

All IPSI's in A carrier or A Control are configured by either means of DHCP or static to communicate to server A or B, which ever is active.

All IPSI's in B carrier or B Control are configured by either means of DHCP or static to communicate to server A or B, which ever is active.

So yes they are exclusive but both servers have control A & B.
 
Hi Legend,
Thks for the reply...

Affirmative on the servers....our stuff is static. What i'm looking to do is move my eth 3 cable to a new switch with the proper vlan on it. My a ipsi's are currently set active so i'm thinking that so long as i leave the eth 0 interfaces alone, control network a will retain control of both of my pn's....my guess is i'll get some minor alarms on that interface, but won't lose the pn...

So here's a hump-day bonus follow up...does the control a interface (eth 0) need to be able to see the b-side ipsi's? Or can they be on completly different networks that can't see each other?

Thanks!
 
dmthames,

Completly different. 255.255.255.0 does not see 255.255.254.0.

you should not loose PN connectivity. the only reason it should bounce from A to B is if for some reason you have a problem on A control and the system feels as if it should interchange due to system health.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top