[Show all top banners]

newguyintown
Replies to this thread:

More by newguyintown
What people are reading
Subscribers
:: Subscribe
Back to: Kurakani General Refresh page to view new replies
 Linux/ Unix: IMMs ACCESS Failed
[VIEWED 8349 TIMES]
SAVE! for ease of future access.
Posted on 09-04-13 3:50 PM     Reply [Subscribe]
Login in to Rate this Post:     0       ?    
 

PROD IMMs ACCESS Failed:

I can not access IMM.
 
Here’s what we’ve tried so far:
1.            Normally can access the IMMs from browser (once connected to network – but the GUI does not always come up for either IMM1 nor IMM2.
2.            The IMMs on PROD2 are fine.
3.            Cannot telnet nor SSH to the IMMs either.
4.            I can ping the IMM IP addresses from the switches, so I think the mgmt network to them is okay…and can get to the AMMs on the same frame.
5.            I rebooted one of the M4s and that did not change the issue.  The access came back on its own.
 
I saw the following message in the IMM web interface when he navigated to IMM Management > Network:
 
The IMM2 is assigned a static IP address. When using a hostname or FQDN (Fully Qualified Domain Name) , at least one DNS (Domain Name System) server must be specified in DNS tab and make sure the DNS server can resolve the hostname or FQDN to the IP address. Otherwise, communication errors will occur.
 
I don’t want to assume this is the issue, but perhaps some investigation could be done.
 
Posted on 09-04-13 3:58 PM     [Snapshot: 4]     Reply [Subscribe]
Login in to Rate this Post:     0       ?    
 

Any ideas/ comments/ feedback to troubleshoot this issue would be highly appreciated.
 
Posted on 09-04-13 4:13 PM     [Snapshot: 5]     Reply [Subscribe]
Login in to Rate this Post:     0       ?    
 

There is definitely something going on with the networking to the IMMs.  From a BNT switch I issued constant ping commands to of the IMM IP addresses in Prod 2:
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 timed out.
10.214.15.17: #2 timed out.
10.214.15.17: #3 timed out.
10.214.15.17: #4 timed out.
10.214.15.17: #5 timed out.
Ping finished.
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 timed out.
10.214.15.17: #2 timed out.
10.214.15.17: #3 timed out.
10.214.15.17: #4 timed out.
10.214.15.17: #5 timed out.
Ping finished.
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 ok, RTT 0 msec.
10.214.15.17: #2 ok, RTT 1 msec.
10.214.15.17: #3 ok, RTT 1 msec.
10.214.15.17: #4 ok, RTT 1 msec.
10.214.15.17: #5 ok, RTT 1 msec.
Ping finished.
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 timed out.
10.214.15.17: #2 timed out.
10.214.15.17: #3 timed out.
10.214.15.17: #4 timed out.
10.214.15.17: #5 timed out.
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 ok, RTT 797 msec.
10.214.15.17: #2 ok, RTT 1 msec.
10.214.15.17: #3 ok, RTT 1 msec.
10.214.15.17: #4 ok, RTT 1 msec.
10.214.15.17: #5 ok, RTT 1 msec.

 
Posted on 09-04-13 4:44 PM     [Snapshot: 25]     Reply [Subscribe]
Login in to Rate this Post:     0       ?    
 

There is definitely something going on with the networking to the IMMs.  From a BNT switch I issued constant ping commands to of the IMM IP addresses in Prod 2:
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 timed out.
10.214.15.17: #2 timed out.
10.214.15.17: #3 timed out.
10.214.15.17: #4 timed out.
10.214.15.17: #5 timed out.
Ping finished.
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 timed out.
10.214.15.17: #2 timed out.
10.214.15.17: #3 timed out.
10.214.15.17: #4 timed out.
10.214.15.17: #5 timed out.
Ping finished.
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 ok, RTT 0 msec.
10.214.15.17: #2 ok, RTT 1 msec.
10.214.15.17: #3 ok, RTT 1 msec.
10.214.15.17: #4 ok, RTT 1 msec.
10.214.15.17: #5 ok, RTT 1 msec.
Ping finished.
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 timed out.
10.214.15.17: #2 timed out.
10.214.15.17: #3 timed out.
10.214.15.17: #4 timed out.
10.214.15.17: #5 timed out.
 
sambx13#ping 10.214.15.17
[host 10.214.15.17, max tries 5, delay 1000 msec , length 0]
10.214.15.17: #1 ok, RTT 797 msec.
10.214.15.17: #2 ok, RTT 1 msec.
10.214.15.17: #3 ok, RTT 1 msec.
10.214.15.17: #4 ok, RTT 1 msec.
10.214.15.17: #5 ok, RTT 1 msec.

 
Posted on 09-04-13 7:28 PM     [Snapshot: 66]     Reply [Subscribe]
Login in to Rate this Post:     0       ?    
 

Is it a layer 3 switch? Post the routing table and the arp table. 

"route -n" or "show route" or "show arp" or "show ethernet switching-table" whichever is close to your switch CLI.

 


Please Log in! to be able to reply! If you don't have a login, please register here.

YOU CAN ALSO



IN ORDER TO POST!




Within last 7 days
Recommended Popular Threads Controvertial Threads
TPS Re-registration case still pending ..
and it begins - on Day 1 Trump will begin operations to deport millions of undocumented immigrants
NOTE: The opinions here represent the opinions of the individual posters, and not of Sajha.com. It is not possible for sajha.com to monitor all the postings, since sajha.com merely seeks to provide a cyber location for discussing ideas and concerns related to Nepal and the Nepalis. Please send an email to admin@sajha.com using a valid email address if you want any posting to be considered for deletion. Your request will be handled on a one to one basis. Sajha.com is a service please don't abuse it. - Thanks.

Sajha.com Privacy Policy

Like us in Facebook!

↑ Back to Top
free counters