TransmitIP trunk card configuration data from TM 3.1 to the IP trunk cards 267
Figure 61
IP trunk card status
If the (a) IP Trunk3.01 (and later) Node is being installed from an
TM 3.1 PC on a remote subnet, and (b) communication with the
Leader 1 and the Followercards is not possible after transmitting
the node properties, card properties and dialing plan to Leader
0 and rebooting the Leader 0 card, this means that the Leader
1 and the Follower cards are unable to communicate with the
remote TM 3.1 PC.This is usually due to the factthat the IP tr unk
card no longer defaults to communicating with the same router
as the one used by TM 3.1. By default, IP traffic is directed to the
TLAN router, as most IP trafficuses the TLAN subnet. If the TM
3.1 PC is on the ELAN subnet, which is separate from the TLAN
subnet, there probably is no routing table entry to route IP traffic
meant for the TM 3.1 PC IP address to that ELAN router.
This can be corrected by connecting a local terminal to the
maintenance port on the faceplate of the Leader 1 and Follower
cards. Use the ITG shell command routeAdd on Leader 1
and each Follower card to add a new IP route for the remote
TM 3.1 PC subnet that points to the ELAN network interface
gateway (router) IP address. Repeat this step every time a card
is reset until the card properties, which contain the card routing
table entry IP addresses, have been successfully transmitted
to each card.
ITG> routeAdd "xxx.xxx.xxx.xxx", "yyy.yyy.yyy.yyy",
where
xxx.xxx.xxx.xxx is the IP address of the remote TM 3.1
PC and
yyy.yyy.yyy.yyy is the IP address of the ELAN network
interface gateway.
Press Enter.
Nortel Communication Server 1000
IP TrunkFundamentals
NN43001-563 02.01 Standard
Release 5.5 21December 2007
Copyright© 2007, Nor tel Networks
.