Stand alone port-network, lost control but not voice.

[manfmmd]

I know it's possible(I have the alarms log), but do not have an answer as to why, so if someone could enlighten me.

I lost the control network (A&B), on a carrier that has no trunking, copper or IP back to any other port-networks...but did not lose the voice, they could still make calls, intra-switch and external. This PN has no other connectivity to the outside world, no ESS, etc. It was isolated other than the 1 CLAN and 2 MEDPRO boards. All stations off of this PN are Digitial or Analog.

It was my understanding that if the control netowrk goes down, without any type of server connectivity, the carrier loses it's functionality.

What am I missing that allowed the carrier and voice to stay up?

 

[aarodriguez]

There a re many errors related do PNC not necessary all causes loss of connectivity, do you have the error log?

 

[manfmmd]

display alarms                                                         Page   3

                                 ALARM REPORT

Port      Mtce      On   Alt          Alarm   Svc   Ack? Date        Date
          Name      Brd? Name         Type    State 1 2  Alarmed     Resolved

PN 05     EXP-PN    n                 MAJOR         c    03/14/10:14 03/14/18:38
PN 05     EXP-PN    n                 MAJOR         c    03/14/10:14 03/14/18:38
PN 05     EXP-PN    n                 MAJOR         c    03/14/10:15 03/14/18:38
05A       PKT-INT   y                 MAJOR   IN    c    03/14/10:13 03/14/18:38
05A       PKT-INT   y                 MAJOR   IN    c    03/14/10:13 03/14/18:38
05B       PKT-INT   y                 MAJOR   IN    n    03/14/18:41 03/14/18:42
05B       PKT-INT   y                 MAJOR   IN    n    03/14/18:41 03/14/18:42
05B       PKT-INT   y                 MAJOR   IN    n    03/18/13:19 03/18/13:20
05A       PKT-INT   y                 MAJOR   IN    c    03/14/18:41 03/18/13:20
05A       PKT-INT   y                 MAJOR   IN    c    03/14/18:41 03/18/13:20

Both Control Networks are trunked over the same fiber through the same switches and broken out in different vlans at the end switch. Looking at the alarms logs again, and looking at my switches, I found out what happened:

.Mar 18 13:19:28.491: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/28, changed state to down
.Mar 18 13:19:28.508: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan8, changed state to down
.Mar 18 13:19:28.743: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/25, changed state to down
.Mar 18 13:19:29.506: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/28, changed state to down
.Mar 18 13:19:29.750: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/25, changed state to down
.Mar 18 13:19:31.755: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/28, changed state to up
.Mar 18 13:19:34.103: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/25, changed state to up
.Mar 18 13:19:35.085: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/28, changed state to up
.Mar 18 13:19:36.108: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/25, changed state to up
.Mar 18 13:20:05.100: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
.Mar 18 13:20:05.100: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan8, changed state to up

My switches at this site are hard-coded for trunking, vlans, etc on one side and the other side is generic. When the fiber was swapped between the business network and the Avaya private network, the trunking came up automatically. My 05B IPSI came back right away, but my 05A IPSI stayed down for some reason. When the fiber was swapped back, everything restored. We are working towards finalizing our netowrk setup out there and hard-coding everything on both sides.