Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ping ip-address board 01B10 192.1.1.22 2

Status
Not open for further replies.

telcomwork

Technical User
Mar 2, 2002
1,625
US
What would be some reasons why I wouldn't be able to ping some CLAN cards but not others? All are setup with data mods and port 17.

Here's my error message. I'm also trying to find out what the code is on Avaya documenation but if anyone knows it would you please share?

End-pt IP Port Port Type Result Time(ms) Error Code

192.1.1.22 01C1317 ETH-PT FAIL 1007

Many thanks
 
telcomwork,

first, are you sure what you're doing? to me, it seems that you're not. ping command basically receives two arguments: to-address - ip address of remote host that you want to ping, and from-address, in this case physical address of the board that should be used to send an icmp packet. if you have more than one c-lan board, it's probably because you have more than one network, either physical or logical, and different c-lans connect to different subnets. therefore, it's perfectly normal not to being able to ping particular hosts from particular c-lan boards, since these subnets can be dedicated without any connectivity between them.
here is an example: if you have a cms system, you should know that avaya recommends using dedicated c-lan board for cms connectivity. in this case, direct connection (or two ports on the switch in dedicated vlan) is used with some private ip addressing scheme, so these private ip addresses would not be reachable from any other c-lan board.
as for the second part of your question, try taking a look here.
 
Not using VLANs.

dwalin I think I know what I'm doing but then again that's why I'm asking some questions. I have other CLAN in the same subnet I can ping just not this one.

The Clan I'm pinging from 1C1317 (192.1.1.24)is in the same subnet and shares the same gateway as the CLAN I'm trying to ping 192.1.1.22 (1C15). One thing I notice is when I status the link it's "restarting". SHould I still be able to ping the CLAN though? It's not like I'm trying to ping a resource outside the PBX..

Thanks all!
 
And if you put a machine on this subnet with a new ip trying to ping these address...

Just an idea but maybe the interface is busy or disable...
 
Haven't tried that yet. Shouldn't I be able to ping from clan to clan, for instance I'm trying to verify connectivity for firware upgrades?

Thank you for helping and your suggestions.
 
One other question to upgrade multiple TN799DP they have to be "Self Download" one at a time or can you use a one CLAN to upgraqe many CLANs in a "Distributed" type of download?
 
If I'm reading the doc correctly it has to be Self but want to be sure
 
telcomwork,

1. if both devices are on the same subnet, you should be able to ping each other. if the link is "restarting", first check data module for this c-lan, then check ethernet settings, then check physical connectivity. maybe it's a wrong port on the lan switch.
2. yes, c-lans have only self-download ability. you can't use one c-lan board as a source for other c-lans.
also it means that you can only upgrade one c-lan at a time.
 
faq690-5977

Tha above may make it go a little easier for you. Each cabinet needs it's own C-LAN to upgrade not only itself but the other packs in the same cabinet that need firmware upgrades.



Mikey
 
For me it your link is restarting obviously the ping never respond. Usually it is restarting when you hav done a bad cable connection, the LAN connection adapter is not the appropiate or in Prologix systems when you have not added a Second Packet Interface in system-parameters maintenance. I think you don´t need a firmware upgrade just to ping the board.

Hope it helps.
 
when a clan is restarting state, ping will not respond. If a busy board and a release board does not do the trick, you will need to reseat the board to let it restart.

the key is fixing the restarting problem first.

you mention TN799DP ...
What type of carrier ?
If it is a G600, CMC1 (proligix) or one of those SCC or MCC carrier have you changed that BUS cable between your carrier backplane and your AMPHENOL connector in the back. These nornally comes only with a CAT3 BUS cable and AVAYA has a field upgrade kit that converts this to a CAT5 BUS cable. To do this you will need to power down the carrier.

Error Code 1007
document id 03_300190 issue 3, page 1127
Ping to the destination failed due to the destination down.
1. Verify that at least one destination reachable through this port is up. Ping this destination (ping ip-address xxx.xxx.xxx.xxx).
2. If the ping to any destination is successful through this port, the link is up, although some destinations are unreachable. Ignore the failure.
3. If ping to every destination fails, test this port (test port location short), and follow the repair procedures for Session Status test (#1286) failures.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top