T.R | Title | User | Personal Name | Date | Lines |
---|
4774.1 | You gotta.. | MCDOUG::doug | pre-retinal integration | Fri Mar 26 1993 14:15 | 13 |
| 1. You gotta have the version of Translan software that *supports* SNMP.
2. You gotta run the Vitalink MIB extensions though the MTU and load them
into your dictionary if you want to see any of the Vitalink-specific
thingies from MCC
3. You gotta use the REC utility on each TransLAN bridge to
configure its IP Address, community names, trap destinations, blah
blah...
4. You gotta make sure that the IP name/address for the TransLAN bridge is
either in your /etc/hosts, bind server or UCX hosts database.
5. You gotta register it as an SNMP object -- same as any other SNMP object
that you register (router, workstation, toaster, etc)
/doug
|
4774.2 | | IOOSRV::GALVIN | Mic, (319) 363-1508 | Sat Mar 27 1993 11:09 | 44 |
| Doug,
#1. The Translan Bridges are at version 11.2, and in the Vitalink
Technical Notes it says they support SNMP, "...SNMP... supported in
Version 11.2... defined as... MIB objects. All MIB I and MIB II
objects and functionality are supported except for IP Rout Table's
ability to accept "sets.""
#2. Ran the MCC_TCPIP_MTU.COM, with no trouble... It updated the
dictionary & parse tables.
#3. I don't understand this one? The "REC" utility on each TransLAN
bridge??? please explain.
#4. UCX SHOW HOST produces:
146.170.64.12 CRACP1 ! this is a TransLAN Bridge on the
same segment as the MCC station.
#5. This is my problem! When I try to register any TransLAN Bridge,
using it's Internet Address I get a partial registration,
"Identifier attributes for unreachable entity are:"
Registered Name LOCAL_NS:.cracp1
Address 146.170.64.12
Name CRACP1
When I try to look at any of the entities, I get (SHOW STATUS
operation):
Internet communications device error
BTW, the version of UCX is 1.3a? Should I attempt to update to UCX
version 2? Could this be a problem?
One last question... is there a way to register an SNMP object
(TransLAN), with just the ethernet address, ie: 08-00-7c... Can I look
at a bridge and determine it's Internet Address by using it's physical
address? Thanks.
/Mic
|
4774.3 | UCX 1.3 OK for Vitalinks | CSOADM::ROTH | ELVIS:: is alive... and reachable!! | Sat Mar 27 1993 21:43 | 17 |
| I was able to access vitalink boxes with UCX v1.3.
The 'rec' is the 'reconfig' command in the Vitalink command interface
available on the Vitalinks. If you don't know what the 'rec' command
is then it's 99% likely that you have not configured the Vitalink.
As Doug pointed out, you must configure the Vitalink to give it its IP
address and other details.
Try this one:
$ UCX TEST <ip address of Vitalink box> !For V1.3 UCX
$ UCX PING <ip address of Vitalink box> !For V2.0 UCX
Does the Vitalink pass or fail the ping test?
Lee
|
4774.4 | "always mount a *scratch* vitalink..." | IOOSRV::GALVIN | Mic, (319) 363-1508 | Tue Mar 30 1993 12:11 | 14 |
| Hi,
Well the case of the missing vitalink(s) has been put to bed! The
problem was quite simple. In running the UCX$CONFIG.COM, I had
*inadvertently* used a 255... Internet address...oops!
The vitalink bridges were very *efficient* in filtering out 255... 8^).
Customer issued a 146... address and I'm now able to manage these
puppies... One question that went unanswered, does UCX version 2 buy
me anything? I'm running VMS 5.5-2, EMS 2.2. Again, thank everyone
for your help...
/Mic
|
4774.5 | | TOOK::MCPHERSON | pre-retinal integration | Tue Mar 30 1993 14:53 | 8 |
| > puppies... One question that went unanswered, does UCX version 2 buy
> me anything? I'm running VMS 5.5-2, EMS 2.2.
UCX 2.0 will buy you
1. lots of bug-fixes.
2. an SNMP agent for your VMS system
/doug
|