changing ethernet functionality/connection - PBX Info :: Your Free PBX, PABX and Telephone Information Resource
Home | Register |    
 
Forums         |        Articles          |        Blogs         |      Software          |      Portals          |      Resource          |      Wiki      |    White Papers         
 
Go Back   PBX Info :: Your Free PBX, PABX and Telephone Information Resource > PBX SYSTEMS > NORTEL > Meridian Systems
   SEARCH  
     
User Name Password      
Save ?
Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications

Tags: ,


Reply
 
LinkBack Thread Tools Display Modes
Old 11-14-2003, 09:16 PM   #1 (permalink)
simmy
Junior Member

Activity Longevity
0/20 20/20
Today Posts
0/0 sssssss22
Rep Power: 6simmy is on a distinguished road
x11 r25.10

We are currently using an ethernet port on the PBX to connect directly to an SECC server via crossover cable. I want to change this config to add the PBX to our LAN- mainly so I can send traps to our network monitoring server. I am pretty clear as to how to change the IP addressing on both the PBX and SECC server..Also, I am clear as to how to send open alarms to any LAN address. But here is my problem

current config (in the M1)
Host address (M1)- 192.168.1.10
default gateway - 192.168.1.11

the SECC server address is 192.168.1.11

Here is basically what it will look like once I add these devices to our LAN-
M1- 10.100.112.2
SECC - 10.100.112.3
default gateway for each - 10.100.112.1

I understand (I think) how to define where to send SNMP traps to-
ld 117
=> set open_alarm 0 10.100.x.x

However-
Since the default gateway is the address of the SECC server (in the current config), I am afraid that simply making the changes above will cut off communication from the PBX to the SECC server. How do I define within the PBX that the SECC servers address is 10.100.112.3, rather than just routing everything to the gateway? make sense?
simmy is offline   sendpm.gif Reply With Quote
Old 11-14-2003, 09:53 PM   #2 (permalink)
Steamer
Junior Member

Activity Longevity
0/20 20/20
Today Posts
0/0 ssssss154
Location: Canada
Rep Power: 6Steamer is on a distinguished road
Country:
changing ethernet functionality/connection

You don't need to configure the SECC address on the M1 but you will have to change the M1 address in SECC.
Remember you MUST isolate the M1 from the customer LAN by a router.
Steamer is offline   sendpm.gif Reply With Quote
Old 11-20-2003, 01:59 PM   #3 (permalink)
Machivelli
Junior Member

Activity Longevity
0/20 20/20
Today Posts
0/0 sssssss12
Rep Power: 6Machivelli is on a distinguished road
Big Red Flag just popped up.
When you say your adding this to your LAN are you talking about your CLAN (Customer LAN) where all of your workstations and servers reside? In other words how are you blocking broadcast messages? Hopefully you’ve read up about that, but if not I’m sure there are a host of people in here that will attest to the problems broadcast messages will have on your switch. As for the Symposium, Steamers right, there’s nothing to configure on the PBX. All you need to do is set up Symposium with the correct IP’s. Is there any other server (I.E. OTM, Call Pilot) attached to the PBX?
Machivelli is offline   sendpm.gif Reply With Quote
Old 11-20-2003, 02:56 PM   #4 (permalink)
simmy
Junior Member

Activity Longevity
0/20 20/20
Today Posts
0/0 sssssss22
Rep Power: 6simmy is on a distinguished road
I will be adding to my CLAN- but will be isolating it from the rest of the network by creating a VLAN which only includes the SECC server and the PBX. Also, I will create access lists that will deny ALL traffic from entering the VLAN- and then defining exactly what can enter on a case by case basis. Both will be plugged directly in to a router- there will be a subnet and VLAN that includes only these 2 devices (for now) - obviously, any server like OTM would be connected within this VLAN/subnet as well..

I do not have OTM or Call pilot now... but this will help me illustrate my worries... Lets say I was adding OTM to this VLAN too.. How does the PBX know the difference between the SECC server and the OTM server unless I define the difference within the PBX? For example- a call comes in to a CDN which is acquired by SECC- the PBX knows it needs to send a packet off to the SECC server to find out where to point this call... Since there are 2 devices on this VLAN other than the PBX, how does the PBX know which device to send the packet to?

Maybe I am over thinking this?
simmy is offline   sendpm.gif Reply With Quote
Old 11-20-2003, 05:07 PM   #5 (permalink)
mrmike
Junior Member

Activity Longevity
0/20 20/20
Today Posts
0/0 ssssss394
Location: Philadelphia
Rep Power: 6mrmike is on a distinguished road
Sounds like your going down the right road. Just make sure that the VLAN
is completely partioned off. If packets start hitting the PBX, it will INI or sysload. I think the packet hits both of the servers and only the secc responds back, not sure on that one.
mrmike is offline   sendpm.gif Reply With Quote
Reply



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
CP4 Core and Ethernet HCJes Meridian Systems 13 02-08-2008 05:09 PM
Ever changed IP addresses in Meridian Max or Link? Ravenlc Meridian Systems 15 05-03-2006 01:00 AM
Ethernet nection for opt 11C zmoataz Meridian Systems 1 07-21-2004 07:15 AM
***Option 11 Ethernet Admin Hookup (Nightmare) *** tech1994 Meridian Systems 1 10-24-2003 06:27 PM


All times are GMT -5. The time now is 04:42 AM.

Tags   |   Advertise    |    Media Partners   |    Admin   |   About us   |   Contact Us   |   RSS   

Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.0.0
Copyright PBXINFO LLC 2006