> System image file is "flash:c3640-i-mz.120-3.T.bin"
Я точно не помню, но ИМХО рекомендован к юзанью с МИКАми IP+
12.0(3)T был очень глюкавым, я-бы поставил что-нибудь поновее,
но берегитесь - 12.0(5)Т с "aaa accounting exec ваша_схема ...." дает очень
плачевный результат, 12.0(5.5)Т хреново работает с "modem recowery action download"
у меня из 12.0(Х)Т на AS5300 сейчас стоит 12.0(6.3)Т (только из-за нового железа) и то-же
не без глюков...
Вообще-же:
========
> But my response is also a question: I'm cautiously contemplating an upgrade
> to 12.0; why do I not unfrequently hear of new problems for features that
> worked so well for good old 11.3T?
First, let's distinguish between 12.0 mainline (which we sometimes
call 12.0M) and 12.0T.
12.0M basically contains hardware / software features as of 11.3(4)T
and since then only bugfixes. 12.0M is targeted to go GD eventually.
12.0T contains ongoing new hardware / software features and will never
go GD.
> Generally speaking: IS 12.0, now at (6), SAFE? What's your experience?
I'll let people with actual field experience speak up on this.
12.0M is SUPPOSED to be safe. 12.0T is NOT supposed to be safe
- it's supposed to be bleeding-edge (and is.)
This gives rise to the following concern: what if you NEED some
12.0T features - either hardware support (e.g. AS5300 double density,
AS5800 NPE-300) or key NAS software features (e.g. L2TP, modem
call-record) but want more stability than the 12.0T train gives
you? This concern is answered by the 12.0(4)XJ train, which delivers
12.0(4)T functionality but with a focus on subsequent bugfixes
rather than bleeding-edge features. (And which will eventually
merge into 12.1(2)M.)
Some good URLs hopefully ...
IOS Roadmap
Mack Coulibaly's IOS White Paper
Aaron
=========
> немного отцензурен ( оставил только про PRI и модемы ) , таким образом
> он стал сильно похож на пример с cisco.com
> !
> modem country mica russia
> !
> isdn switch-type primary-net5
> !
modemcap entry mica-V90:FD=&f&d2s0=3_далее_по-вкусу....
> !
> controller E1 0/0
> pri-group timeslots 1-31
> !
> !
> interface Loopback0
> ip address x.x.x.x 255.255.255.255
> no ip directed-broadcast
> !
> interface Serial0/0:15
> no ip address
> no ip directed-broadcast
> isdn switch-type primary-net5
> isdn incoming-voice modem
> no cdp enable
> !
> interface Group-Async1
> mtu 576
Это нафига?!!!
Я-бы на месте юзера за ваше горло подержался-бы за такие шуточки....
> ip unnumbered Ethernet3/1
Unnumbered лучше строить от loopback
> no ip directed-broadcast
> encapsulation ppp
> dialer in-band
Хммм, ИМХО вредительство - переводите в процесс-свичинг....
> async dynamic address
> async dynamic routing
> async mode interactive
> ppp authentication pap callin
Уж тогда-бы aaa схемы привели... Ж:-/
> group-range 65 94
> !
> interface Dialer1
> mtu 576
> ip unnumbered Ethernet3/1
> no ip directed-broadcast
> encapsulation ppp
> no ip mroute-cache
> dialer in-band
> dialer-group 1
> no fair-queue
> no cdp enable
> ppp authentication pap callin
> ppp multilink
> !
> line 65 94
> session-timeout 10 output
> exec-timeout 0 0
> autoselect during-login
> autoselect ppp
> modem Dialin
Если у вас это, то
> rotary 1
нафига вот это?!
modem autoconf type mica-V90
> exec-character-bits 8
> transport input all
> escape-character NONE
> stopbits 1
> end
Если не заработает - шлите
sh modem conf для отвечающего и не отвечающего модема.
===
Good luck!
Andrey Zimin
AVZ7-RIPE
MTU-Inform ISP team
=============================================================================
"inet-admins" Internet access mailing list. Maintained by East Connection ISP.
Mail "unsubscribe inet-admins" to Majordomo@info.east.ru if you want to quit.
Archive is accessible on
