Mitel 3300 MXe System IP Config

[pichels]

Hi,

I'm not sure where to start but I am trying to configure our 3300 w/ a 5550 IP Console phone on our network.

We have a separate internal subnet of "203.57.229.0".
We have a seperate VLAN configured on our CISCO 3750 Core Switch.

I just want to connect a PC(w/ IP console software) on this lan, assign it an IP w/ the 3300's internal DHCP server or a static, I don't care.
I just want a "flat" lan/subnet - 203.57.229.0 that I can use to make sure a very "basic" setup works.

############################
Current System IP config:

Hostname = Mitel3300

System IP = 203.57.229.2

Subnet Mask = 255.255.255.0

Gateway IP = 203.57.229.250 (This is a current 2600 router on our network!)

Layer2 Switch IP = 203.57.229.0(The vendor set it this way - why are we using an internal switch or routing in the 3300?)

E2TCard IP = 203.57.229.3

No QOS enabled?
No DNS enabled.

Tag VLAN1 on trunk ports = disabled?
IGMP Snooping = enabled

IP Routing setup?

Firewall?

DHCP is configured for 203.57.229.100-200

SNMP is enabled.

###################################


The port I have setup for Static access and is Vlan 9.
We have other PIX ACL's, and 2600 router "routes" that have already been in place for printers that were setup on this network.

Any help is greatly appreciated.
I could draw a diagram as well.
NOTE: We are "not" using IP phones yet - just an IP console.

Thanks!

SP

 

[TheMitelGuy]

Start with the IP Phone first, and make sure it works. Then add the IP console. It's probably going to be easier that way.

 

[slapin]

I don't see any possible issues in a flat L2 network. Keep in mind that you need to supply correct DHCP options for mask and gateway settings. From network point of view an IP phone is a normal host. As long as two computers can communicate IP phones, ICPs and consoles will work.

 

[pichels]

Hi,

Thanks for the comments.
Right now I cannot communicate with the 3300.
I can't even talk to it with another PC.
That is why I listed all my settings.
I am confused as to what settings in the System IP config needs to be set for a flat LAN?
Can you help?
Much appreciated!

SP

 

[slapin]

Ok, do this. Assign a static IP out of DHCP range to your computer and connect it to ICP with a crossover cable. Get it working, then connect it trough the switch if it would not be able to communicate then you have to look at your VLAN config. I assume that ICP and your computer in the same VLAN connected to ports in "access mode

 

[pichels]

Hi again,

Sorry if I'm a bit slow and new to the 3300 and it's internal switch(L2) & routing, FW, DHCP, etc...

So, we need to hookup a cross-over cable if we don't use the 3300's(ICP, right?) internal L2 switch, correct?

I have all the L2 settings listed from above configured by the vendor so I'm not sure that I know how to change correctly.

We did have a PC and computer working together before we switched the gateway from 229.1 to 229.250 for the System IP config and rebooted.
Now, we can't connect to the ETH1 or ETH2 ports on the 3300 with a laptop!

1. So, unless we want to use a cross-over cable on the ETH1 or ETH2 ports to connect a computer or another switch...we need to use the 3300's internal L2 switch?
If we use the internal switch, we should be able to connect to the 3300 from the ETH1 or ETH2 port to a Cisco 3570 switch(via straight cable, no cross-over) that has a "current" LAN setup of 203.57.229.0, with a subnet, gateway, etc.

2. If the 3300 is to be connected to our 3570 Cisco switch via straight cat5 cable - are there specific port settings that need to be set? (You mentioned "access mode" - I think you mean on the 3300/ICP settings or System IP config, right?)

Thanks for the quick responses!

SP

 

[kwbMitel]

You say the static address is setup for VLAN 9.

VLAN's is the next step (Not Basic)

Once you get into VLAN's the ports that the consoles(or sets) are connected to need to be configured to accept tagged packets for the appropriate VLAN and the Network needs to be configured to "Route" the traffic to the controller port.

For your "Basic Design" I would start without VLAN's

*******************************************************
Consistancy... Is only a virtue when you're not a total screwup.

 

[slapin]

1. Not really L2 switch is just an extension of Eth1 and Eth2 ports. Could you tell us exact model of your 3300? Gateway settings don't affect communications inside the same network.

2."access mode" is the mode of the port on your Cisco 3570. It can work in access mode (VLAN tags stripped) or trunk mode (with VLAN protocol and tags) or even in mixed when host which doesn't understand VLAN tags can communicate over native VLAN and host which does use VLAN tags will communicate in predefined VLAN.

ICP has serial console, but you should use only if you clearly understand what are you doing

 

[pichels]

Hi,

Ok, I'll just start without Vlan's but the System Config is screwed up and I can't even connect with a laptop/PC now.

I "can" connect with the IP console PC though and view the settings - will someone help me with the config and/or send me an example of how the System IP config should be setup on a flat VLAN? Please? <smile>

Also, I don't want to have to connect with a cross-over in the future or obviously a serial cable ever, unless really needed in an emergency!

We have a 3300 MXe - here is the Vendor's breakdown of parts, not very detailed...

#######################################################

1 51008924 Management Access Point EM GBL
1 50002976 Power Cord Pack NA
1 50003560 DUAL T1/E1 TRUNK MMC
1 50005362 3300 MX
1 54002534 A-AMC 3300 SOFTWARE PKG #2
242 54000297 AMC 3300 - 1 MAILBOX LICENSE
1 50004203 PERIPHERAL NODE III 120V (NA)
3 MC330AB DNIC LINE CARD (CR)
1 50002979 Quad DSP MMC
40 9132-015-200-NA SUPERSET 4015 DARK
2 PT-P25X25G 25 FT PREMADE S/E MALE CABLE
1 PT-P25X25G 25 FT PREMADE S/E MALE CABLE
2 S89B Siemon Termination Blocks Stand-Off Bracket (Individual)
2 S66M-150 Siemon Termination Blocks 50 Pr. (Individual)

##########################################################

NOTE:

And now we are just trying to add a 5550 IP console - NO IP phones!
We are sticking with our old PBX(digital sets) stuff for at least 2-3 yrs.

Lastly, I don't want to jump to conclusions and really want to setup a flat LAN first...
But, ultimately I need to setup the 3300 on our VLAN so I and others can connect to the ADMIN CONSOLE software from a web browser on our network and so the Receptionist can access the 5550 IP console in the front office.
And later after I've ironed all this out configure the 3300 for setup of IP phones.
Make sense?

And so - my options on our 3570 switch don't show "access mode" unless I am missing something...I'm not much of a network admin either!

Any idea how I can find out if I have "access-mode" settings or the required settings on the 3570 port in cmd-line mode or GUI? (Sorry, I know you guys may not be Cisco Net admins!)

I cant seem to paste any images from the Cisco NET Assistant software(GUI) in here...shucks.(Wish I could zip and upload?)


Cisco3750Stack#sh interface FastEthernet6/0/32
FastEthernet6/0/32 is down, line protocol is down (notconnect)
Hardware is Fast Ethernet, address is 0016.9d06.7324 (bia 0016.9d06.7324)
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 20:25:49, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
53071 packets output, 3907305 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out


Thanks again for all of your help!

SP

 

[slapin]

I'd recommend to hire someone to fix your system. It's kind of hard to start from explanation how to use Cisco CLI.
You don't need to use a serial cable for ICP unless you cannot get any other kind of connection (there are few more options including SSL/Telnet).
We use out-of-band ethernet/serial interface adaptors for remote locations. In event of hardware/software problem which prevents normal bootup process or config got corrupted I can get access to the console from our central site.

Your sample of Cisco config says that port is not even connected

 

[woody1976]

Have you told the MXe what VLAN it is in in the ip config form? If so after the reboot only packets with a tag of this vlan would be able to communicate to the 3300, connect to RS232 console port access via hyperterminal and do the following command, vlan_off. But if all your inter vlan routing and default gateways are correct you should be able to connect to the 3300 from your other vlans. Also to connect a laptop directly to a switchport on the MXe a crossover is NOT required just a normal straight through.