From: Alex Dean (Alex.Dean@xxxxxxxxxxxxx)
Date: Wed Sep 15 1999 - 17:37:39 GMT-3
Mike
There are a couple of things that spring to mind:
1) By default when you re-build a Catalyst its VTP mode is set to
client (I think). Anywayway, if it is not in server or transparent mode
it will not allow you to create any VLANs other than the existing
VLAN0001. To fix this type set vtp mode server OR set vtp mode
transparent. You may first need to name your VTP domain with something
like set VTP domain CCIE.
2) If you clear (delete) a VLAN from a switch it automatically
dis-ables all the ports in that VLAN. You need to do a set port enable
on them after assigning them to a new VLAN.
Hope this helps.
Cheers
Alex (6 Days to go....)
>>> "Mike Wang" <mike_wang51@hotmail.com> 16/09/99 02:47:24 >>>
Thanks Alex.
I have another question if you do not mind.
I have a Cat5k with supervise engine I and 12 port 10/100 Fastethernet
module. I try to set up VLAN on port 1-4 for VLAN 2.
when I type in "set vlan 2 2/1-4" it seems normal that changes those
port to
vlan, but it does not work. I did a sho vlan, vlan 2 is not there, I
did a
sho vlan 2, says no vlan 2 information. I did a sho ports, tell me
ports
1-4 in vlan2 is inactive. before I setup the vlan, I clear the config
and
reset the box. It seems like there is some software forced reason make
the
vlan2 inactive.(I changed all other factors like duplex, speed to
10mbps,
still does not work). How every, the default vlan1 is working fine. Do
you
have any idea why this and how to recovery? Thanks,
Mike
>From: "Alex Dean" <Alex.Dean@telecom.co.nz>
>To: mike_wang51@hotmail.com
>Subject: Re: snapshot over ISDN BRI w/ RIP problem
>Date: Mon, 13 Sep 1999 09:52:31 +1200
>
>Mike
>
>Check out the following:
>
>R5:
>username R6 password cisco
>interface BRI0
> no ip address
> encapsulation ppp
> ipx network 6005
> no ipx route-cache
> ipx watchdog-spoof
> ipx spx-spoof
> ipx spx-idle-time 30
> isdn answer1 3560085:5
> dialer map snapshot 1 name r6 3560085:6
> dialer map ipx 6005.00b0.0346.9bc6 name r6 broadcast 3560085:6
> dialer-group 1
> snapshot client 5 100 dialer
> ppp authentication chap
>!
>dialer-list 1 protocol ipx list 999
>access-list 999 deny any any all any 457
>access-list 999 deny any any all any rip
>access-list 999 deny any any all any sap
>access-list 999 permit any any all any all
>
>R6:
>username R5 password cisco
>interface BRI0
> no ip address
> encapsulation ppp
> ipx network 6005
> no ipx route-cache
> ipx watchdog-spoof
> ipx spx-spoof
> ipx spx-idle-time 30
> dialer map ipx 6005.00b0.0057.349a name r5 broadcast 3560085:5
> isdn answer1 3560085:6
> dialer-group 1
> snapshot server 5
> ppp authentication chap
>dialer-list 1 protocol ipx list 999
>access-list 999 deny any any all any 457
>access-list 999 deny any any all any rip
>access-list 999 deny any any all any sap
>access-list 999 permit any any all any all
>
>Cheers
>Alex.
>
>
> >>> "Mike Wang" <mike_wang51@hotmail.com> 11/09/99 10:05:19 >>>
>Alex,
>
>I did add dialer name on R2 but doesn't work. I will try again.
>
>I think the real thing I want is config Snapshot for IPX, that is to
>inactivate RIP/SAP updates. I could not figure it out, Pleae help. I
>am not
>sure the sample I am using is correct. If you have one Snapshot IPX
>sample
>please email me. Thanks,
>
>What's 60 in the config "dialer map snapshot 60 1002"
>stands for? I see books say "sequence number" or "protocol number",
>what is
>that?
>THanks,
>Mike
>
>R2(Server):
>
>interface BRI0
>no ip address
>encapsulation ppp
>ipx network AAA
>dialer map ipx AAA.0000.3031.5e08 broadcast 1003
>dialer-group 1
>snapshot server 5 dialer
>
>dialer-list 1 protocol ipx permit
>
>R3(client):
>interface BRI0
>no ip address
>encapsulation ppp
>ipx network AAA
>dialer map snapshot 60 1002
>dialer map ipx AAA.00e0.b05a.54b0 broadcast 1003
>dialer-group 1
>snapshot client 5 8 suppress-statechange-update dialer
>
>dialer-list 1 protocol ipx permit
>
>
> >From: "Alex Dean" <Alex.Dean@telecom.co.nz>
> >To: ccielab@groupstudy.com, mike_wang51@hotmail.com
> >Subject: Re: snapshot over ISDN BRI w/ RIP problem
> >Date: Sat, 11 Sep 1999 09:35:42 +1200
> >
> >Did you try adding
> >dialer map snashot...
> >to R2. Even if it doesn't dial it may still need the map statement
>so
> >it forwards the "interesting" traffic when the link is up. And I
>would
> >still try adding the name parameter to the map statements because
>from
> >experience it does do strange things. However just change one
thing
>at
> >a time so you know what fixed it when you get it going.
> >
> >Also, use debug dialer (shows what traffic it finds interesting/not
> >intersting and whether or not it dials as a result), and show
dialer.
> >
> >Cheers
> >Alex.
> >
> > >>> "Mike Wang" <mike_wang51@hotmail.com> 11/09/99 04:53:54 >>>
> >Alex,
> >Still doesn't work. And I am sure it is not a PPP auth problem
>because
> >I did
> >debug and server can get client updates.
> >Mike
> >
> >
> > >From: "Alex Dean" <Alex.Dean@telecom.co.nz>
> > >To: ccielab@groupstudy.com
> > >CC: mike_wang51@hotmail.com
> > >Subject: Re: snapshot over ISDN BRI w/ RIP problem
> > >Date: Fri, 10 Sep 1999 17:56:03 +1200
> > >
> > >Mike
> > >
> > >Try putting a dialer map snapshot... statement on R2.
> > >Also, I have encountered some odd behaviour with PPP CHAP if I
> >haven't
> > >included the name parameter on my dialer maps.
> > >
> > >Good luck.
> > >
> > >Cheers
> > >Alex.
> > >
> > > >>> "Mike Wang" <mike_wang51@hotmail.com> 10/09/99 15:40:37 >>>
> > >Hi,
> > >
> > >I built a simple ISDN Snapshot routing over ISDN BRI scenario,
but
> > >client
> > >side can not get RIP update during active period. Please help.
> >Thanks,
> > >Mike
> > >
> > >Server could get RIP update of network 172.18.0.0. But Client
could
> >not
> > >get
> > >RIP update of network 172.17.0.0. Debug IP Packet on server side
> > >shows:
> > >
> > >RIP: Update queued
> > >RIP: sending v1 update to 255.255.255.255 via Ethernet0
>(172.17.2.1)
> > >RIP: Update sent via BRI0
> > >IP: s=192.68.1.5 (local), d=255.255.255.255 (BRI0), len 32,
sending
> > >broad/multicast
> > >IP: s=192.68.1.5 (local), d=255.255.255.255 (BRI0:1), len 32,
> > >encapsulation
> > >failed
> > >
> > >Server config:
> > >R2#wr t
> > >Building configuration...
> > >
> > >Current configuration:
> > >!
> > >version 11.2
> > >no service password-encryption
> > >no service udp-small-servers
> > >no service tcp-small-servers
> > >!
> > >hostname R2
> > >!
> > >!
> > >username R3 password 0 cisco
> > >username R4 password 0 cisco
> > >no ip domain-lookup
> > >isdn switch-type basic-5ess
> > >!
> > >interface Ethernet0
> > >ip address 172.17.2.1 255.255.255.0
> > >!
> > >interface Serial0
> > >ip address 172.16.1.5 255.255.255.252
> > >bandwidth 1544
> > >shutdown
> > >no fair-queue
> > >clockrate 1300000
> > >!
> > >interface Serial1
> > >no ip address
> > >shutdown
> > >!
> > >interface Serial2
> > >no ip address
> > >shutdown
> > >!
> > >interface Serial3
> > >no ip address
> > >shutdown
> > >!
> > >interface BRI0
> > >ip address 192.68.1.5 255.255.255.0
> > >encapsulation ppp
> > >dialer map ip 192.68.1.6 broadcast 1003
> > >dialer-group 1
> > >snapshot server 5 dialer
> > >no fair-queue
> > >ppp authentication chap
> > >!
> > >router rip
> > >network 172.17.0.0
> > >network 192.68.1.0
> > >!
> > >no ip classless
> > >!
> > >dialer-list 1 protocol ip permit
> > >!
> > >line con 0
> > >exec-timeout 0 0
> > >line aux 0
> > >line vty 0 4
> > >login
> > >!
> > >
> > >Client config:
> > >R3#wr t
> > >Building configuration...
> > >
> > >Current configuration:
> > >!
> > >version 11.2
> > >no service password-encryption
> > >no service udp-small-servers
> > >no service tcp-small-servers
> > >!
> > >hostname R3
> > >!
> > >!
> > >username R2A password 0 cisco
> > >username R2 password 0 cisco
> > >no ip domain-lookup
> > >isdn switch-type basic-5ess
> > >!
> > >interface Serial0
> > >ip address 172.16.1.6 255.255.255.252
> > >bandwidth 1544
> > >no fair-queue
> > >!
> > >interface Serial1
> > >ip address 172.16.2.1 255.255.255.0
> > >bandwidth 1544
> > >clockrate 1300000
> > >!
> > >interface Serial2
> > >no ip address
> > >shutdown
> > >!
> > >interface Serial3
> > >no ip address
> > >shutdown
> > >!
> > >interface TokenRing0
> > >ip address 172.18.1.1 255.255.255.0
> > >ring-speed 16
> > >!
> > >interface BRI0
> > >ip address 192.68.1.6 255.255.255.0
> > >encapsulation ppp
> > >dialer idle-timeout 5
> > >dialer map ip 192.68.1.5 broadcast 1002
> > >dialer map snapshot 60 1002
> > >dialer-group 1
> > >snapshot client 5 8 suppress-statechange-update dialer
> > >no fair-queue
> > >ppp authentication chap
> > >!
> > >interface Dialer1
> > >no ip address
> > >encapsulation ppp
> > >ppp authentication chap
> > >pulse-time 0
> > >!
> > >router rip
> > >network 192.68.1.0
> > >network 172.18.0.0
> > >!
> > >no ip classless
> > >!
> > >dialer-list 1 protocol ip permit
> > >!
> > >line con 0
> > >exec-timeout 0 0
> > >line aux 0
> > >line vty 0 4
> > >login
> > >!
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:50 GMT-3