| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1780.1 | check these things out | NETCAD::CURRIER | | Wed Dec 14 1994 14:17 | 9 |
| Check the speed of your OBM port. Does it match that of your comm
port? Also, the MAM expects full rs232 at the OBM port. Verify that
you cable supports all the signals. We've had bad cables in the past.
When you say that you've set up the Hub900 IN-Bound and Out-Bound IP
addresses I assume that you selected the 'Set Out-if-Band Interface IP
Address' entry on the set-up menu. Also, make sure that the adaptor
that you have conencted to the OBM port is H8571-J.
|
| 1780.2 | a little closer | KAOFS::S_BAINS | | Wed Dec 14 1994 14:54 | 10 |
| Well I am a little closer, I can now ping the hub (i had to make the
laptop IP address the same as the OBM IP address). Now when I start
Hubwatch from windows and give it the OBM ip address I get back that
the agent does not respond. I have double checked my files and the
PWTCP.ini file and all looks OK. The Hub900 that I am playing with is a
stand alone ie not connected to anything and the one module that is in
the hub is a Decrepeater900TM. I should still be able to bring up
Hubwatch right!
santokh
|
| 1780.3 | Pinging yourself? | NAC::FORREST | | Thu Dec 15 1994 10:27 | 7 |
| Santokh, I think that by making the Laptop IP address= Hub OBM IP
address, you are really getting the Ping response from your Laptop.
Have you checked out the instructions in Appendix B in the HUBwatch
Installation and Configuration manual?
jack
|
| 1780.4 | still HUBling along | KAOFS::S_BAINS | | Thu Dec 15 1994 17:41 | 8 |
| Jack,
I went thru appendix B several times and everything looks okay. It said
in the manual to make the pc ip address the same as the OBM port
address (iwas a little confused there) this was on page 2-5 Hubwatch
for Windows USE manual
santokh
|
| 1780.5 | PC IP <> OBM IP | NETCAD::SLAWRENCE | | Fri Dec 16 1994 12:20 | 12 |
|
Those setup instructions are a little misleading.
IF you are connecting the OBM port to a Terminal Server port in order
to provide SLIP to it, then the 'Host Address' configured for that
Terminal Server port must be the same as the OBM port address for the
hub it is connected to.
IF you are connecting a PC or other NMS system directly to the OBM port
using a crossover cable or modems, then the IP addresses of the hub OBM
port and the PC must be different.
|
| 1780.6 | thank for the help | KAOFS::S_BAINS | | Mon Dec 19 1994 12:39 | 7 |
| Thanks for clearing that up for me. I am going to take another look at
the cable that I made up, maybe I'll just order the right cable.
Thanks for the help
santokh
|
| 1780.7 | still no go | KAOFS::S_BAINS | | Thu Dec 22 1994 12:51 | 7 |
| I have the right cable now, but I still cannot Ping to the hub. What
should my IP Mask be set for?. Right now I have it set for
255.255.255.2
thanks
santokh
|
| 1780.8 | | NETCAD::SLAWRENCE | | Thu Dec 22 1994 15:45 | 5 |
|
Try just describing in as much detail as you can stand, including your
PC configuration file contents and the output on 'Show Current
Settings' of the hub setup port.
|