From: Jesse Sales <jsales@last-call.cisco.com>
Subject: Re: (Still) can't reach remote Cisco via MOP remote console
Date: 16 Nov 92 16:15:54 PST
X-Note1: mail msgid was <CMM.0.90.2.721959354.jsales@last-call.cisco.com>
X-Note2: message-id generated by recnews

Your Case Number is:

	40311

We will begin working your problem shortly. Please reference this case
number in  all correspondence on  this subject. For  email, begin your
subject line with  "Case" followed by the  number above.  For example,
"Case ##### additional info".
	
You may  also contact  the   TAC   (Technical Assistance  Center)  via
telephone  at (800) 553-2447  or (415) 903-7209,   or by FAX  at (415)
903-8787. Our operating hours are 0500  to 1800 Pacific Standard Time,
USA. In all   cases,  providing your  service  contract    number will
accelerate our assistance.
	-------------------------------------------------------

> Now that 14 months have gone by, and I hadn't read about it in release notes or
> on CIO, I tried this again to see if by some chance it was fixed.  Nope.  :-(
> Moreover, the remote IGS at the end of the serial link (running 8.3(5)) no
> longer even sees the connection attempt!  Looks like someone tidied this up
> but in the opposite direction.
> 
> Is it still Cisco's intention to remove this restriction?  Any idea when?
> The main reason we want this is given at the very end of this message.
> 
> Thank you,
> Marty Adkins
> Networks & Communications
> Westinghouse Electronic Systems Group
> Internet: Adkins@plaza.wec.com
> 
> >From:   PLAZA::VSG          "Marty Adkins, VAX Support Group, MS 1615, WIN 285-1479"  9-SEP-1991 19:07:40.57
> >To:     TRON::"uunet!cisco.com!john"
> >CC:     TRON::"cisco@spot.colorado.edu",VSG
> >Subj:   RE: Remote console (MOP) not passed in 8.2(4)?
> > 
> >>From:  TRON::"uunet!cisco.com!john"  9-SEP-1991 18:02:38.40
> >>To:    plaza::vsg
> >>CC:    VSG
> >>Subj:  Remote console (MOP) not passed in 8.2(4)?
> >>
> >>
> >>
> >>By phone line I meant any serial line. sorry for my term usage.
> >>
> >>
> >>MOP console connects to ciscos are presently support on incoming
> >>ethernet ports not over serial lines. MOP connections to units
> >>at the end of serial lines will be supported in a future release
> >>(best ESTIMATE 2nd qtr '92)
> >>
> >>    VAXenE                   VAXenF
> >>     |                       |
> >>   A--ether---B ----T1----C----ether---D
> >>
> >>
> >>VAXenF can MOP connect to C,D, and A  but not B
> >>VAXenE can MOP connect to B,A, and D  but not C
> >>
> >>
> >>Regards,
> >>John Wright
> >>Customer Engineering Analyst
> >>cisco Systems, Inc.
> >...............................................................................
> >Thanks for the quick response.  That kind of restriction in the implementation
> >never occurred to me!  Just in case you haven't already heard it from others,
> >we use MOP connect when we need to make a configuration change on a remote
> >Cisco which has no out-of-band console connection, and the change we wish to
> >make will shut down IP.  E.G., to change the serial port address to unnumbered,
> >the configuator insists that we first remove the existing IP address, which
> >of course pulls the rug out from under you.
> > 
> >Marty Adkins
> >Distributed Systems
> >Westinghouse Electronic Systems Group
> >Adkins@Plaza.WEC.COM
> ..............................................................................
> >From:   PLAZA::VSG          "Marty Adkins, VAX Support Group, MS 1615, WIN 285-1479"  9-SEP-1991 14:27:59.07
> >To:     TRON::"cs@cisco.com"
> >CC:     ECLUS::NETWORK,VSG
> >Subj:   Remote console (MOP) not passed in 8.2(4)?
> > 
> >We were bit by the 8.2(3) bug which broke MOP when DECnet was being routed.
> >Since we started running 8.2(4) on our AGS, we can now make a MOP connection
> >from a DECnet node to the AGS (they're on the same LAN), but cannot connect
> >to other Ciscos beyond the AGS.  The AGS and the other boxes are configured
> >to bridge MOP.  If I enable "debug mop" on the AGS, a MOP connection to it
> >looks as expected:
> > 
> >MOP: Reserving console for aa00.0400.2e11
> >MOP: Got request_id message from aa00.0400.2e11
> >MOP: Sending sysid message to aa00.0400.2e11
> > 
> >Now if we try to connect to one of the IGSs (also running 8.2(4)), connected
> >via a serial link to the AGS, here's the MOP debug output from the IGS:
> > 
> >MOP: Reserving console for aa00.0400.2e11
> >MOP: Got request_id message from aa00.0400.2e11
> >MOP: Sending sysid message to aa00.0400.2e11
> >MOP: Console reservation from aa00.0400.2e11 while reserved by aa00.0400.2e11
> >MOP: Reserving console for aa00.0400.2e11
> >MOP: Got request_id message from aa00.0400.2e11
> >MOP: Sending sysid message to aa00.0400.2e11
> >MOP: Console reservation from aa00.0400.2e11 while reserved by aa00.0400.2e11
> >MOP: Reserving console for aa00.0400.2e11
> >MOP: Got request_id message from aa00.0400.2e11
> >MOP: Sending sysid message to aa00.0400.2e11
> >MOP: Console reservation from aa00.0400.2e11 while reserved by aa00.0400.2e11
> >MOP: Reserving console for aa00.0400.2e11
> >MOP: Got request_id message from aa00.0400.2e11
> >MOP: Sending sysid message to aa00.0400.2e11
> >MOP: Console reservation from aa00.0400.2e11 while reserved by aa00.0400.2e11
> >MOP: Reserving console for aa00.0400.2e11
> >MOP: Got request_id message from aa00.0400.2e11
> >MOP: Sending sysid message to aa00.0400.2e11
> > 
> >The DECnet host gives up with:
> >  NCP>connect via sva-0 phy addr aa-00-04-00-2b-13
> >  Target does not respond
> > 
> >Note that the IGS did get the messages and respond, but the responses 
> >apparently never made it back to the DECnet host.  I'm guessing that the AGS
> >didn't bridge them in the reverse direction.
> > 
> >Here's the config info for the AGS and one of the IGSs --
> > 
> >cenrt1#sh hard
> >GS Software (GS3-BF), Version 8.2(4) 
> >Copyright (c) 1986-1991 by cisco Systems, Inc.
> >Compiled Tue 28-May-91 13:55 by mlb
> > 
> >System Bootstrap, Version 4.3(3) 
> > 
> >cenrt1 uptime is 4 days, 22 hours, 26 minutes
> >System restarted by bus error at PC 0x36950, address 0x39E0118
> >Running default software
> > 
> >CSC3 (68020) processor with 4096K bytes of memory.
> >Bridging software.
> >2 MCI controller.
> >1 cBus controller.
> >8 Ethernet/IEEE 802.3 interface.
> >6 Serial network interface.
> >Environmental Controller.
> >64K bytes of multibus memory.
> >64K bytes of non-volatile configuration memory.
> >Configuration register is 0x101
> > 
> >cenrt1#wr ter
> > 
> >Current configuration:
> >!
> >enable-password ______________
> >!
> >ip accounting-list 129.228.0.0 0.0.255.255
> >ip accounting-transits 500
> >!
> >decnet routing 4.810
> >decnet node-type area
> >decnet max-address 1023
> >decnet max-hops 10
> >!
> >interface Ethernet 0
> >ip address 129.228.44.200 255.255.255.0 secondary
> >ip address 129.228.39.1 255.255.255.0 secondary
> >ip address 129.228.46.1 255.255.255.0 secondary
> >ip address 129.228.4.88 255.255.255.0
> >ip accounting
> >decnet cost 3
> >bridge-group 1
> >!
> >interface Serial 0
> >ip address 129.228.99.2 255.255.255.0
> >no ip route-cache
> >bandwidth 64
> >shutdown
> >hold-queue 60 out
> >decnet cost 5
> >no decnet route-cache
> >bridge-group 1
> >bridge-group 1 lat-compression
> >bridge-group 1 output-type-list 201
> >!
> >interface Ethernet 1
> >no ip address
> >shutdown
> >!
> >interface Serial 1              <======= serial link to IGS
> >ip unnumbered Ethernet0
> >bandwidth 768
> >decnet cost 4
> >bridge-group 1
> >!
> >interface Serial 2
> >ip unnumbered Ethernet0
> >bandwidth 512
> >decnet cost 5
> >bridge-group 1
> >!
> >interface Serial 3
> >ip address 129.228.98.1 255.255.255.0
> >!
> >interface Serial 4
> >ip address 129.228.97.1 255.255.255.0
> >!
> >interface Serial 5
> >ip unnumbered Ethernet0
> >decnet cost 4
> >bridge-group 1
> >bridge-group 1 output-type-list 201
> >!
> >interface Ethernet 2
> >no ip address
> >shutdown
> >!
> >interface Ethernet 3
> >no ip address
> >shutdown
> >!
> >interface Ethernet 4
> >no ip address
> >shutdown
> >!
> >interface Ethernet 5
> >no ip address
> >shutdown
> >!
> >interface Ethernet 6
> >no ip address
> >shutdown
> >!
> >interface Ethernet 7
> >no ip address
> >shutdown
> >!
> >router rip
> >network 129.228.0.0
> >!
> >ip default-network 129.228.0.0
> >!
> >domain-list BWI.WEC.COM
> >domain-list BALT.WEC.COM
> >ip name-server 129.228.4.1
> >ip name-server 129.228.4.8
> >snmp-server community
> >snmp-server community riggiO RO
> >bridge 1 protocol dec
> >bridge 1 forward-time 24
> >access-list 201 permit 0x6004 0x0000
> >access-list 201 permit 0x6002 0x0000
> >access-list 201 permit 0x6001 0x0000
> >access-list 201 permit 0x9000 0x0000
> >access-list 201 deny   0x0000 0xFFFF
> >priority-list 1 protocol bridge medium
> >hostname cenrt1
> >logging buffered
> >!
> >line con 0
> >login
> >line vty 0 4
> >login
> >line con 0
> >escape-character 3
> >exec-timeout 0 0
> >password __________
> >line aux 0
> >escape-character 3
> >exec-timeout 0 0
> >password __________
> >line vty 0
> >escape-character 3
> >exec-timeout 30 0
> >password __________
> >line vty 1
> >escape-character 3
> >exec-timeout 30 0
> >password __________
> >line vty 2
> >escape-character 3
> >exec-timeout 30 0
> >password __________
> >line vty 3
> >escape-character 3
> >exec-timeout 30 0
> >password __________
> >line vty 4
> >escape-character 3
> >exec-timeout 30 0
> >password __________
> >!
> >end
> >...............................................................................
> >macrtr#sh har
> >IGS-BR Software, Version 8.2(4) 
> >Copyright (c) 1986-1991 by cisco Systems, Inc.
> >Compiled Tue 28-May-91 14:56 by mlb
> > 
> >System Bootstrap, Version 4.3(3) 
> > 
> >macrtr uptime is 1 week, 3 days, 1 hour, 1 minute
> >System restarted by power-on
> >Running default software
> > 
> >cisco IGS (68020) processor (revision D) with 4608K bytes of memory.
> >Processor board serial number 00227338
> >Bridging software.
> >1 Ethernet/IEEE 802.3 interface.
> >1 Serial network interface.
> >16K bytes of non-volatile configuration memory.
> >Configuration register is 0x101
> > 
> >macrtr#wr ter
> > 
> >Current configuration:
> >!
> >enable-password _________________
> >!
> >decnet routing 4.811
> >decnet node-type routing-iv
> >decnet max-address 1023
> >decnet max-hops 10
> >!
> >interface Ethernet 0
> >ip address 129.228.27.10 255.255.255.0
> >decnet cost 4
> >bridge-group 1
> >!
> >interface Serial 0
> >ip address 129.228.26.1 255.255.255.0
> >bandwidth 768
> >decnet cost 5
> >bridge-group 1
> >!
> >router rip
> >network 129.228.0.0
> >!
> >domain-list BWI.WEC.COM
> >domain-list BALT.WEC.COM
> >ip name-server 129.228.4.1
> >ip name-server 129.228.4.8
> >snmp-server community riggiO RO
> >bridge 1 protocol dec
> >bridge 1 forward-time 24
> >hostname macrtr
> >logging buffered
> >!
> >line con 0
> >login
> >line aux 0
> >login
> >line vty 0 4
> >login
> >line con 0
> >escape-character 3
> >exec-timeout 15 0
> >password __________
> >line aux 0
> >escape-character 3
> >exec-timeout 15 0
> >password __________
> >line vty 0
> >escape-character 3
> >exec-timeout 15 0
> >password __________
> >line vty 1
> >escape-character 3
> >exec-timeout 15 0
> >password __________
> >line vty 2
> >escape-character 3
> >exec-timeout 15 0
> >password __________
> >line vty 3
> >escape-character 3
> >exec-timeout 15 0
> >password __________
> >line vty 4
> >password __________
> >!
> >end
> > 
> >Marty Adkins
> >Distributed Systems
> >Westinghouse Electronic Systems Group
> > 
> >U.S. Mail:                          Westinghouse DECnet: PLAZA::ADKINS
> >  Westinghouse Electric Corp.       MTS400: ADKINS.M.J
> >  P.O. Box 746 MS 1615              X.400: 6=Adkins.M.J@5=Westinghouse@3=WEMS
> >  Baltimore, Md. 21203                     @2=DIALCOM@1=US
> >  (301)765-1479/(WIN)285-1479       Internet: Adkins@Plaza.WEC.COM
>