Signaling Servers

[worldwidedialtone]

When setting up signaling servers and using a BayStack 470 as my router/hub, I did not find a place to enter a T-LAN IP address for the Baystack. The Leader Signal Server came up fine. My problems started with the Follower and the Media Gateway Card. Using Element Manager I could not add the card or do the "Introduce Follower to Leader" in the Node Configration. I can "ping" everything on the E-LAN side (top of BayStack) but not "ping" anything on the T-LAN side. Hope this makes sense. Double checked by cabling and tested it so I know that is not my problem. Thanks in advance for any enlightenment.

 

[johnpoole]

shot in the dark, the e-lan is enbedded, just the nortel side of the network, the t-lan must be a different network, and that is where your phone plug in..

john poole
bellsouth business
columbia,sc

 

[worldwidedialtone]

Was told when setting up the BayStack to have the E-LAN from both Signaling servers on the top and the T-lan from both servers connected to the bottom. Then MIRAN, Call Pilot and the switch along with OTM PC and CDR PC connected to the ELAN (top half). The Media Gateway Card E-LAN to the top and the T-LAN to the bottom. Top part or E-LAN seems to work just fine. My first one for an installation so most of it and the concept is new to me and a bit fuzzy to say the least.

 

[johnpoole]

as long as the c-lan and t-lan or not on the same braodcast domain. the call pilot connecets to both the t and e, but that is a dual nic server, working as a basic router betweent the two ports, thus blocking broadcast and unicast. in ld 117 make sure the switch ethernet port is built right and active, right subnet, then you should be able to ping the e lan from that load.. ping btw is a broadcast, so it needs to be blocked between the two nets. not as hard as it seems, after you get one up the 1st time..

john poole
bellsouth business
columbia,sc

 

[rhynecomm]

Data Networking for Voice over IP
NTP 553-3001-160

The TLAN subnet is a 100BaseT full-duplex LAN that connects all Voice Gateway Media Cards and Signaling Servers within an IP telephony node. An IP telephony node is defined as a logical grouping of Voice Gateway Media Cards and Signaling Servers.
A device in a single IP telephony node cannot be a member of more than one subnet/VLAN. However, a subnet can have more that one IP telephony node as a member.
Nortel Networks recommends use of a Layer 2 switch with broadcast and multicast rate limiting for the TLAN subnet.
Use of a Layer 2 switch with broadcast and multicast rate limiting is recommended for the TLAN subnet.
Optionally, the TLAN subnet can be configured as a restricted-access subnet.
This can be accomplished by using a packet filtering device (for example, a firewall) to restrict traffic, based on source IP address or TCP/UDP port numbers, allowed to enter the TLAN subnet.
Port prioritization is recommended for all TLAN onnections. For detailed information on port prioritization, see “QoS mechanisms” on page 47.
Recommendation
Nortel Networks recommends that customers configure the TLAN
subnet to carry only CS 1000-specific traffic, and be separated from the rest of the enterprise IP network by a Layer 3 switch. Deploy the IP Phones on the client side of the enterprise IP network.

 

[dlesap]

ELAN and TLAN must be in separated Subnets, and may be routed.
When configuring the Node in Element manager, you have to enter the datas in the right order : Node, Codecs, Lan, Card(s), SigServ before to transmit to all elements. You will have to restart manually all these elements : SSs, MCs.
The transmited parameters will failed for MCs, but will be OK after reboot.
If you are not sure about the Switch configuration, replace it with your own hubs for test only. One hub for each LAN.
The switch ports MUST be in autonegociated for Duplex AND speed.

 

[worldwidedialtone]

Okay, let me ask this: Is there a place on the BayStack 470 that has an input field for an IP address for the T-Lan. If there is, I missed it on the first go around.

 

[dlesap]

I don't know any switch conf. But i guess that it have to be correctly configured with a subnet, not IP@

 

[biv343]

The Baystack 470 is a layer 2 only device, it doesn't route.

You'd want to split the switch into two VLANs, say VLAN1 and VLAN 2. Assign the ports to the VLANs, set the PVID on the port to match the VLAN, and you're good to go. There is a management IP address on the switch which can be tied to a VLAN.