Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
Has anyone seen this? We have a DECagent 90 at 1.0 in a community hub, and no bridge in the first 8 slots, but have it in slot 16. The rev of the 90fl is F04. Upon power up the bridge wasn't seen and if added dropped on the next poll. It was decided that the agent should be switched to a standalone to see if it would help. The agent was told to be a standalone and then powered down. We then got a power supply for it and fired it back up. This time it found the bridge but for some reason all previous information in the agent's proms were gone!!! Needless to say the customer isn't impressed. Why did we lose the information previously stored in the prom?? Thanks Gregg
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
180.1 | You changed communities | EMDS::SEAVER | Bill Seaver, HUBwatch Mktg | Thu Mar 11 1993 22:18 | 11 |
The real expert on this is KALI::GAUDET, but I will try a few answers. 1. Agent 1.0 does not see bridge in 16. Try V 1.1- see VMS_LAUNCH.TXT for location. If the bug still exists, contact KALI::GAUDET. 2. As to "loosing all the data". I'm not sure what you mean. You do not mention having to reload the agent, so I'm assuming you "lost all" data about modules in the hub. This would happen becaue you defined a new community for the bridge, since I assume the agent's community went with it to stand alone. Repeaters should be autodiscovered, but 90L+ will not be. |