[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cisco-nsp
Subject:    Re: [nsp] MFSC
From:       "S Vijay" <vijay () netmagicsolutions ! com>
Date:       2000-11-23 11:52:50
[Download RAW message or body]

Hi ,

Work around for this is associate the interface sc0 to some VLAN and
configure an IP for that
VLAN in the MSFC card as

in the switch

>set interface sc0 100 10.1.1.1/30

In the router

int vlan 100
 ip address 10.1.1.2 255.255.255.252
 no shut

so when u telnet to 10.1.1.2 from ur machine...from the router (MSFC Card )
do a telnet into
10.1.1.1...This works

Vijay
----- Original Message -----
From: Adam Rothschild <asr@latency.net>
To: Dave Cahill <dcahill@salesforce.com>
Cc: <cisco-nsp@puck.nether.net>
Sent: Thursday, November 23, 2000 10:54 AM
Subject: Re: [nsp] MFSC


> On Tue, Nov 21, 2000 at 08:46:09PM -0800, Dave Cahill wrote:
> > I know you can get from a Catalyst Engine to the MFSC by typing
> > "session 15" I am looking for the reverse?
>
> I don't think there is one, unfortunately.  Would be nice.
>
> msfc1.nyc2.us#sh u
>     Line       User       Host(s)              Idle       Location
> *  1 vty 0     asr        idle                 00:00:00 127.0.0.11
>
>   Interface  User      Mode                     Idle Peer Address
>
> msfc1.nyc2.us#sh ip ro 127.0.0.11
> Routing entry for 127.0.0.0/8
>   Known via "connected", distance 0, metric 0 (connected, via
>   interface)
>   Routing Descriptor Blocks:
>   * directly connected, via EOBC0/6
>       Route metric is 0, traffic share count is 1
> msfc1.nyc2.us#ping 127.0.0.11
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 127.0.0.11, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
> msfc1.nyc2.us#telnet 127.0.0.11
> % Invalid IP address
> msfc1.nyc2.us#
>
> -adam
>
>

[prev in list] [next in list] [prev in thread] [next in thread]