[mse.rus77]

Коллеги, приветствую. Проблема с EX4200-24T, девайс новый, из коробки.

Включаем, идет бут:

 

U-Boot 1.1.6 (Feb 6 2008 - 11:27:42)

 

Board: EX4200-24T 2.17

EPLD: Version 6.0 (0x85)

DRAM: Initializing (1024 MB)

FLASH: 8 MB

USB: scanning bus for devices... 2 USB Device(s) found

scanning bus for storage devices... 1 Storage Device(s) found

 

Consoles: U-Boot console

Found compatible API, ver. 7

 

FreeBSD/PowerPC U-Boot bootstrap loader, Revision 2.1

(marcelm@apg-bbuild01.juniper.net, Wed Feb 6 11:23:55 PST 2008)

Memory: 1024MB

Loading /boot/defaults/loader.conf

/kernel data=0x7fcbac+0x8774c syms=[0x4+0x6ee90+0x4+0x9bae3]

 

 

Hit [Enter] to boot immediately, or space bar for command prompt.

Booting [/kernel]...

Kernel entry at 0xa00000e0 ...

GDB: no debug ports present

KDB: debugger backends: ddb

KDB: current backend: ddb

platform_early_bootinit: EX Series Early Boot Initialization

Copyright © 1996-2010, Juniper Networks, Inc.

All rights reserved.

Copyright © 1992-2006 The FreeBSD Project.

Copyright © 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

The Regents of the University of California. All rights reserved.

JUNOS 10.0S10.1 #0: 2010-11-08 21:23:50 UTC

builder@ormonth.juniper.net:/volume/build/junos/10.0/service/10.0S10.1/obj-powerpc/bsd/sys/compile/JUNIPER-EX

Timecounter "decrementer" frequency 50000000 Hz quality 0

cpu0: Freescale e500v2 core revision 2.2

cpu0: HID0 80004080<EMCP,TBEN,EN_MAS7_UPDATE>

real memory = 1050673152 (1002 MB)

avail memory = 1029038080 (981 MB)

ETHERNET SOCKET BRIDGE initialising

Initializing EXSERIES platform properties ...

nexus0: <PPC e500 Nexus device>

ocpbus0: <on-chip peripheral bus> on nexus0

openpic0: <OpenPIC in on-chip peripheral bus> iomem 0xfef40000-0xfef600b3 on ocpbus0

uart0: <16550 or compatible> iomem 0xfef04500-0xfef0450f irq 58 on ocpbus0

uart0: console (9600,n,8,1)

uart1: <16550 or compatible> iomem 0xfef04600-0xfef0460f irq 58 on ocpbus0

lbc0: <Freescale 8533 Local Bus Controller> iomem 0xfef05000-0xfef05fff,0xff000000-0xffffffff irq 22 on ocpbus0

cfi0: <AMD/Fujitsu - 8MB> iomem 0xff800000-0xffffffff on lbc0

syspld0 iomem 0xff000000-0xff00ffff on lbc0

tsec0: <eTSEC ethernet controller> iomem 0xfef24000-0xfef24fff irq 45,46,50 on ocpbus0

tsec0: hardware MAC address b0:c6:9a:63:72:7f

miibus0: <MII bus> on tsec0

e1000phy0: <Marvell 88E1112 Gigabit PHY> on miibus0

e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto

pcib0: <Freescale MPC8544 PCI host controller> iomem 0xfef08000-0xfef08fff,0xf0000000-0xf3ffffff on ocpbus0

pci0: <PCI bus> on pcib0

pci0: <serial bus, USB> at device 18.0 (no driver attached)

ehci0: <Philips ISP156x USB 2.0 controller> mem 0xf0001000-0xf00010ff irq 22 at device 18.2 on pci0

usb0: EHCI version 1.0

usb0: <Philips ISP156x USB 2.0 controller> on ehci0

usb0: USB revision 2.0

uhub0: Philips EHCI root hub, class 9/0, rev 2.00/1.00, addr 1

uhub0: 2 ports with 2 removable, self powered

umass0: STMicroelectronics ST72682 High Speed Mode, rev 2.00/2.10, addr 2

pcib1: <Freescale MPC8544 PCI Express host controller> iomem 0xfef0a000-0xfef0afff,0xe0000000-0xe3ffffff,0xec000000-0xec0fffff irq 42 on ocpbus0

pci1: <PCI bus> on pcib1

pcib2: <PCI-PCI bridge> at device 0.0 on pci1

pci2: <PCI bus> on pcib2

mpfe0: <Juniper EX-series Packet Forwarding Engine> mem 0xa4000000-0xa40fffff,0xa0000000-0xa3ffffff irq 19 at device 0.0 on pci2

pcib3: <Freescale MPC8544 PCI Express host controller> iomem 0xfef0b000-0xfef0bfff,0xe8000000-0xebffffff,0xec200000-0xec2fffff irq 43 on ocpbus0

pci3: <PCI bus> on pcib3

pcib4: <PCI-PCI bridge> at device 0.0 on pci3

pci4: <PCI bus> on pcib4

mpfe1: <Juniper EX-series Packet Forwarding Engine> mem 0xb4000000-0xb40fffff,0xb0000000-0xb3ffffff irq 18 at device 0.0 on pci4

i2c0: <MPC85XX OnChip i2c controller> iomem 0xfef03000-0xfef03014 irq 59 on ocpbus0

i2c1: <MPC85XX OnChip i2c controller> iomem 0xfef03100-0xfef03114 irq 59 on ocpbus0

idma0: <mp85xxx DMA Controller> iomem 0xfef21000-0xfef21300 irq 36 on ocpbus0

Initializing product: 41 ..

bme0:Virtual BME driver initializing

Timecounters tick every 1.000 msec

Loading the NETPFE picpeer module

IPsec: Initialized Security Association Processing.

da0 at umass-sim0 bus 0 target 0 lun 0

da0: <ST ST72682 2.10> Removable Direct Access SCSI-2 device

da0: 40.000MB/s transfers

da0: 1000MB (2048000 512 byte sectors: 64H 32S/T 1000C)

if_pfe_open: listener socket opened, listening on ...

Trying to mount root from ufs:/dev/da0s1a

Attaching /packages/jbase via /dev/mdctl...

Mounted jbase package on /dev/md0...

Verified manifest signed by PackageProduction_10_0_0

Verified jboot signed by PackageProduction_10_0_0

Verified jbase-10.0S10.1 signed by PackageProduction_10_0_0

/packages/jcrypto-ex-10.0S10.1 not present.

/packages/jdocs-ex-10.0S10.1 not present.

Mounted jkernel-ex package on /dev/md1...

Verified manifest signed by PackageProduction_10_0_0

Verified jkernel-ex-10.0S10.1 signed by PackageProduction_10_0_0

/packages/jpfe-ex42x-10.0S10.1 not present.

Mounted jroute-ex package on /dev/md2...

Verified manifest signed by PackageProduction_10_0_0

Verified jroute-ex-10.0S10.1 signed by PackageProduction_10_0_0

/packages/jswitch-ex-10.0S10.1 not present.

Mounted jweb-ex package on /dev/md3...

Verified manifest signed by PackageProduction_10_0_0

Verified jweb-ex-10.0S10.1 signed by PackageProduction_10_0_0

Executing /packages/mnt/jweb-ex-10.0S10.1/mount.post..

Automatic reboot in progress...

FILE SYSTEM CLEAN; SKIPPING CHECKS

clean, 51449 free (33 frags, 6427 blocks, 0.0% fragmentation)

FILE SYSTEM CLEAN; SKIPPING CHECKS

clean, 28282 free (50 frags, 3529 blocks, 0.2% fragmentation)

FILE SYSTEM CLEAN; SKIPPING CHECKS

clean, 61059 free (219 frags, 7605 blocks, 0.3% fragmentation)

FILE SYSTEM CLEAN; SKIPPING CHECKS

clean, 160780 free (20 frags, 20095 blocks, 0.0% fragmentation)

FILE SYSTEM CLEAN; SKIPPING CHECKS

clean, 160780 free (20 frags, 20095 blocks, 0.0% fragmentation)

Creating initial configuration...mgd: error: Couldn't open lib "/usr/lib/dd//libjcrypto-dd.so": Cannot open "/usr/lib/dd//libjcrypto-dd.so"

mgd: error: Couldn't open lib "/usr/lib/dd//libjcrypto_junos-dd.so": Cannot open "/usr/lib/dd//libjcrypto_junos-dd.so"

mgd: error: Couldn't open lib "/usr/lib/dd//libjdocs-dd.so": Cannot open "/usr/lib/dd//libjdocs-dd.so"

mgd: error: Couldn't open lib "/opt/lib/dd/libjswitch-dd.so": Cannot open "/opt/lib/dd/libjswitch-dd.so"

mgd: error: Couldn't open lib "/opt/lib/dd/libautod-dd.so": Cannot open "/opt/lib/dd/libautod-dd.so"

mgd: commit complete

Setting initial options: debugger_on_panic=NO debugger_on_break=NO.

Starting optional daemons: .

Doing initial network setup:

.

Initial interface configuration:

additional daemons:.

Additional routing options:kern.module_path: /boot//kernel;/bootLoading the NETPFE ethernet module

/modules -> /booLoading the EX-series platform NETPFE module

t//kernel;/boot/modules;/modules

grat_arp_on_ifup=YES: net.link.ether.inet.grat_arp_on_ifup: 1 -> 1

grat_arp_delay=${grat_arp_delay}: net.link.ether.inet.grat_arp_delay: 0 -> 0

kld netpfe drv: ifpfed_ethkld platform: ex_ifpfe if_vcpkern.module_path: /boot//kernel;/boot/modules;/modules -> /boot//kernel;/boot/modules;/modules;/modules/peertype

kld peertype: peertype_hcm peertype_pfem peertype_sfi peertype_slavere.

Doing additional network setup:.

Starting final network daemons:.

setting ldconfig path: /usr/lib /opt/lib

starting standard daemons: cron.

Local package initialization:.

kern.securelevel: -1 -> 1

starting local daemons:.

Sat Apr 16 16:10:35 UTC 2011

 

Amnesiac (ttyu0)

 

В итоге, часть CLI недоступна (по сравнению с EX4200-24F), на LCD дисплее пишет: Loading junos (хотя в консоль пускает), на кнопки не реагирует.

 

Что это может быть?

[pfexec]

Что это может быть?

сделайте реинсталл 11.4R10 (или 12.3R5, если очень хочется) с форматом.

Verified jbase-10.0S10.1 signed by PackageProduction_10_0_0

10.0S10 :D вам такой анахронизм не нужен в любом случае, а апгрейдить его "мягко" устанеш.

Edited March 13, 2014 by pfexec

[mse.rus77]

Что это может быть?

сделайте реинсталл 11.4R10 (или 12.3R5, если очень хочется) с форматом.

Verified jbase-10.0S10.1 signed by PackageProduction_10_0_0

10.0S10 :D вам такой анахронизм не нужен в любом случае, а апгрейдить его "мягко" устанеш.

Коллега, а как нам быть в случае того, что поддержка на девайсы не куплена, где брать софт?

[pfexec]

Коллега, а как нам быть в случае того, что поддержка на девайсы не куплена, где брать софт?

идите на support.juniper.net и регайтесь.

после этого сможете спокойно скачать junos желанной версии. :)

Edited March 13, 2014 by pfexec

[mse.rus77]

После входа в систему вот что имеем:

--- JUNOS 10.0S10.1 built 2010-11-08 21:23:50 UTC

root@:LC:0% cli

rend_dlinit: not a proper library: /usr/lib/render//libkmd-render.so: Cannot open "/usr/lib/render//libkmd-render.so"

rend_dlinit: not a proper library: /usr/lib/render//liblldpd-render.so: Cannot open "/usr/lib/render//liblldpd-render.so"

rend_dlinit: not a proper library: /usr/lib/render//libeswd-render.so: Cannot open "/usr/lib/render//libeswd-render.so"

rend_dlinit: not a proper library: /usr/lib/render//libdot1xd-render.so: Cannot open "/usr/lib/render//libdot1xd-render.so"

rend_dlinit: not a proper library: /usr/lib/render//libautod-render.so: Cannot open "/usr/lib/render//libautod-render.so"

rend_dlinit: not a proper library: /usr/lib/render//libsflowd-render.so: Cannot open "/usr/lib/render//libsflowd-render.so"

rend_dlinit: not a proper library: /usr/lib/render//libvccpd-render.so: Cannot open "/usr/lib/render//libvccpd-render.so"

{linecard:0}

root> show version

 

{linecard:0}

root> show version detail

 

{linecard:0}

root> configure

Entering configuration mode

 

{linecard:0}[edit]

root# set ?

Possible completions:

> access Network access configuration

> access-profile Access profile for this instance

> accounting-options Accounting data configuration

+ apply-groups Groups from which to inherit configuration data

> chassis Chassis configuration

> class-of-service Class-of-service configuration

> diameter Diameter protocol layer

> event-options Event processing configuration

> firewall Define a firewall configuration

> forwarding-options Configure options to control packet forwarding

> groups Configuration groups

> interfaces Interface configuration

> jsrc JSRC partition configuration

> jsrc-partition JSRC partition configuration

> logical-systems Logical systems

> multicast-snooping-options Multicast snooping option configuration

> policy-options Routing policy option configuration

> protocols Routing protocol configuration

> routing-instances Routing instance configuration

> routing-options Protocol-independent routing option configuration

> security Security configuration

> services

> snmp Simple Network Management Protocol configuration

> system System parameters

{linecard:0}[edit]

root# run show configuration

## Last commit: 2011-04-16 15:43:14 UTC by root

version 10.0S10.1;

system {

root-authentication {

encrypted-password "$1$OReVqebR$65Wt8HmVbB4.e40mJwfYH1"; ## SECRET-DATA

}

syslog {

user * {

any emergency;

}

file messages {

any notice;

authorization info;

}

file interactive-commands {

interactive-commands any;

}

}

}

chassis {

container-devices {

device-count 1;

}

}

interfaces {

ge-0/0/0 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/1 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/2 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/3 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/4 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/5 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/6 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/7 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/8 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/9 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/10 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/11 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/12 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/13 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/14 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/15 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/16 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/17 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/18 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/19 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/20 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/21 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/22 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/0/23 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/1/0 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

xe-0/1/0 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/1/1 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

xe-0/1/1 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/1/2 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

ge-0/1/3 {

unit 0 {

##

## Warning: statement ignored: unsupported platform (ex4200-24t)

##

family ethernet-switching;

}

}

}

protocols {

igmp-snooping {

##

## invalid path element 'vlans'

##

vlan all;

}

}

 

{linecard:0}[edit]

root#

 

 

Почему оно считает себя linecard а не RE ? Почему про интерфейсы так пишет и почему их больше ge-0/1/0 - ge-0/1/3 ?

Edited March 13, 2014 by mse.rus77

[pfexec]

Почему оно считает себя linecard а не RE ? Почему про интерфейсы так пишет и почему их больше в два раза?

я думаю самое время для фразы: "позовите одмина, он вам поможет."

[pfexec]

http://kb.juniper.net/InfoCenter/index?page=content&id=KB20643 - читаем как поставить с форматом

http://rutracker.org/forum/viewtopic.php?t=4045147 - качаем софт

[MonaxGT]

Почему оно считает себя linecard а не RE ? Почему про интерфейсы так пишет и почему их больше ge-0/1/0 - ge-0/1/3 ?

 

А как вы инициализировали кластер? загрузкой или с предустановками?

 

Поменяйте софт, как рекомендовал pfexec.

 

Я собирал на 12.3 (вроде), все работало прекрасно. По поводу невидимых интерфейсов, то просто создайте их используя аналогичные порты.

Например порт ge-0/0/1, то порты бэкапа будут ge-1/0/1 - вроде бы, могу ошибаться, собирал один раз.

[mse.rus77]

Почему оно считает себя linecard а не RE ? Почему про интерфейсы так пишет и почему их больше ge-0/1/0 - ge-0/1/3 ?

 

А как вы инициализировали кластер? загрузкой или с предустановками?

 

Поменяйте софт, как рекомендовал pfexec.

 

Я собирал на 12.3 (вроде), все работало прекрасно. По поводу невидимых интерфейсов, то просто создайте их используя аналогичные порты.

Например порт ge-0/0/1, то порты бэкапа будут ge-1/0/1 - вроде бы, могу ошибаться, собирал один раз.

Устройство не в стэке, но такое ощущение, что когда-то оно в нем было в роли бэкапа. Хотя странно, мы еще этот девайс не эксплуатировали.

[mse.rus77]

http://kb.juniper.net/InfoCenter/index?page=content&id=KB20643 - читаем как поставить с форматом

http://rutracker.org/forum/viewtopic.php?t=4045147 - качаем софт

Большое спасибо, все получилось.