ADAN oddness - DNUM 18 ???

[Barbarian7]

whoa.
Our nightly LD 43 EDD is failing with a "NO GO. BAD DATA", and I think this might be why.

Has anyone ever seen this?

ADAN     TTY 7 
  CTYP DCHI       <----- !!!!
  GRP  
  DNUM 18         <----- !!!!
  DES  PTY_&
  BPS  110 
  BITL 5
  STOP **** 
  PARY NONE 
  FLOW NO  
  USER 
  XSM  NO

Cannot out tty 7 - refuses with SCH5584
SCH5584
TTY cannot be outed.

This *was* added as DNUM 7 CTYP PTY (GRP was not prompted for), but "flipped" to this after adding a DCH:

ADAN     DCH 40 
  CTYP MSDL 
  GRP  2 
  DNUM 9 
  PORT 2 
  DES  CISCO_A
  USR  PRI 
  DCHL 76 
  OTBF 32 
  PARM RS422  DTE 
  DRAT 64KC
  CLOK EXT 
  IFC  D100
  SIDE USR 
  CNEG 1 
  RLS  ID  **
  RCAP ND2 
  T200 3 
  T203 10 
  N200 3 
  N201 260 
  K    7

Any ideas?

Barbarian

 

[bigindian65]

Funky. Are you saying that chgd up on its own?
Can you add some more printouts?
LD 37
stat

ld 96
MAP dch

ld 96
stat all dch - & MSDL and post that info

 

[Barbarian7]

Funky. Are you saying that chgd up on its own?

Yessir. And this is not the first time something like this has happened...

>ld 37
IOD000 
.stat

TTY  0 : ENBL   DES: Maint_Term_9600
TTY  1 : ENBL   DES: modem
TTY  2 : ENBL   DES: System_Monitor
TTY  3 : ENBL   DES: sw_9600
TTY  4 : ENBL   DES: cdr
TTY  10 : ENBL   DES: Core_Terminal
TTY  11 : ENBL   DES: Core_Modem


>ld 96
DCH000 
.map dch
DCH 040 : GROUP 02  MSDL 09  PORT 2 
DCH 041 : GROUP 02  MSDL 09  PORT 3 
DCH 062 : GROUP 02  MSDL 08  PORT 0 
DCH 063 : GROUP 01  MSDL 15  PORT 1 

.stat dch 40
DCH 040 : OPER       EST   ACTV  AUTO
 DES : CISCO_A
.stat dch 41
DCH 041 : OPER       EST   ACTV  AUTO
 DES : CISCO_B
.stat dch 62
DCH 062 : OPER       EST   SERV  AUTO BKUP 063 
 DES : XXX_DCH
.stat dch 63
DCH 063 : OPER       EST   STBY  AUTO PRIM 062 
 DES : XXX_DCH

.stat msdl 9
GROUP 2
GROUP 2  MSDL 9: ENBL
   DCH      40  OPER        PORT 2 
   DCH      41  OPER        PORT 3

But apart from tty 7 being unusable (!) and the EDD failing, everything else is OK. The DCH stuff seems to be working.

B

 

[bigindian65]

So, even though TTY 7 doesn't show up in 37. If you prt your ADANs in 22, it will prt out as being there? Or is it gone now because of Dch 40

 

[bigindian65]

It almost looks like a most incorrect engineering job, just by quick view, never seen a sys monitor not TTY 0. Guess it is not that big a deal, but strange.

Psuedo TTYs for 81c & SS, OTM. Recommendation is at least 2 as TTY 14 & 15, ports 0 thru 7. Looks like to me, someone tried to built Psuedo TTY 7, instead of TTY XX ON port 7. That is the recommended default config there 14 & 15 on port 0 thru 7 option.
The fact that your Sys_Monitor isn't on TTY 0 makes me think it could be a bad install some what.

 

[Reusser]

Sounds like some corruption - I would schedule a reload - you can do parrellel reload if large switch.

Put in split mode and reload and clear any problems then cutover to correct CPU.

Hopefully you have been keeping track of changes

 

[Barbarian7]

Psuedo TTYs for 81c & SS, OTM. Recommendation is at least 2 as TTY 14 & 15, ports 0 thru 7.

So... are you recommending something like:

ADAN
NEW TTY 14  CTYP PTY  DNUM 14  PORT 0
.
.
NEW TTY 14  CTYP PTY  DNUM 14  PORT 1
.
.
etc

... say for port 0,1,2,3 ? Which would then give us 4 PTYs, all on the same TTY/DNUM ?
I read a post that hinted you were restricted to 4... maybe that's only on an 11C... our's is an 81C

B

 

[bigindian65]

4s the limit, that is correct. I'm saying if you could get your two Psuedo TTYs to dnum 14 & 15, port 0 & 1 respectively, that would be ideal. I would smoke any others if there before doing the recommended config

 

[Barbarian7]

OK.
So that would be :
dnum 14 port 0
dnum 14 port 1
dnum 15 port 0
dnum 15 port 1

Are those the correct steps in ADAN, ie: doing NEW TTY 14 (twice) for TTY 14, once with port 0, then again with port 1?

Thanks,
B

 

[bigindian65]

no you want

14 port 0

15 port 1

 

[Barbarian7]

...so what is the relevance of "port #" then if we are only putting one PTY per DNUM?

 

[bigindian65]

I really do not know, I would guess it has something to do with the fact that it is psuedo, and the port range is given by Nortel as 0 thru 7 for a choice, must want PTYs to each have unique port numbers, even though on different DNUMs.