IRC Networks
Irc Logs Stats
Start date: 2007-09-27 02:48:27
Last update: 2008-10-24 20:19:38
Channels: 41
Logged Lines: 6230436
Size: 1834.30 MB
Powered by
Channel Info
Network: freenodeChannel: #cisco |
Search in www.irclog.org
Log from #cisco at freenode 2006-05-17
[21:08]<[mzvzyw]>I just hear the term most often in reference to FR, but I'm relatively new to all this.
[21:09]<dzzc1lyvn>hmm
[21:09]<dzzc1lyvn>look at this
[21:10]<dzzc1lyvn>http://pastebin.com/723064
[21:11]<dzzc1lyvn>which two do you all think..
[21:11]<vcul>traffic shaping is mostly used in pipes that are rate-limited. FR is CIR'ed so it has to be used
[21:11]<dzzc1lyvn>I know A for sure..
[21:12]<crvpyvn>[Matrix] - traffic shaping has a very specific meaning, and it's quite distinct from other QoS mechanisms.
[21:12]<[mzvzyw]>they're all valid commands
[21:12]<fjzvxnz-wjzc>i'm guessing D, but I'm no switching expert
[21:12]<vcul>yeah that's what I would have checked too :)
[21:13]<crvpyvn>[Matrix] - and although it's common in Frame Relay environments it certainly is not restricted to them.
[21:13]<[mzvzyw]>cool
[21:13]<[mzvzyw]>Catfive: I like your nick btw
[21:14]<dzzc1lyvn>[Matrix]>
[21:14]<vcul>five-legged cat?
[21:14]<dzzc1lyvn>you won't do all 3
[21:14]<crvpyvn>[Matrix] - roughly speaking, traffic-shaping is 'friendly policing': rather than simply drop packets outright that exceed the specified rate, we instead buffer the packets in a queue that is emptied at the specified rate.
[21:16]<[mzvzyw]>Well B would work assuming you didn't add more vlans
[21:17]<[mzvzyw]>you wouldn't think you'd need both A and C
[21:17]<msxjv>A/D
[21:17]<[mzvzyw]>err, yeah
[21:17]<msxjv>but you have to assume some things
[21:17]<msxjv>yeah, but it was listed as 'd'
[21:17]<msxjv>*shrug*
[21:18]<dzzc1lyvn>yeah
[21:18]<dzzc1lyvn>the answers are A/D
[21:19]<[mzvzyw]>I'd think just A.
[21:19]<[mzvzyw]>Since all VLAN's are allowed by default aren't they?
[21:19]<snppysx>here it is with option c http://pastebin.com/723082
[21:20]<[mzvzyw]>but since the original config is "switchport trunk allowed vlan all", when you enter the "switchport trunk allowed vlan remove 3,4,50" I wonder if it does away with the implied all. Hmm.
[21:20]<msxjv>here's another question: since you don't have the config, would it hurt to apply both a and d?
[21:21]<[mzvzyw]>I'll test it on a switch, gimme a few
[21:23]<gndyvx>[Matrix]: remove will change the confi to
[21:23]<dzzc1lyvn>lol
[21:23]<gndyvx>switchport allowed vlan 1-2,5-49,49-1005,1015-4096
[21:23]<gndyvx>or what ever
[21:23]<dzzc1lyvn>nemith
[21:23]<[mzvzyw]>so it keeps the implied all then
[21:23]<dzzc1lyvn>no
[21:23]<gndyvx>you should always ,atch both side
[21:23]<dzzc1lyvn>it's A and D
[21:23]<[mzvzyw]>gotcha
[21:24]<gndyvx>well it's no longer all now is it
[21:24]<dzzc1lyvn>hmm
[21:25]<[mzvzyw]>true. :)
[21:25]<gndyvx>i don't think D will do it, A will
[21:25]<dzzc1lyvn>so you will just remove..the ones you don't want
[21:25]<dzzc1lyvn>I was thinking about that too
[21:25]<gndyvx>it depends on your end result
[21:25]<dzzc1lyvn>you don't need to add any
[21:25]<dzzc1lyvn>they are already active
[21:26]<dzzc1lyvn>so I just want to have those.
[21:26]<[mzvzyw]>right, that's what I said... lol
[21:26]<gndyvx>usually what i do is define strictly what vlans i want on the trunk and explicitly define them
[21:26]<dzzc1lyvn>well yea
[21:26]<gndyvx>switchport mode trunk 1,2,3
[21:26]<gndyvx>in answer A) you are removing the vlans that you don't want on the trunk, any new vlans created will automatically be trunked
[21:27]<[mzvzyw]>same with B
[21:27]<gndyvx>initially the same result, diffent when thinking ahead
[21:27]<dzzc1lyvn>yeah
[21:27]<dzzc1lyvn>let's not think ahead.
[21:27]<[mzvzyw]>so A and B
[21:27]<dzzc1lyvn>cuz it's a question
[21:28]<gndyvx>yes
[21:28]<msxjv>I tend to not assume that any of the VLANs were allowed or filtered to begin with
[21:28]<msxjv>because it's a question
[21:28]<gndyvx>B would be safer
[21:28]<gndyvx>like dshot says
[21:28]<dzzc1lyvn>hmm
[21:29]<dzzc1lyvn>it's a question
[21:29]<dzzc1lyvn>ohh my
[21:29]<dzzc1lyvn>http://pastebin.com/723064
[21:29]<msxjv>Well, they tell you the active VLANs, they don't show you 'show int trunk'
[21:29]<gndyvx>i would mark B
[21:29]<msxjv>you can assume, ok they're probably all active
[21:29]<msxjv>or you can assume nothing
[21:30]<dzzc1lyvn>they only stated
[21:30]<dzzc1lyvn>which ones are active
[21:31]<dzzc1lyvn>If you use except key then All(1 to 4094) VLANs will be allowed except those you pointed out.
[21:31]<dzzc1lyvn>If you use remove key you just remove VLANs from already configured vlan's list
[21:31]<gndyvx>right
[21:31]<snppysx>where did this ambiguous question come from?
[21:31]<msxjv>all test questions are ambiguous like this
[21:31]<[mzvzyw]>Since it didn't specify I'd assume a default trunk config, and A and B would be correct answers.
[21:32]<msxjv>they'd rather whore you over via logic than test your knowledge
[21:32]<gndyvx>alright alreayd
[21:32]<gndyvx>we get the point
[21:32]<[mzvzyw]>They're probably testing to see if you know whether or not all vlans are allowed by default. ;)
[21:32]<snppysx>heh
[21:32]<gndyvx>[Matrix]: who cares!
[21:33]<[mzvzyw]>Cisco cares!
[21:33]<[mzvzyw]><.<
[21:33]<gndyvx>it's not from a real test.. or Dark3Lite would be violating his NDA
[21:33]<[mzvzyw]>lol
[21:33]<drdrsaggg>REPORTED!
[21:33]<gndyvx>heh
[21:33]<drdrsaggg>GG!
[21:33]<fjzvxnz-wjzc>http://pastebin.com/723117 <--- i feel like i've just given up part of my soul or something :(
[21:33]<gndyvx>anyway.. if it was a cisco test... it would say Choose one or Choose two







